CN117121571A - Sounding reference signal power control employing non-scheduled downlink control information - Google Patents

Abstract

Aspects relate to wireless communications with Sounding Reference Signal (SRS) power control using non-scheduled Downlink Control Information (DCI) configured to trigger aperiodic SRS without scheduled data and without a Channel State Information (CSI) request. The non-schedule is configured to include at least two Transmit Power Control (TPC) commands. The first TPC command is configured for power control of a Physical Uplink Shared Channel (PUSCH) transmitted by the UE to the base station. The second TPC commands are configured for power control of one or more Sounding Reference Signal (SRS) resource sets. Additionally, the first TPC command may be independent of the second TPC command, with different power control being implemented for PUSCH transmissions and SRS transmissions. Additionally, the non-scheduled DCI may be formatted according to DCI format 0_1 or DCI format 0_2.

Description

Sounding reference signal power control employing non-scheduled downlink control information

Cross Reference to Related Applications

The present application claims priority and benefit from U.S. patent and trademark office filed U.S. application Ser. No.17/713,068 at 4 at 2022 and U.S. provisional application Ser. No.63/171,501 at 4 at 2021, which are all incorporated herein by reference as if fully set forth below and for all applicable purposes.

Technical Field

The techniques discussed below relate generally to wireless communications, and more particularly to Sounding Reference Signal (SRS) power control using non-scheduled Downlink Control Information (DCI) configured to trigger aperiodic SRS without scheduled data and without a Channel State Information (CSI) request.

Introduction to the invention

A next generation wireless communication system (e.g., 5 GS) may include a 5G core network and a 5G Radio Access Network (RAN), such as a New Radio (NR) -RAN. The NR-RAN supports communication via one or more cells. For example, a wireless communication device, such as a User Equipment (UE), may access a cell via a network entity or node, which may be implemented, for example, by a base station or g B node (gNB).

In a 5G RAN, sounding Reference Signals (SRS) are reference signals transmitted by a UE to a gNB or base station (or other network node) in the Uplink (UL) direction. SRS may provide information about the combined effects of multipath fading, scattering, doppler and power loss of the transmitted signal, for example. This information may in turn be used by the base station or the gNB to estimate the channel quality of the UL channel over a wide frequency range (e.g., full bandwidth) and to allocate transmission resources to a bandwidth region (e.g., bandwidth portion) with better channel quality, or for positioning. A particular type of SRS is an aperiodic SRS (a-SRS), which is a "triggered type" SRS transmission that can be configured by a Radio Resource Control (RRC) layer, and which is triggered by Downlink Control Information (DCI) transmitted on the Downlink (DL) from the gNB to the UE.

Brief summary of some examples

The following presents a simplified summary of one or more aspects of the disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure, and is intended to neither identify key or critical elements of all aspects of the disclosure nor delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a form as a prelude to the more detailed description that is presented later.

According to one aspect, a method for communicating at a base station is disclosed. The method comprises the following steps: configuring Downlink Control Information (DCI) to include a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; and preparing the DCI for transmission to at least one User Equipment (UE).

In another aspect, a network entity (such as a base station) is disclosed that includes a processor configured to: configuring Downlink Control Information (DCI) to include a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets. The processor is also configured to prepare the DCI for transmission to at least one User Equipment (UE).

According to yet another aspect, a method for communicating at a User Equipment (UE) is provided. The method comprises the following steps: processing Downlink Control Information (DCI) received from a network entity, the DCI including a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets. The method also includes configuring resources for at least one of PUSCH transmission and SRS transmission based on the first TPC command or the second TPC command.

In yet another aspect, a user equipment is disclosed that includes a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor is configured to: receiving Downlink Control Information (DCI) configured to include a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets. The processor also configures resources for at least one of PUSCH transmission and SRS transmission based on the first TPC command or the second TPC command; and transmitting the configured resources for at least one of PUSCH transmission and SRS transmission.

These and other aspects of the present disclosure will be more fully understood upon review of the following detailed description. Other aspects, features and embodiments of the present disclosure will become apparent to those ordinarily skilled in the art upon review of the following description of specific exemplary embodiments of the disclosure in conjunction with the accompanying figures. While features of the present disclosure may be discussed below with respect to certain embodiments and figures, all embodiments of the present disclosure may include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments of the disclosure discussed herein. In a similar manner, while example embodiments may be discussed below as device, system, or method embodiments, it should be appreciated that such example embodiments may be implemented in a variety of devices, systems, and methods.

Brief Description of Drawings

Fig. 1 is a schematic illustration of a wireless communication system in accordance with some aspects.

Fig. 2 is a conceptual illustration of an example of a radio access network according to some aspects.

Fig. 3 is a schematic illustration of an example of radio resources in an air interface utilizing Orthogonal Frequency Division Multiplexed (OFDM) signals, in accordance with some aspects.

Fig. 4 illustrates an example of a DCI bit field according to some aspects.

Fig. 5 is a call flow diagram illustrating an example of triggering for Sounding Reference Signal (SRS) transmission and signaling for Transmit Power Control (TPC) in accordance with some aspects.

Fig. 6 illustrates an example of non-scheduled DCI triggering an a-SRS transmission including both PUSCH and SRS Transmit Power Control (TPC) in accordance with some aspects.

Fig. 7A-7C illustrate different configurations of DCI including TPC for PUSCH and SRS, the DCI including an indication of TPC SRS power adjustment status, according to some aspects.

Fig. 8A-8C illustrate examples of different configurations of DCI including TPC for PUSCH and SRS, the DCI including an indication of TPC SRS power adjustment status, according to some aspects.

Fig. 9A and 9B illustrate examples of transmission timelines with several slots of non-scheduled and scheduled trigger DCIs, according to some aspects.

Fig. 10 illustrates another example of a transmission timeline with a number of slots of non-scheduled and scheduled trigger DCI according to some aspects.

Fig. 11 is a block diagram illustrating an example of a hardware implementation of a network entity or node employing a processing system in accordance with some aspects.

Fig. 12 is a flow chart illustrating a method for configuring and transmitting DCI in a network entity or node, according to some aspects.

Fig. 13 is a block diagram illustrating an example of a hardware implementation of a User Equipment (UE) employing a processing system in accordance with some aspects.

Fig. 14 is a flow chart illustrating an example of a method for communicating in a UE, according to some aspects.

Fig. 15 is a flow chart illustrating another example of a method for communicating in a UE, according to some aspects.

Detailed Description

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. It will be apparent, however, to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

While aspects and embodiments are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases may be produced in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may be produced via integrated chip embodiments and other non-module component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail/shopping devices, medical devices, artificial intelligence enabled devices, etc.). While some examples may or may not be specific to each use case or application, the broad applicability of the described innovations may occur. Implementations may range from chip-level or module components to non-module, non-chip-level implementations, and further to aggregated, distributed or Original Equipment Manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical environments, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals must include several components (e.g., hardware components including antennas, radio Frequency (RF) chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders/summers, etc.) for analog and digital purposes. The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end user equipment, and the like, of various sizes, shapes, and configurations.

The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Referring now to fig. 1, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 by way of illustrative example and not limitation. The wireless communication system 100 includes three interaction domains: a core network 102, a Radio Access Network (RAN) 104, and at least one scheduled entity 106. The at least one scheduled entity 106 may be referred to as a User Equipment (UE) 106 in the following discussion. RAN 104 includes at least one scheduling entity 108. The at least one scheduling entity 108 may be referred to as a Base Station (BS) 108 in the following discussion. By way of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as, but not limited to, the internet.

RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to UEs 106. As one example, RAN 104 may operate in accordance with the third generation partnership project (3 GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, the RAN 104 may operate under a mix of 5G NR and evolved universal terrestrial radio access network (eUTRAN) standards (commonly referred to as LTE). The 3GPP refers to this hybrid RAN as the next generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

As illustrated, the RAN 104 includes a plurality of base stations 108. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be variously referred to by those skilled in the art as a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), an Access Point (AP), a Node B (NB), an evolved node B (eNB), a next generation node B (gNB), a Transmission Reception Point (TRP), or some other suitable terminology. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. The TRP may communicate on the same carrier frequency or different carrier frequencies within the same frequency band or different frequency bands.

The radio access network 104 is further illustrated as supporting wireless communications for a plurality of mobile devices. A mobile device may be referred to as a User Equipment (UE) in the 3GPP standards, but may also be referred to by those skilled in the art as a Mobile Station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an Access Terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. The UE may be a device that provides a user with access to a network service.

Within this document, a "mobile" device need not necessarily have mobility capability, and may be stationary. The term mobile device or mobile equipment refers broadly to a wide variety of devices and technologies. The UE may include several hardware structural components sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, and so forth, electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile equipment, cellular (cell) phones, smart phones, session Initiation Protocol (SIP) phones, laptops, personal computers, notebooks, netbooks, smartbooks, tablet devices, personal Digital Assistants (PDAs), and a wide variety of embedded systems, e.g., corresponding to the "internet of things" (IoT). Additionally, the mobile apparatus may be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a Global Positioning System (GPS) device, an object tracking device, an unmanned aerial vehicle, a multi-axis aircraft, a four-axis aircraft, a remote control device, a consumer and/or wearable device (such as eyeglasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, and the like. The mobile device may additionally be a digital home or smart home appliance such as a home audio, video and/or multimedia appliance, vending machine, smart lighting device, home security system, smart meter, etc. The mobile device may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device (e.g., smart grid) that controls power, lighting, water, etc.; industrial automation and enterprise equipment; a logistics controller; agricultural equipment; military defenses, vehicles, airplanes, boats, weapons, and the like. Still further, the mobile device may provide networked medical or telemedicine support, i.e., remote health care. The remote healthcare device may include a remote healthcare monitoring device and a remote healthcare supervising device, whose communications may be given priority or prioritized access over other types of information, for example, in the form of prioritized access to critical service data transmissions and/or associated QoS to critical service data transmissions.

Wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over an air interface may be referred to as Downlink (DL) transmissions. In some examples, the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108). Another way to describe this point-to-multipoint transmission scheme may be to use the term broadcast channel multiplexing. The transmission from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as an Uplink (UL) transmission. In some examples, the term uplink may refer to point-to-point transmissions originating at a scheduled entity (described further below; e.g., UE 106).

In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within this disclosure, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities, as discussed further below. That is, for scheduled communications, the UE 106 (which may be a scheduled entity) may utilize resources allocated by the scheduling entity 108.

The base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE may act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs).

As illustrated in fig. 1, the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly, scheduling entity 108 is a node or device responsible for scheduling traffic (including downlink traffic 112 and, in some examples, uplink traffic 116 and/or uplink control information 118 from one or more scheduled entities 106 to scheduling entity 108) in a wireless communication network. In another aspect, the scheduled entity 106 is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., grants), synchronization or timing information), or other control information, from another entity in the wireless communication network, such as scheduling entity 108.

Additionally, uplink and/or downlink control information and/or traffic information may be divided in time into frames, subframes, slots, and/or symbols. As used herein, a symbol may refer to a unit of time that carries one Resource Element (RE) per subcarrier in an Orthogonal Frequency Division Multiplexing (OFDM) waveform. In some examples, a slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 millisecond (ms). Multiple subframes or slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and the waveforms may be organized using any suitable scheme, and the various time divisions of the waveforms may have any suitable duration.

In general, the base station 108 may include a backhaul interface for communicating with a backhaul portion 120 of a wireless communication system. Backhaul 120 may provide a link between base station 108 and core network 102. Further, in some examples, the backhaul network may provide interconnection between respective base stations 108. Various types of backhaul interfaces may be employed, such as direct physical connections using any suitable transport network, virtual networks, and so forth.

The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5 GC). In other examples, core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

