Method and apparatus for user equipment (UE) assisted uplink resource modification in a wireless communication system

Abstract

The present application relates to user equipment (UE) assisted uplink resource modification. In one implementation, the UE may determine that there is an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant, and transmit a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant. In another implementation, the network entity may receive a message from the UE indicating an impending lack of uplink data on the uplink communication channel during a scheduled period defined by the configured grant, and adjust at least one resource associated with the configured grant in response to receiving the message.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATION(S)

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 975,576, filed on February 12, 2020, entitled “TECHNIQUES FOR UE-ASSISTED UPLINK RESOURCE MODIFICATION IN A WIRELESS COMMUNICATION SYSTEM,” and U.S. Patent Application No. 17 / 173,894, filed on February 11, 2021, entitled “TECHNIQUES FOR UE-ASSISTED UPLINK RESOURCE MODIFICATION IN A WIRELESS COMMUNICATION SYSTEM,” both of which are expressly incorporated herein by reference in their entirety.

[0003] background

[0004] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to user equipment (UE) assisted uplink resource modification.

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). 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.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. For example, the fifth generation (5G) wireless communication technology (which may be referred to as NR) is designed to expand and support diverse usage scenarios and applications relative to current mobile network generations. On the one hand, 5G communication technology may include: enhanced mobile broadband for human-centric use cases for accessing multimedia content, services, and data; ultra-reliable low latency communications (URLLC) with certain specifications on latency and reliability; and massive machine type communications, which may allow very large numbers of connected devices and the transmission of relatively small amounts of non-delay sensitive information.

[0007] For example, for various communication technologies (such as but not limited to NR), some implementations may increase transmission speed and flexibility but also increase transmission complexity. Thus, improvements to wireless communication operations may be desirable.

[0008] Overview

[0009] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0010] An example implementation includes a method of wireless communications at a user equipment (UE), the method comprising determining an impending lack of uplink data for transmission on an uplink communications channel to a network entity during a time period defined by a configured grant, and transmitting a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining the lack of uplink data for transmission on the uplink communications channel.

[0011] Another example implementation includes an apparatus for wireless communication, the apparatus comprising a memory and at least one processor in communication with the memory. The at least one processor may be configured to determine an impending lack of uplink data for transmission on an uplink communication channel to a network entity during a period defined by a configured grant. The at least one processor may be configured to transmit a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining a lack of uplink data for transmission on the uplink communication channel.

[0012] An additional example implementation includes an apparatus for wireless communication. The apparatus includes means for determining an impending lack of uplink data for transmission on an uplink communication channel to a network entity during a period defined by a configured grant, and means for transmitting a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining the lack of uplink data for transmission on the uplink communication channel.

[0013] Another example implementation includes a computer-readable medium storing computer code executable by a processor for wireless communication, the computer code including code for determining an impending lack of uplink data for transmission on an uplink communication channel to a network entity during a time period defined by a configured grant, and code for transmitting a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining the lack of uplink data for transmission on the uplink communication channel.

[0014] Another example implementation includes a method of wireless communications at a network entity, the method comprising receiving a message from a UE indicating an impending lack of uplink data on an uplink communication channel during a scheduled time period defined by a configured grant, and adjusting at least one resource associated with the configured grant in response to receiving the message.

[0015] Another example implementation includes an apparatus for wireless communication, the apparatus comprising a memory and at least one processor in communication with the memory. The at least one processor may be configured to receive a message from a UE indicating an impending lack of uplink data on an uplink communication channel during a scheduled period defined by a configured grant. The at least one processor may be configured to adjust at least one resource associated with the configured grant in response to receiving the message.

[0016] An additional example implementation includes an apparatus for wireless communication. The apparatus may include means for receiving a message from a UE indicating an impending lack of uplink data on an uplink communication channel during a scheduled period defined by a configured grant, and means for adjusting at least one resource associated with the configured grant in response to receiving the message.

[0017] Another example implementation includes a computer-readable medium storing computer code executable by a processor for wireless communication, the computer code including code for receiving a message from a UE indicating an impending lack of uplink data on an uplink communication channel during a scheduled time period defined by a configured grant, and code for adjusting at least one resource associated with the configured grant in response to receiving the message.

[0018] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate rather than limit the disclosed aspects, wherein like reference numerals designate like elements, and wherein:

[0021] Figure 1 An example of a wireless communication system according to various aspects of the present disclosure is illustrated;

[0022] Figure 2 is a block diagram illustrating an example of a network entity (also referred to as a base station) according to various aspects of the present disclosure;

[0023] Figure 3 is a block diagram illustrating an example of a user equipment (UE) according to various aspects of the present disclosure;

[0024] Figure 4A is an example data communication session over time on an uplink in accordance with aspects of the present disclosure;

[0025] Figure 4B is an example medium access control (MAC) signaling session over time on an uplink in accordance with aspects of the present disclosure;

[0026] Figure 4C are example MAC indications and layer 1 signaling over time on the uplink according to aspects of the present disclosure;

[0027] Figure 4D are example layer 1 indications and layer 1 signaling over time on the uplink according to aspects of the present disclosure;

[0028] Figure 4E is example layer 1 signaling over time on the uplink according to aspects of the present disclosure;

[0029] Figure 5 is a flow chart of a method for wireless communication at a UE according to various aspects of the present disclosure;

[0030] Figure 6 is a flowchart of another method for wireless communication at a network entity according to various aspects of the present disclosure; and

[0031] Figure 7 is a block diagram illustrating an example of a MIMO communication system including a base station and UEs according to various aspects of the present disclosure.

[0032] Detailed Description

[0033] Now, various aspects are described with reference to the accompanying drawings. In the following description, for the purpose of explanation, numerous specific details are set forth to provide a thorough understanding of one or more aspects. However, it is apparent that such aspects can also be practiced without these specific details.

[0034] The described features generally relate to UE-assisted uplink resource modification. Specifically, in a new radio (NR) uplink, for periodic data transmitted on the uplink, the network may set a non-dynamic (semi-persistent) grant for such transmission. Using non-dynamic grants can reduce control overhead. In some aspects, there may be two types of non-dynamic grants. The first type may be a configured grant type 1, which provides parameters, configuration information, and activation via radio resource control (RRC) signaling. The second type may be a configured grant type 2, which includes periodic configuration via RRC signaling and activation using a physical downlink control channel (PDCCH), as well as parameter configuration and a media access control (MAC) control element (CE) for confirming the activation signal. In some implementations, if the UE is configured with a non-dynamic grant and the UE has no data to transmit, the UE abandons transmitting the data. However, the UE may benefit from notifying the network when there is a lack of data for uplink transmission associated with the grant, so as to more efficiently utilize resources and potentially save energy at the network.

