Method and apparatus for signal transmission

Abstract

Systems and methods for signal transmission are presented. A wireless communication device can receive downlink control information (DCI) from a wireless communication node. The DCI can include a plurality of blocks, each or multiple of the plurality of blocks for a respective wireless communication device. The wireless communication device can receive the DCI to trigger an aperiodic sounding reference signal (SRS). The wireless communication device can receive a configuration from the wireless communication node via higher layer signaling. The wireless communication device can receive the configuration to configure a parameter srs-TPC-PDCCH-Group to be Type A, Type B, Type C, or Type D.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including but not limited to systems and methods for signal transmission. BACKGROUND

[0002] The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new radio interface, referred to as 5G New Radio (5G NR), and a next generation packet core network (NG-CN or NGC). The 5G NR will have three main components: a 5G access network (5G-AN), a 5G core network (5GC), and a user equipment (UE). To facilitate different data services and requirements, the units of the 5GC (also referred to as network functions) have been simplified, with some being software-based and some being hardware-based so that they can be adjusted as needed. SUMMARY

[0003] The example embodiments disclosed herein are directed to addressing issues associated with one or more problems in the prior art and provide additional features that will be apparent in connection with the following details as disclosed in connection with the accompanying drawings. In accordance with various embodiments, example systems, methods, apparatus and computer program products are disclosed herein. It should be understood, however, that these embodiments are given by way of example and are not limiting as to the scope of the disclosure, and that modifications can be made by those of ordinary skill in the art to the disclosures recited herein without departing from the scope of the disclosure.

[0004] At least one aspect is directed to a system, method, apparatus, or computer readable medium. A wireless communication device can receive, from a wireless communication node, downlink control information (DCI). The wireless communication device can receive the DCI to trigger an aperiodic sounding reference signal (SRS). The wireless communication device can receive, from the wireless communication node, a configuration via higher layer signaling. The wireless communication device can receive the configuration to configure a parameter srs-TPC-PDCCH-Group to be Type A, Type B, Type C, or Type D.

[0005] In some embodiments, a wireless communication device can transmit at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission to a wireless communication node in a component carrier (CC) of a sounding reference signal (SRS). In some embodiments, the wireless communication device can transmit at least one of the PUSCH transmission or the PUCCH transmission in the CC of the SRS in accordance with a configured parameter srs-TPC-PDCCH-Group. In some embodiments, the DCI can include a plurality of blocks, each (or each group of) one or more blocks of the plurality of blocks for a respective wireless communication device.

[0006] In some embodiments, SRS power control can be bundled with PUSCH power control. In some embodiments, when SRS power control is bundled with PUSCH power control, a first block of the plurality of blocks can include a SRS request field associated with a group of component carriers (CCs) of the wireless communication device. In some embodiments, when SRS power control is bundled with PUSCH power control, the first block of the plurality of blocks can include a plurality of transmit power control (TPC) command fields, the plurality of TPC command fields including a first TPC command field. In some embodiments, each of the TPC command fields can be associated with a respective CC of the group of CCs. In some embodiments, when SRS power control is bundled with PUSCH power control, the first block of the plurality of blocks can include a SRS request field associated with a CC of the wireless communication device. In some embodiments, when SRS power control is bundled with PUSCH power control, the first block of the plurality of blocks can include a first TPC command field associated with the CC.

[0007] In some embodiments, the use of the first TPC command field can be configured / set to include at least one of slotOffset, SRSFreqDomainConfig, SRSTimedomainConfig, resourceMapping, TCI state, or SpatialRelationlnfo. In some embodiments, the use of the plurality of TPC command fields can be configured to slotOffset. In some embodiments, the value of each of the plurality of TPC command fields can correspond to a respective set of one or more slot offsets. In some embodiments, the use of the plurality of TPC command fields can be configured to SpatialRelationlnfo, TCI state, SRSTimedomainConfig, or resourceMapping. In some embodiments, the value of each of the plurality of TPC command fields can correspond to a respective set of parameters of SpatialRelationlnfo, TCI state, SRSTimedomainConfig, or resourceMapping.

[0008] In some embodiments, SRS power control can not be tied to PUSCH power control. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a SRS request field associated with a CC of the wireless communication device. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a first TPC command field associated with the CC. In some embodiments, a SRS request field value can be used to trigger a SRS in a CC in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled. In some embodiments, each monitoring cell used to monitor a PDCCH transmission to convey a corresponding DCI can include a corresponding CC in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled. In some embodiments, each monitoring cell that includes a corresponding CC in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled can be different from monitoring cells used to monitor a PDCCH transmission to convey a corresponding DCI that include corresponding CCs in which no PUSCH transmission or PUCCH transmission is scheduled.

[0009] In some embodiments, SRS power control can not be tied to PUSCH power control. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a SRS request field associated with a set of CCs of the wireless communication device. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a plurality of TPC command fields, the plurality of TPC command fields including a first TPC command field. In some embodiments, each of the TPC command fields can be associated with a respective CC of the set of CCs. In some embodiments, at least one of the PUSCH transmission or the PUCCH transmission can be scheduled in the set of CCs. In some embodiments, a monitoring cell for monitoring the PDCCH transmission to convey the corresponding DCI can include the set of CCs in which at least one of the PUSCH transmission or the PUCCH transmission can be scheduled. In some embodiments, a monitoring cell including the set of CCs in which at least one of the PUSCH transmission or the PUCCH transmission can be scheduled can be different from a monitoring cell including the corresponding CCs in which no PUSCH transmission or PUCCH transmission is scheduled for monitoring the PDCCH transmission to convey the corresponding DCI.

[0010] At least one aspect is directed to a system, method, apparatus, or computer readable medium. A wireless communication node can transmit downlink control information (DCI) to a wireless communication device. The wireless communication node can transmit the DCI to trigger an aperiodic sounding reference signal (SRS). The wireless communication node can transmit a configuration to the wireless communication device via higher layer signaling, the wireless communication node can transmit the configuration to configure a parameter srs-TPC-PDCCH-Group as Type A, Type B, Type C, or Type D.

[0011] In some embodiments, the wireless communication node can receive the configured parameter srs-TPC-PDCCH-Group from the wireless communication device. In some embodiments, the wireless communication node can receive the configured parameter to schedule at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission in a component carrier (CC) of the SRS. In some embodiments, the DCI can include a plurality of blocks, each of the plurality of blocks or the plurality of blocks for a respective wireless communication device.

[0012] In some embodiments, SRS power control can be bundled with PUSCH power control. In some embodiments, when SRS power control is bundled with PUSCH power control, a first block of the plurality of blocks can include a SRS request field associated with a set of component carriers (CCs) of the wireless communication device. In some embodiments, when SRS power control is bundled with PUSCH power control, a first block of the plurality of blocks can include a plurality of transmit power control (TPC) command fields, the plurality of transmit power control (TPC) command fields including a first TPC command field. In some embodiments, each of the TPC command fields can be associated with a respective CC of the set of CCs. In some embodiments, when SRS power control is bundled with PUSCH power control, a first block of the plurality of blocks can include a SRS request field associated with a CC of the wireless communication device. In some embodiments, when SRS power control is bundled with PUSCH power control, a first block of the plurality of blocks can include a first TPC command field associated with the CC.