Referring now to fig. 2, a schematic illustration of a RAN200 is provided by way of example and not limitation. In some examples, RAN200 may be the same as RAN 104 described above and illustrated in fig. 1. The geographical area covered by the RAN200 may be divided into cellular areas (cells) that may be uniquely identified by a User Equipment (UE) based on an identification broadcast from one access point or base station. Fig. 2 illustrates macro cells 202, 204, and 206, and small cell 208, each of which may include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. The radio links within a sector may be identified by a single logical identification belonging to the sector. In a sectorized cell, multiple sectors within the cell may be formed by groups of antennas, with each antenna being responsible for communication with UEs in a portion of the cell.

Various base station arrangements may be utilized. For example, in fig. 2, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a Remote Radio Head (RRH) 216 in the cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH by a feeder cable. In the illustrated example, the cells 202, 204, and 206 may be referred to as macro cells because the base stations 210, 212, and 214 support cells having a large size. Further, base station 218 is shown in small cell 208 (e.g., a micro cell, pico cell, femto cell, home base station, home node B, home evolved node B, etc.), small cell 208 may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell because base station 218 supports cells having a relatively small size. Cell sizing may be done according to system design and component constraints.

It will be appreciated that the radio access network 200 may include any number of wireless base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of a given cell. The base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and/or 218 may be the same as base station/scheduling entity 108 described above and illustrated in fig. 1.

Within RAN 200, cells may include UEs that may be in communication with one or more sectors of each cell. Further, each base station 210, 212, 214, and 218 may be configured to provide an access point to a core network (e.g., as illustrated in fig. 1) for all UEs in the respective cell. For example, UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UEs 230 and 232 may be in communication with base station 214 via RRH 216; and UE 234 may be in communication with base station 218. In some examples, the UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and/or 242 may be the same as the UE/scheduled entity 106 described above and illustrated in fig. 1.

In some examples, an Unmanned Aerial Vehicle (UAV) 220 (which may be an unmanned aerial vehicle or a four-axis aerial vehicle) may be a mobile network node and may be configured to function as a UE. For example, UAV220 may operate within cell 202 by communicating with base station 210. In some examples, UAV220 may be configured to act as a BS (e.g., serving UE 236). That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station (such as UAV 220).

In the radio access network 200, the ability of a UE to communicate independent of its location while moving is referred to as mobility. The various physical channels between the UE and the radio access network are typically set up, maintained and released under control of access and mobility management functions (AMFs). The AMF (not shown in fig. 2) may include a Security Context Management Function (SCMF) that manages security contexts for both control plane and user plane functionality, and a security anchor function (SEAF) that performs authentication.

The radio access network 200 may utilize DL-based mobility or UL-based mobility to enable mobility and handover (i.e., the connection of a UE is transferred from one radio channel to another). In a network configured for DL-based mobility, the UE may monitor various parameters of signals from its serving cell and various parameters of neighboring cells during a call with a scheduling entity, or at any other time. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, the UE may make a handover or handoff from the serving cell to the neighboring (target) cell if the UE moves from one cell to another cell, or if the signal quality from the neighboring cell exceeds the signal quality from the serving cell for a given amount of time. For example, UE 224 (illustrated as a vehicle, but any suitable form of UE may be used) may move from a geographic region corresponding to its serving cell 202 to a geographic region corresponding to neighbor cell 206. When the signal strength or quality from the neighbor cell 206 exceeds the signal strength or quality of the serving cell 202 for a given amount of time, the UE 224 may transmit a report message to its serving base station 210 indicating the condition. In response, UE 224 may receive the handover command and the UE may experience a handover to cell 206.

In a network configured for UL-based mobility, UL reference signals from each UE may be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214/216 may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signal (PSS), unified Secondary Synchronization Signal (SSS), and unified Physical Broadcast Channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive carrier frequencies and slot timings from these synchronization signals, and transmit uplink pilot or reference signals in response to the derived timings. Uplink pilot signals transmitted by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214/216) within radio access network 200. Each of these cells may measure the strength of the pilot signal and the radio access network (e.g., one or more of base stations 210 and 214/216 and/or a central node within the core network) may determine a serving cell for UE 224. As UE 224 moves within radio access network 200, the network may continue to monitor uplink pilot signals transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighbor cell exceeds the signal strength or quality measured by the serving cell, network 200 may handover UE 224 from the serving cell to the neighbor cell with or without notification to UE 224.

Although the synchronization signals transmitted by the base stations 210, 212, and 214/216 may be uniform, the synchronization signals may not identify a particular cell, but may identify a partition that includes multiple cells operating on the same frequency and/or having the same timing. The use of zones in a 5G network or other next generation communication network enables an uplink-based mobility framework and improves the efficiency of both the UE and the network, as the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

In various implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides proprietary use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of spectrum without the need for government granted licenses. While it is still generally desirable to follow some technical rules to access the unlicensed spectrum, any operator or device may gain access. The shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be needed to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs. For example, a licensee of a portion of licensed spectrum may provide Licensed Shared Access (LSA) to share the spectrum with other parties, e.g., to gain access using conditions determined by the appropriate licensee.

The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming problems sometimes occur with respect to FR2, which is commonly (interchangeably) referred to as the "millimeter wave" band in various documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

In view of the above, unless specifically stated otherwise, it is to be understood that, if used herein, the term "sub-6 GHz" or the like may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that, if used herein, the term "millimeter wave" may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

The air interface in radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices. For example, the 5G NR specification utilizes an Orthogonal Frequency Division Multiplexed (OFDM) waveform with a Cyclic Prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210 and multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete fourier transform spread OFDM with CP (DFT-s-OFDM), also known as single carrier frequency division multiple access (SC-FDMA). However, it is within the scope of the present disclosure that multiplexing and multiple access are not limited to the above-described schemes, and may be provided using Time Division Multiple Access (TDMA), code Division Multiple Access (CDMA), frequency Division Multiple Access (FDMA), sparse Code Multiple Access (SCMA), resource Spread Multiple Access (RSMA), or other suitable multiple access schemes. Further, multiplexing DL transmissions from base station 210 to UEs 222 and 224 may be provided using Time Division Multiplexing (TDM), code Division Multiplexing (CDM), frequency Division Multiplexing (FDM), orthogonal Frequency Division Multiplexing (OFDM) transmission, sparse Code Multiplexing (SCM), or other suitable multiplexing scheme.