[0035] In one aspect, the present disclosure includes methods, apparatus (devices), and non-transitory computer-readable media for wireless communications for determining an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a time period defined by a configured grant, and transmitting a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining the lack of uplink data for transmission on the uplink communication channel.

[0036] In another implementation, the present disclosure includes methods, apparatus, and non-transitory computer-readable media for wireless communications for receiving a message from a UE indicating an impending lack 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.

[0037] The following will refer to Figure 1-7 The described features are presented in more detail.

[0038] As used in this application, the terms "component", "module", "system" and similar terms are intended to include computer-related entities, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component can be, but not limited to, a process, a processor, an object, an executable, a thread of execution, a program, and / or a computer running on a processor. As an illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside in a process and / or a thread of execution, and a component may be localized on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media on which various data structures are stored. These components can communicate by means of local and / or remote processes, such as according to a signal having one or more data packets, such as data from a component that interacts with another component in a local system, a distributed system, and / or interacts with other systems across a network such as the Internet. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0039] The technology described herein can be used for various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are usually used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA). CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM TMRadio technologies such as LTE and UTRA. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are new UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio frequency spectrum bands. However, the following description describes an LTE / LTE-A system for example purposes, and LTE terminology is used in most of the following descriptions, but these techniques can also be applied beyond LTE / LTE-A applications (e.g., to fifth generation (5G) NR networks or other next generation communication systems).

[0040] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, substitute, or add various procedures or components. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

[0041] Various aspects or features will be presented in the form of systems that may include a number of devices, components, modules, and the like, etc. It should be understood and appreciated that the various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Combinations of these approaches may also be used.

[0042] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base station 102 (which may also be referred to as a network entity) may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell may include a base station. A small cell may include a femto cell, a pico cell, and a micro cell. In an example, the base station 102 may also include a gNB 180, as further described herein.

[0043] In one example, some nodes, such as base station 102 / gNB 180, may have a modem 240 and a communication component 242 for UE-assisted uplink resource modification, as described herein. Although base station 102 / gNB 180 is shown as having a modem 240 and a communication component 242, this is an illustrative example, and substantially any node may include a modem 240 and a communication component 242 for providing the corresponding functionality described herein.

[0044] In another example, some nodes of the wireless communication system, such as UE 104, may have a modem 340 and a communication component 342 for UE-assisted uplink resource modification, as described herein. Although UE 104 is shown as having a modem 340 and a communication component 342, this is an illustrative example, and substantially any node or type of node may include a modem 340 and a communication component 342 for providing the corresponding functionality described herein.

[0045] The base station 102 configured for 4G LTE (which may be collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a backhaul link 132 (e.g., using an S1 interface). The base station 102 configured for 5G NR (which may be collectively referred to as the Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a backhaul link 184. The base station 102 may perform, among other functions, one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. Base stations 102 may communicate with each other directly or indirectly (e.g., through EPC 160 or 5GC 190) over backhaul links 134 (e.g., using an X2 interface). Backhaul links 132, 134, and / or 184 may be wired or wireless.

[0046] The base station 102 may communicate wirelessly with one or more UEs 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group (which may be referred to as a closed subscriber group (CSG)). The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (e.g., for x component carriers) for transmission in the DL and / or UL direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0047] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0048] The wireless communication system may further include a Wi-Fi access point (AP) 150 in communication with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0049] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0050] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz band” in various documents and articles. Similar naming issues sometimes arise regarding FR2, which is often (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 as the “millimeter wave” (mmW) band by the International Telecommunication Union (ITU).

[0051] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used herein, the term "sub-6 GHz" and the like may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used herein, the term "millimeter wave" and the like may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band. However, communications using mmW radio frequency bands have extremely high path loss and short range. The mmW base station 180 can utilize beamforming 182 with the UE 104 to compensate for the high path loss and short range.

[0052] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0053] 5GC 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 may be a control node that processes signaling between UE 104 and 5GC 190. In general, AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be delivered via UPF 195. UPF 195 may provide UE IP address allocation for one or more UEs and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0054] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable term. Base station 102 provides an access point for UE 104 to EPC 160 or 5GC 190. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, positioning systems (e.g., satellite, terrestrial), multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, robots, drones, industrial / manufacturing equipment, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality eyepieces, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), vehicles / vehicle equipment, meters (e.g., parking meters, electricity meters, gas meters, water meters, flow meters), gas pumps, large or small kitchen appliances, medical / health care equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some UE 104 may be referred to as IoT devices (e.g., meters, gas pumps, monitors, cameras, industrial / manufacturing equipment, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 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 communication 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.

[0055] Now go to Figure 2-Figure 7 , various aspects are depicted with reference to one or more components and one or more methods that can perform the actions or operations described herein, where various aspects in dashed lines may be optional. Figure 5 and 6The operations described in the description are presented in a particular order and / or as being performed by example components, but it should be understood that the order of these actions and the components performing the actions may vary depending on the implementation. Moreover, it should be understood that the following actions, functions, and / or components described may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or by any other combination of hardware components and / or software components capable of performing the described actions or functions.

[0056] refer to Figure 2 , an example of an implementation of a node such as a base station 102 (e.g., base station 102 and / or gNB 180, as described above) may include various components, some of which have been described above and are further described herein, including components such as one or more processors 212 and memory 216 and a transceiver 202 in communication via one or more buses 244, which may operate in conjunction with a modem 240 and / or a communication component 242 for UE-assisted uplink resource modification.

[0057] In one aspect, the one or more processors 212 may include the modem 240 and / or may be part of the modem 240 using one or more modem processors. Thus, various functions associated with the communication component 242 may be included in the modem 240 and / or the processor 212, and in one aspect, may be performed by a single processor, while in other aspects, different ones of these functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 212 may include any one or any combination of the following: 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 the transceiver 202. In other aspects, some of the features of the one or more processors 212 and / or the modem 240 associated with the communication component 242 may be performed by the transceiver 202.

[0058] In addition, the memory 216 can be configured to store local versions of data and / or applications 275 used herein, or the communication component 242 and / or one or more subcomponents thereof executed by the at least one processor 212. The memory 216 can include any type of computer-readable medium usable by a computer or the at least one processor 212, such as random access memory (RAM), read-only memory (ROM), tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when the base station 102 is operating the at least one processor 212 to execute the communication component 242 and / or one or more subcomponents thereof, the memory 216 can be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining the communication component 242 and / or one or more subcomponents thereof and / or data associated therewith.

[0059] The transceiver 202 may include at least one receiver 206 and at least one transmitter 208. The receiver 206 may include hardware for receiving data and / or software executable by a processor, the code including instructions and stored in a memory (e.g., a computer-readable medium). The receiver 206 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 206 may receive signals transmitted by at least one base station 102. In addition, the receiver 206 may process such received signals and may also obtain measurements of the signals, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), and the like. The transmitter 208 may include hardware for transmitting data and / or software executable by a processor, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 208 may include, but are not limited to, an RF transmitter.