[0013] In some embodiments, the use of the first TPC command field can be configured to include at least one of slotOffset, SRSFreqDomainConfig, SRSTimedomainConfig, resourceMapping, TCI state, or SpatialRelationlnfo. In some embodiments, the use of the plurality of TPC command fields can be configured to slotOffset. In some embodiments, a value of each of the plurality of TPC command fields can correspond to a respective set of one or more slot offsets. In some embodiments, the use of the plurality of TPC command fields can be configured to SpatialRelationlnfo, TCI state, SRSTimedomainConfig, or resourceMapping. In some embodiments, a value of each of the plurality of TPC command fields can correspond to a respective set of parameters of SpatialRelationlnfo, TCI state, SRSTimedomainConfig, or resourceMapping.

[0014] In some embodiments, SRS power control can not be tied to PUSCH power control. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a SRS request field associated with a CC of the wireless communication device. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a first TPC command field associated with the CC. In some embodiments, a SRS request field value can be used to trigger a SRS in a CC in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled. In some embodiments, each monitoring cell used to monitor for a PDCCH transmission to convey a corresponding DCI can include a corresponding CC in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled. In some embodiments, each monitoring cell that includes a corresponding CC in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled can be different from monitoring cells used to monitor for a PDCCH transmission to convey a corresponding DCI that include corresponding CCs for which no PUSCH transmission or PUCCH transmission is scheduled.

[0015] In some embodiments, SRS power control can not be tied to PUSCH power control. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a SRS request field associated with a set of CCs of the wireless communication device. In some embodiments, if SRS power control is not tied to PUSCH power control, a first block of the plurality of blocks can include a plurality of TPC command fields including a first TPC command field. In some embodiments, each of the TPC command fields can be associated with a respective CC of the set of CCs. In some embodiments, at least one of a PUSCH transmission or a PUCCH transmission can be scheduled in the set of CCs. In some embodiments, a monitoring cell used to monitor for a PDCCH transmission to convey a corresponding DCI can include the set of CCs in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled. In some embodiments, the monitoring cell that includes the set of CCs in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled can be different from monitoring cells used to monitor for a PDCCH transmission to convey a corresponding DCI that include corresponding CCs for which no PUSCH transmission or PUCCH transmission is scheduled.

[0016] In some embodiments, a group common DCI (or other DCI) can be used to trigger / cause one or more aperiodic SRS transmissions in one or more CCs with at least one PUSCH and / or PUCCH transmission. The CCs can have / support the capability of triggering / performing at least one PUSCH and / or PUCCH transmission (e.g., PUSCH and / or PUCCH transmissions in different slots). In some embodiments, the group common DCI (or other DCI) can be associated / related / linked with multiple wireless communication devices (e.g., a group of one or more UEs). If one or more aperiodic SRS transmissions are triggered (e.g., triggered by the group common DCI), a TPC command field can be used to indicate / provide / specify SRS configuration parameters. Thus, the TPC command field can indicate SRS configuration parameters (or other parameters) instead of configuring SRS power control. BRIEF DESCRIPTION OF DRAWINGS

[0017] Various example embodiments of the present solution will be described in detail below with reference to the following drawings or accompanying figures. The accompanying figures are provided for purposes of illustration only and are not intended to limit the scope of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0018] Figure 1 A cellular communication network in which the example techniques disclosed herein can be implemented is shown in accordance with embodiments of the present disclosure;

[0019] Figure 2 Block diagrams of example base stations and user equipment terminals in accordance with some embodiments of the present disclosure are shown;

[0020] Figures 3-4 Various tables showing example configurations between TPC command field values and one or more slotOffset values in accordance with some embodiments of the present disclosure are shown;

[0021] Figure 5 A table showing example configurations between TPC command field values, cumulative power of SRS transmissions, and absolute power of SRS transmissions in accordance with some embodiments of the present disclosure is shown; and

[0022] Figure 6 A flowchart of an example method for signal transmission in accordance with some embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0023] Various example embodiments of the present solution are described below with reference to the accompanying drawings, so as to enable a person of ordinary skill in the art to make and use the present solution. As will be apparent to those of ordinary skill in the art upon reading the present disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the particular order and / or hierarchy of steps in the methods disclosed herein are merely examples. The specific order or hierarchy of steps disclosed in the methods can be re-arranged, or combined, or divided, while still remaining within the scope of the present solution, based on design preferences. Thus, those of ordinary skill in the art will understand that the methods disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless explicitly stated otherwise.

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

[0025]

[0026]

[0027]

[0028]

[0029] 1. Mobile communication technology and environment

[0030] Figure 1 A wireless communication network and / or system 100 in which the example techniques disclosed herein can be implemented is shown in accordance with embodiments of the present disclosure. In the following discussion, the wireless communication network 100 can 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 a cluster of base stations 102 (hereinafter “BS 102”; also referred to as wireless communication nodes) and user equipment terminals 104 (hereinafter “UE 104”; also referred to as wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), as well as cells 126, 130, 132, 134, 136, 138, and 140 that cover a geographic area 101. In the example network 100, the BSs 102 are configured to serve the UEs 104 in their respective coverage areas 103, 105, 107, 109, 111, 113, and 115. The BSs 102 are also configured to communicate with each other, e.g., via a wired or wireless backhaul link 112, to exchange information about the UEs 104 and / or the network 100. Figure 1In particular, the BS 102 and the UE 104 are contained within respective geographic boundaries of a cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 can include at least one base station operating over a bandwidth allocated to it to provide sufficient wireless coverage to its intended users.

[0031] For example, the BS 102 can operate over an allocated channel transmission bandwidth to provide sufficient coverage to the UE 104. The BS 102 and the UE 104 can communicate via downlink wireless frames 118 and uplink wireless frames 124, respectively. Each wireless frame 118 / 124 can be further divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are described herein as non-limiting examples of "communication nodes," which can generally practice the methods disclosed herein. According to various embodiments of the present solution, such communication nodes can 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) is shown in accordance with some embodiments of the present solution. The system 200 can include components and elements configured to support well-known or conventional operating features that need not be elaborated upon herein. In one illustrative embodiment, the system 200 can be used to transmit (e.g., send and receive) data symbols in a wireless communication environment, such as the wireless communication environment 100 described above. Figure 1

[0033] The system 200 generally includes a base station 202 (hereinafter "BS 202") and a user equipment terminal 204 (hereinafter "UE 204"). The 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 of which is coupled and interconnected to each other as needed via a data communication bus 220. The 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 of which is coupled and interconnected to each other as needed via a data communication bus 240. The BS 202 communicates with the 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 will be appreciated by one of ordinary skill in the art, in addition to the Figure 2 ​The system 200 can also include any number of modules beyond those shown. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0035] According to some embodiments, the UE transceiver 230 can be referred to herein as an "uplink" transceiver 230, which includes radio frequency (RF) transmitters and RF receivers, each including circuitry coupled to an antenna 232. A duplex switch (not shown) can alternatively couple the uplink transmitter or receiver to the uplink antenna in a time duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 can be referred to herein as a "downlink" transceiver 210, which includes radio frequency (RF) transmitters and RF receivers, each including circuitry coupled to an antenna 212. A downlink duplex switch can alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time duplexed 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 the downlink antenna 212, the uplink receiver circuitry is coupled to the uplink antenna 232 for receiving transmissions over the wireless transmission link 250. Conversely, the operation of the two transceiver modules 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 for receiving transmissions over the wireless transmission link 250. In some embodiments, there is a tight time synchronization with minimal guard time between changes in duplex direction.