The air interface in radio access network 200 may further utilize one or more duplexing algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in two directions. Full duplex means that two endpoints can communicate with each other at the same time. Half duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex emulation is typically implemented for wireless links using Time Division Duplexing (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in the other direction, where the direction may change very rapidly, e.g., several times per slot. In wireless links, full duplex channels typically rely on physical isolation of the transmitter and receiver, as well as suitable interference cancellation techniques. Full duplex emulation is typically achieved for wireless links by utilizing Frequency Division Duplexing (FDD) or Space Division Duplexing (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated from each other using Space Division Multiplexing (SDM). In other examples, full duplex communications may be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full duplex communication may be referred to as sub-band full duplex (SBFD), also known as flexible duplex.

In a further aspect of the RAN 200, side-chain signals may be used between UEs without having to rely on scheduling or control information from the base station. For example, two or more UEs (e.g., UEs 226 and 228) may communicate with each other using peer-to-peer (P2P) or side link signals 227 without the need to relay the communication through a base station (e.g., base station 212). In a further example, UE 238 is illustrated in communication with UEs 240 and 242. Here, UE 238 may be used as a scheduling entity or primary side link device, and UEs 240 and 242 may be used as scheduled entities or non-primary (e.g., secondary) side link devices. In yet another example, the UE may be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network, and/or mesh network. In a mesh network example, UEs 240 and 242 may optionally communicate directly with each other via side-link signals in addition to communicating with UE 238 (e.g., acting as a scheduling entity). Thus, in a wireless communication system having scheduled access to time-frequency resources and having a cellular, P2P, or mesh configuration, a scheduling entity and one or more scheduled entities may utilize the scheduled resources to communicate. In some examples, side link signals 227 include side link traffic (e.g., physical side link shared channels) and side link control (e.g., physical side link control channels).

In some examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of serving base station 212 may each communicate with base station 212 using cellular signals and with each other using direct link signals (e.g., side link signals 227) without relaying the communication through the base station. In an example of a V2X network within the coverage area of base station 212, base station 212 and/or one or both of UEs 226 and 228 may act as a scheduling entity to schedule side link communications between UEs 226 and 228.

Various aspects of the disclosure will be described with reference to OFDM waveforms, examples of which are schematically illustrated in fig. 3. Those of ordinary skill in the art will appreciate that the various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles may also be applied to SC-FDMA waveforms.

Referring now to fig. 3, an expanded view of an example DL subframe 302A or 302B is illustrated, which shows an OFDM resource grid 304. However, as those skilled in the art will readily appreciate, the physical layer (PHY) transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in a horizontal direction in units of OFDM symbols, and frequency is in a vertical direction in units of subcarriers. The 5G NR supports a scalable parameter design, where different parameter designs may be used for different radio spectrum, different bandwidths, etc. For example, subcarrier spacings (SCS) of 15kHz, 30kHz, 60kHz, etc. may be used in different scenarios.

The resource grid 304 may be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation where multiple antenna ports are available, a corresponding plurality of resource grids 304 may be available for communication. The resource grid 304 is partitioned into a plurality of Resource Elements (REs) 306. REs (which are 1 subcarrier x 1 symbol) are the smallest discrete part of the time-frequency grid and contain a single complex value representing data from a physical channel or signal. Each RE may represent one or more information bits, depending on the modulation utilized in a particular implementation. In some examples, the RE blocks may be referred to as Physical Resource Blocks (PRBs) or, more simply, resource Blocks (RBs) 308, which contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number being designed independent of the parameters used. In some examples, an RB may include any suitable number of consecutive OFDM symbols in the time domain, depending on the parameter design. Within this disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to a single communication direction (transmission or reception for a given device).

Scheduling of UEs (e.g., scheduled entities) for downlink, uplink, or side-link transmissions generally involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWP). Each bandwidth portion (BWP) may include two or more contiguous or consecutive RBs. Thus, the UE typically utilizes only a subset of the resource grid 304. In some examples, an RB may be the smallest resource unit that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate of that UE. The RBs may be scheduled by a base station (e.g., gNB, eNB, RSU, etc.), or may be self-scheduled by a UE implementing D2D side-link communication.

In this illustration, RB 308 is shown to occupy less than the entire bandwidth of subframe 302A, with some subcarriers above and below RB 308 being illustrated. In a given implementation, subframe 302A may have a bandwidth corresponding to any number of one or more RBs 308. Further, in this illustration, RB 308 is shown to occupy less than the entire duration of subframe 302A, but this is merely one possible example.

Each 1ms subframe 302A may include one or more contiguous slots. As an illustrative example, in the example shown in fig. 3, one subframe 302B includes four slots 310. In some examples, a slot may be defined according to a specified number of OFDM symbols having a given Cyclic Prefix (CP) length. For example, a slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots having a shorter duration (e.g., one or two OFDM symbols). In some cases, these mini-slots may occupy resources scheduled for ongoing slot transmissions for the same or different UEs to transmit. Any number of resource blocks may be utilized within a subframe or slot.

An expanded view of one of the slots 310 illustrates the slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry control channels (e.g., physical Downlink Control Channels (PDCCHs)), while the data region 314 may carry data channels (e.g., physical Downlink Shared Channels (PDSCH) or Physical Uplink Shared Channels (PUSCH)). Of course, a slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. The structure illustrated in fig. 3 is merely an example, and a different time slot structure may be utilized, and one or more may be included for each of the control region and the data region.

Although not illustrated in fig. 3, individual REs 306 within RBs 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, and the like. Other REs 306 within an RB 308 may also carry pilot or reference signals including, but not limited to, demodulation reference signals (DMRS), control Reference Signals (CRS), or Sounding Reference Signals (SRS). These pilot or reference signals may be provided to the recipient device to perform channel estimation for the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channels within RB 308.

In some examples, the time slots 310 may be used for broadcast or unicast communications. In a V2X or D2D network, broadcast communication may refer to point-to-multipoint transmission by one device (e.g., a vehicle, base station (e.g., RSU, gNB, eNB, etc.), UE, or other similar device) to other devices. Unicast communication may refer to a point-to-point transmission by one device to a single other device.

In an example, the control region 312 of the slot 310 may include a Physical Downlink Control Channel (PDCCH) including Downlink Control Information (DCI) transmitted by a base station (e.g., gNB, eNB, RSU, etc.) towards one or more UEs of a group of UEs, which may include one or more side-link devices (e.g., V2X/D2D devices). In some examples, the DCI may include synchronization information to synchronize communications by multiple side-link devices on a side-link channel. Further, the DCI may include scheduling information indicating one or more resource blocks allocated to a side-link device for side-link communication in control region 312 and/or data region 314. For example, the control region 312 of the slot may also include control information transmitted by the side link device on the side link channel, while the data region 314 of the slot 310 may include data transmitted by the side link device on the side link channel. In some examples, the control information may be transmitted within a physical side chain control channel (PSCCH), and the data may be transmitted within a physical side chain shared channel (PSSCH).

In DL transmissions (e.g., over the Uu interface), a transmitting device (e.g., scheduling entity) may allocate one or more REs 306 (e.g., within control region 312) to carry UL control information to one or more scheduled entities, including one or more DL control channels, such as PBCH and/or Physical Downlink Control Channel (PDCCH), etc. The transmitting device may further allocate one or more REs 306 to carry other DL signals such as DMRS, phase tracking reference signals (PT-RS), channel state information-reference signals (CSI-RS), primary Synchronization Signals (PSS), and Secondary Synchronization Signals (SSS).

The synchronization signals PSS and SSS and in some examples also PBCH and PBCH DMRS may be transmitted in a Synchronization Signal Block (SSB) comprising 3 consecutive OFDM symbols numbered in ascending order from 0 to 3 via a time index. In the frequency domain, SSBs may be spread over 240 contiguous subcarriers, with the subcarriers numbered in ascending order from 0 to 239 via a frequency index. Of course, the present disclosure is not limited to this particular SSB configuration. Other non-limiting examples may utilize more or less than two synchronization signals, may include one or more supplemental channels in addition to the PBCH, may omit the PBCH, and/or may use a different number of symbols and/or non-consecutive symbols for the SSB.

SSBs may be used to transmit System Information (SI) and/or provide a reference to SI transmitted via another channel. Examples of system information may include, but are not limited to: subcarrier spacing, system frame number, cell Global Identifier (CGI), cell barring indication, common control resource set (coreset) list, common search space list, search space for system information block 1 (SIB 1), paging search space, random access search space, and uplink configuration information. Two specific examples of CORESET include PDCCH CORESET 0 and CORESET 1.

The PDCCH may carry Downlink Control Information (DCI) including, but not limited to, power control commands, scheduling information, grants, and/or RE assignments for DL and UL transmissions. The physical layer (PHY) carries hybrid automatic repeat request (HARQ) feedback transmissions, such as Acknowledgements (ACKs) or Negative Acknowledgements (NACKs). HARQ is a well-known technique to those of ordinary skill in the art, wherein for accuracy, the integrity of a packet transmission may be checked on the receiving side, for example, using any suitable integrity check mechanism, such as a checksum (checksum) or Cyclic Redundancy Check (CRC). If the integrity of the transmission is acknowledged, an ACK may be transmitted, and if not acknowledged, a NACK may be transmitted. In response to the NACK, the transmitting device may send HARQ retransmissions, which may enable chase combining, incremental redundancy, and so on.

In UL transmissions (e.g., over the Uu interface), a transmitting device (e.g., a scheduled entity) may utilize one or more REs 306 to carry UL control information to the scheduling entity, including one or more UL control channels, such as a Physical Uplink Control Channel (PUCCH). UL control information may include various packet types and categories including pilot, reference signals, and information configured to enable or assist in decoding uplink data transmissions. For example, UL control information may include DMRS or SRS. In some examples, the control information may include a Scheduling Request (SR), i.e., a request for a scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted on the control channel, the scheduling entity may transmit downlink control information, which may schedule resources for uplink packet transmission. UL control information may also include HARQ feedback, channel State Feedback (CSF), or any other suitable UL control information.

In addition to control information, one or more REs 306 (e.g., within data region 314) may also be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as on PDSCH for DL transmissions; or may be carried on a Physical Uplink Shared Channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 within the data region 314 may be configured to carry SIBs (e.g., SIB 1) that carry system information that may enable access to a given cell.

These physical channels are typically multiplexed and mapped to transport channels for handling by the Medium Access Control (MAC) layer. The transport channel carries blocks of information, which are called Transport Blocks (TBs). The Transport Block Size (TBS), which may correspond to the number of information bits, may be a controlled parameter based on the Modulation and Coding Scheme (MCS) and the number of RBs in a given transmission.

The channels or carriers described above with reference to fig. 1-3 are not necessarily all channels or carriers available between the scheduling entity and the scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

The 5G-NR network may further support Carrier Aggregation (CA) of component carriers transmitted from different cells and/or different Transmission Reception Points (TRPs) in a multi-cell transmission environment. Different TRPs may be associated with a single serving cell or multiple serving cells. In some aspects, the term component carrier may refer to a carrier frequency (or band of frequencies) used for communication within a cell.

Additionally, the 5G-NR utilizes Sounding Reference Signals (SRS) that are transmitted on the UL from the UE to the network, such as, for example, from the UE to a base station or a gNB. Further, triggered SRS or aperiodic SRS (a-SRS) may be used, where transmission of a-SRS resources is triggered by Downlink Control Information (DCI) transmitted from a network node, such as a base station or gNB, for example, on DL.

In some scenarios, the 3gpp 5g NR specification may provide SRS enhancements in which enhanced or non-scheduled DCIs (e.g., DCI formats 0_1 and 0_2) trigger a-SRS without scheduled data or CSI requests. It should be noted here that the term "non-scheduled DCI" as used herein may be defined as DCI that is not used to schedule transmission resources on UL or DL, but is used for other purposes such as flexible triggering of a-SRS and for power control as will be described herein. In other aspects, the term "non-scheduled DCI" may further encompass DCI configured to trigger only aperiodic SRS without scheduled data and without CSI request.

When non-scheduled DCI is used for the purpose of triggering an a-SRS without PUSCH and without CSI request, it should be noted that the bit field within the DCI (e.g., DCI format 0_1 or 0_2) may be diverted for enhancement of the a-SRS trigger and more specifically for functions in the UE such as Transmit Power Control (TPC) for transmission of SRS. For example, the TPC bit field for PUSCH may be diverted for SRS power control. Additionally, two power controls may be used for SRS transmission, either configured separately from PUSCH power control or configured identically to PUSCH power control.

It should also be noted that SRS power control (i.e., P) for setting the power of SRS transmission may be determined based on the following condition _SRS )：

Wherein power may be configured per SRS resource set. The SRS power control adjustment state is made for the active UL BWP b and SRS transmission occasion i of carrier f of the serving cell c. Additionally, there may be the same or separate adjustment states for PUSCH and SRS transmissions, and in case of the same adjustment states for PUSCH and SRS, at least two further first and second adjustment states indicated by l are equal to 0 or 1, respectively. Further, in case of the same SRS and PUSCH power control adjustment state, h _b,f,c The value of (i, l) is equal to f _b,f,c (i, l) wherein f _b,f,c (i, l) is the current PUSCH power control adjustment state. In the case of separate adjustment states between PUSCH and SRS transmissions, one closed loop index (i.e., one adjustment state) is defined for SRS only (i.e., no value of l in function h (no)). Thus, the first and second substrates are bonded together,wherein the value delta _SRSb,f,x (m) is for example jointly encoded with other TPC commands in the PDCCH with DCI format 2_3 (which is used for transmission of TPC command groups for SRS transmission by one or more UEs).

As mentioned above, the bit field within the non-scheduled DCI may be a reused or diverted bit field in the normal DCI. In particular, these fields may be diverted to indicate power control, such as SRS power control. As an example showing DCI format 0_1 and DCI format 0_2 bit fields, table 400 in fig. 4 illustrates various fields used within each of these DCI formats. By way of example only, non-zero fields highlighted in gray in fig. 4 may be candidates for reuse, such as non-zero DCI bit fields related to scheduling, including Modulation and Coding Scheme (MCS), new Data Indicator (NDI), redundancy Version (RV), HARQ process number, downlink Assignment Index (DAI), TPC commands for scheduled PUSCH, SRS Resource Indicator (SRI), and antenna port. It can be seen that DCI0_1 has more candidate bit fields (18 bits) than DCI format 0_2 (8 bits).

Fig. 5 illustrates a call flow diagram 500 that illustrates an example of scheduling SRS transmissions in a wireless communication system including a Base Station (BS) 502 and a UE504. In some examples, BS 502 may correspond to any of the base stations or scheduling entities shown in any of fig. 1, 2, and 11. In some examples, the UE504 may correspond to any of the UEs or scheduled entities shown in any of fig. 1, 2, and 13.

In step 506, the bs 502 may configure the UE for receiving SRS triggers employing non-scheduled DCI and for SRS transmission including TPC. For example, the BS 502 may send an RRC message to the UE504, wherein the RRC message specifies resources and other information to be used by the UE504 for SRS transmission. It should be noted that step 506 may be optional and that the UE may be preconfigured in some aspects.

In step 508 of fig. 5, bs 502 configures DCI (e.g., non-scheduled DCI) for SRS triggered transmission and may further include TPC information. For example, BS 502 may configure the non-scheduled DCI to include TPC for both PUSCH and SRS transmissions, which may also be the same or different, as will be discussed in more detail below.

In step 510, the bs 502 triggers SRS transmission by transmitting configured DCI to the UE504. In one example, the BS 502 may transmit the DCI configured in step 508 to the UE504 via the PDCCH.

In step 512, the ue 504 determines whether there are available slots for SRS transmission. Further, according to some examples, the UE may determine PUSCH and SRS transmit power commands (i.e., TPC) based on information within the received non-scheduled DCI. Further, as will be discussed later, the DCI may also include control or power adjustment status indications (e.g., the value of l as discussed above), and the power control is based at least in part on these status indications.

In step 514, the ue 504 transmits SRS transmissions on the set of scheduled SRS resources. Additionally, if PUSCH transmission is allocated, PUSCH transmission is also implemented, as shown at step 516.

In some aspects, the configured non-scheduled or "dummy" DCI as determined in step 508 may trigger two or more sets of a-SRS resources, which may have different power control configurations, one set configured to follow PUSCH and the other set configured to have separate power control. In the present 3GPP specifications, if separate Power Control (PC) is used, the only previously known method for closed loop Power Control (PC) of SRS is through a Group Common (GC) DCI format 2_3, which is used for transmission of TPC command groups for SRS transmission by one or more UEs.

Thus, the configuration for the non-scheduled DCI may include an indication of two (or more) TPC commands within the payload of the DCI. In one example, a first TPC command of the two or more TPC commands may be for PUSCH (δ _PUSCH ) And (5) controlling power. The command may be applied to both the triggered a-SRS with the same power control as PUSCH and all future granted PUSCHs. At least one other second TPC command in the non-scheduled DCI is used for SRS (delta _SRS ) And (5) controlling power. This may be applied to the triggered a-SRS resource set(s) with power control separate from PUSCH power control. The second TPC bit field may be introduced by diverting some of the unused bit fields. In a further aspect, the base station may introduce a new RRC parameter indicating whether the non-scheduled DCI contains an additional second TPC command for the SRS with separate power control. As an example, the RRC signaling/configuration may correspond to step 508 in fig. 5.