[0060] Moreover, in one aspect, the base station 102 may include an RF front end 288 that may operate in communication with one or more antennas 265 and the transceiver 202 for receiving and transmitting radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 288 may be connected to the one or more antennas 265 and may include one or more low noise amplifiers (LNA) 290, one or more switches 292, one or more power amplifiers (PA) 298, and one or more filters 296 for transmitting and receiving RF signals. The antenna 265 may include one or more antennas, antenna elements, and / or antenna arrays.

[0061] In one aspect, the LNA 290 can amplify the received signal to a desired output level. In one aspect, each LNA 290 can have a specified minimum and maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular LNA 290 and its specified gain value based on the desired gain value for a particular application.

[0062] In addition, for example, one or more PAs 298 can be used by the RF front end 288 to amplify the signal to obtain an RF output at a desired output power level. In one aspect, each PA 298 can have a specified minimum and maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular PA 298 and its specified gain value based on the desired gain value for a particular application.

[0063] In addition, for example, one or more filters 296 can be used by the RF front end 288 to filter the received signal to obtain the input RF signal. Similarly, in one aspect, for example, a corresponding filter 296 can be used to filter the output from the corresponding PA 298 to produce an output signal for transmission. In one aspect, each filter 296 can be connected to a specific LNA 290 and / or PA 298. In one aspect, the RF front end 288 can use one or more switches 292 to select a transmit or receive path using a specified filter 296, LNA 290, and / or PA 298 based on the configuration as specified by the transceiver 202 and / or the processor 212.

[0064] As such, the transceiver 202 may be configured to transmit and receive wireless signals through one or more antennas 265 via the RF front end 288. In an aspect, the transceiver may be tuned to operate at a specified frequency so that the UE 104 may communicate, for example, with one or more base stations 102 or one or more cells associated with the one or more base stations 102. In an aspect, the modem 240 may configure the transceiver 202 to operate at a specified frequency and power level based on, for example, a UE configuration of the UE 104 and a communication protocol used by the modem 240.

[0065] In one aspect, modem 240 may be a multi-band-multi-mode modem that may process digital data and communicate with transceiver 202 so that digital data is sent and received using transceiver 202. In one aspect, modem 240 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, modem 240 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, modem 240 may control one or more components (e.g., RF front end 288, transceiver 202) of UE 104 to enable transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, modem configuration may be based on the mode of the modem and the frequency band used. In another aspect, modem configuration may be based on UE configuration information associated with UE 104, such as provided by the network during cell selection and / or cell reselection.

[0066] In one aspect, the processor(s) 212 may correspond to a Figure 6 and 7 Similarly, the memory 216 may correspond to one or more of the processors described in the base station in FIG. Figure 7 The memory described in the base station.

[0067] Reference Figure 3 , an example of an implementation of UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 312 and memory 316 in communication via one or more buses 344 and a transceiver 302, which may operate in conjunction with a modem 340.

[0068] The transceiver 302, receiver 306, transmitter 308, one or more processors 312, memory 316, application 375, bus 344, RF front end 388, LNA 390, switch 392, filter 396, PA 398, and one or more antennas 365 may be the same as or similar to corresponding components of the base station 102 as described above, but are configured or otherwise programmed for base station operations rather than base station operations.

[0069] In one aspect, processor(s) 312 may correspond to a combination of Figure 7 Similarly, the memory 316 may correspond to one or more of the processors described in conjunction with the UE. Figure 7 The memory described by the UE in.

[0070] Figure 4Ais an example data communication session 400 on the uplink over time. For example, from the perspective of the gNB, the lack of data reception may be due to the fact that no data was detected or the UE may have no data to transmit on the uplink. Therefore, the gNB may wait for a number of 'N' missing data receptions before concluding that the UE does not have any data to transmit on the uplink. However, a more efficient and dynamic approach in terms of resource usage may allow the UE to explicitly notify the gNB that resources may no longer be utilized and may therefore be released or suspended for a duration of time. Accordingly, releasing, suspending or skipping resources at the gNB may also create opportunities for network energy savings at the gNB.

[0071] Figure 4B is an example media access control (MAC) signaling session 420 on the uplink over time. In this implementation, one of the triggers for a buffer status report (BSR) transmission may be when there is space left that is not filled with payload to be transmitted. Thus, the UE may include a regular BSR in the payload corresponding to the last uplink data to be transmitted to the network entity (e.g., gNB), rather than including padding. In certain aspects, the BSR MAC CE carries a logical channel group identifier (LCG ID) as well as the buffer size. In addition to the BSR, the UE may also include information related to modifications to non-dynamic resources (e.g., suspending / releasing non-dynamic grants). Such resource modification information may indicate, for example, releasing or suspending resources, suspending length, or skipping resources.

[0072] Figure 4C 430 and Layer 1 signaling 440 over time on the uplink. Specifically, if the information to be communicated to the gNB is larger than the space available in the payload / BSR, the payload / BSR may carry a flag that notifies the gNB that upcoming non-dynamic grant modification information is expected in the next PUCCH or PUSCH transmission. In one aspect, the resource modification information may be transmitted in the PUCCH that occurs 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 the next scheduled PUSCH.

[0073] Figure 4D450 and layer 1 signaling 460 over time on the uplink. Specifically, in some cases, there may be no room left in the last non-dynamically granted carrier data to carry resource modification information on the uplink. In some cases, a modification timeline that is faster than what layer 2 signaling can provide may be desired. In this case, layer 1 signaling may be used to convey the modification information. In one implementation, the layer 1 indication may point to a PUCCH transmission. In another implementation, the layer 1 indication may point to a PUSCH. The PUSCH carrying the last data may use a layer 1 indication to notify the network that the next PUCCH or PUSCH transmission may carry resource modification information and when the PUCCH or PUSCH transmission is expected, or may request a release or suspension to be performed according to some predetermined rule (if previously defined).

