Patent Description:
Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, and orthogonal frequency-division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.

For example, a fifth generation (<NUM>) wireless communications technology (which can be referred to as NR) is envisaged to expand and support diverse usage scenarios and applications with respect to current mobile network generations. In an aspect, <NUM> communications technology can include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.

For example, for various communications technology such as, but not limited to NR, some implementations may increase transmission speed and flexibility but also transmission complexity. Thus, improvements in wireless communication operations may be desired.

<CIT> describes a method in an access node or evolved Node B for granting uplink transmission resources to one of a plurality of UEs.

An example implementation includes a method of wireless communication at a user equipment (UE), according to claim <NUM>.

A further example implementation includes an apparatus for wireless communications according to claim <NUM>.

Another example implementation includes a method of wireless communication at a network entity, according to claim <NUM>.

The described features generally relate to UE-assisted uplink resource modification. Specifically, in New Radio (NR) uplink, for periodic data being transmitted on the uplink, the network can set-up non-dynamic (semi-persistent) grants for such transmission. The use of non-dynamic grants may be to reduce the control over head. In some aspects, there may be two non-dynamic grants. A first type may be a configured grant type <NUM>, which provides parameters, configuration information, and activation via radio resource control (RRC) signaling. A second type may be a configured grant type <NUM>, which include periodicity configuration via RRC signaling and activation using a physical downlink control channel (PDCCH) for activation, as well as parameter configuration and medium access control (MAC) control element (CE) for acknowledgement of the activation signal. In some implementations, if the UE is configured with a non-dynamic grant and the UE does not have data to transmit, the UE forgoes transmitting the data. However, the UE may benefit from notifying the network when there is an absence of data for uplink transmission associated with the grant for more efficient utilization of the resources and potential energy reduction at the network.

In an aspect, the present disclose includes a method, apparatus, and non-statutory computer readable medium for wireless communications for determining an upcoming absence of uplink data for transmission on an uplink communication channel to a network entity during a period defined by a configured grant, and transmitting a message to the network entity to trigger adjustment of at least one resource associated with the configured grant based on determining the absence of uplink data for transmission on the uplink communication channel.

In another implementation, the present disclose includes a method, apparatus, and non-statutory computer readable medium for wireless communications for receiving a message from a UE representing an upcoming absence of uplink data on an uplink communication channel during a scheduled period defined by a configured grant, and adjusting at least one resource associated with the configured grant in response to receiving the message.

As used in this application, the terms "component," "module," "system" and the like are intended to include a computer-related entity, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.

Techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" may often be used interchangeably. IS-<NUM> Releases <NUM> and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-<NUM> (TIA-<NUM>) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. The description below, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to fifth generation (<NUM>) NR networks or other next generation communication systems).

The wireless communications system (also referred to as a wireless wide area network (WWAN)) can include base stations <NUM>, UEs <NUM>, an Evolved Packet Core (EPC) <NUM>, and/or a <NUM> Core (5GC) <NUM>. The base stations <NUM>, which may also be referred to as network entities, may include macro cells (high power cellular base station) and/or small cells (low power cellular base station). The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells. In an example, the base stations <NUM> may also include gNBs <NUM>, as described further herein.

In one example, some nodes such as base station <NUM>/gNB <NUM>, may have a modem <NUM> and communicating component <NUM> for UE-assisted uplink resource modification, as described herein. Though a base station <NUM>/gNB <NUM> is shown as having the modem <NUM> and communicating component <NUM>, this is one illustrative example, and substantially any node may include a modem <NUM> and communicating component <NUM> for providing corresponding functionalities described herein.

In another example, some nodes such as UE <NUM> of the wireless communication system may have a modem <NUM> and communicating component <NUM> for UE-assisted uplink resource modification, as described herein. Though a UE <NUM> is shown as having the modem <NUM> and communicating component <NUM>, this is one illustrative example, and substantially any node or type of node may include a modem <NUM> and communicating component <NUM> for providing corresponding functionalities described herein.

The base stations <NUM> configured for <NUM> LTE (which can collectively be referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through backhaul links <NUM> (e.g., using an S1 interface). The base stations <NUM> configured for <NUM> NR (which can collectively be referred to as Next Generation RAN (NG-RAN)) may interface with 5GC <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or 5GC <NUM>) with each other over backhaul links <NUM> (e.g., using an X2 interface). The backhaul links <NUM>, <NUM> and/or <NUM> may be wired or wireless.