As will be described below, one aspect relates to whether the non-scheduled or dummy DCI includes TPC commands. In an aspect, higher layer parameters and/or other RRC signaling/configuration may enable the UE to determine whether the non-scheduled DCI includes TPC commands for the a-SRS resource set. Further, if the UE determines that the DCI includes TPC, the DCI may include a single TPC command or a plurality of TPC commands. In the case of two TPC commands, one may be used for PUSCH power control and the other may be used for SRS power control, as examples. If there is a single TPC command in the non-scheduled DCI, the UE may be configured to know whether the TPC command is PUSCH or SRS power control.

As an example of a non-scheduled DCI format, fig. 6 illustrates one example of DCI600 configured with TPC commands or information for both PUSCH and SRS. As shown, DCI600 may be configured to include a first TPC command or command field 602 for PUSCH. Additionally, other used bits fields 604 are shown in DCI 600. Further, the DCI600 includes a second TPC command, command field or information 606, which may be placed in an unused bit field or a bit field that is diverted to the non-scheduled DCI 600. Additionally, DCI600 may include other unused bit fields, as shown at 608.

In some particular aspects, DCI600 may be configured as non-scheduled DCI format 0_1 or non-scheduled DCI format 0_2. In another aspect, the value delta _SRSb,f,c (m) indicated in non-scheduled DCI format 0_1 or non-scheduled DCI format 0_2. In a further aspect, the TPC command field (e.g., 602 or 606) to the non-scheduled DCI format 0_1 or the non-scheduled DCI format 0_2 to the cumulative δ _SRSb,f,c Or delta _PUSCHb,f,c Value or absolute delta _SRSb,f,c Or delta _PUSCHb,f,c The mapping of values may follow table 1 below.

TABLE 1

In some other aspects, when SRS is triggered using non-scheduled DCI, may be δ _SRSb,f,c A separate table is configured with a look-up or greater power adjustment in dB values. An example is shown in table 2 below.

TPC command field	Cumulative delta SRS,b,f,c [dB]	Absolute delta SRS,b,f,c [dB]
			0	-2	-6
1	0	-2
			2	2	2
3	4	6

TABLE 2

Regarding the multiple power control adjustment states, it should be noted that the 3GPP standard does not consider separating SRS power control from PUSCH power control (in particular regarding closed loop power control adjustment states), while only two separate closed loop adjustment states for SRS are allowed. Two closed loop adjustment states are typically only possible for SRS when they are shared with PUSCH closed loop power control adjustment states (and if PUSCH is configured with "two PUSCH-PC-adjustment states" parameters). Nonetheless, for SRS resource sets with power control separate from PUSCH power control, it is possible to have two power control adjustment states. In such a case, the network configures "two SRS-PC-adjustment states" parameters for UL Component Carriers (CCs), where the SRS resource set is configured to:

wherein item h _b,c,f (i-i ₀ L) is for SRS transmission occasion (i-i) with adjustment state l ₀ ) Is a cumulative of TPC commands and termsIs from the transmission opportunity (i-i) for SRS power control adjustment state/ ₀ ) The sum of the new TPC command values (in DCIs 2_3) from now on.

It should be further noted that DCI may trigger multiple SRS resource sets configured with at least four different PC adjustment states. The first state is where the PC adjustment state for SRS is the same as PUSCH with adjustment state l=0. The second state is where the PC adjustment state is the same as PUSCH with adjustment state l=1. The third state is where the PC adjustment state is separate from the PUSCH PC with adjustment state l=0. Finally, the fourth adjustment state is where the PC adjustment state is separate from the PUSCH PC with adjustment state l=1. If the DCI is configured to carry two TPC commands (e.g., with PUSCH delta _PUSCH Same and separate delta _SRS ) Then whether the TPC command applies to the first adjustment state or the second adjustment state, the 3GPP has specified that for scheduling DCI, the SRI bit field is used to indicate the adjustment state and that for GC-DCI format 2-2, the l value is explicitly indicated. For non-scheduled DCI, the SRI bit field may be reversed. Thus, an indication of the adjustment state needs to be indicated. Specifically, as known from 3GPP, if the UE is provided with SRI-PUSCH-PowerControl (SRI-PUSCH-power control), the UE obtains a mapping between a set of values of an SRI field in the form of DCI scheduling PUSCH transmission of an l value (or l values) provided by SRI-PUSCH-closed loop index (SRI-PUSCH-closed loop index), and determines an l value mapped to the SRI field value. If PUSCH transmission is scheduled by a DCI format that does not include an SRI field, or if SRI-PUSCH-PowerControl is not provided to the UE, l=0. Furthermore, if the UE obtains the information from DCI format 2_2 with the TPC-PUSCH-RNTI addedOne TPC command for the scrambled CRC, the value of l is provided by the closed loop indicator field with DCI format 2_2.

In view of the above, when there are multiple TPC commands and states that may be configured in non-scheduled DC, there may be several different scenarios or configurations to determine or indicate the power adjustment state for SRS TPC. For the case where the SRI bit field in the non-scheduled DCI is not reused or diverted for other functionality, several options are possible. In one option, the DCI may be configured to follow current 3GPP specifications for determining a power adjustment state (based on SRI) for PUSCH TPC commands.

On the other hand, to determine and/or indicate a power state for SRS TPC, in one option, the power state may be explicitly indicated in the non-scheduled DCI. For example, the explicit indication may utilize a one-bit-converted bit field in the DCI as the indication. As an example of this configuration, fig. 7A shows a configured non-scheduled DCI 710 in which a TPC SRS power adjustment state is indicated. Specifically, fig. 7A illustrates DCI 710 with used bit fields 712 (including SRI and SRS requests). Additionally, a TPC command bit field 714 for PUSCH is included. Further, DCI 710 includes TPC command bit field 716 for SRS. In this example, DCI 710 also includes an explicit indication of power adjustment state/in a single-bit field 718. Additionally, DCI 710 may include other unused bits/bit fields 720.

In another option, for l=0 and l=1, two SRS TPC commands may be explicitly indicated. As an example, fig. 7B shows a configured non-scheduled DCI730 in which a TPC SRS power adjustment state is indicated. Specifically, fig. 7B illustrates DCI 732 with used bit fields 730 (including SRI and SRS requests). Additionally, a TPC command bit field 734 for PUSCH is included. Further, DCI730 includes two TPC command bit fields for each respective power adjustment state for SRS TPC. In this example, DCI730 includes an explicit indication of power adjustment state l=0 in bit field 736. Additionally, DCI730 includes an explicit indication of power adjustment state l=1 in second bit field 738. DCI730 may include other unused bits/bit fields as shown at 740.

In yet another option for indicating a power state, the SRS request bit field may implicitly indicate a power state. In one example of this indication, for a triggered SRS resource set with multiple trigger states, one trigger state is marked (e.g., by RRC) as an indicator of which state the TPC command applies to. In another alternative, if all triggered sets are configured with the same adjustment state (such as l=0 (or l=1)), TPC commands are applied to the state l=0 (or l=1).

In yet another alternative, the determination or indication of the power adjustment state may be made according to other predetermined rules. For example, in one alternative, the TPC command may be predetermined to be applied to both states. In another example, TPC commands may be applied to states having a greater number of triggered SRS resource sets. For example, in the case of a total of five triggered sets having two triggered SRS resource sets configured with l=0 and three triggered SRS resource sets configured with l=1, TPC will map to state l=1, which has a greater number of SRS resource sets. In yet another example, the TPC command is applied to the power adjustment state corresponding to the SRS resource set with the largest/smallest set ID.

Fig. 7C illustrates an exemplary DCI configuration for the implicit indication scenario discussed above. As shown, DCI 750 includes a used bits field 752 that includes SRI and SRS requests. Additionally, a TPC command bit field 754 for PUSCH is included. Further, DCI 750 includes TPC command bit field 756 without explicit indication of a power adjustment state. DCI 750 may include other unused bits/bit fields, as indicated at 758. It should be noted that both examples illustrated by fig. 7C implicitly indicate the power adjustment state apply to the scheduled DCI format with added TPC commands for SRS. In some scenarios, if the non-scheduled DCI does not indicate which power state, the TPC command may have a default state (l=0).

In another scenario in which multiple TPC commands and states are indicated in the non-scheduled DCI, the SRI bit field may be diverted for other functionality. In this case, the determination of the power state for SRS TPC may follow the examples discussed above in connection with fig. 7A-7C, and are not repeated here. However, various options are also possible for determining the power state for PUSCH TPC commands. In a first option, the power state for PUSCH TPC may be indicated explicitly in the DCI. As an example, fig. 8A shows this option with DCI 810. The DCI 810 includes a used bits field 812 that includes an SRS request but does not include an SRI. Additionally, DCI 810 includes TPC commands 814 for PUSCH. Furthermore, an explicit indication of the adjustment power state l is provided in a single bit field 816, which may be a bit field that is toggled with one bit. Additionally, other bit fields 818 are shown and may include TPC commands for the SRS, as discussed, for example, with respect to fig. 7A-7C.

In another option, two TPC commands for different PUSCH power states may be indicated in the DCI. As an example, fig. 8B shows DCI 830 including used bit fields 832, which used bit fields 832 include SRS requests but do not include SRIs. Additionally, DCI 830 includes a first TPC command 834 to adjust power state l=0 for an indication of PUSCH. Further, an explicit indication of the adjusted power state l=1 is provided in the second TPC command in bit field 836. Additionally, other bit fields 838 are shown and may include TPC commands for the SRS, as discussed, for example, with respect to fig. 7A-7C.

In another option, two TPC commands for different PUSCH power states may be indicated in the DCI. As an example, fig. 8B shows DCI 830 including used bit fields 832, which used bit fields 832 include SRS requests but do not include SRIs. Additionally, DCI 830 includes a first TPC command 834 to adjust power state l=0 for an indication of PUSCH. Further, an explicit indication of the adjusted power state l=1 is provided in the second TPC command in bit field 836. Additionally, other bit fields 838 are shown and may include TPC commands for the SRS, as discussed, for example, with respect to fig. 7A-7C.

In yet another option, in which the SRI bit field may be diverted, the power state for PUSCH TPC may be implicitly indicated by a pre-configuration, a pre-determination, or some other a priori configuration at the base station and/or UE. As an illustration of this scenario, fig. 8C shows DCI 850 including used bit fields 832, which used bit fields 832 include SRS requests but do not include SRIs. Additionally, the DCI 850 includes TPC commands 854 for PUSCH. In some examples, PUSCH TPC commands are applied to the default power state (e.g., l=0). The presence of bit field 854 or its position in DCI 850 may, for example, implicitly indicate a power adjustment state for PUSCH TPC. Additionally, other bit fields 856 are shown and may include TPC commands for the SRS, as discussed, for example, with respect to fig. 7A-7C.

It should be further noted that the non-scheduled DCI may be configured to trigger the a-SRS for a group or set of Component Carriers (CCs), such as in a Carrier Aggregation (CA) scenario. Here, a DCI bit field (e.g., CIF or some other diverted bit field) may be configured to indicate which CC set is triggered. The DCI payload may contain a plurality of TPC commands for each CC within the CC set. The CC may be configured with PUSCH (e.g., SRS PC may be the same as PUSCH or separate). Otherwise, if PUSCH is not configured, SRS has separate power control. Thus, in an aspect, triggering an a-SRS by a non-scheduled DCI (e.g., DCI format 0_1 or DCI format 0_2) on a group of CCs (i.e., a set of CCs) may be configured to indicate one or more TPC commands per each CC in the set of CCs. In a further aspect, if the CC is not configured with PUSCH, a single TPC command may be indicated. It should be noted here that in the case where two power adjustment states are configured, then a similar rule as discussed in connection with fig. 7A-7C may be followed to determine a power state adjustment value (e.g., l=0 or 1). If the CC is configured with PUSCH, two TPC commands may be indicated; i.e. one for PUSCH and the other for SRS. Again, rules similar to those discussed above in connection with fig. 7A-7C or fig. 8A-8C may be used to determine the power adjustment state.