[0074] Figure 4E is example layer 1 signaling 470 over time on the uplink. In some aspects, the UE may already have an upcoming PUCCH opportunity. In this scenario, the present implementation may use the scheduled PUCCH opportunity to also transmit resource modifications on the PUCCH. In some aspects, an existing PUCCH format may be used. Otherwise, a new PUCCH format may be defined. In some aspects, if there is no upcoming PUCCH opportunity, the next PUSCH opportunity may be used to carry resource modification information as a known sequence or scrambling code. In one aspect, the resource modification information may correspond to a resource release that provides a complete release of all resources. On the other hand, the resource modification information may correspond to a resource dormancy that provides a resource suspension that begins immediately and lasts for a duration (e.g., 'M' time periods). On the other hand, the resource modification information may correspond to a resource skip that provides for skipping resources for several time periods.

[0075] Figure 5 A flow chart illustrating an example of a method 500 for wireless communication at a UE. In one example, a UE 104 may use Figure 1 , 3 and one or more components described in 7 to perform the functions described in method 500.

[0076] At block 502, the method 500 may determine that there is an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant. In one aspect, the communication component 342 (e.g., in conjunction with the processor(s) 312, the memory 316, and / or the transceiver 302) may be configured to determine that there is an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant. Thus, the UE 104, the processor(s) 312, the communication component 342, or one of its subcomponents may define a means for determining that there is an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant. For example, in one aspect, the UE 104 may determine that there are unused uplink resources based on its uplink data payload and the assigned uplink resources indicated in the uplink grant.

[0077] At block 504, method 500 may transmit a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on a determination of a lack of uplink data for transmission on the uplink communication channel. In one aspect, communication component 342 (e.g., in conjunction with processor(s) 312, memory 316, and / or transceiver 302) may be configured to transmit a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on a determination of a lack of uplink data for transmission on the uplink communication channel. Thus, UE 104, processor(s) 312, communication component 342, or one of its subcomponents may define means for transmitting a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on a determination of a lack of uplink data for transmission on the uplink communication channel. For example, in an aspect, the UE 104 may operate the processor 302 to generate a message in the form of data bits, and may further operate the transceiver 302, the RF front end 388, and the one or more antennas 365 to transmit the data bits as a wireless signal or waveform, as described.

[0078] In certain aspects, this message may be transmitted using a MAC CE.

[0079] In certain aspects, this message may be transmitted using a BSR MAC CE.

[0080] In certain aspects, the message may further include adjustment information for at least one resource associated with the configured grant.

[0081] In certain aspects, transmitting the message may include transmitting the final uplink data and adjustment information using a MAC CE.

[0082] In certain aspects, the MAC CE may be transmitted on the last resource of the PUSCH transmission along with the final uplink data.

[0083] In certain aspects, the message may further include an indication corresponding to a flag indicating that adjustment information is to be transmitted.

[0084] In certain aspects, the indication may further include information about the resource carrying the adjustment information, including an offset from the resource carrying the flag.

[0085] In certain aspects, the method 500 may further include determining that the final uplink data and the buffer status report meet a payload size threshold, the payload size threshold representing a maximum size of a PUSCH transmission corresponding to a defined time period allocated by the configured grant, and transmitting adjustment information of at least one resource associated with the configured grant to the network entity, the indication may correspond to a flag indicating that the adjustment information to be transmitted is transmitted based on the determination that the final uplink data and the buffer status report meet the payload size threshold. In one aspect, the communication component 342 (e.g., in combination with the processor(s) 312, the memory 316, and / or the transceiver 302) may be configured to determine that the final uplink data and the buffer status report meet a payload size threshold, the payload size threshold representing a maximum size of a PUSCH transmission corresponding to a defined time period allocated by the configured grant, and transmitting adjustment information of at least one resource associated with the configured grant to the network entity, the indication may correspond to a flag indicating that the adjustment information to be transmitted is transmitted based on the determination that the final uplink data and the buffer status report meet the payload size threshold. Thus, the UE 104, the processor(s) 312, the communication component 342, or one of its subcomponents may define means for determining that the final uplink data and buffer status report meet a payload size threshold, the payload size threshold representing a maximum size of a PUSCH transmission corresponding to a defined time period allocated by a configured grant, and means for transmitting adjustment information of at least one resource associated with the configured grant to a network entity, the indication of which may correspond to a flag indicating that the adjustment information to be transmitted is transmitted based on the determination that the final uplink data and buffer status report meet the payload size threshold. For example, in one aspect, the UE 104 may compare the size of the uplink data and buffer status report to the payload size threshold and identify whether the comparison meets the threshold to trigger the generation of data bits representing the adjustment information, and may further operate the transceiver 302, the RF front end 388, and the one or more antennas 365 to transmit these data bits as a wireless signal or waveform, as described.

[0086] In certain aspects, the adjustment information may be transmitted on the PUCCH prior to the next scheduled PUSCH transmission associated with the configured grant.

[0087] In certain aspects, the adjustment information may be transmitted on a subsequently scheduled PUSCH transmission associated with a configured grant after a layer 1 indication is transmitted on the current PUSCH, the layer 1 indication corresponding to an indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.

[0088] In certain aspects, the message in the PUSCH may correspond to a layer 1 indication pointing to the transmission of adjustment information on the PUCCH or PUSCH.

[0089] In certain aspects, transmitting the message may include using a configured granted PUSCH transmission to transmit final uplink data and a layer 1 indication corresponding to a payload including a number of bits or a scrambling code used to scramble the PUSCH.

[0090] In some aspects, the method 500 may further include transmitting scheduling information for at least one resource associated with the configured grant via a subsequent PUSCH. In one aspect, the communication component 342 (e.g., in combination with the processor(s) 312, the memory 316, and / or the transceiver 302) may be configured to transmit scheduling information for at least one resource associated with the configured grant via a subsequent PUSCH. Thus, the UE 104, the processor(s) 312, the communication component 342, or one of their subcomponents may define means for transmitting scheduling information for at least one resource associated with the configured grant via a subsequent PUSCH. For example, in one aspect, the UE 104 may operate the processor 302 to generate adjustment information in the form of data bits, and may further operate the transceiver 302, the RF front end 388, and the one or more antennas 365 to transmit these data bits as wireless signals or waveforms, as described.