The base stations <NUM> may wirelessly communicate with one or more UEs <NUM>. A network that includes both small cell and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group, which can be referred to as a closed subscriber group (CSG). The base stations <NUM> / UEs <NUM> may use spectrum up to Y MHz (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (e.g., for x component carriers) used for transmission in the DL and/or the UL direction. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

In another example, certain UEs <NUM> may communicate with each other using device-to-device (D2D) communication link <NUM>.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In <NUM> NR two initial operating bands have been identified as frequency range designations FR1 (<NUM> - <NUM>) and FR2 (<NUM> - <NUM>). Although a portion of FR1 is greater than <NUM>, FR1 is often referred to (interchangeably) as a "Sub-<NUM>" band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a "millimeter wave" (mmW) band in documents and articles, despite being different from the extremely high frequency (EHF) band (<NUM> - <NUM>) which is identified by the International Telecommunications Union (ITU) as a "millimeter wave" band.

Communications using the mmW radio frequency band have extremely high path loss and a short range. The mmW base station <NUM> may utilize beamforming <NUM> with the UE <NUM> to compensate for the path loss and short range.

The 5GC <NUM> may include a Access and Mobility Management Function (AMF) <NUM>, other AMFs <NUM>, a Session Management Function (SMF) <NUM>, and a User Plane Function (UPF) <NUM>. The AMF <NUM> can be a control node that processes the signaling between the UEs <NUM> and the 5GC <NUM>. Generally, the AMF <NUM> can provide QoS flow and session management. User Internet protocol (IP) packets (e.g., from one or more UEs <NUM>) can be transferred through the UPF <NUM>. The UPF <NUM> can provide UE IP address allocation for one or more UEs, as well as other functions.

The base station <NUM> provides an access point to the EPC <NUM> or 5GC <NUM> for a UE <NUM>. Examples of UEs <NUM> include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a positioning system (e.g., satellite, terrestrial), a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, robots, drones, an industrial/manufacturing device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a vehicle/a vehicular device, a meter (e.g., parking meter, electric meter, gas meter, water meter, flow meter), a gas pump, a large or small kitchen appliance, a medical/healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs <NUM> may be referred to as IoT devices (e.g., meters, pumps, monitors, cameras, industrial/manufacturing devices, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC/enhanced MTC (eMTC, also referred to as CAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. The UE <NUM> may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Turning now to <FIG>, aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional. Although the operations described below in <FIG> and <FIG> is presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation. Moreover, it should be understood that the following actions, functions, and/or described components may be performed by a specially-programmed processor, a processor executing specially-programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions.

Referring to <FIG>, one example of an implementation of a node such as base station <NUM> (e.g., a base station <NUM> and/or gNB <NUM>, as described above) may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and/or communicating component <NUM> for UE-assisted uplink resource modifications.

In an aspect, the one or more processors <NUM> can include a modem <NUM> and/or can be part of the modem <NUM> that uses one or more modem processors. Thus, the various functions related to communicating component <NUM> may be included in modem <NUM> and/or processors <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver <NUM>. In other aspects, some of the features of the one or more processors <NUM> and/or modem <NUM> associated with communicating component <NUM> may be performed by transceiver <NUM>.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or communicating component <NUM> and/or one or more of its subcomponents being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining communicating component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when base station <NUM> is operating at least one processor <NUM> to execute communicating component <NUM> and/or one or more of its subcomponents.

Moreover, in an aspect, base station <NUM> may include RF front end <NUM>, which may operate in communication with one or more antennas <NUM> and transceiver <NUM> for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one base station <NUM> or wireless transmissions transmitted by UE <NUM>. The antennas <NUM> may include one or more antennas, antenna elements, and/or antenna arrays.

In an aspect, the processor(s) <NUM> may correspond to one or more of the processors described in connection with the UE in <FIG> and <FIG>.

Referring to <FIG>, one example of an implementation of UE <NUM> may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM>.

The transceiver <NUM>, receiver <NUM>, transmitter <NUM>, one or more processors <NUM>, memory <NUM>, applications <NUM>, buses <NUM>, RF front end <NUM>, LNAs <NUM>, switches <NUM>, filters <NUM>, PAs <NUM>, and one or more antennas <NUM> may be the same as or similar to the corresponding components of base station <NUM>, as described above, but configured or otherwise programmed for base station operations as opposed to base station operations.

<FIG> is an example data communication session <NUM> over time on the uplink. For example, from the perspective of a gNB, a lack of data reception may either be due to undetected data or the UE may have no data to transmit on the uplink. Therefore, the gNB may wait for a number of absent data receptions, 'N', before concluding the UE does not have any data to transmit on the uplink. However, a more efficient and dynamic manner in terms of resource usage may be such that the UE explicitly notifies the gNB that the resources may no longer be utilized and hence, can be released or suspended for a duration of time. Accordingly, releasing, suspending, or skipping of resources at the gNB may also create opportunities for network energy savings at the gNB.

<FIG> is an example media access control (MAC) signaling session <NUM> over time on the uplink. In such implementation, one of the triggers for a buffer status report (BSR) transmission may be when there is space left unfilled by a payload to be transmitted. As such, rather than include padding, the UE can include a regular BSR in the payload corresponding to a last uplink data that is to be transmitted to the network entity (e.g., gNB). In some aspects, the BSR MAC CE carries the logical channel group identifier (LCG ID) and the buffer size. In addition to the BSR, the UE can include information related to the modification of the non-dynamic resources, e.g., suspension/release of the non-dynamic grant. Such resource modification information may indicate, for example, a release or suspension of resources, a suspension length, or a skipping of resources.

<FIG> is an example MAC indication <NUM> and Layer <NUM> signaling <NUM> over time on the uplink. Specifically, if the information to be conveyed to the gNB is larger than the space available in the payload/BSR, then the payload/BSR can carry a flag informing the gNB to expect an upcoming transmission of non-dynamic grant modification information in the next PUCCH or PUSCH transmission. In one aspect, the resource modification information may be transmitted in the PUCCH occurring before the scheduled PUSCH. The PUCCH information may include the flag and may be offset from the current PUSCH. In another aspect, the resource modification information may be transmitted to the gNB using a next scheduled PUSCH.

<FIG> is an example Layer <NUM> indication <NUM> and Layer <NUM> signaling <NUM> over time on the uplink. Specifically, in some cases, there may be no space left in the last non-dynamic grant carrier data to carry resource modification information on the uplink. In certain cases, a faster modification timeline may be desired than can be provided by Layer <NUM> signaling. In this case, the Layer <NUM> signaling can be used in conveying the modification information. In one implementation, an Layer <NUM> indication may point to a PUCCH transmission. In another implementation, a Layer <NUM> indication may point to PUSCH. The PUSCH carrying the last data may use a Layer <NUM> indication to notify the network that the next PUCCH or PUSCH transmission may carry the resource modification information and when to expect the PUCCH or PUSCH transmission, or release or suspension may be requested to be carried out according to some predetermined rule if previously defined.

<FIG> is an example Layer <NUM> signaling <NUM> over time on the uplink. In some aspects, the UE may already have an upcoming PUCCH occasion. In such scenario, the present implementations may use the scheduled PUCCH occasion to also transmit the resource modification on the PUCCH. In some aspects, existing PUCCH formats may be used. Otherwise, new PUCCH formats may be defined. In some aspects, if there are no upcoming PUCCH occasions, the next PUSCH occasion may be used to carry the resource modification information either as a known sequence or scrambling code. In one aspect, the resource modification information may correspond to a resource release providing complete release of all resources. In another aspect, the resource modification information may correspond to resource dormancy providing resource suspension starting immediately for a duration, e.g., 'M' periods. In a further aspect, the resource modification information may correspond to resource skipping providing skipping resource for a number of periods.

<FIG> illustrate a flow chart of an example of a method <NUM> for wireless communication at a UE. In an example, a UE <NUM> can perform the functions described in method <NUM> using one or more of the components described in <FIG>, <FIG>, <FIG>, and <FIG>.

At block <NUM>, the method <NUM> determines an upcoming absence of uplink data for transmission on an uplink communication channel to a network entity during a period defined by a configured grant. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to determine an upcoming absence of uplink data for transmission on an uplink communication channel to a network entity during a period defined by a configured grant. Thus, the UE <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for determining an upcoming absence of uplink data for transmission on an uplink communication channel to a network entity during a period defined by a configured grant. For example, in an aspect, the UE <NUM> may determine there are unused uplink resources based on its uplink data payload and the assigned uplink resources indicated in the uplink grant.

At block <NUM>, the method <NUM> transmits a message to the network entity to trigger adjustment of at least one resource associated with the configured grant based on determining the absence of uplink data for transmission on the uplink communication channel. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to transmit a message to the network entity to trigger adjustment of at least one resource associated with the configured grant based on determining the absence of uplink data for transmission on the uplink communication channel. Thus, the UE <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for transmitting a message to the network entity to trigger adjustment of at least one resource associated with the configured grant based on determining the absence of uplink data for transmission on the uplink communication channel. For example, in an aspect, the UE <NUM> can operate processor <NUM> to generate the message in the form of data bits, and may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to transmit the data bits as a wireless signal or waveform, as described.

In some aspects, the message may be transmitted using a MAC CE.

In some aspects, the message may be transmitted using a BSR MAC CE.

In some aspects, the message may further include adjustment information of the at least one resource associated with the configured grant.

In some aspects, transmitting the message may include transmitting final uplink data and the adjustment information using a the MAC CE.

In some aspects, the MAC CE may be transmitted on a last resource of a PUSCH transmission along with final uplink data.

In some aspects, the message may further include an indication corresponding to a flag indicating an upcoming transmission of adjustment information.

In some aspects, the indication may further include information about the resource carrying the adjustment information including an offset from a resource carrying the flag.

In some aspects, the method <NUM> may further include determining that the final uplink data and the buffer status report satisfies a payload size threshold value representing a maximum size of a PUSCH transmission corresponding to the defined period allocated by the configured grant, and transmitting the adjustment information of the at least one resource associated with the configured grant to the network entity, the indication may be corresponds to the flag indicating the upcoming transmission of adjustment information is transmitted based on determining that final uplink data and the buffer status report satisfies a payload size threshold value. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to determine that the final uplink data and the buffer status report satisfies a payload size threshold value representing a maximum size of a PUSCH transmission corresponding to the defined period allocated by the configured grant, and transmit the adjustment information of the at least one resource associated with the configured grant to the network entity, the indication may be corresponds to the flag indicating the upcoming transmission of adjustment information is transmitted based on determining that final uplink data and the buffer status report satisfies a payload size threshold value. Thus, the UE <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for determining that the final uplink data and the buffer status report satisfies a payload size threshold value representing a maximum size of a PUSCH transmission corresponding to the defined period allocated by the configured grant, and transmitting the adjustment information of the at least one resource associated with the configured grant to the network entity, the indication may be corresponds to the flag indicating the upcoming transmission of adjustment information is transmitted based on determining that final uplink data and the buffer status report satisfies a payload size threshold value. For example, in an aspect, the UE <NUM> may compare a size of the uplink data and the buffer status report to the payload size threshold and identify if the comparison meets the threshold so as to trigger generation data bits that represent the adjustment information, and may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to transmit the data bits as a wireless signal or waveform, as described.

In some aspects, the adjustment information may be transmitted on a PUCCH prior to the next scheduled PUSCH transmission associated with the configured grant.

According to the invention, the adjustment information is transmitted on a subsequent scheduled PUSCH transmission associated with the configured grant after a Layer <NUM> indication is transmitted on a current PUSCH, the Layer <NUM> indication corresponding to an indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.

In some aspects, the message in the PUSCH may correspond to a Layer <NUM> indication pointing to the adjustment information transmission on a PUCCH or PUSCH.

In some aspects, transmitting the message may include transmitting final uplink data and the Layer <NUM> indication using a PUSCH transmission of the configured grant, the Layer <NUM> indication corresponding to a payload including a number of bits or a scrambling code used to scramble the said PUSCH.

In some aspects, the method <NUM> may further include transmitting, via a subsequent PUSCH, the adjustment information of the at least one resource associated with the configured grant. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to transmit, via a subsequent PUSCH, the adjustment information of the at least one resource associated with the configured grant. Thus, the UE <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for transmitting, via a subsequent PUSCH, the adjustment information of the at least one resource associated with the configured grant. For example, in an aspect, the UE <NUM> can operate processor <NUM> to generate the adjustment information in the form of data bits, and may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to transmit the data bits as a wireless signal or waveform, as described.

In some aspects, the method <NUM> may further include transmitting, via PUCCH, the adjustment information of the at least one resource associated with the configured grant. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to transmit, via PUCCH, the adjustment information of the at least one resource associated with the configured grant. Thus, the UE <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for transmitting, via PUCCH, the adjustment information of the at least one resource associated with the configured grant. For example, in an aspect, the UE <NUM> can operate processor <NUM> to generate the adjustment information in the form of data bits, and may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to transmit the data bits as a wireless signal or waveform, as described.

In some aspects, transmitting, via a PUCCH, the message may include transmitting adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload including a number of bits or scrambling code used for scrambling the PUCCH.

In some aspects, transmitting, via a PUSCH, the message may include transmitting adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload including a number of bits or scrambling code used for scrambling the PUSCH.

In some aspects, the adjustment of the at least one resource may correspond to at least one of a release of the at least one resource, a suspension of the at least one resource for a duration, or a skipping of the at least one resource for a certain duration.

<FIG> illustrate a flow chart of an example of a method <NUM> for wireless communication at a network entity such as base station <NUM>. In an example, a base station <NUM> can perform the functions described in method <NUM> using one or more of the components described in <FIG>, <FIG>, <FIG>, and <FIG>.

At block <NUM>, the method <NUM> may receive a message from a UE representing an upcoming absence of uplink data on an uplink communication channel during a scheduled period defined by a configured grant. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to receive a message from a UE representing an upcoming absence of uplink data on an uplink communication channel during a scheduled period defined by a configured grant. In one example, the data can be associated with a priority level. Thus, the base station <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for receiving a message from a UE representing an upcoming absence of uplink data on an uplink communication channel during a scheduled period defined by a configured grant. For example, in an aspect, the base station <NUM> may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to receiving the message in the form of data bits as a wireless signal or waveform, as described.

At block <NUM>, the method <NUM> may adjust at least one resource associated with the configured grant in response to receiving the message. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to adjust at least one resource associated with the configured grant in response to receiving the message. Thus, the base station <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for adjusting at least one resource associated with the configured grant in response to receiving the message. For example, in an aspect, the base station <NUM> may operate processor <NUM> to process the message and the adjustment the resource.

In some aspects, the method <NUM> may further include transmitting an adjustment message indicating adjustment of the at least one resource associated with the configured grant to the UE. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to transmit an adjustment message indicating adjustment of the at least one resource associated with the configured grant to the UE. In one example, the data can be associated with a priority level. Thus, the base station <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for transmitting an adjustment message indicating adjustment of the at least one resource associated with the configured grant to the UE. For example, in an aspect, the base station <NUM> may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to transmit the adjustment message in the form of data bits as a wireless signal or waveform, as described.

In some aspects, the method <NUM> may further include withdrawing the configured grant in response to adjusting the at least one resource, and forgoing transmission of an adjustment message indicating adjustment of the at least one resource to the UE. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to withdraw the configured grant in response to adjusting the at least one resource, and forgoing transmission of an adjustment message indicating adjustment of the at least one resource to the UE. In one example, the data can be associated with a priority level. Thus, the base station <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for withdrawing the configured grant in response to adjusting the at least one resource, and forgoing transmission of an adjustment message indicating adjustment of the at least one resource to the UE. For example, in an aspect, the base station <NUM> may operate processor <NUM> to remove the grant and not activate the communication components to transmit the adjustment the resource.

In some aspects, receiving the message may include receiving final uplink data and the adjustment information using a MAC CE.

In some aspects, the MAC CE is transmitted on a last resource of a PUSCH transmission along with final uplink data.

In some aspects, the indication may further include information about a resource carrying the adjustment information including an offset from a resource carrying the flag.

In some aspects, the adjustment information may be transmitted on a subsequent scheduled PUSCH transmission associated with the configured grant after the Layer <NUM> indication is transmitted on a current PUSCH carrying the message.

In some aspects, the message in a PUSCH may corresponds to a Layer <NUM> indication pointing to the adjustment information transmission on a PUCCH or another PUSCH.

In some aspects, receiving the message may include receiving final uplink data and the Layer <NUM> indication using a PUSCH transmission of the configured grant, the Layer <NUM> indication corresponding to a payload including a number of bits or a scrambling code used to scramble the PUSCH.

In some aspects, the method <NUM> may further include receiving, via a subsequent PUSCH, the adjustment information of the at least one resource associated with the configured grant. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to receive, via a subsequent PUSCH, the adjustment information of the at least one resource associated with the configured grant. In one example, the data can be associated with a priority level. Thus, the base station <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for receiving, via a subsequent PUSCH, the adjustment information of the at least one resource associated with the configured grant. For example, in an aspect, the base station <NUM> may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to receive the adjustment information in the form of data bits as a wireless signal or waveform, as described.

In some aspects, the method <NUM> may further include receiving, via PUCCH, the message and the adjustment information of the at least one resource associated with the configured grant. In an aspect, the communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, and/or transceiver <NUM>, may be configured to receive, via PUCCH, the message and the adjustment information of the at least one resource associated with the configured grant. In one example, the data can be associated with a priority level. Thus, the base station <NUM>, the processor(s) <NUM>, the communicating component <NUM> or one of its subcomponents may define the means for receiving, via PUCCH, the message and the adjustment information of the at least one resource associated with the configured grant. For example, in an aspect, the base station <NUM> may further operate the transceiver <NUM>, RF front end <NUM>, and one or more antennas <NUM> to receive the adjustment information in the form of data bits as a wireless signal or waveform, as described.

In some aspects, receiving, via a physical uplink control channel (PUCCH), the message may include receiving adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload including a number of bits or scrambling code used for scrambling the PUCCH.

In some aspects, receiving, via a PUSCH, the message may include receiving adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload including a number of bits or scrambling code used for scrambling the PUCCH.

<FIG> is a block diagram of a MIMO communication system <NUM> including a base station <NUM> and a UE <NUM>. The MIMO communication system <NUM> may illustrate aspects of the wireless communication access network <NUM> described with reference to <FIG>. The base station <NUM> may be an example of aspects of the base station <NUM> described with reference to <FIG>. The base station <NUM> may be equipped with antennas <NUM> and <NUM>, and the UE <NUM> may be equipped with antennas <NUM> and <NUM>. In the MIMO communication system <NUM>, the base station <NUM> may be able to send data over multiple communication links at the same time. Each communication link may be called a "layer" and the "rank" of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station <NUM> transmits two "layers," the rank of the communication link between the base station <NUM> and the UE <NUM> is two.

The UE <NUM> may be an example of aspects of the UEs <NUM> described with reference to <FIG> and <FIG>. At the UE <NUM>, the UE antennas <NUM> and <NUM> may receive the DL signals from the base station <NUM> and may provide the received signals to the modulator/demodulators <NUM> and <NUM>, respectively. Each modulator/demodulator <NUM> through <NUM> may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator <NUM> through <NUM> may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector <NUM> may obtain received symbols from the modulator/demodulators <NUM> and <NUM>, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (Rx) processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE <NUM> to a data output, and provide decoded control information to a processor <NUM>, or memory <NUM>.

The processor <NUM> may in some cases execute stored instructions to instantiate a communicating component <NUM> (see e.g., <FIG> and <FIG>).

The functions described herein may be implemented in hardware, software, or any combination thereof. Due to the nature of software, functions described above can be implemented using software executed by a specially programmed processor, hardware, hardwiring, or combinations of any of these. " That is, unless specified otherwise, or clear from the context, the phrase, for example, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, for example the phrase "X employs A or B" is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. Also, as used herein, including in the claims, "or" as used in a list of items prefaced by "at least one of" indicates a disjunctive list such that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (A and B and C).

Claim 1:
A method of wireless communication at a user equipment, UE, (<NUM>) comprising:
identifying (<NUM>) an upcoming absence of uplink data for transmission on an uplink communication channel to a network entity during a period defined by a configured grant; and
transmitting (<NUM>) a message including adjustment information of at least one resource associated with the configured grant to the network entity (<NUM>), the message triggering adjustment of the at least one resource associated with the configured grant based on identifying the absence of uplink data for transmission on the uplink communication channel, characterized in that the message including the adjustment information is transmitted on a subsequent scheduled physical uplink shared channel, PUSCH, transmission associated with the configured grant after a Layer <NUM> indication is transmitted on a current PUSCH, the Layer <NUM> indication corresponding to a distinct indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.