In other aspects, it should be noted that the UE may be configured with TPC power accumulation, where TPC commands received from the base station are accumulated, as mentioned above. In the case when the UE receives a non-scheduled or "dummy" DCI indicating both an SRS TPC command and a trigger a-SRS resource set at a certain time (e.g., t=3 indicates SRS transmission in the fourth UL slot or time instance from zero to 3), the UE may receive DCI with a UL grant and another TPC command for PUSCH TPC in an intermediate period as an example. As an illustration of this scenario, fig. 9A shows a time flow diagram 900 of several DL slots/symbols (D), flexible slots/symbols (S), and UL slots/symbols (U). In this example, non-scheduled trigger DCI902 is received by a UE during a downlink slot/symbol 904. The trigger DCI902 schedules transmission of SRS resource set 906 in a future UL slot/symbol 908. In this example, the slot/symbol may be at time or symbol/slot number of t=3 as the fourth UL slot, but this is exemplary and not limited thereto.

At this intermediate time, the UE may receive another trigger DCI910 during a downlink slot/symbol 912. In this example, DCI910 may include UL grant and PUSCH TPC commands. Thus, in the case of TPC power accumulation, the UE has two options-either to continue TPC accumulation or to ignore TPC commands received between the non-scheduled trigger DCI and SRS transmission. Thus, in one configuration, the UE may be configured to disregard TPC commands in received intermediate DCI such as DCI910 (or multiple DCIs received in the period between DCI902 and SRS 906). In another configuration, the UE may continue TPC accumulation from the time the DCI902 is triggered to the time instance of the SRS transmission 906.

Fig. 9B illustrates another timeline 920 that shows another example of SRS transmission with separate power control. In this example, DCI 922 is a trigger DCI in slot/symbol 924 that includes TPC commands for SRS transmission 926 in a subsequent UL slot/symbol 928. In this example, prior to SRS transmission 926 during slot/symbol 928, the UE may receive another non-scheduled DCI 930 indicating another TPC command for the SRS transmission. Thus, in the case of TPC power accumulation, the UE has two options-either (1) continue TPC accumulation, or (2) ignore SRS TPC commands received in the second non-scheduled DCI 930.

It should be further noted that in the case of TPC accumulation for non-scheduled DCI, it should be noted that if SRS-powercontrol adjustment states indicate individual power control adjustments and the UE is configured with higher layer parameters 'srsceossedloopoweradjustment' using non-scheduled DCI, then the update of the power control adjustment state for SRS transmission occasion i may occur at SRS resource set q _s At the beginning of each SRS resource; otherwise, the updating of the power control adjustment state for SRS transmission opportunity i occurs in SRS resource set q _s At the beginning of the first transmitted SRS resource.

Further, regarding the SRS power control timeline, it should be noted that the relationship

The UE is on SRS transmission occasion i-i on active UL BWP b representing carrier f of serving cell c for SRS power control adjustment state ₀ Previous K _SRS (i-i ₀ ) -1 symbol and K preceding SRS transmission occasion i _SRS (i) Received between symbols having radix C (S _i ) TPC command value set S of (2) _i The sum of TPC command values in (i), where i ₀ >0 is the SRS transmission occasion i-i for it ₀ Previous K _SRS (ii-i ₀ ) The code element is earlier than K before SRS transmission time i _SRS (i) The smallest integer of the individual symbols. If the SRS transmission is aperiodic (i.e., A-SRS), then K _SRS (i) Is the number of symbols of active UL BWP b for carrier f of serving cell c after the last symbol of the corresponding PDCCH triggering SRS transmission and before the first symbol of SRS transmission.

In a further aspect, it should be noted that SRS TPC may be configured to power up (or power back-off or power down) instantaneously or once. For example, fig. 10 illustrates a scenario in which SRS-TPC commands 1002 at a slot/symbol 1004 are considered as one-time power adjustment over closed loop power control only for a corresponding triggered SRS transmission, as shown at 1006.

In the example or scenario of fig. 10, the set of resources for one-time power adjustment may be configured in at least several ways. According to the first scenario, the resource set may be configured with PUSCH→f _b,, (i,l)+δ _SRS The same PC state. In a second scenario, the resource set may be configured with a separate PC state h _b,, (i,l)+δ _SRS Independent of the PC state of PUSCH.

Fig. 11 is a block diagram conceptually illustrating an example of a hardware implementation of a network entity or node 1100 employing a processing system 1114, in accordance with some aspects of the present disclosure. According to various aspects of the disclosure, an element, or any portion of an element, or any combination of elements, may be implemented with a processing system 1114 that includes one or more processors 1104. In some implementations, the network node 1100 may correspond to any of the BSs (e.g., gnbs, enbs, etc.) or scheduling entities shown in any of fig. 1 and 2. In a further aspect, the network entity or node 1100 may be configured as a base station operable within an open RAN (O-RAN) environment, wherein the base station (e.g., 1100) is split and includes different parts including a Distributed Unit (DU), a Centralized Unit (CU), and a Radio Unit (RU). In yet further aspects, the processing portions of the disclosed and illustrated network entity 1100 may be implemented within RU, DU, and/or CU, or within portions of each.

Network node 1100 may be implemented with a processing system 1114 that includes one or more processors 1104. Examples of processor 1104 include microprocessors, microcontrollers, digital Signal Processors (DSPs), field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, network node 1100 may be configured to perform any one or more of the functions described herein. That is, the processor 1104 as utilized in the network node 1100 may be used to implement any one or more of the processes and procedures described herein.

In this example, the processing system 1114 may be implemented with a bus architecture, represented generally by the bus 1102. Bus 1102 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1114 and the overall design constraints. Bus 1102 communicatively couples various circuitry including one or more processors (represented generally by processor 1104), memory 1105, and computer-readable media (represented generally by computer-readable media 1106). Bus 1102 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. Bus interface 1108 provides an interface between bus 1102 and transceiver 1110, and between bus 1102 and interface 1130. The transceiver 1110 provides a communication interface or means for communicating with various other apparatus over a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1110, each configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial). At least one interface 1130 (e.g., a network interface and/or a user interface) provides a communication interface or means for communicating with various other apparatus and devices (e.g., other devices housed within the same apparatus as network node 1100 or an external apparatus) over an internal bus or external transmission medium, such as an ethernet cable.

The processor 1104 is responsible for managing the bus 1102 and general processing, including the execution of software stored on the computer-readable medium 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described infra for any particular apparatus. The computer-readable medium 1106 and the memory 1105 may also be used for storing data that is manipulated by the processor 1104 when executing software.

One or more processors 1104 in a processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether described in software, firmware, middleware, microcode, hardware description language, or other terminology. The software may reside on a computer readable medium 1106.

Computer-readable medium 1106 may be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact Disk (CD) or Digital Versatile Disk (DVD)), smart cards, flash memory devices (e.g., card, stick, or key drive), random Access Memory (RAM), read Only Memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), registers, removable disk, and any other suitable medium for storing software and/or instructions that can be accessed and read by a computer. The computer-readable medium 1106 may reside in the processing system 1114, outside the processing system 1114, or distributed across multiple entities comprising the processing system 1114. The computer-readable medium 1106 may be implemented in a computer program product. By way of example, a computer program product may include a computer readable medium in an encapsulating material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and overall design constraints imposed on the overall system.

UE 1100 may be configured to perform any one or more of the operations described herein (e.g., as described above in connection with fig. 1-10 and as described below in connection with fig. 12). In some aspects of the disclosure, the processor 1104 as utilized in the network node 1100 may include circuitry configured for various functions.

The processor 1104 may be configured to generate, schedule, and modify resource assignments or grants for time-frequency resources (e.g., a set of one or more resource elements). For example, processor 1104 may schedule time-frequency resources within a plurality of time-division duplex (TDD) and/or frequency-division duplex (FDD) subframes, slots, and/or mini-slots to carry user data traffic and/or control information to and/or from a plurality of UEs.

The processor 1104 may be configured to: resources are scheduled for transmission of downlink reference signals (e.g., SSBs or CSI-RSs) or DCI (or SRS triggers) on multiple downlink beams for a downlink beam sweep according to the selected downlink beam sweep type and the number of selected downlink reference signal resources indicated in an uplink beam refinement request received from the UE. The processor 1104 may be further configured to: resources are scheduled for uplink transmission of uplink reference signals (e.g., SRS) on a plurality of uplink beams of an uplink beam sweep according to the selected beam sweep type and the number of selected uplink reference signal resources indicated in the request. The processor 1104 may be further configured to schedule resources that the UE may use to transmit the request. For example, the uplink beam refinement request resources may include resources scheduled for transmission of PUCCH, PUSCH, physical Random Access Channel (PRACH) occasion, or RRC message. In some examples, the processor 1104 may be configured to schedule PUSCH resources for uplink beam refinement requests in response to receiving a scheduling request from a UE.

The processor 1104 may be further configured to schedule resources for transmission of the uplink signals. In some examples, based on an indication of an uplink signal associated with one or more uplink transmit beams included in the request, the resource may be associated with one or more uplink transmit beams and one or more corresponding receive beams applied to the uplink signal (e.g., based on uplink BPL). In some examples, the resource may be associated with a multiplexing scheme that indicates a number of uplink transmit beams to be used for an uplink signal, a number of repetitions of each uplink transmit beam for the uplink signal, and when more than one uplink transmit beam is used to transmit the uplink signal.

The processor 1104 may include communication and processing circuitry 1141. The communication and processing circuitry 1141 may include one or more hardware components that provide physical structure to perform various processes related to wireless communication (e.g., signal reception and/or signal transmission) as described herein. The communication and processing circuitry 1141 may further include one or more hardware components that provide physical structure to perform various processes related to signal processing (e.g., processing received signals and/or processing signals for transmission) as described herein. In some examples, communication and processing circuitry 1141 may include two or more transmit/receive chains. The communication and processing circuitry 1141 may be further configured to execute the communication and processing software 1151 included on the computer readable medium 1106 to implement one or more functions described herein.

In some examples, communication and processing circuitry 1141 may be configured to trigger the a-SRS in the UE via transceiver 1110 and antenna array 1120 (such as through DCI in the PDCCH). Further, the communication and processing circuitry 1141 may be configured to receive uplink a-SRS signals from a UE and process the uplink a-SRS signals received from the UE.

In some other examples, the communication and processing circuitry 1141 may be configured to communicate higher layer information (such as RRC configuration information) to the UE. For example, the communication and processing circuitry 1141 may communicate RRC parameters to the UE indicating whether the transmitted non-scheduled DCI will include additional TPC for SRS power control and further indicating, for example, whether the power control is separate from PUSCH power control. Other higher layer information that may be determined and transmitted using the communication and processing circuitry 1141 may include RRC information indicating, for a triggered SRS resource set having multiple trigger states, one trigger state is marked as an indicator of which power adjustment state the TPC command applies to.

Processor 1104 may also include DCI configuration circuitry 1142 configured to configure, construct, or determine a non-scheduled DCI structure to be transmitted to the UE for triggering the SRS resource set(s). The circuitry 1142 may be configured to configure the non-scheduled DCI to include TPC commands for an a-SRS to be transmitted to the UE, and TPC commands for a PUSCH, such as shown in fig. 6, for example. Additionally, circuitry 1142 may be configured to construct the non-scheduled DCI to include power adjustment status information, indications, or values as discussed, for example, in connection with fig. 7A-7C or fig. 8A-8C. Additionally, DCI configuration circuitry 1142 may be configured to decide which bit fields in the non-scheduled DCI to be diverted or reused for communicating TPC commands and power adjustment states to the UE. Further, DCI configuration circuitry 1142 may be configured to operate according to various processes disclosed herein in connection with fig. 5-10 and 12. DCI configuration circuitry 1142 may be further configured to execute DCI configuration circuitry software 1152 included on computer-readable medium 1106 to implement one or more functions described herein.