[0091] In certain aspects, the method 500 may further include transmitting adjustment information for at least one resource associated with the configured grant via the PUCCH. In one aspect, the communication component 342 (e.g., in conjunction with the processor(s) 312, the memory 316, and / or the transceiver 302) may be configured to transmit adjustment information for at least one resource associated with the configured grant via the PUCCH. Thus, the UE 104, the processor(s) 312, the communication component 342, or one of their subcomponents may define means for transmitting adjustment information for at least one resource associated with the configured grant via the PUCCH. For example, in one aspect, the UE 104 may operate the processor 302 to generate the adjustment information in the form of data bits, and may further operate the transceiver 302, the RF front end 388, and the one or more antennas 365 to transmit the data bits as a wireless signal or waveform, as described.

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

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

[0094] In certain aspects, the adjustment of the at least one resource may correspond to at least one of releasing the at least one resource, suspending the at least one resource for a duration, or skipping the at least one resource for a duration.

[0095] Figure 6 A flow chart illustrating an example of a method 600 for wireless communication at a network entity, such as a base station 102. In an example, the base station 102 may use Figure 1 , 2 and one or more components described in 7 to perform the functions described in method 600.

[0096] In block 602, method 600 may receive from a UE a message indicating that uplink data will soon be lacking on an uplink communication channel during a scheduled period defined by a configured grant. In one aspect, communication component 242 (e.g., in combination with processor(s) 212, memory 216, and / or transceiver 202) may be configured to receive from a UE a message indicating that uplink data will soon be lacking on an uplink communication channel during a scheduled period defined by a configured grant. In one example, data may be associated with a priority level. Thus, base station 102, processor(s) 212, communication component 242, or one of its subcomponents may define a device for receiving from a UE a message indicating that uplink data will soon be lacking on an uplink communication channel during a scheduled period defined by a configured grant. For example, in one aspect, base station 102 may further operate transceiver 202, RF front end 288, and one or more antennas 265 to receive a message in the form of data bits as a wireless signal or waveform, as described.

[0097] At block 604, method 600 may adjust at least one resource associated with the configured grant in response to receiving the message. In an aspect, communication component 242 (e.g., in conjunction with processor(s) 212, memory 216, and / or transceiver 202) may be configured to adjust at least one resource associated with the configured grant in response to receiving the message. Thus, base station 102, processor(s) 212, communication component 242, or one of their subcomponents may define means for adjusting at least one resource associated with the configured grant in response to receiving the message. For example, in an aspect, base station 102 may operate processor 202 to process the message and the adjustment of the resource.

[0098] In certain aspects, the method 600 may further include transmitting to the UE an adjustment message indicating an adjustment to at least one resource associated with the configured grant. In one aspect, the communication component 242 (e.g., in conjunction with the processor(s) 212, the memory 216, and / or the transceiver 202) may be configured to transmit to the UE an adjustment message indicating an adjustment to at least one resource associated with the configured grant. In one example, the data may be associated with a priority level. Thus, the base station 102, the processor(s) 212, the communication component 242, or one of its subcomponents may define a means for transmitting to the UE an adjustment message indicating an adjustment to at least one resource associated with the configured grant. For example, in one aspect, the base station 102 may further operate the transceiver 202, the RF front end 288, and the one or more antennas 265 to transmit the adjustment message in the form of data bits as a wireless signal or waveform, as described.

[0099] In certain aspects, the method 600 may further include withdrawing the configured grant in response to adjusting the at least one resource and forgoing transmitting an adjustment message to the UE indicating the adjustment to the at least one resource. In one aspect, the communication component 242 (e.g., in conjunction with the processor(s) 212, the memory 216, and / or the transceiver 202) may be configured to withdraw the configured grant in response to adjusting the at least one resource and forgo transmitting an adjustment message to the UE indicating the adjustment to the at least one resource. In one example, the data may be associated with a priority level. Thus, the base station 102, the processor(s) 212, the communication component 242, or one of its subcomponents may define a means for withdrawing the configured grant in response to adjusting the at least one resource and forgoing transmitting an adjustment message to the UE indicating the adjustment to the at least one resource. For example, in one aspect, the base station 102 may operate the processor 202 to remove the grant and not activate the communication component to transmit the adjustment to the resource.

[0100] In certain aspects, this message may be transmitted using a MAC CE.

[0101] In certain aspects, this message may be transmitted using a BSR MAC CE.

[0102] In certain aspects, the message may further include adjustment information for at least one resource associated with the configured grant.

[0103] In certain aspects, receiving the message may include receiving the final uplink data and adjustment information using a MAC CE.

[0104] In certain aspects, the MAC CE is transmitted along with the final uplink data on the last resource of the PUSCH transmission.

[0105] In certain aspects, the message may further include an indication corresponding to a flag indicating that adjustment information is to be transmitted.

[0106] In certain aspects, the indication may further include information about the resource carrying the adjustment information, including an offset from the resource carrying the flag.

[0107] In certain aspects, the adjustment information may be transmitted on the PUCCH prior to the next scheduled PUSCH transmission associated with the configured grant.

[0108] In certain aspects, the adjustment information may be transmitted on a subsequently scheduled PUSCH transmission associated with the configured grant after the layer 1 indication is transmitted on the current PUSCH carrying the message.

[0109] In certain aspects, the message in the PUSCH may correspond to a layer 1 indication pointing to the transmission of adjustment information on the PUCCH or another PUSCH.

[0110] In certain aspects, receiving the message may include receiving final uplink data using a configured granted PUSCH transmission and a layer 1 indication corresponding to a payload including a number of bits or a scrambling code used to scramble the PUSCH.

[0111] In certain aspects, method 600 may further include receiving adjustment information for at least one resource associated with a configured grant via a PUSCH. In one aspect, communication component 242 (e.g., in conjunction with processor(s) 212, memory 216, and / or transceiver 202) may be configured to receive adjustment information for at least one resource associated with a configured grant via a PUSCH. In one example, the data may be associated with a priority level. Thus, base station 102, processor(s) 212, communication component 242, or one of its subcomponents may define means for receiving adjustment information for at least one resource associated with a configured grant via a PUSCH. For example, in one aspect, base station 102 may further operate transceiver 202, RF front end 288, and one or more antennas 265 to receive adjustment information in the form of data bits of a wireless signal or waveform, as described.