[0036] UE transceiver 230 and base station transceiver 210 are configured to communicate via wireless data communication link 250, and in cooperation with appropriately configured RF antenna arrangements 212 / 232 capable of supporting a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, UE transceiver 230 and base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure need not be limited in application to a particular standard and associated protocols. Rather, UE transceiver 230 and base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0037] According to various embodiments, BS 202 can be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. According to some embodiments, UE 204 can be embodied in various types of user equipment such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, or the like. Processor modules 214 and 236 can be implemented or realized with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a 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 manner, the processors can be implemented as a microprocessor, a controller, a microcontroller, a state machine, or the like. The processors can also be implemented as a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

[0038] Furthermore, the steps of the methods or algorithms described in connection with the embodiments disclosed herein can be embodied directly in hardware, in software modules executed by processor modules 214 and 236, respectively, in firmware, or in any 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 integral to processor modules 214 and 236, respectively. In some embodiments, memory modules 216 and 234 can each include cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 214 and 236, respectively. Memory modules 216 and 234 can also each include non-volatile memory for storing instructions to be executed by processor modules 214 and 236, respectively.

[0039] Network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of base station 202 that enable bidirectional communications 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 can be configured to support Internet or WiMAX traffic. In a non-limiting, exemplary deployment, network communication module 218 provides an 802.3 Ethernet interface that enables base station transceiver 210 to communicate with a conventional Ethernet-based computer network. In this manner, network communication module 218 can 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 term "configured to," "adapted to," and variations thereof mean that the device, component, circuit, structure, machine, signal, etc. is 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 “open systems interconnection model”) is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is broken into seven subcomponents or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI model also defines logical networks and effectively describes the transmission of computer packets through the use of different layer protocols. The OSI model can also be referred to as the seven-layer OSI model or seven-layer model. In some embodiments, the first layer can be a physical layer. In some embodiments, the second layer can be a medium access control (MAC) layer. In some embodiments, the third layer can be a radio link control (RLC) layer. In some embodiments, the fourth layer can be a packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer can be a radio resource control (RRC) layer. In some embodiments, the sixth layer can be one of a non-access stratum (NAS) layer or an internet protocol (IP) layer, and the seventh layer is the other layer.

[0041] 2. System and method for signal transmission

[0042] In certain systems (e.g., rel-17 new radio (NR) access based systems and / or other systems), an increasing number of wireless communication devices (e.g., UEs, terminals, or served nodes) can be located in a serving cell (or other cell). In some embodiments, one or more wireless communication devices of the serving cell can receive / obtain one or more signals / transmissions / messages from a wireless communication node (e.g., a terrestrial terminal, a base station, a gNB, an eNB, or a serving node). The one or more wireless communication devices of the serving cell can transmit / broadcast one or more signals (e.g., sounding reference signals (SRS) and / or other signals) to the wireless communication node. In some embodiments, the one or more wireless communication devices can transmit / broadcast at least one SRS (such as an aperiodic SRS). If the one or more wireless communication devices of the serving cell transmit at least one aperiodic SRS, signaling overhead can occur (e.g., signaling overhead to trigger the one or more aperiodic SRS).