In some further examples, processor 1104 may also include TPC status indication circuitry 1143 configured to assist DCI configuration circuitry 1142 to indicate a power adjustment status for TPC commands for SRS or PUSCH. In aspects, TPC status indication circuitry 1143 may include determining whether the DCI is configured to explicitly include power adjustment status information, such as discussed in connection with fig. 7A, 7B, 8A, or 8B. The TPC status indication circuitry 1143 may be further configured to execute TPC status indication software 1153 included on the computer readable medium 1106 to implement one or more functions described herein.

Fig. 12 is a flow chart illustrating an example wireless communication method 1200 in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method 1200 may be performed by the network node 1100 (e.g., a gNB or base station) illustrated in fig. 11. In some examples, the method 1200 may be performed by any suitable apparatus or device for implementing the functions or algorithms described below.

At block 1202, method 1200 includes configuring Downlink Control Information (DCI) to include a plurality of Transmit Power Control (TPC) commands. The TPC commands in the DCI include a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH) and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets. In an aspect, the processing of block 1202 may be implemented by means for configuring the DCI, which may be implemented by processor 1104 and in particular aspects by DCI configuration circuitry 1142 or its equivalent.

Additionally, the method 1200 includes transmitting the DCI to at least one User Equipment (UE) for triggering an SRS, as shown in block 1204. The DCI may be configured as non-scheduled DCI configured to trigger the one or more SRS sets. Additionally, the method 1200 may include: at least a second TPC command is placed in the reused bit fields of the non-scheduled DCI, wherein the reused bit fields include one or more bit fields configured in the scheduled DCI for scheduling transmission resources.

In other aspects, it should be noted that method 1200 may be applied to scenarios in which the one or more SRS sets are aperiodic SRS sets triggered by the DCI. Further, the first TPC command may be independent of the second TPC command or may be the same power control for each of the PUSCH and the one or more SRS resource sets. Further, the first TPC command and the second TPC command may implement different power control for each of the respective PUSCH and the one or more SRS resource sets. In other aspects, the DCI is formatted according to DCI format 0_1 or DCI format 0_2.

In yet other aspects, the method 1200 may further comprise: the DCI includes an indication of a power adjustment state for a second TPC command configured for power control of the one or more SRS resource sets. In some examples, the indication of the power adjustment state includes at least one bit in the DCI that indicates one of two power adjustment states, such as illustrated in fig. 7A, for example. In other aspects, the DCI may be configured to include a second TPC command including a first bit field having the second TPC command and a first power adjustment state and a second bit field having the second TPC command and a second power adjustment state, such as illustrated, for example, in fig. 7B.

The method 1200 may further include: the indication includes signaling or configuration communicated by the base station to the UE configured to allow the UE to derive the power adjustment state based on characteristics of the second TPC command in the DCI. In one example, the characteristics of the second TPC command include: for a triggered SRS resource set having a plurality of trigger states, one of the plurality of trigger states is designated as an indication for conveying to which of the two power adjustment state indicators the TPC command applies. In another example, the characteristics of the second TPC command include: for a plurality of triggered SRS resource sets, a configuration in which all of the plurality of triggered sets are configured with the same power adjustment state indicates that the second TPC command applies to the same power adjustment state. In yet another example, the indication includes signaling or configuration communicated to the UE to allow the UE to derive the power adjustment state based on at least one predetermined condition or setting. Further, the at least one predetermined condition or setting comprises a predetermined regarding that the second TPC command is applicable to both of the two available power adjustment states. In another aspect, the second TPC command may be applicable to a default power state adjustment (i.e., the default power state of the UE itself is adjusted or modified, or alternatively, the default power state is adjusted to some new value for TPC).

In other aspects, method 1600 may include: the at least one predetermined condition or setting includes applying a second TPC command having a power adjustment state associated with a power adjustment state corresponding to a greater or lesser number of sets of triggered SRS resources among the plurality of sets of triggered SRS resources. Further, the at least one predetermined condition or setting includes applying a second TPC command having a power adjustment state associated with the power adjustment state corresponding to a larger or smaller triggered SRS resource set identifier (set ID) of the plurality of triggered SRS resource sets. In one example, the DCI includes an SRS Resource Indicator (SRI) bit field (i.e., the bit field is not diverted). In yet other aspects, the method 1200 includes: the DCI includes a power adjustment status indication for the first TPC command without including an SRS Resource Indicator (SRI) (i.e., the SRI bit field has been reused or diverted).

In other aspects of method 1200, the power adjustment status indication further comprises: the DCI is configured to include a first TPC command including a first bit field having the first TPC command and a first power adjustment state and a second bit field having the first TPC command and a second power adjustment state. In other aspects, the power adjustment state indication includes signaling or configuration communicated by the base station to the UE that is configured to allow the UE to derive the power adjustment state based on characteristics of the first TPC command in the DCI.

In still other aspects, method 1600 may include: the DCI is further configured to indicate one or more TPC commands for each Component Carrier (CC) in a set of CCs. In a further example, the first TPC command is not included in the DCI when the CC is not configured with the PUSCH.

Fig. 13 is a block diagram conceptually illustrating an example of a hardware implementation of a User Equipment (UE) employing a processing system 1314, in accordance with some aspects of the present disclosure. According to various aspects of the disclosure, an element, or any portion of an element, or any combination of elements, may be implemented with a processing system 1314 including one or more processors 1304. In some implementations, the UE 1300 may correspond to any of the UEs or scheduling entities shown in any of fig. 1 and 2.

The UE 1300 may be implemented with a processing system 1314 including one or more processors 1304. Examples of processor 1304 include microprocessors, microcontrollers, digital Signal Processors (DSPs), field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, UE 1300 may be configured to perform any one or more of the functions described herein. That is, the processor 1304 as utilized in the UE 1300 may be utilized to implement any one or more of the processes and procedures described below.

In this example, the processing system 1314 may be implemented with a bus architecture, represented generally by the bus 1302. The bus 1302 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1314 and the overall design constraints. The bus 1302 communicatively couples various circuitry including one or more processors (represented generally by the processor 1304), memory 1305, and computer-readable media (represented generally by the computer-readable media 1306). The bus 1302 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. Bus interface 1308 provides an interface between bus 1302 and transceiver 1310, and between bus 1302 and interface 1330. The transceiver 1310 provides a communication interface or means for communicating with various other apparatus over a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1310, each configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial). At least one interface 1330 (e.g., a network interface and/or a user interface) provides a communication interface or means to communicate with various other apparatuses and devices (e.g., other devices housed within the same apparatus as UE 1300 or an external apparatus) over an internal bus or via an external transmission medium, such as an ethernet cable.

The processor 1304 is responsible for managing the bus 1202 and general processing, including the execution of software stored on the computer-readable medium 1306. The software, when executed by the processor 1304, causes the processing system 1314 to perform the various functions described infra for any particular apparatus. The computer-readable medium 1306 and memory 1305 may also be used for storing data that is manipulated by the processor 1304 when executing software.

One or more processors 1304 in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether described in software, firmware, middleware, microcode, hardware description language, or other terminology. The software may reside on a computer readable medium 1306.

Computer-readable medium 1306 may be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact Disk (CD) or Digital Versatile Disk (DVD)), smart cards, flash memory devices (e.g., card, stick, or key drive), random Access Memory (RAM), read Only Memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), registers, removable disk, and any other suitable medium for storing software and/or instructions that can be accessed and read by a computer. The computer-readable medium 1306 may reside in the processing system 1314, external to the processing system 1314, or distributed across multiple entities including the processing system 1314. The computer readable medium 1306 may be implemented in a computer program product. By way of example, a computer program product may include a computer readable medium in an encapsulating material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and overall design constraints imposed on the overall system.

The UE 1300 may be configured to perform any one or more of the operations described herein (e.g., as described above in connection with fig. 5-10 and as described below in connection with fig. 14 or 15). In some aspects of the disclosure, the processor 1304 as utilized in the UE 1300 may include circuitry configured for various functions.

The processor 1304 may be configured to generate, schedule, and modify resource assignments or grants for time-frequency resources (e.g., a set of one or more resource elements). For example, the processor 1304 may schedule time-frequency resources within a plurality of Time Division Duplex (TDD) and/or Frequency Division Duplex (FDD) subframes, slots, and/or mini-slots to carry user data traffic and/or control information to and/or from a plurality of UEs.

The processor 1304 may be configured to schedule resources for reception of downlink reference signals (e.g., SSB, DCI, or CSI-RS) on a plurality of downlink beams of a downlink beam sweep according to a selected downlink beam sweep type and a number of selected downlink reference signal resources indicated in an uplink beam refinement request received from a UE. The processor 1304 may be further configured to: resources are scheduled and transmitted for uplink transmission of uplink reference signals (e.g., in response to SRS or a-SRS triggering DCI and slot offset configuration, as disclosed herein) on multiple uplink beams of an uplink beam sweep according to the selected beam sweep type and the number of selected uplink reference signal resources indicated in the request. The processor 1304 may be further configured to schedule resources that the UE may use to transmit the request. For example, the uplink beam refinement request resources may include resources scheduled for PUCCH, PUSCH, PRACH occasion or transmission of RRC messages. In some examples, the processor 1104 may be configured to schedule PUSCH resources for uplink beam refinement requests in response to transmitting a scheduling request to a network node (such as a gNB or base station).

The processor 1304 may be further configured to schedule resources for transmission of the uplink signal. In some examples, based on an indication of an uplink signal associated with one or more uplink transmit beams included in the request, resources may be associated with one or more uplink transmit beams and one or more corresponding receive beams applied to the uplink signal (e.g., based on uplink BPL). In some examples, the resource may be associated with a multiplexing scheme that indicates a number of uplink transmit beams to be used for an uplink signal, a number of repetitions of each uplink transmit beam for the uplink signal, and when more than one uplink transmit beam is used to transmit the uplink signal.

The processor 1304 may include communication and processing circuitry 1341. The communication and processing circuitry 1341 may include one or more hardware components that provide the physical structure to perform various processes related to wireless communication (e.g., signal reception and/or signal transmission) as described herein. The communication and processing circuitry 1341 may further include one or more hardware components that provide the physical structure to perform various processes related to signal processing (e.g., processing received signals and/or processing signals for transmission) as described herein. In some examples, the communication and processing circuitry 1341 may include two or more transmit/receive chains. The communication and processing circuitry 1341 may be further configured to execute the communication and processing software 1351 included on the computer-readable medium 1306 to implement one or more functions described herein.

In some examples, communication and processing circuitry 1341 may be configured to receive downlink beamformed signals at millimeter wave frequencies or sub-6 GHz frequencies via transceiver 1310 and antenna array 1320. For example, the communication and processing circuitry 1341 may be configured to receive PDCCH signals, including triggered, non-scheduled DCI for an a-SRS transmission, via at least one first antenna panel in the antenna array 1320 and the transceiver 1310.

The communication and processing circuitry 1341 may also be configured to receive RRC signaling at an upper layer. In one aspect, the communication and processing circuitry 1341 may receive and process this RRC layer signaling for implementing various TPC reception and power adjustment status indications, as discussed above in connection with fig. 5-10 and fig. 12. In a particular aspect, DCI configuration and power adjustment status information including predetermined configurations used to implement various aspects may be stored in memory 1305 as represented by DCI/power adjustment status configuration information 1315. It should be noted herein that in some implementations, at least a portion of configuration 1315 may be pre-stored or pre-defined, and not derived from RRC signaling, according to some aspects, or derived from RRC signaling alone in other aspects.