[0112] In certain aspects, the method 600 may further include receiving the message and adjustment information for at least one resource associated with the configured grant via a PUCCH. In one aspect, the communication component 242 (e.g., in conjunction with the processor(s) 212, the memory 216, and / or the transceiver 202) may be configured to receive the message and adjustment information for at least one resource associated with the configured grant via a PUCCH. In one example, the data may be associated with a priority level. Thus, the base station 102, the processor(s) 212, the communication component 242, or one of its subcomponents may define a means for receiving the message and adjustment information for at least one resource associated with the configured grant via a PUCCH. For example, in one aspect, the base station 102 may further operate the transceiver 202, the RF front end 288, and the one or more antennas 265 to receive the adjustment information in the form of data bits of a wireless signal or waveform, as described.

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

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

[0115] In certain aspects, the adjustment of the at least one resource may correspond to at least one of releasing the at least one resource, suspending the at least one resource for a duration, or skipping the at least one resource for a duration.

[0116] Figure 7 1 is a block diagram of a MIMO communication system 700 including a base station 102 and a UE 104. The MIMO communication system 700 may be explained with reference to Figure 1 The wireless communication access network 100 is described in detail. The base station 102 may be a reference Figure 1 Examples of various aspects of base station 102 are described. Base station 102 may be equipped with antennas 734 and 735, and UE 104 may be equipped with antennas 752 and 753. In MIMO communication system 700, base station 102 may be able to send data on multiple communication links simultaneously. Each communication link may be referred to as a "layer", and the "rank" of a communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station 102 transmits two "layers", the rank of the communication link between base station 102 and UE 104 is 2.

[0117] At the base station 102, the transmit (Tx) processor 720 may receive data from a data source. The transmit processor 720 may process the data. The transmit processor 720 may also generate a control symbol or a reference symbol. The transmit MIMO processor 730 may perform spatial processing (e.g., precoding) on ​​the data symbol, the control symbol, or the reference symbol, where applicable, and may provide an output symbol stream to the transmit modulators / demodulators 732 and 733. Each modulator / demodulator 732 to 733 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 732 to 733 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. In one example, the DL signals from the modulators / demodulators 732 and 733 may be transmitted via antennas 734 and 735, respectively.

[0118] UE 104 may be a reference Figure 1 and Figure 3Examples of various aspects of the UE 104 described. At the UE 104, the UE antennas 752 and 753 can receive DL signals from the base station 102 and can provide the received signals to the modulators / demodulators 754 and 755, respectively. Each modulator / demodulator 754 to 755 can condition (e.g., filter, amplify, downconvert, and digitize) the respective received signals to obtain input samples. Each modulator / demodulator 754 to 755 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 756 can obtain the received symbols from the modulator / demodulators 754 and 755, perform MIMO detection on the received symbols where applicable, and provide detected symbols. The receive (Rx) processor 758 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to the data output, and provide decoded control information to the processor 780 or the memory 782.

[0119] Processor 780 may, in some cases, execute stored instructions to instantiate communication component 342 (eg, see Figure 1 and 3 ).

[0120] On the uplink (UL), at the UE 104, a transmit processor 764 may receive and process data from a data source. The transmit processor 764 may also generate reference symbols for a reference signal. The symbols from the transmit processor 764 may be precoded by a transmit MIMO processor 766, if applicable, further processed by modulators / demodulators 754 and 755 (e.g., for SC-FDMA, etc.), and transmitted to the base station 102 according to the communication parameters received from the base station 102. At the base station 102, the UL signal from the UE 74 may be received by antennas 734 and 735, processed by modulators / demodulators 732 and 733, detected by a MIMO detector 736, if applicable, and further processed by a receive processor 738. The receive processor 738 may provide decoded data to a data output and to the processor 740 or memory 742.

[0121] The components of the UE 104 may be implemented individually or collectively with one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the modules mentioned may be a device for performing one or more functions related to the operation of the MIMO communication system 1000. Similarly, the components of the base station 102 may be implemented individually or collectively with one or more ASICs adapted to perform some or all applicable functions in hardware. Each of the components mentioned may be a device for performing one or more functions related to the operation of the MIMO communication system 700.

[0122] Some additional examples

[0123] Aspects described herein may also include one or more of the following implementation examples described in the following numbered clauses.

[0124] 1. A method for wireless communication at a user equipment (UE), comprising:

[0125] determining an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; and

[0126] A message is transmitted to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining a lack of uplink data for transmission on the uplink communication channel.

[0127] 2. The method of clause 1, wherein the message is transmitted using a medium access control (MAC) control element (CE).

[0128] 3. A method as described in any preceding clause, wherein the message is transmitted using a buffer status report (BSR) MAC CE.

[0129] 4. The method of any preceding clause, wherein the message further comprises adjustment information for the at least one resource associated with the configured grant.

[0130] 5. A method as described in any preceding clause, wherein transmitting the message includes using the MAC CE to transmit final uplink data and the adjustment information.

[0131] 6. A method as described in any preceding clause, wherein the MAC CE is transmitted together with final uplink data on the last resource of a Physical Uplink Shared Channel (PUSCH) transmission.

[0132] 7. A method as described in any preceding clause, further comprising determining that the final uplink data and the buffer status report meet a payload size threshold, the payload size threshold representing a maximum size of a physical uplink shared channel (PUSCH) transmission corresponding to a defined time period allocated by the configured grant; and

[0133] transmitting the adjustment information of the at least one resource associated with the configured grant to the network entity,

[0134] The indication corresponds to a flag indicating that the adjustment information to be transmitted is transmitted based on determining that final uplink data and the buffer status report meet a payload size threshold.

[0135] 8. A method as described in any preceding clause, wherein the adjustment information is transmitted on a physical uplink control channel (PUCCH) prior to a subsequent scheduled physical uplink shared channel (PUSCH) transmission associated with the configured grant.

[0136] 9. A method as described in any preceding clause, wherein the message in the PUSCH corresponds to a layer 1 indication, and the layer 1 indication points to the adjustment information transmission on the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH).

[0137] 10. The method of any preceding clause, wherein the message further comprises an indication corresponding to a flag indicating that adjustment information is to be transmitted.

[0138] 11. A method as described in any preceding clause, wherein the indication further includes information about the resource carrying the adjustment information, the information including an offset from the resource carrying the flag.