[0043] In certain systems (e.g., long term evolution (LTE), new radio (NR), and / or other 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 obtain / acquire one or more UL channel state measurements and / or other measurements. In certain systems with DL and UL slots in the same frequency band (e.g., time division duplexing (TDD) systems and / or other systems), SRS can be used to obtain one or more DL channel state information (CSI) measurements and / or other measurements. In some embodiments, SRS can be used to measure / obtain / determine CSI of a channel between a wireless communication node and a wireless communication device. In LTE systems, for example, a wireless communication device can transmit / send / broadcast UL SRS on the last data symbol (or other symbol) of a subframe. The wireless communication device can transmit the UL SRS based on one or more parameters indicated / specified / provided by the wireless communication node. The one or more parameters can include a frequency band, a frequency domain location, a sequence cyclic shift, a periodicity, a subframe offset, and / or other parameters indicated by the wireless communication node. In some embodiments, the wireless communication node can determine / measures CSI of one or more UL channels of the wireless communication device. The wireless communication node can determine / measures the CSI based on the received SRS (e.g., aperiodic SRS). In response to determining / measuring the CSI, the wireless communication node can perform one or more operations in accordance with the determined / measured CSI. For example, the wireless communication node can perform frequency selection and / or closed loop power control in accordance with the determined CSI.

[0044] In some embodiments, SRSs can be transmitted / broadcasted / sent according to one or more time-domain types, such as periodic SRSs, semi-persistent SRSs, aperiodic SRSs, and / or other types. A time-domain type can be configured and / or determined for a SRS resource set, which includes one or more SRS resources. The one or more SRS resources can include one or more frequency-domain and / or time-domain resources (e.g., locations in time domain, locations in frequency domain, and / or other resources) allocated for SRSs. Radio resource control (RRC) signaling and / or other types of signaling can be used to configure periodic SRS transmissions. In some embodiments, medium access control 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. The one or more SRS configurations can include frequency resources, time-domain resources (e.g., number of orthogonal frequency-division multiplexing (OFDM) symbols), periodicity, time offset (e.g., slot offset), and / or other SRS configurations. In some embodiments, SRS configurations corresponding to aperiodic SRS transmissions can be configured by using RRC signaling, MAC-CE signaling, and / or other types of signaling. One or more aperiodic SRS transmissions can be activated / triggered / occasioned by downlink control information (DCI), such as wireless communication device (e.g., UE)-specific DCI and / or common group DCI.

[0045] In certain systems, such as LTE Release 10 based systems, at least one non- precoded SRS can be used in UL communication (e.g., antenna-specific SRS). In some embodiments, a de-modulation reference signal (DMRS) of a physical uplink shared channel (PUSCH) can perform precoding in UL communication. A wireless communication node can receive / obtain a non-precoded SRS. In response to receiving the non-precoded SRS, the wireless communication node can estimate raw CSI. In some embodiments, the wireless communication node can not be able to estimate raw CSI based on a precoded DMRS. Thus, when using one or more antennas to perform one or more non-precoded SRS transmissions, the wireless communication device can use additional SRS resources. By using additional SRS resources when transmitting using one or more antennas (e.g., performing one or more non-precoded SRS transmissions), the number of wireless communication devices that can be simultaneously multiplexed in a wireless communication system can be reduced. In some embodiments, a wireless communication device can transmit / transmit / broadcast SRSs configured with higher layer signaling (e.g., Type 0 trigger) and / or DCI (e.g., Type 1 trigger). Higher layer signaling (e.g., RRC signaling, MAC-CE signaling, and / or other types of signaling) can be used to configure periodic SRS transmissions. In some embodiments, DCI can be used to configure aperiodic SRS transmissions. Aperiodic SRS transmissions can provide improved / enhanced SRS resource usage and / or flexibility for scheduling at least one SRS.

[0046] In certain systems (e.g., based on NR Rel-15), SRS usage can be categorized into one or more categories (e.g., four categories). The one or more categories can include beam management, codebook-based, non-codebook-based, and / or antenna switching. Certain systems (e.g., NR) can support beam indication by informing / indicating a wireless communication device that a physical downlink shared channel (PDSCH) transmission and / or a physical downlink control channel (PDCCH) transmission uses a same transmission beam as a configured reference signal (e.g., a channel state information reference signal (CSI-RS), a synchronization signal (SS) block, and / or other reference signal). Thus, beam indication can imply informing a wireless communication device to transmit / broadcast the PDSCH and / or PDCCH using a same spatial filter as the configured reference signal. In some embodiments, beam indication can be based on configuration of one or more transmission configuration indication (TCI) states and / or DL signaling. Each TCI state can include information of a reference signal (e.g., a CSI-RS, a SS block, and / or other reference signal). In some embodiments, a DL transmission (e.g., a PDCCH, a PDSCH, and / or other downlink transmission) can be associated with at least one TCI. If a DL transmission is associated / linked / correlated with a TCI, a wireless communication node can inform / indicate a wireless communication device to assume performing the DL transmission using a same spatial filter as a reference signal associated with the TCI.

[0047] In some embodiments, a wireless communication network and / or a wireless communication node can include a base station of a macro cell (or other cell), a base station of a small cell (or other cell) and / or a transmission node, a transmission node (or other node) in a high frequency communication system (or other communication system), a transmission node (or other node) in an Internet of Things (IoT) system (or other system), a satellite node, and / or other wireless communication node. A wireless communication device can include a user equipment such as a mobile phone / device and / or a portable device node (e.g., a car and / or a satellite node) in a communication system.

[0048] In a wireless communication system, a wireless communication node can transmit DCI to one or more wireless communication devices to trigger / cause one or more aperiodic SRS transmissions. In some embodiments, a new / novel / enhanced / updated DCI can be used to trigger / cause one or more aperiodic SRS transmissions by one or more wireless communication devices. The systems and methods presented herein include novel methods (e.g., by using the novel / enhanced DCI) for reducing / lowering signaling overhead of triggering one or more aperiodic SRS transmissions and / or updating TCI states by at least 25% (e.g., 35%, 45%, or other percentage).

[0049] For example, a DCI (e.g., a DCI with a DCI format X, a DCI with a DCI format 2_3, and / or other DCI with other DCI format) can be used to transmit / send / broadcast a plurality of blocks (e.g., a block 1, a block 2, a block B, and / or other blocks). One or more blocks of the plurality of blocks can correspond to respective wireless communication devices. In some embodiments, a wireless communication node can transmit the plurality of blocks by using a DCI format X (e.g., a DCI format 2_3, a DCI format 2_7, a DCI format 2_8, a DCI format 2_9, and / or other DCI format) with a cyclic redundancy check (CRC) scrambled by a TCI-SRS-RNTI and / or a SRS-TCI-RNTI (where RNTI refers to a radio network temporary identifier). In some embodiments, a wireless communication node can transmit the plurality of blocks by using a DCI format 2_3 (or other DCI format) with a CRC scrambled by a TPC-SRS-RNTI (TPC = transmit power control). A type of DCI format (e.g., a DCI format 2_3, a DCI format X, and / or other DCI format) can determine / indicate a RNTI, where the RNTI can be used to encrypt the DCI. In some embodiments, a starting / initial position of a block can be determined / indicated / specified by at least one parameter (e.g., startingBitOfFormatX) signaled / configured by a higher layer (e.g., a RRC layer, a medium access control (MAC) layer, and / or other layer). The one or more higher layer signaling / configuration can provide / specify / indicate the parameter to a wireless communication device configured with each block (e.g., a block 1, a block 2, …, a block B). For example, the higher layer signaling / configuration can provide a value A of the parameter startingBitOfFormatX to one or more wireless communication devices configured with a block B, a scheme A

[0050] In some embodiments, at least one of the one or more options discussed herein (e.g., example implementation / embodiment) can be used for each block of the plurality of blocks.

[0051] a. Option 1: One block corresponds to one set of component carriers

[0052] In some embodiments, a wireless communication device (e.g., a UE) can receive / obtain a configuration via higher layer signaling (e.g., RRC signaling and / or MAC layer signaling) to configure a parameter srs-TPC-PDCCH-Group as Type A, Type B, Type C, and / or Type D. The wireless communication device can schedule / transmit one or more UL transmissions (e.g., PUSCH transmissions, physical uplink control channel (PUCCH) transmissions, and / or other transmissions) in a component carrier (CC) of SRS. The wireless communication device can use the configured srs-TPC-PDCCH-Group parameter (or other parameter) to schedule / configure / support / transmit the one or more UL transmissions (e.g., being set as Type A, Type B, Type C, and / or Type D can imply / indicate / represent / imply that the one or more PUSCH transmissions and / or PUCCH transmissions can be scheduled / supported in the CC of SRS). In some embodiments, SRS power control can be bundled / associated / related / linked / bound with PUSCH power control in the UL transmissions. If the SRS power control is bundled / bound with the PUSCH power control, the higher layer signaling can be used to configure a first block (e.g., associated with at least one wireless communication device) of a plurality of blocks.

[0053] In some embodiments, a block (e.g., a first block) can include one or more fields. The one or more fields of the block can include a SRS request field, a plurality of TPC command fields, and / or other fields. The SRS request field can be associated / related / linked with a set of component carriers (CCs) of a wireless communication device. The SRS request field can use / occupy 0 or 2 bits (or other bits) of the block. In some embodiments, a higher layer parameter such as fieldTypeFormatX can determine / indicate whether the block includes / provides the SRS request field. For example, if a value of the fieldTypeFormatX parameter is 0 (or other number), the SRS request field can be excluded from the first block. In another example, if a value of the fieldTypeFormatX parameter is 1 (or other number), the first block can include the SRS request field.

[0054] In some embodiments, each TPC command field (e.g., TPC command 1, TPC command 2, TPC command N, and / or other fields) in the plurality of TPC command fields can be associated / related / linked with a respective UL carrier and / or CC in the set of CCs. Thus, for the set of CCs, each TPC command field can be associated with a CC in the set of CCs. In a particular system, the TPC command fields can be used for SRS power control. However, if SRS power control is bundled / bound with PUSCH power control, SRS power control can be performed by using PUSCH power control mechanism instead of the TPC command fields. Thus, the TPC command fields can be used to indicate one or more associations / configurations (e.g., indicating a mapping between a TPC command field and a selected slotOffset). In some embodiments, a higher layer parameter (e.g., cc-IndexInOneCC-Set and / or other parameters) can indicate / provide / specify / determine / configure an association between each TPC command field and a respective UL carrier and / or CC.

[0055] b. Option 2: one block corresponds to one component carrier

[0056] In some embodiments, a wireless communication device (e.g., a UE) can receive / obtain a configuration via higher layer signaling (e.g., RRC signaling and / or MAC layer signaling) to configure the parameter srs-TPC-PDCCH-Group as Type A, Type B, Type C, and / or Type D. The wireless communication device can schedule / transmit one or more UL transmissions (e.g., PUSCH transmissions, PUCCH transmissions, and / or other transmissions) in a CC of the SRS. The wireless communication device can use the configured srs-TPC-PDCCH-Group parameter (or other parameters) to schedule / transmit the one or more UL transmissions. In some embodiments, SRS power control can be bundled with PUSCH power control in the UL transmissions. If SRS power control is bundled with PUSCH power control, higher layer signaling can be used to configure one or more blocks (e.g., associated with at least one wireless communication device). Each block in the one or more blocks can be applicable / to correspond to a UL carrier and / or CC. If the wireless communication device is associated / related / linked with more than one CC, more than one block can be configured for the CCs of the wireless communication device.

[0057] In some embodiments, each of the one or more blocks (e.g., the first block) can include one or more fields. The one or more fields of each block can include an SRS request field, at least one TPC command field, and / or other fields. The SRS request field can be associated / related / linked with a CC of the wireless communication device. The SRS request field can use / occupy 0 or 2 bits (or other bits) of each block. In some embodiments, a higher layer parameter such as fieldTypeFormatX can determine / indicate whether each block includes / provides the SRS request field. For example, if the value of the fieldTypeFormatX parameter is 0 (or other number), the SRS request field can be excluded from the block. In another example, if the value of the fieldTypeFormatX parameter is 1 (or other number), the block can include the SRS request field. In some embodiments, the at least one TPC command field (e.g., the first TPC command field) can be associated / related / linked with all CCs in a set of CCs. Thus, the at least one TPC command field can be associated with a CC. In some embodiments, the TPC command field can use / occupy 2 bits (or other bits) of the block.

[0058] In one or more embodiments discussed herein, dynamic parameter selection (DPS) and / or other terminology can replace the TPC command. In some embodiments, the use / purpose / application of the TPC command field (e.g., the first TCP command field) can be configured / determined by one or more higher layer parameters. The use / purpose / application of the TPC command field can be configured to include at least one of slotOffset, SRSFreqDomainConfig, SRSTimedomainConfig, resourceMapping, TCI state, and / or SpatialRelationInfo.

[0059] In some embodiments, the use / purpose / application of the configured TPC command field can indicate / provide / specify one or more configurations of the SRS. For example, the use / purpose of the SRSFreqDomainConfig can indicate / specify / provide a frequency domain configuration of the SRS. In one example, the use of the SRSTimedomainConfig can specify a time domain configuration of the SRS. In some embodiments, the use of the resourceMapping can indicate a mapping / association of the SRS resource in the time domain.

[0060] In some embodiments, the use of the multiple TPC command fields can be configured to be slotOffset. The value of each of the multiple TPC command fields can correspond to / refer to a respective set of one or more slot offsets (or other time offsets). Referring now toFigure 3 An example of a mapping or configuration 300 between TPC command field values and one or more slotOffset values is depicted. For example, the use of multiple TPC command fields can be configured as slotOffset. In the same example, TPC command field value 0 can indicate that one or more slotOffset configured with higher layer parameter (e.g., slotOffsetTrigger) is set to 0. The one or more slotOffset can be configured with at least one higher layer parameter such as slotOffsetTrigger. In some embodiments, one or more values of slotOffset can be configured / determined in a SRS resource set. Each of the one or more values of slotOffset can be configured with one or more trigger states. Figure 3 An example mapping between TPC command field values and slotOffset values is depicted, where each value of slotOffset can be configured / associated / linked to one or more trigger states.

[0061] In some embodiments, a value of slotOffset can not be configured with one or more trigger states. Thus, each value of the multiple TPC command fields can correspond to a respective slotOffset value. Referring now to Figure 4 An example of a mapping or configuration 400 between TPC command field and slotOffset is depicted. Configuration 400 shows an example mapping between TPC command field values and slotOffset values, where slotOffset can not be configured with one or more trigger states (e.g., one-to-one mapping between TPC command field and slot offset). For example, TPC command field value 2 can indicate / specify / choose a slotOffset value corresponding to the third slotOffset. In another example, TPC command field value 1 can specify / indicate / choose a slotOffset value corresponding to the second slotOffset.

[0062] In some embodiments, the usage (e.g., purpose or application) of the plurality of TPC command fields can be configured as SpatialRelationlnfo, TCI state, SRS TimedomainConfig, and / or resourceMapping. A wireless communication device (e.g., a UE) can be configured with one or more parameter sets including a SpatialRelationlnfo parameter set (e.g., SRS-SpatialRelationlnfo and / or SRS-SpatialRelationlnfoPos-r16), a TCI state parameter set, and / or other parameter sets. Accordingly, the wireless communication device can use a value of each of the plurality of TPC command fields to dynamically select / determine at least one of the one or more parameter sets (e.g., a parameter set of SpatialRelationlnfo, TCI state, SRS TimedomainConfig, resourceMapping, and / or other parameter sets). The value of each of the plurality of TPC command fields can correspond to a respective parameter set of SpatialRelationlnfo, TCI state, SRS TimedomainConfig, and / or resourceMapping. One or more examples discussed herein can illustrate one or more parameter set configurations of a wireless communication device.

[0063] • Example 1: SpatialRelationlnfo parameter set

[0064]

[0065] • Example 2: SpatialRelationlnfo parameter set

[0066]

[0067]

[0068] • Example 3: TCI state parameter set

[0069]

[0070] In some embodiments, the usage of multiple TPC command fields can be configured as SRSTimedomainConfig and / or resourceMapping. For example, a wireless communication device (e.g., a UE) can be configured using one or more parameter sets including a set of resource mapping parameters. Accordingly, the wireless communication device can use the value of each of the multiple TPC command fields to dynamically select / determine at least one of the one or more parameter sets (e.g., a set of parameters for resourceMapping and / or other parameter sets). One or more examples discussed herein can illustrate one or more parameter set configurations (e.g., a set of parameters for resourceMapping) for a wireless communication device.

[0071] • Example 4: resourceMapping parameter set

[0072]

[0073] B, Scheme B

[0074] In some embodiments, a wireless communication device (e.g., a UE) can receive / obtain a configuration via higher layer signaling (e.g., RRC signaling and / or MAC layer signaling) to configure the parameter srs-TPC-PDCCH-Group as Type A, Type B, Type C, and / or Type D. The wireless communication device can schedule / transmit one or more UL transmissions (e.g., PUSCH transmissions, PUCCH transmissions, and / or other transmissions) in a CC of SRS. The wireless communication device can use the configured srs-TPC-PDCCH-Group parameter (or other parameter) to schedule, configure, or enable support for the one or more UL transmissions. In some embodiments, SRS power control can not be bundled / bound / associated / linked with PUSCH power control in the UL transmissions. If SRS power control is not bound with PUSCH power control, higher layer signaling can be used to configure one or more blocks (e.g., associated with at least one wireless communication device). Each of the one or more blocks can apply / correspond to an UL carrier and / or CC.

[0075] In some embodiments, each of the one or more blocks (e.g., a first block) can include one or more fields. The one or more fields of each block can include an SRS request field, at least one TPC command field, and / or other fields. The SRS request field can be associated / related / linked with a CC of the wireless communication device. If the wireless communication device uses one or more CCs, the wireless communication device can use at least one block for each CC. For example, if the wireless communication device uses two CCs, the wireless communication device can use two blocks (e.g., one block for each CC). Each block for each CC can include / provide / indicate / specify an SRS request field, at least one TPC command field, and / or other fields corresponding to the respective CC. The SRS request field can use / occupy 0 or 2 bits (or other bits) of each block. In some embodiments, a higher layer parameter such as fieldTypeFormatX can determine / indicate whether each block includes / provides an SRS request field. For example, if the value of the fieldTypeFormatX parameter is 0 (or other number), the SRS request field can be excluded from the block. In another example, if the value of the fieldTypeFormatX parameter is 1 (or other number), the block can include the SRS request field.

[0076] In some embodiments, the at least one TPC command field (e.g., a first TPC command field) can be associated / related / linked with at least one CC of the wireless communication device. If SRS power control is not bundled / bound with PUSCH power control, the TPC command field can be used for SRS power control. In some embodiments, the TPC command field can use / occupy 2 bits (or other bits) of the block.

[0077] In some embodiments, the value of the SRS request field can be used to trigger / cause an SRS in a CC. At least one PUSCH and / or PUCCH transmission can be scheduled in the CC. In some embodiments, the TPC command field can indicate / provide / specify a cumulative and / or absolute power of the SRS transmission, as shown in Figure 5 For example, a TPC command field value of 0 (or other number) can indicate an absolute power of the SRS transmission of -4 dB (or other number), and / or a cumulative power of the SRS transmission of -1 dB (or other number). In another example, a TPC command field value of 2 (or other number) can specify an absolute power of the SRS transmission of 1 dB (or other number), and / or a cumulative power of the SRS transmission of 1 dB (or other number).

[0078] In some embodiments, each monitoring cell (e.g., CC) can monitor PDCCH transmissions (or other transmissions) to convey / indicate a corresponding DCI (e.g., SRS DCI format) to a wireless communication device. Each monitoring cell can include a corresponding CC in which at least one of a PUSCH transmission and / or a PUCCH transmission can be scheduled. In some embodiments, each such monitoring cell can be different from another monitoring cell used to monitor PDCCH transmissions (or other transmissions) to convey / indicate a corresponding DCI. The other monitoring cell can include a corresponding CC that does not have a scheduled PUSCH transmission and / or PUCCH transmission. In some embodiments, a wireless communication node can convey / provide / indicate / specify / send a corresponding DCI (e.g., SRS DCI format) to a wireless communication device. The corresponding DCI can support triggering one or more PUCCH and / or PUSCH transmissions. The wireless communication node can provide the corresponding DCI with a CRC scrambled by a TPC-SRS-RNTI (e.g., a particular type of RNTI).

[0079] C, Scheme C

[0080] In some embodiments, a wireless communication device (e.g., UE) can receive / obtain a configuration via higher layer signaling (e.g., RRC signaling and / or MAC layer signaling) to configure a parameter srs-TPC-PDCCH-Group as Type A, Type B, Type C, and / or Type D. The wireless communication device can schedule / transmit one or more UL transmissions (e.g., PUSCH transmissions, PUCCH transmissions, and / or other transmissions) in a CC of SRS. The wireless communication device can use the configured srs-TPC-PDCCH-Group parameter (or other parameter) to support, schedule, and / or configure the one or more UL transmissions. In some embodiments, SRS power control can not be bundled / bound / associated / linked with PUSCH power control in the UL transmissions. If SRS power control is not bundled / bound with PUSCH power control, higher layer signaling can be used to configure a first block (e.g., associated with at least one wireless communication device).

[0081] In some embodiments, a block (e.g., a first block) can include one or more fields. The one or more fields of the block can include an SRS request field, a plurality of TPC command fields, and / or other fields. The SRS request field can be associated with / related to / linked to a set of CCs of a wireless communication device. The SRS request field can use / occupy 0 or 2 bits (or other bits) of the block. In some embodiments, a higher layer parameter such as fieldTypeFormatX can determine / indicate whether the block includes / provides the SRS request field. For example, if the value of the fieldTypeFormatX parameter is 0 (or other number), the SRS request field can be excluded from the first block. In another example, if the value of the fieldTypeFormatX parameter is 1 (or other number), the first block can include the SRS request field.

[0082] In some embodiments, each TPC command field (e.g., TPC command 1, TPC command 2, TPC command N, and / or other fields) of the plurality of TPC command fields can be associated with / related to / linked to a respective UL carrier and / or CC of the set of CCs. Thus, for a set of CCs, each TPC command field can be associated with a CC of the set of CCs. In a particular system, the TPC command fields can be used for SRS power control. In some embodiments, a higher layer parameter (e.g., cc-IndexInOneCC-Set and / or other parameters) can indicate / provide / specify / determine / configure the association between each TPC command field and a respective UL carrier and / or CC.

[0083] In some embodiments, at least one of PUSCH and / or PUCCH transmissions can be scheduled within a set of CCs. A set of CCs with PUCCH and / or PUSCH transmissions can be different from another set of CCs without PUCCH and / or PUSCH transmissions. In some embodiments, one or more monitoring cells can monitor / indicate / provide one or more corresponding DCIs (e.g., SRS DCI format). These one or more monitoring cells can include a set of CCs, within which at least one of PUSCH and / or PDSCH transmissions can be scheduled. These one or more monitoring cells can be different from other monitoring cells used to monitor PDCCH transmissions to send corresponding DCIs. Other monitoring cells can include corresponding CCs without PUSCH and / or PUCCH transmissions. In some embodiments, a wireless communication node can transmit / provide / indicate / specify / send the one or more corresponding DCIs (e.g., SRS DCI format) to a wireless communication device. The one or more corresponding DCIs can support triggering one or more PUCCH and / or PUSCH transmissions. The wireless communication node can provide the one or more corresponding DCIs with a CRC scrambled by TPC-SRS-RNTI (e.g., a specific type of RNTI for the corresponding DCI format).

[0084] D. Signal transmission methods

[0085] Figure 6 A flowchart of method 650 for signal transmission is shown. Method 650 can be used in conjunction with this document. Figures 1-5 Detailed description of any components and devices used for implementation. In general, method 650 may include receiving a DCI to trigger an aperiodic SRS (652). Method 650 may include receiving configuration to configure parameters srs-TPC-PDCCH-Group (654).

[0086] Referring now to operation (652), and in some embodiments, a wireless communication device (e.g., a UE) can receive / obtain a DCI to trigger / cause an aperiodic SRS. A wireless communication node can transmit / broadcast the DCI to the wireless communication device. In some embodiments, at least one DCI can trigger an aperiodic SRS in one or more wireless communication devices. The DCI (e.g., a DCI format 2_3 with a CRC scrambled by a TPC-SRS-RNTI and / or other DCI) can include / provide / include a plurality of blocks (e.g., a block 1, a block 3, and / or other blocks). One or more blocks of the plurality of blocks can correspond to a respective wireless communication device. In some embodiments, SRS power control can be bundled / bound to PUSCH power control. If SRS power control is bound to PUSCH power control, a first block of the plurality of blocks can include / contain / indicate an SRS request field, a plurality of TPC command fields, and / or other fields. The SRS request field can be associated / linked / correlated to a set of CCs of the wireless communication device. The plurality of TPC command fields (e.g., a TPC command 1, a TPC command 2, and / or other TPC command fields) can include a first TPC command field. Each TPC command field of the plurality of TPC command fields can be associated / linked / correlated to a respective CC of the set of CCs.

[0087] In some embodiments, if SRS power control is bundled / bound to PUSCH power control, a first block of the plurality of blocks of the DCI can include / contain an SRS request field, a first TPC command field, and / or other fields. Higher layer signaling (e.g., RRC signaling) can be used to configure one or more fields of the first block. The SRS request field (e.g., 0 or 2 bits of the DCI) can be associated / correlated / linked to a CC of the wireless communication device. In some embodiments, a higher layer parameter such as fieldTypeFormatX can determine / indicate whether the first block includes / provides an SRS request field. The first TPC command field (e.g., 2 bits of the DCI) can be associated to a CC of the wireless communication device.

[0088] In some embodiments, the usage (or purpose / application) of the first TPC command field can be configured to include at least one of slotOffset, SRSFreqDomainConfig, SRSTimedomainConfig, resourceMapping, TCI state, and / or SpatialRelationlnfo. A higher layer parameter can be used to configure the usage of the first TPC command field (or other TPC command fields). The usage of the TPC command field can indicate / provide / specify one or more SRS configurations (e.g., frequency domain configuration and / or time domain configuration) and / or at least one mapping (e.g., SRS resource mapping in time domain). In some embodiments, the usage of the plurality of TPC command fields can be configured to slotOffset. If the usage is configured to slotOffset, the value of each of the plurality of TPC command fields can correspond to a respective set of one or more slot offsets. For example, each value of the slot offset can be configured with one or more triggering states, where the value of the TPC command field (e.g., 0 or other number of TPC command field values) maps / associates / links to one or more slot offsets.

[0089] In some embodiments, the usage of the plurality of TPC command fields can be configured to SpatialRelationlnfo, TCI state, SRSTimedomainConfig, and / or resourceMapping. The value of each of the plurality of TPC command fields (e.g., configured to SpatialRelationlnfo, TCI state, and / or others) can correspond to a respective set of parameters of SpatialRelationlnfo, TCI state, SRSTimedomainConfig, and / or resourceMapping. In some embodiments, the value of the TPC command field can indicate / specify at least one of the respective set of parameters to the wireless communication device. The wireless communication device can select the set of parameters indicated / specified by the value of the TPC command field.

[0090] In some embodiments, SRS power control can not be tied with PUSCH power control. If SRS power control is not tied with PUSCH power control, a first block of the plurality of blocks of DCI can include a SRS request field, a first TPC command field, and / or other fields. The SRS request field and / or the first TPC command field can be linked / associated / related with a CC of the wireless communication device. In some embodiments, a higher layer parameter (e.g., fieldTypeFormatX) can indicate / specify whether the SRS request field is included in the first block. In some embodiments, a value of the SRS request field can be used to trigger / cause a SRS in a CC of the wireless communication device. At least one of a PUSCH transmission and / or a PUCCH transmission can be scheduled in the CC of the wireless communication device. In some embodiments, each monitoring cell (e.g., CC) can monitor one or more PDCCH transmissions (or other transmissions) that indicate / send / specify corresponding DCI. A wireless communication node can transmit / send / broadcast a PDCCH (or other transmissions) to convey corresponding DCI (e.g., SRS DCI format) to the wireless communication device. The wireless communication node can provide / indicate / specify the corresponding DCI with a CRC scrambled by a TPC-SRS-RNTI (e.g., a particular type of RNTI). The corresponding DCI can support triggering one or more PUSCH transmissions, PUCCH transmissions, and / or other transmissions. Each monitoring cell can include a corresponding CC in which at least one of a PUSCH transmission and / or a PUCCH transmission can be scheduled. In some embodiments, each monitoring cell can be different / differentiated / separated from another monitoring cell. The other monitoring cell can monitor a PDCCH transmission (or other transmissions) to convey corresponding DCI (e.g., SRS DCI format). The other monitoring cell can include a corresponding CC without a scheduled PUSCH transmission, PUCCH transmission, and / or other transmissions.

[0091] In some embodiments, SRS power control can not be bundled / linked / associated with PUSCH power control. If SRS power control is not bundled with PUSCH power control, a first of the plurality of blocks of DCI can include / contain / provide a SRS request field, a plurality of TPC command fields, and / or other fields. The SRS request field can be associated / linked with a set of CCs of the wireless communication device. The plurality of TPC command fields (e.g., a 1stTPC command, a 2ndTPC command, and / or other TPC command fields) can include a first TPC command field (or other field). Each of the plurality of TPC command fields can be associated / linked with a respective CC of the set of CCs of the wireless communication device. In some embodiments, at least one of a PUSCH transmission, a PUCCH transmission, and / or other transmission can be scheduled in the set of CCs of the wireless communication device. In some embodiments, a monitoring cell (e.g., a CC) can monitor one or more PDCCH transmissions that convey / specify / indicate one or more corresponding DCIs. The wireless communication node can transmit / broadcast the corresponding DCIs with CRC scrambled by TPC-SRS-RNTI. The monitoring cell can include a set of CCs of the wireless communication device. At least one PUSCH transmission, PUCCH transmission, and / or other transmission can be scheduled in the set of CCs. The monitoring cell can be different / distinct / separate / different from another monitoring cell for monitoring PDDCH transmissions (or other transmissions). The PDCCH transmissions can convey / indicate / specify / provide the corresponding DCIs. The other monitoring cell can include corresponding CCs that do not have scheduled PUSCH transmissions, PUCCH transmissions, and / or other transmissions.

[0092] Referring now to operation (654), and in some embodiments, the wireless communication device can receive / obtain the configuration via higher layer signaling (e.g., RRC signaling, MAC layer signaling, and / or other types of signaling). The wireless communication node can use the higher layer signaling (or other types of signaling) to send / transmit / broadcast the configuration to the wireless communication device. The wireless communication device can receive / obtain a configuration for configuring the parameter srs-TPC-PDCCH-Group as Type A, Type B, Type C, and / or Type D (e.g., srs-TPC-PDCCH-Group = Type C and / or srs-TPC-PDCCH-Group = Type D). In some embodiments, the wireless communication device can schedule / transmit at least one of a PUSCH transmission, a PUCCH transmission, and / or other transmissions to the wireless communication node in a CC of the SRS (e.g., in accordance with the configured parameter srs-TPC-PDCCH-Group). The wireless communication node can receive / obtain the configured parameter srs-TPC-PDCCH-Group (or other parameters) from the wireless communication device to schedule the at least one transmission (e.g., PUSCH, PUCCH, and / or other transmissions). The wireless communication device can schedule / transmit the at least one transmission to the wireless communication node in accordance with the configured parameter srs-TPC-PDCCH-Group (or other parameters).

[0093] While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not limitation. Likewise, the various figures can depict example architectures or configurations, which can be employed, as provided for by the present solution, in various environments and architectures. However, it should be appreciated that the present solution is not limited to the illustrated example architectures or configurations, but can be employed in a multitude of different example architectures and configurations. Additionally, it should be appreciated that one or more features of an embodiment could be employed with respect to another embodiment. Accordingly, the breadth and scope of the present solution should not be limited by any of the above-described illustrative embodiments.

[0094] It should also be understood that any reference to an element herein using a designation such as "first," "second," and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element.

[0095] Moreover, those skilled in the art will appreciate that the information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, which can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields, or particles, optical fields or particles, or any combination thereof.

[0096] Those of skill would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software" or a "software module"), or any combination thereof. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality, without reference to the particular

[0097] Moreover, those skilled in the art will appreciate that the various illustrative logical blocks, modules, devices, components, and circuits described herein can be implemented or performed with an integrated circuit (IC), which can 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. The logical blocks, modules, and circuits can also include antennas and / or transceivers to communicate with various components within a network or within a device. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration.

[0098] If implemented in software, the functions can be stored on a computer-readable medium, which can be one or more of various types of storage devices such as a magnetic disc, optical disc, or flash memory, etc. In some embodiments, the functionality of the methods disclosed herein can be provided within the hardware components, such as those shown in FIG. 1. In some embodiments, the hardware components can include a set of one or more processors coupled to a storage device, such as a volatile memory (e.g., random access memory), or a non-volatile storage device (e.g., a magnetic or optical disc). Further, the functionality of the methods disclosed herein can be provided within a set of one or more processors coupled to a storage device, such as a volatile memory (e.g., random access memory), or a non-volatile storage device (e.g., a magnetic or optical disc). In some embodiments, the storage device can be a storage device within a set of one or more processors coupled to a storage device, such as a volatile memory (e.g., random access memory), or a non-volatile storage device (e.g., a magnetic or optical disc).

[0099] In this document, the term "module" as used herein, refers to software, firmware, hardware, and any combination of these elements that is used to perform an associated function described herein. Furthermore, a variety of modules can be described as separate modules; however, as would be apparent to one of ordinary skill in the art, two or more modules can be combined to form a single module that performs the associated functions according to embodiments of the present solution.

[0100] Furthermore, memory or other storage devices and communication components can be employed in embodiments of the present solution. It will be appreciated that, for clarity, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains can be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical, physical or time organization of functions.

[0101] Various modifications to the implementations described will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other implementations without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the implementations shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein and made apparent to others skilled in the art by the teachings herein.

Claims

1. A method of wireless communication, comprising: receiving, by a wireless communication device, a downlink control information (DCI) from a wireless communication node to trigger an aperiodic sounding reference signal (SRS), wherein the DCI comprises a plurality of blocks, each one or more of the plurality of blocks is for a respective wireless communication device, wherein, when SRS power control is bundled with physical uplink shared channel (PUSCH) power control, a first block of the plurality of blocks comprises: a SRS request field associated with a set of component carriers (CCs) of the wireless communication device, and a plurality of transmit power control (TPC) command fields including a first TPC command field, each of the TPC command fields is associated with a respective CC of the set of CCs, wherein usage of the plurality of TPC command fields is configured to include slotOffset, SRSTimedomainConfig, resourceMapping, TCI state, or SpatialRelationInfo. 2.The method of claim 1, comprising: receiving, by the wireless communication device, a configuration from the wireless communication node via higher layer signaling to configure a parameter srs-TPC-PDCCH-Group to be Type A, Type B, Type C, or Type D. 3.The method of claim 1, comprising: transmitting, by the wireless communication device, at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission to the wireless communication node in a component carrier (CC) of the SRS according to the configured parameter srs-TPC-PDCCH-Group.

4. The method of claim 1, wherein, usage of the first TPC command field is configured to include at least one of slotOffset, SRSFreqDomainConfig, SRSTimedomainConfig, resourceMapping, TCI state, or SpatialRelationInfo.

5. The method of claim 1, wherein, usage of the plurality of TPC command fields is configured to slotOffset, a value of each of the plurality of TPC command fields corresponds to a respective set of one or more slot offsets.

6. The method of claim 1, wherein, usage of the plurality of TPC command fields is configured to SpatialRelationInfo, TCI state, SRSTimedomainConfig, or resourceMapping, a value of each of the plurality of TPC command fields corresponds to a respective set of parameters of SpatialRelationInfo, TCI state, SRSTimedomainConfig, or resourceMapping.

7. The method of claim 1, wherein, when SRS power control is not bundled with physical uplink shared channel (PUSCH) power control, a first block of the plurality of blocks comprises: a SRS request field associated with a component carrier (CC) of the wireless communication device, and a first transmit power control, TPC, command field associated with the CC.

8. The method of claim 7, wherein: a value of the SRS request field is used to trigger a sounding reference signal (SRS) in the CC, at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission is schedulable in the CC, or each monitoring cell for monitoring a physical downlink control channel (PDCCH) transmission for a corresponding DCI includes a corresponding CC in which at least one of a PUSCH transmission or a PUCCH transmission is schedulable, the each monitoring cell being different from a monitoring cell for monitoring a PDCCH transmission for a corresponding DCI that includes a corresponding CC for which no PUSCH transmission or PUCCH transmission is scheduled.

9. The method of claim 1, wherein, when SRS power control is not bundled with physical uplink shared channel (PUSCH) power control, a first of the plurality of blocks includes: an SRS request field associated with a set of component carriers (CCs) of the wireless communication device, and a plurality of transmit power control (TPC) command fields, the plurality of TPC command fields including a first TPC command field, each of the TPC command fields being associated with a respective CC of the set of CCs.

10. The method of claim 9, wherein: at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission is schedulable in the set of CCs, or a monitoring cell for monitoring a physical downlink control channel (PDCCH) transmission for a corresponding DCI includes a set of CCs in which at least one of a PUSCH transmission or a PUCCH transmission is schedulable, the monitoring cell being different from a monitoring cell for monitoring a PDCCH transmission for a corresponding DCI that includes a corresponding CC for which no PUSCH transmission or PUCCH transmission is scheduled.

11. A method of wireless communication, comprising: transmitting, by a wireless communication node, a downlink control information (DCI) to a wireless communication device to trigger an aperiodic sounding reference signal (SRS), wherein the DCI includes a plurality of blocks, each or multiple of the plurality of blocks being for a respective wireless communication device, wherein, when SRS power control is bundled with physical uplink shared channel (PUSCH) power control, a first of the plurality of blocks includes: an SRS request field associated with a set of component carriers (CCs) of the wireless communication device, and a plurality of transmit power control (TPC) command fields including a first TPC command field, each of the TPC command fields being associated with a respective CC of the set of CCs, The usage of the plurality of TPC command fields is configured to include slotOffset, SRSTimedomainConfig, resourceMapping, TCI state, or SpatialRelationInfo.

12. The method of claim 11, comprising: transmitting, by the wireless communication node to the wireless communication device via higher layer signaling, a configuration to configure a parameter srs-TPC-PDCCH-Group to be of Type A, Type B, Type C, or Type D.

13. The method of claim 11, comprising: receiving, by the wireless communication node from the wireless communication device, the configured parameter srs-TPC-PDCCH-Group to schedule at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission in a component carrier (CC) of the SRS.

14. The method of claim 11, wherein, The usage of the first TPC command field is configured to include at least one of slotOffset, SRSFreqDomainConfig, SRSTimedomainConfig, resourceMapping, TCI state, or SpatialRelationInfo.

15. The method of claim 11, wherein, The usage of the plurality of TPC command fields is configured to slotOffset, a value of each of the plurality of TPC command fields corresponds to a respective set of one or more slot offsets.

16. The method of claim 11, wherein, The usage of the plurality of TPC command fields is configured to SpatialRelationInfo, TCI state, SRSTimedomainConfig, or resourceMapping, a value of each of the plurality of TPC command fields corresponds to a respective set of parameters of SpatialRelationInfo, TCI state, SRSTimedomainConfig, or resourceMapping.

17. The method of claim 11, wherein, When SRS power control is not bundled with physical uplink shared channel (PUSCH) power control, a first block of the plurality of blocks includes: an SRS request field associated with a component carrier (CC) of the wireless communication device, and a first transmit power control (TPC) command field associated with the CC.

18. The method of claim 17, wherein: a value of the SRS request field is used to trigger the SRS in the CC, at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission is able to be scheduled in the CC, or Each monitoring cell for monitoring physical downlink control channel (PDCCH) transmissions to convey corresponding DCI includes a corresponding CC in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled, the each monitoring cell being different from a monitoring cell for monitoring PDCCH transmissions to convey corresponding DCI that includes a corresponding CC for which no PUSCH transmission or PUCCH transmission is scheduled.

19. The method of claim 11, wherein, When SRS power control is not tied to physical uplink shared channel (PUSCH) power control, a first block of the plurality of blocks includes: an SRS request field associated with a set of component carriers (CCs) of the wireless communication device, and a plurality of transmit power control (TPC) command fields, the plurality of TPC command fields including a first TPC command field, each of the TPC command fields being associated with a respective CC of the set of CCs.

20. The method of claim 19, wherein: at least one of a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission can be scheduled in the set of CCs, or a monitoring cell for monitoring physical downlink control channel (PDCCH) transmissions to convey corresponding DCI includes a set of CCs in which at least one of a PUSCH transmission or a PUCCH transmission can be scheduled, the monitoring cell being different from a monitoring cell for monitoring PDCCH transmissions to convey corresponding DCI that includes a corresponding CC for which no PUSCH transmission or PUCCH transmission is scheduled.

21. 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 of claims 1-20.

22. A wireless communication apparatus, comprising: at least one processor configured to perform the method of any of claims 1-20.

22. A wireless communication apparatus, comprising: at least one processor configured to perform the method of any of claims 1-20.

Images