The processor 1304 also includes TPC command reception circuitry 1342, the TPC command reception circuitry 1342 being configured to receive various non-scheduled DCI configurations as discussed herein, including receiving SRS and/or PUSCH TPC commands in the non-scheduled DCI. TPC command receiving circuitry 1342 may include functionality for determining, decoding, or obtaining power adjustment state information as discussed herein. In an aspect, TPC command reception circuitry 1342 may derive power adjustment state information from the received DCI, or infer the power adjustment state information from RRC signaling configuration or from information stored in memory information 1315. The TPC command reception circuitry 1342 may be further configured to execute TPC command reception software 1352 included on the computer-readable medium 1306 to implement one or more functions described herein.

The processor 1304 also includes TPC accumulation circuitry 1343, the TPC accumulation circuitry 1343 being configured to determine whether to accumulate TPC commands in the scheduled DCI received between receipt of the non-scheduled DCI and a transmission time of the SRS resource set, such as discussed above in connection with fig. 9. Additionally, TPC accumulation circuitry 1343 may be further configured to determine whether the SRS TPC command in the non-scheduled DCI is a one-time power adjustment and also decide whether the SRS resource set is to be configured with the same power control state as PUSCH or with a separate power control state, as an example, as discussed above in connection with fig. 10. The TPC accumulation circuitry 1343 may be configured to execute TPC accumulation software 1353 included on the computer-readable medium 1306 to implement one or more of the functions described herein.

Fig. 14 is a flow chart illustrating an example wireless communication method 1400 in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method 1400 may be performed by the UE 1300 illustrated in fig. 13. In some examples, the method 1400 may be performed by any suitable apparatus or device for implementing the functions or algorithms described below.

At block 1402, the ue may process Downlink Control Information (DCI) received from a network entity, the downlink control information configured to include a plurality of Transmit Power Control (TPC) commands, wherein a first TPC command of the plurality of TPC commands is configured for power control of a Physical Uplink Shared Channel (PUSCH) and a second TPC command of the plurality of TPC commands is configured for power control of one or more Sounding Reference Signal (SRS) resource sets. Further, the process in block 1402 may include non-scheduled, triggered DCI reception using an apparatus for receiving the DCI, which may be implemented by processor 1304, as shown in fig. 13, and circuitry 1341, circuitry 1342, and/or transceiver 1310, or equivalents thereof.

The method 1400 further includes the UE configuring resources for at least one of PUSCH transmission and SRS transmission based on the first or second TPC commands as indicated in block 1402. It should be noted that the processing in block 1402 may include reception using means for configuring SRS/PUSCH resources, which may be implemented by the processor 1304, as well as the circuitry 1341, the circuitry 1342, the circuitry 1343, the memory information 1315, and/or the transceiver 1310 shown in fig. 13, or equivalents thereof.

In some aspects, the DCI is non-scheduled DCI configured to trigger one or more SRS sets in the UE. In a further aspect, at least the second TPC command is placed in a reused bit field of the non-scheduled DCI, wherein the reused bit fields include one or more bit fields configured in the scheduled DCI for scheduling transmission resources. Further, the one or more SRS sets are aperiodic SRS sets triggered by the DCI. In other aspects, the first TPC command is independent of the second TPC command.

In yet other aspects, the method 1400 may include: the UE sets transmit powers of the PUSCH and SRS resource sets based on the first TPC command and the second TPC command, respectively, and then transmits the PUSCH and SRS resource sets, wherein the first TPC command and the second TPC command are configured to implement the same power control in the UE for each of the PUSCH and the one or more SRS resource sets. In other aspects, the method 1400 may include: the UE sets transmit power and transmits PUSCH and SRS resource sets based on the first TPC command and the second TPC command, respectively, wherein the first TPC command and the second TPC command are configured to implement different power control for each of the respective PUSCH and the one or more SRS resource sets.

In still other aspects, the method 1400 may include: the DCI further includes an indication of a power adjustment state for a second TPC command configured for power control of the one or more SRS resource sets, and the UE is configured to set transmit power of the one or more SRS resource sets based in part on the indicated power adjustment state.

In still other aspects, the method 1400 may include receiving Radio Resource Control (RRC) signaling. In this aspect, the RRC signaling may include one or more parameters to configure the UE to identify at least one of a TPC command for the PUSCH and a TPC command for the SRS, including the first TPC command or the second TPC command. Further, the UE may then configure power control for at least one of PUSCH transmission and SRS transmission based on the received one or more parameters.

It should also be noted that method 1400 may also include operations where the DCI includes non-scheduled DCI configured to trigger transmission of at least one of the one or more Sounding Reference Signal (SRS) resource sets at a first time, such as illustrated in fig. 9A, 9B, or 10. In this case, the method further comprises receiving at least one scheduling DCI before the first time, wherein the at least one scheduling DCI comprises further TPC commands. The UE may then respond to the further TPC command based on a predetermined setting. In one example, responding to the further TPC command includes ignoring the further TPC command based on a predetermined setting or accumulating the further TPC command based on a predetermined setting. Additionally, the non-scheduled Downlink Control Information (DCI) may include one-time power adjustment DCI for a corresponding triggered transmission of a Sounding Reference Signal (SRS) resource set for use with a closed-loop power control procedure. Here, the UE may then configure the SRS resource set with the further TPC command based on a predetermined configuration that is further based on the power control power adjustment state of the PUSCH.

Fig. 15 is a flow chart illustrating an example wireless communication method 1400 in accordance with some aspects of the present disclosure. As described herein, some or all of the illustrated features may be omitted from a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method 1500 may be performed by the UE 1300 illustrated in fig. 13. In some examples, the method 1500 may be performed by any suitable apparatus or device for implementing the functions or algorithms described below.

At block 1502, a ue may receive non-scheduled Downlink Control Information (DCI) configured to trigger transmission of a Sounding Reference Signal (SRS) resource set at a first time and including a first TPC command configured for power control of the SRS resource set. Next, at block 1504, the ue may receive at least one scheduling DCI prior to the first time, wherein the at least one scheduling DCI includes a second TPC command. Finally, the method 1500 includes responding to or acting on the second TPC command based on a predetermined setting, as shown in block 1506. In aspects, the responding to the second TPC command includes ignoring the second TPC command based on a predetermined setting. In another aspect, the response to the second TPC command includes accumulating the second TPC command based on a predetermined setting, such as discussed above in connection with fig. 9.

In yet other aspects, the method 1500 may include accumulating a plurality of TPC commands for each of a respective plurality of scheduling DCIs received prior to the first time. In other aspects, the method 1500 may include: the non-scheduled Downlink Control Information (DCI) includes one-time power adjustment DCI for a corresponding triggered transmission of a Sounding Reference Signal (SRS) resource set for use with a closed-loop power control procedure, and the UE configures the SRS resource set with TPC commands based on a predetermined configuration. In yet a further aspect, the predetermined configuration includes controlling the power adjustment state using the same power as a Physical Uplink Shared Channel (PUSCH). In another example, the predetermined configuration includes controlling the power adjustment state using a different power than PUSCH.

It should be further noted that the present disclosure may include the following further aspects of the present disclosure.

Aspect 1: a method for communicating at a base station, comprising: configuring Downlink Control Information (DCI) to include a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; and preparing the DCI for transmission to at least one User Equipment (UE).

Aspect 2: the method of aspect 1, wherein the DCI is non-scheduled DCI configured to trigger the one or more SRS resource sets.

Aspect 3: the method of any of aspects 1 or 2, wherein at least the second TPC command is placed in a reused bit field of the non-scheduled DCI, wherein the reused bit fields include one or more bit fields configured in the scheduled DCI for scheduling transmission resources.

Aspect 4: the method of any one of aspects 1-3, wherein the one or more SRS resource sets are aperiodic SRS resource sets triggered by the DCI.

Aspect 5: the method of any one of aspects 1-4, wherein the DCI further includes an indication of a power adjustment state for the second TPC command configured for power control of the one or more SRS resource sets.

Aspect 6: the method of aspect 5, wherein the indication of the power adjustment state further comprises: configuring the DCI to include the second TPC command includes: a first bit field having the second TPC command and the first power adjustment state and a second bit field having the second TPC command and the second power adjustment state.

Aspect 7: the method of claim 5, wherein the indication of the power adjustment state comprises signaling or configuration communicated to the UE to allow the UE to derive the power adjustment state based on at least one predetermined condition or setting, wherein the at least one predetermined condition or setting comprises a predetermined regarding that the second TPC command is applicable to both of the two available power adjustment states.

Aspect 8: the method of claim 7, wherein the at least one predetermined condition and setting comprises applying a second TPC command having a power adjustment state associated with a greater or lesser number of triggered SRS resource sets in the plurality of triggered SRS resource sets or a power adjustment state corresponding to a greater or lesser triggered SRS resource set identifier (set ID) in the plurality of triggered SRS resource sets.

Aspect 9: the method of any one of aspects 1 to 8, wherein the DCI includes an SRS Resource Indicator (SRI) bit field.

Aspect 10: the method of any of aspects 1-8, wherein the DCI includes a power adjustment status indication for the first TPC command without including an SRS Resource Indicator (SRI).

Aspect 11: the method of aspect 10, wherein the power adjustment status indication further comprises: configuring the DCI to include the first TPC command includes: a first bit field having the first TPC command and a first power adjustment state and a second bit field having the first TPC command and a second power adjustment state.

Aspect 12: the method of any one of aspects 1-11, wherein the DCI is further configured to indicate one or more TPC commands for each Component Carrier (CC) in a set of CCs.

Aspect 13: a network entity, comprising: a processor configured to: configuring Downlink Control Information (DCI) to include a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; and preparing the DCI for transmission to at least one User Equipment (UE).

Aspect 14: the network entity of aspect 13, wherein the DCI is non-scheduled DCI configured to trigger the one or more SRS resource sets.

Aspect 15: a method for communicating at a User Equipment (UE), comprising: processing Downlink Control Information (DCI) received from a network entity, the DCI including a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; and configuring resources for at least one of PUSCH and SRS transmission based on the first TPC command or the second TPC command.

Aspect 16: the method of aspect 15, wherein the DCI is non-scheduled DCI configured to trigger the one or more SRS resource sets in the UE.

Aspect 17: the method of any of aspects 15 or 16, wherein at least the second TPC command is placed in a reused bit field of the non-scheduled DCI, wherein the reused bit fields include one or more bit fields configured in the scheduled DCI for scheduling transmission resources.

Aspect 18: the method of any one of aspects 15 to 17, wherein the one or more SRS sets are aperiodic SRS sets triggered by the DCI.

Aspect 19: the method of any one of aspects 15 to 18, further comprising: setting transmit powers of PUSCH and SRS resource sets based on the first TPC command and the second TPC command, respectively; transmitting PUSCH and SRS resource sets; wherein the first TPC command and the second TPC command are configured to implement the same power control in the UE for each of the PUSCH and the one or more SRS resource sets.

Aspect 20: the method of any one of aspects 15 to 18, further comprising: setting transmit powers of PUSCH and SRS resource sets based on the first TPC command and the second TPC command, respectively; transmitting PUSCH and SRS resource sets; wherein the first TPC command and the second TPC command are configured to implement different power control for each of the respective PUSCH and the one or more SRS resource sets.

Aspect 21: the method of any one of aspects 15 to 20, wherein the DCI is formatted according to DCI format 0_1 or DCI format 0_2.

Aspect 22: the method of any one of aspects 15 to 21, wherein the DCI further includes an indication of a power adjustment state for a second TPC command configured for power control of the one or more SRS resource sets; and setting a transmit power of the one or more SRS resource sets based in part on the indicated power adjustment state.