[0139] 12. A method as described in any of the preceding clauses, wherein the adjustment information is transmitted on a subsequently scheduled physical uplink shared channel (PUSCH) transmission associated with the configured grant after a layer 1 indication is transmitted on a current PUSCH, wherein the layer 1 indication corresponds to a different indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.

[0140] 13. A method as described in any of the preceding clauses, wherein transmitting the message includes using the configured granted physical uplink shared channel (PUSCH) transmission to transmit final uplink data and the layer 1 indication, the layer 1 indication corresponding to a payload including a number of bits or a scrambling code for scrambling the PUSCH.

[0141] 14. A method as described in any preceding clause, further comprising transmitting the adjustment information of the at least one resource associated with the configured grant via a subsequent PUSCH.

[0142] 15. A method as described in any preceding clause, further comprising transmitting the adjustment information of the at least one resource associated with the configured grant via a PUCCH.

[0143] 16. A method as described in any of the preceding clauses, wherein transmitting the message via a physical uplink control channel (PUCCH) includes transmitting adjustment information for the at least one resource associated with the configured grant, the adjustment information corresponding to a payload comprising a number of bits or a scrambling code for scrambling the PUCCH.

[0144] 17. A method as described in any of the preceding clauses, wherein transmitting the message via a physical uplink shared channel (PUSCH) includes transmitting adjustment information for the at least one resource associated with the configured grant, the adjustment information corresponding to a payload comprising a number of bits or a scrambling code for scrambling the PUSCH.

[0145] 18. The method of any preceding clause, wherein the adjustment of the at least one resource corresponds to at least one of:

[0146] releasing the at least one resource,

[0147] suspending the at least one resource for a duration, or

[0148] The at least one resource is skipped for a duration.

[0149] 19. An apparatus for wireless communication, comprising:

[0150] Memory; and

[0151] at least one processor in communication with the memory, wherein the at least one processor is configured to:

[0152] determining an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; and

[0153] A message is transmitted to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining a lack of uplink data for transmission on the uplink communication channel.

[0154] 20. The apparatus of clause 19, wherein the message is transmitted using a medium access control (MAC) control element (CE).

[0155] 21. An apparatus as described in any preceding clause, wherein the message is transmitted using a Buffer Status Report (BSR) MAC CE.

[0156] 22. An apparatus as described in any preceding clause, wherein the message further includes adjustment information for the at least one resource associated with the configured grant.

[0157] 23. An apparatus as described in any preceding clause, wherein transmitting the message is final uplink data and the adjustment information transmitted using the MAC CE.

[0158] 24. An apparatus as described in any preceding clause, wherein the MAC CE is transmitted together with final uplink data on the last resource of a Physical Uplink Shared Channel (PUSCH) transmission.

[0159] 25. An apparatus as described in any preceding clause, wherein the at least one processor is further configured to:

[0160] determining that the final uplink data and the buffer status report satisfy a payload size threshold, the payload size threshold representing a maximum size of a physical uplink shared channel (PUSCH) transmission corresponding to a defined time period allocated by the configured grant; and

[0161] transmitting the adjustment information of the at least one resource associated with the configured grant to the network entity,

[0162] The adjustment information includes a flag indicating that the adjustment information to be transmitted is transmitted based on determining that the final uplink data and the buffer status report meet a payload size threshold.

[0163] 26. An apparatus as described in any preceding clause, wherein the adjustment information is transmitted on a physical uplink control channel (PUCCH) prior to a subsequent scheduled physical uplink shared channel (PUSCH) transmission associated with the configured grant.

[0164] 27. An apparatus as described in any of the preceding clauses, wherein in order to transmit the message via a physical uplink control channel (PUCCH), the at least one processor is further configured to transmit adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload comprising a number of bits or a scrambling code for scrambling the PUCCH.

[0165] 28. An apparatus as described in any preceding clause, wherein in order to transmit the message via a physical uplink shared channel (PUSCH), the at least one processor is further configured to transmit adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload comprising a number of bits or a scrambling code for scrambling the PUSCH.

[0166] 29. A computer readable medium storing computer code executable by a processor for wireless communication, the computer code comprising code for:

[0167] determining an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; and

[0168] A message is transmitted to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining a lack of uplink data for transmission on the uplink communication channel.

[0169] 30. A device for wireless communication, comprising:

[0170] means for determining an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; and

[0171] Means for transmitting a message to the network entity to trigger an adjustment of at least one resource associated with the configured grant based on determining a lack of uplink data for transmission on the uplink communication channel.

[0172] The above detailed description set forth above in conjunction with the accompanying drawings describes examples and does not represent the only examples that can be implemented or fall within the scope of the claims. The term "example" when used in this description means "used as an example, instance, or illustration", rather than "better than" or "better than other examples". This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0173] Information and signals may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, computer executable codes or instructions stored on computer-readable media, or any combination thereof.

[0174] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed with a specially programmed device, such as, but not limited to, a processor designed to perform the functions described herein, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The specially programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0175] The functions described herein may be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, each function may be stored as one or more instructions or codes on or transmitted by a non-transient computer-readable medium. Other examples and implementations fall within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the above functions may be implemented using software, hardware, hard wiring, or any combination thereof executed by a specially programmed processor. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations. In addition, the term "or" is intended to represent an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clearly seen from the context, phrases such as "X adopts A or B" are intended to represent any natural concurrent arrangement. That is, for example, the phrase "X adopts A or B" is satisfied by any of the following instances: X adopts A; X adopts B; or X adopts both A and B. Additionally, as used herein (including in the claims), “or” used in a list of items followed by “at least one of” indicates a disjunctive list so that, for example, a list “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).

[0176] Computer-readable media include both computer storage media and communication media, including any media that facilitates a computer program to be transferred from one place to another. Storage media can be any available media that can be accessed by a general or special-purpose computer. As an example and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code means of an instruction or data structure form and can be accessed by a general or special-purpose computer or a general or special-purpose processor. Similarly, any connection is also properly referred to as a computer-readable medium. For example, if software is transmitted from a website, a server or other remote sources using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, wherein disk usually reproduces data magnetically, while disc reproduces data optically with laser. Combinations of the above media are also included in the scope of computer-readable media.

[0177] The previous description of the disclosure is provided to enable those skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the common principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. In addition, although the elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural is also contemplated unless explicitly stated to be limited to the singular. In addition, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment, unless otherwise stated. Thus, the disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment UE, comprising: identifying an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; as well as A message including adjustment information of at least one resource associated with the configured grant is transmitted to the network entity, the message triggering adjustment of the at least one resource associated with the configured grant based on identifying a lack of uplink data for transmission on the uplink communication channel, wherein the message including the adjustment information is transmitted on a subsequently scheduled PUSCH transmission associated with the configured grant after a layer 1 indication is transmitted on a current physical uplink shared channel PUSCH, the layer 1 indication corresponding to a different indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.

2. The method of claim 1, wherein the message is transmitted using a Medium Access Control (MAC) Control Element (CE).

3. The method of claim 2, wherein the message is transmitted using a Buffer Status Report (BSR) MAC CE. 4 . The method of claim 1 , wherein transmitting the message comprises transmitting the final uplink data and the adjustment information using a medium access control (MAC) control element (CE).

5. The method of claim 3, wherein the MAC CE is transmitted together with final uplink data on the last resource of a physical uplink shared channel (PUSCH) transmission.

6. The method of claim 5, further comprising determining that the final uplink data and the buffer status report satisfy a payload size threshold, the payload size threshold representing a maximum size of a Physical Uplink Shared Channel (PUSCH) transmission corresponding to a 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 adjustment information includes a flag indicating that the adjustment information to be transmitted is transmitted based on determining that the final uplink data and the buffer status report meet a payload size threshold.

7. The method of claim 1, wherein the adjustment information is transmitted on a Physical Uplink Control Channel (PUCCH) prior to a subsequent scheduled Physical Uplink Shared Channel (PUSCH) transmission associated with the configured grant.

8. The method of claim 1, wherein the message in the PUSCH corresponds to a layer 1 indication pointing to the adjustment information on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

9. The method of claim 1, wherein the message further includes an indication corresponding to a flag indicating that the adjustment information is to be transmitted.

10. The method of claim 9, wherein the indication further comprises information about a resource carrying the adjustment information, the information comprising an offset from a resource carrying the flag.

11. The method of claim 1 , wherein transmitting the message comprises transmitting final uplink data and the layer 1 indication using the configured granted physical uplink shared channel (PUSCH) transmission, the layer 1 indication corresponding to a payload including a number of bits or a scrambling code for scrambling the PUSCH.

12. The method of claim 11, further comprising transmitting the adjustment information of the at least one resource associated with the configured grant via a subsequent PUSCH.

13. The method of claim 11, further comprising transmitting the adjustment information of the at least one resource associated with the configured grant via a PUCCH.

14. The method of claim 1, wherein transmitting the message via a physical uplink control channel (PUCCH) comprises transmitting adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload comprising a number of bits or a scrambling code for scrambling the PUCCH.

15. The method of claim 1, wherein transmitting the message via a physical uplink shared channel (PUSCH) comprises transmitting adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload comprising a number of bits or a scrambling code for scrambling the PUSCH.

16. The method of claim 1, wherein the adjustment of the at least one resource corresponds to at least one of: releasing the at least one resource, suspending the at least one resource for a duration, or The at least one resource is skipped for a duration.

17. An apparatus for wireless communication, comprising: Memory; as well as at least one processor in communication with the memory, wherein the at least one processor is configured to: identifying an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; as well as A message including adjustment information of at least one resource associated with the configured grant is transmitted to the network entity, the message triggering adjustment of the at least one resource associated with the configured grant based on identifying a lack of uplink data for transmission on the uplink communication channel, wherein the message including the adjustment information is transmitted on a subsequently scheduled PUSCH transmission associated with the configured grant after a layer 1 indication is transmitted on a current physical uplink shared channel PUSCH, the layer 1 indication corresponding to a different indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.

18. The apparatus of claim 17, wherein the message is transmitted using a Medium Access Control (MAC) Control Element (CE).

19. The apparatus of claim 18, wherein the message is transmitted using a Buffer Status Report (BSR) MAC CE.

20. The apparatus of claim 17, wherein the message is final uplink data and the adjustment information transmitted using a medium access control (MAC) control element (CE).

21. The apparatus of claim 19, wherein the MAC CE is transmitted together with final uplink data on a last resource of a Physical Uplink Shared Channel (PUSCH) transmission.

22. The device according to claim 21, characterized in that The at least one processor is further configured to: determining that the final uplink data and the buffer status report satisfy a payload size threshold, the payload size threshold representing a maximum size of a physical uplink shared channel (PUSCH) transmission corresponding to a defined time 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 adjustment information includes a flag indicating that the adjustment information to be transmitted is transmitted based on determining that the final uplink data and the buffer status report meet a payload size threshold.

23. The apparatus of claim 17, wherein the adjustment information is transmitted on a Physical Uplink Control Channel (PUCCH) prior to a subsequently scheduled Physical Uplink Shared Channel (PUSCH) transmission associated with the configured grant.

24. The apparatus of claim 17, wherein, in order to transmit the message via a physical uplink control channel (PUCCH), the at least one processor is further configured to transmit adjustment information of the at least one resource associated with the configured grant, the adjustment information corresponding to a payload comprising a number of bits or a scrambling code for scrambling the PUCCH.

25. The apparatus of claim 17, wherein to transmit the message via a physical uplink shared channel (PUSCH), the at least one processor is further configured to transmit 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 a scrambling code for scrambling the PUSCH.

26. A non-transitory computer readable medium storing computer code executable by a processor for wireless communication, the computer code comprising code for: identifying an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; and A message including adjustment information of at least one resource associated with the configured grant is transmitted to the network entity, the message triggering adjustment of the at least one resource associated with the configured grant based on identifying a lack of uplink data for transmission on the uplink communication channel, wherein the message including the adjustment information is transmitted on a subsequently scheduled PUSCH transmission associated with the configured grant after a layer 1 indication is transmitted on a current physical uplink shared channel PUSCH, the layer 1 indication corresponding to a different indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.

27. A device for wireless communication, comprising: means for identifying an impending lack of uplink data for transmission to a network entity on an uplink communication channel during a period defined by a configured grant; as well as Means for transmitting to the network entity a message including adjustment information of at least one resource associated with the configured grant, the message triggering adjustment of the at least one resource associated with the configured grant based on identifying a lack of uplink data for transmission on the uplink communication channel, wherein the message including the adjustment information is transmitted on a subsequently scheduled PUSCH transmission associated with the configured grant after a layer 1 indication is transmitted on a current physical uplink shared channel, PUSCH, the layer 1 indication corresponding to a different indication represented by a number of bits or a scrambling code used to scramble the current PUSCH.

Images