Aspect 23: the method of any one of aspects 15 to 22, further comprising: deriving the power adjustment state based on characteristics of the second TPC command in the DCI; wherein the indication of the power adjustment state for the second TPC command includes signaling or configuration communicated by the base station to the UE configured to allow the UE to derive the power adjustment state.

Aspect 24: the method of claim 23, wherein the characteristics of the second TPC command include: for a triggered SRS resource set having a plurality of trigger states, one of the plurality of trigger states is designated as an indication for conveying to which of the two power adjustment state indicators the TPC command applies.

Aspect 25: the method of claim 23, wherein the characteristics of the second TPC command include: for a plurality of triggered SRS resource sets, a configuration in which all of the plurality of triggered sets are configured with the same power adjustment state indicates that the second TPC command applies to the same power adjustment state.

Aspect 26: the method of any one of aspects 15 to 25, further comprising: power control for at least one of PUSCH transmission and SRS transmission is configured based on one or more parameters in received Radio Resource Control (RRC) signaling, the RRC signaling including the one or more parameters to configure the UE to identify at least one of TPC commands for PUSCH and TPC commands for SRS, the at least one TPC command including the first TPC command or the second TPC command.

Aspect 27: the method of any one of aspects 15-26, wherein the DCI comprises non-scheduled DCI configured to trigger transmission of at least one of the one or more Sounding Reference Signal (SRS) resource sets at a first time, the method further comprising: receiving at least one scheduling DCI before the first time, wherein the at least one scheduling DCI includes further TPC commands; and responding to the further TPC command based on a predetermined setting.

Aspect 28: the method of claim 27, wherein responding to the further TPC command includes one of: the further TPC commands are ignored based on the predetermined setting or accumulated based on the predetermined setting.

Aspect 29: the method of claim 27, further comprising: the non-scheduled Downlink Control Information (DCI) includes a one-time power adjustment DCI for a corresponding triggered transmission of the Sounding Reference Signal (SRS) resource set for use with a closed-loop power control procedure; wherein the UE configures the SRS resource set with the further TPC command based on a predetermined configuration, the predetermined configuration further controlling a power adjustment state based on the power of the PUSCH.

Aspect 30: a user equipment, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: receiving Downlink Control Information (DCI) configured to include a plurality of Transmit Power Control (TPC) commands including: a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; configuring resources for at least one of PUSCH transmission and SRS transmission based on the first TPC command or the second TPC command; and transmitting the configured resources for at least one of PUSCH transmission and SRS transmission.

Aspect 31: an apparatus configured for wireless communication comprising at least one means for performing the method of any one of aspects 1-12 or aspects 15-29.

Aspect 32: a non-transitory computer-readable medium storing computer-executable code comprising code for causing an apparatus to perform the method of any one of aspects 1 to 12 or aspects 15 to 29.

Several aspects of a wireless communication network have been presented with reference to example implementations. As will be readily appreciated by those skilled in the art, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

As an example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), evolved Packet System (EPS), universal Mobile Telecommunications System (UMTS), and/or Global System for Mobile (GSM). The various aspects may also be extended to systems defined by third generation partnership project 2 (3 GPP 2), such as CDMA2000 and/or evolution data optimized (EV-DO). Other examples may be implemented within systems employing Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, ultra Wideband (UWB), bluetooth, and/or other suitable systems. The actual telecommunications standards, network architectures, and/or communication standards employed will depend on the particular application and the overall design constraints imposed on the system.

Within this disclosure, the phrase "exemplary" is used to mean "serving as an example, instance, or illustration. Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object a physically contacts object B and object B contacts object C, then objects a and C may still be considered coupled to each other even though they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even though the first object is never in direct physical contact with the second object. The terms "circuitry" and "circuitry" are used broadly and are intended to encompass both hardware implementations of electronic devices and conductors, which, when connected and configured, enable performance of the functions described in this disclosure, without limitation as to the type of electronic circuitry, as well as software implementations of information and instructions, which, when executed by a processor, enable performance of the functions described in this disclosure. As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), validating, parsing, selecting, choosing, establishing, receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc.

One or more of the components, steps, features, and/or functions illustrated in fig. 1-15 may be rearranged and/or combined into a single component, step, feature, or function, or implemented in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from the novel features disclosed herein. The apparatus, devices, and/or components illustrated in any of fig. 1-15 may be configured to perform one or more methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware.

It is to be understood that the specific order or hierarchy of steps in the methods disclosed are illustrations of example processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented, unless specifically recited herein.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more". The term "some" means one or more unless specifically stated otherwise. The phrase referring to a list of items "at least one of" refers to any combination of these items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a, a; b; c, performing operation; a and b; a and c; b and c; and a, b and c. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents that are presently or later to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims (30)

1. A method for communicating at a base station, comprising:

configuring Downlink Control Information (DCI) to include a plurality of Transmit Power Control (TPC) commands, the plurality of Transmit Power Control (TPC) commands comprising:

a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and

a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; and

the DCI is prepared for transmission to at least one User Equipment (UE).

2. The method of claim 1, wherein the DCI is a non-scheduled DCI configured to trigger the one or more SRS resource sets.

3. The method of claim 2, wherein at least the second TPC command is placed in a reused bit field of the non-scheduled DCI, wherein the reused bit field includes one or more bit fields configured in a scheduled DCI for scheduling transmission resources.

4. The method of claim 2, wherein the one or more SRS resource sets are aperiodic SRS resource sets triggered by the DCI.

5. The method of claim 1, wherein the DCI further comprises an indication of a power adjustment state for the second TPC command configured for power control of the one or more SRS resource sets.

6. The method of claim 5, wherein the indication of the power adjustment state further comprises: the DCI is configured to include the second TPC command including a first bit field having the second TPC command and a first power adjustment state and a second bit field having the second TPC command and a second power adjustment state.

7. The method of claim 5, wherein the indication of the power adjustment state comprises signaling or configuration communicated to the UE to allow the UE to derive the power adjustment state based on at least one predetermined condition or setting, wherein the at least one predetermined condition or setting comprises a predetermined determination that the second TPC command is applicable to both of two available power adjustment states.

8. The method of claim 7, wherein the at least one predetermined condition and setting comprises applying the second TPC command with a power adjustment state associated with a greater or lesser number of triggered SRS resource sets of a plurality of triggered SRS resource sets or a power adjustment state corresponding to a greater or lesser triggered SRS resource set identifier (set ID) of the plurality of triggered SRS resource sets.

9. The method of claim 1, wherein the DCI includes an SRS Resource Indicator (SRI) bit field.

10. The method of claim 1, wherein the DCI includes a power adjustment status indication for the first TPC command without including an SRS Resource Indicator (SRI).

11. The method of claim 10, wherein the power adjustment status indication further comprises: the DCI is configured to include the first TPC command including a first bit field having the first TPC command and a first power adjustment state and a second bit field having the first TPC command and a second power adjustment state.

12. The method of claim 1, wherein the DCI is further configured to indicate one or more TPC commands for each Component Carrier (CC) in a set of CCs.

13. A network entity, comprising:

a processor configured to:

configuring Downlink Control Information (DCI) to include a plurality of Transmit Power Control (TPC) commands, the plurality of Transmit Power Control (TPC) commands comprising:

a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and

A second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; and

the DCI is prepared for transmission to at least one User Equipment (UE).

14. The network entity of claim 13, wherein the DCI is a non-scheduled DCI configured to trigger the one or more SRS resource sets.

15. A method for communicating at a User Equipment (UE), comprising:

processing Downlink Control Information (DCI) received from a network entity, the DCI including a plurality of Transmit Power Control (TPC) commands including:

a first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and

a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets; and

resources for at least one of PUSCH transmission and SRS transmission are configured based on the first TPC command or the second TPC command.

16. The method of claim 15, wherein the DCI is a non-scheduled DCI configured to trigger the one or more SRS resource sets in the UE.

17. The method of claim 16, wherein at least the second TPC command is placed in a reused bit field of the non-scheduled DCI, wherein the reused bit field includes one or more bit fields configured in a scheduled DCI for scheduling transmission resources.

18. The method of claim 16, wherein the one or more SRS sets are aperiodic SRS sets triggered by the DCI.

19. The method of claim 15, further comprising:

setting transmit powers of the PUSCH and SRS resource sets based on the first TPC command and the second TPC command, respectively; and

transmitting the PUSCH and SRS resource sets;

wherein the first TPC command and the second TPC command are configured to implement the same power control in the UE for each of the PUSCH and the one or more SRS resource sets.

20. The method of claim 15, further comprising:

setting transmit powers of the PUSCH and SRS resource sets based on the first TPC command and the second TPC command, respectively; and

transmitting the PUSCH and SRS resource sets;

wherein the first TPC command and the second TPC command are configured to implement different power control for each of the respective PUSCH and the one or more SRS resource sets.

21. The method of claim 15, wherein the DCI is formatted according to DCI format 0_1 or DCI format 0_2.

22. The method of claim 15, wherein the DCI further comprises an indication of a power adjustment state for the second TPC command configured for power control of the one or more SRS resource sets; and

the transmit power of the one or more SRS resource sets is set based in part on the indicated power adjustment state.

23. The method of claim 22, further comprising:

deriving the power adjustment state based on characteristics of the second TPC command in the DCI;

wherein the indication of the power adjustment state for the second TPC command includes signaling or configuration communicated by a base station to the UE configured to allow the UE to derive the power adjustment state.

24. The method of claim 23, wherein the characteristic of the second TPC command comprises: for a triggered SRS resource set having a plurality of trigger states, one of the plurality of trigger states is designated as an indication for conveying to which of two power adjustment state indicators the TPC command applies.

25. The method of claim 23, wherein the characteristic of the second TPC command comprises: for a plurality of triggered SRS resource sets, a configuration in which all of the plurality of triggered sets are configured with the same power adjustment state indicates that the second TPC command is applied to the same power adjustment state.

26. The method of claim 15, further comprising:

power control for at least one of PUSCH transmission and SRS transmission is configured based on one or more parameters in received Radio Resource Control (RRC) signaling, the RRC signaling including the one or more parameters to configure the UE to identify at least one of TPC commands for PUSCH and TPC commands for SRS, the at least one TPC command including the first TPC command or the second TPC command.

27. The method of claim 15, wherein the DCI comprises non-scheduled DCI configured to trigger transmission of at least one of the one or more Sounding Reference Signal (SRS) resource sets at a first time, the method further comprising:

receiving at least one scheduling DCI before the first time, wherein the at least one scheduling DCI includes further TPC commands; and

The further TPC commands are responded to based on a predetermined setting.

28. The method of claim 27, wherein responding to the further TPC command comprises one of: ignoring the further TPC command based on the predetermined setting or accumulating the further TPC command based on the predetermined setting.

29. The method of claim 27, further comprising:

the non-scheduled Downlink Control Information (DCI) includes a one-time power adjustment DCI for a corresponding triggered transmission of at least one of the one or more Sounding Reference Signal (SRS) resource sets for use with a closed-loop power control procedure;

wherein the UE configures the at least one of the one or more SRS resource sets with the further TPC commands based on a predetermined configuration, the predetermined configuration being further based on a power control power adjustment state of the PUSCH.

30. A user equipment, comprising:

a transceiver;

a memory; and

a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to:

receiving Downlink Control Information (DCI) configured to include a plurality of Transmit Power Control (TPC) commands, the plurality of TPC commands comprising:

A first TPC command of the plurality of TPC commands configured for power control of a Physical Uplink Shared Channel (PUSCH); and

a second TPC command of the plurality of TPC commands configured for power control of one or more Sounding Reference Signal (SRS) resource sets;

configuring resources for at least one of PUSCH transmission and SRS transmission based on the first TPC command or the second TPC command; and

configured resources for at least one of the PUSCH transmission and the SRS transmission are transmitted.