Method and apparatus for wireless communication

Abstract

A user equipment (UE) may be provided with multiple scheduling configurations and / or configured grants (CGs). Aspects of the present disclosure provide techniques for sending an indication from a UE to a base station indicating that the UE has no data to send to the BS during an allocated transmission time interval to prevent the base station from allocating resources for transmission.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present application claims the benefit of U.S. Provisional Application No. 62 / 868,473, filed on June 28, 2019, entitled “TECHNIQUES FOR INDICATING LACK OF DATA FOR TRANSMISSION,” and U.S. Patent Application No. 16 / 911,072, filed on June 24, 2020, entitled “TECHNIQUES FOR INDICATING LACK OF DATA FOR TRANSMISSION,” which are assigned to the assignee of the present application and are hereby expressly incorporated herein by reference for all purposes. Background Art Technical Field

[0004] The present disclosure relates generally to communication systems, and more particularly to techniques for a user device to indicate to a base station or other wireless device when data for transmission is lacking at the user device.

[0005] introduce

[0006] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0007] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol, enabling different user equipment to communicate at the city, country, region and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is a continuous evolution of mobile broadband released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR can be based on 4G Long Term Evolution (LTE) standards. There is a need to further improve 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0008] A brief summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive overview of all anticipated aspects, and is not intended to identify key or important elements of all aspects, nor is it intended to delimit the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a concise form before the more detailed description presented later.

[0009] Various aspects of the present disclosure provide techniques for a user equipment (UE) to indicate a lack of data for transmission. For example, the UE may send an indication to a base station indicating that no data is available for transmission, or that no data is to be sent for an allocated transmission time interval (TTI). Such an indication (e.g., a no data indication) may be viewed, for example, by the base station as involving allocation of UE resources. In one example, such a no data indication may cause the base station to not allocate certain additional resources to the UE, for example, for the purpose of retransmission.

[0010] In aspects of the present disclosure, a method, a non-transitory computer-readable medium, and an apparatus are provided to facilitate wireless communication implemented by a UE. The method may include determining whether the UE has any data to send during a configured authorization opportunity assigned to the UE by a base station. The method may also include generating a no data indication based on a determination that the UE does not have any data for transmission during the configured authorization opportunity. In some examples, the method may also include sending a no data indication to the base station.

[0011] In some aspects of the present disclosure, a non-transitory computer-readable medium may include instructions that, when executed by a processor of a UE, cause the processor to determine whether the UE has any data to send during a configured authorization opportunity assigned to the UE by a base station, generate a no-data indication based on a determination that there is no data for transmission during the configured authorization opportunity, and send the no-data indication to the base station.

[0012] In certain aspects, the UE may include a memory storing instructions and a processor communicatively coupled to the memory, the processor configured to execute the instructions to determine whether the UE has any data to send during a configured authorization opportunity assigned to the UE by a base station, generate a no data indication based on a determination that the UE does not have any data for transmission during the configured authorization opportunity, and send the no data indication to the base station.

[0013] Some aspects of the present disclosure include a UE comprising means for determining whether the UE has any data to send during a configured grant opportunity assigned to the UE by a base station, means for generating a no-data indication based on a determination that the UE does not have any data for transmission during the configured grant opportunity, and means for sending the no-data indication to the base station.

[0014] To accomplish the aforementioned and related objectives, 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 one or more aspects. However, these features are merely indicative of several different ways in which the principles of various aspects may be used, and the specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0016] Figure 2A is a diagram showing a first example of a 5G / NR frame.

[0017] Figure 2B is a diagram showing an example of DL channels within a 5G / NR subframe.

[0018] Figure 2C is a diagram showing a second example of a 5G / NR frame.

[0019] Figure 2D is a diagram showing an example of UL channels within a 5G / NR subframe.

[0020] Figure 3A is a first example of a message diagram illustrating example messages and flows for sending a no data indicator from a UE to a base station to prevent the base station from allocating additional resources for retransmission.

[0021] Figure 3B is a second example of a message diagram illustrating example messages and flows for sending a no data indicator from a UE to a base station to prevent the base station from allocating additional resources for retransmission.

[0022] Figure 4 is a flow chart illustrating an example method for UE wireless communications.

[0023] Figure 5 yes Figure 1 A schematic diagram of example components of a UE.

[0024] Figure 6 yes Figure 1 A schematic diagram of example components of a base station.

[0025] Figure 7 is a flow chart illustrating an example method for base station wireless communications. DETAILED DESCRIPTION

[0026] The detailed description set forth below in conjunction with the accompanying drawings is intended to describe various configurations and is not intended to represent that only the configurations of these concepts described herein can be implemented. The detailed description includes specific details for providing a thorough understanding of the purpose of various concepts. However, it is apparent to those skilled in the art that these concepts can be implemented without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams to avoid blurring these concepts.

[0027] In general, one requirement of wireless communication is to minimize the packet transmission delay for reliable and low-latency service. Existing wireless systems have several fundamental limitations that prevent them from supporting low latency. For example, one obstacle is the radio resource allocation delay between the base station and one or more user equipments (UEs). When the UE wants to send a packet, the radio resource authorization process precedes the packet transmission. In order to send a resource scheduling request and send a packet on the scheduled resources, the UE needs at least eight (8) milliseconds (ms). In Long Term Evolution (LTE), the semi-persistent scheduling (SPS) feature is introduced for periodic data transmission for services such as Voice over IP (VoIP). When the base station configures SPS radio resources, the UE can use the periodic resources without an additional scheduling request process. However, a disadvantage of this implementation is that when the UE has no data to send, the resources are usually wasted and idle.

[0028] In order to reduce the waste of periodically allocated resources, 5G implements the sharing of resources via one or more scheduling configurations and / or configured authorizations. In such an implementation, the base station can allocate one or more scheduling configurations and / or configured authorization resources to the requesting UE, and the UE can use the resource when they have data to send. By allocating scheduling configurations and / or configured authorization resources, the 5G network eliminates the packet transmission delay of the scheduling request process and increases the utilization rate of the allocated periodic wireless resources. However, in some cases, the UE may not have any data to send, and will still be, is being or has been allocated resources by the base station for a specific transmission time interval (TTI). In this case, if the base station does not receive any uplink data from the UE on the allocated resources during the expected TTI, the base station can assume that the uplink data may have been lost in transmission (for example, due to poor channel conditions or communication links). In this way, the base station can allocate a second set of resources to the UE to attempt retransmission. However, allocating another set of resources to send non-existent data from the UE will waste additional resources that can be allocated to other transmissions of other UEs.

[0029] Various aspects of the present disclosure provide techniques for sending an indication from a UE to a base station indicating that no data has been, is being, or will be sent during an allocated transmission time interval to prevent the reallocation of resources for retransmission. In one example, the UE may send an indication that no data is being sent in at least a portion of the allocated configured grant and / or scheduling configuration. To this end, the time resources of each scheduling configuration and / or configured grant opportunity may be divided into a plurality of portions: a first time period for sending an indication of whether the UE has data to send and a second time period for sending data (if available) on a physical uplink shared channel (PUSCH). Thus, if the UE has data to send, the UE may send a PUSCH, and if there is no data to send, a "no data" indication is sent. Such signaling may prevent the base station from allocating additional resources for retransmission.

[0030] Additionally or alternatively, the time resources of each configured grant opportunity may not be time division multiplexed (TDM). In fact, in some cases, if PUSCH is transmitted, it may partially or completely overlap in time / frequency with the region where the no data indicator is transmitted. In addition, it should be understood that the no data indicator may not necessarily use all resource elements (REs) of an orthogonal frequency division multiplexing (OFDM) symbol. Instead, the no data indicator may be transmitted on one or more REs in one or more OFDM symbols.

[0031] In another example, the no data indication may be sent on resources shared by multiple UEs. In other words, each UE may not need dedicated resources for sending a no data indication to the base station to save signaling overhead. In such an implementation, one or more UEs may select resources to send a no data indication randomly or based on the order of PUSCH opportunities that are sensed to have no energy. If the UE selects resources randomly, the base station may use a pseudo-omnidirectional beam to receive potential indicators from unknown UEs. Conversely, if the UE selects resources based on sensed energy, the base station may predict the UE in the same manner on each resource and prepare the corresponding receiver beam to receive the indication with improved link quality.

[0032] Additionally, in some cases, no data indications may be aligned across different cells to prevent interference with PUSCH transmissions from neighboring cells. As such, the duration for no data indications may be exchanged and coordinated by the base station between multiple cells so that each cell may schedule uplink data transmissions that are rate matched around the no data indicator duration of the neighboring cells to avoid interference.

[0033] In some examples, the no data indication may be an invalid blank packet or alternatively a "null packet" (e.g., sending a packet that contains no actual data but only a packet header) to prevent the base station from allocating additional resources for retransmission. In such a case, the packet may be one or both of a buffer status report (BSR) or a power headroom report (PHR). For example, if the BSR value indicates that there is data in the buffer, the UE may send a BSR, otherwise a PHR. This may be accomplished by explicitly setting the BSR / PHR trigger configuration parameters so that the report is always sent, or by bypassing specific conditions of the BSR / PHR reporting rules for these IIOT / CG configurations. Finally, it should be understood that the base station may switch between the multiple types of configurations discussed above based in part on load factors (e.g., the percentage of time the UE has data to send).

[0034] Several aspects of telecommunication systems are now presented with reference to various devices and methods. These devices and techniques are described in the following detailed description and illustrated in the accompanying drawings by various block components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0035] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, or other suitable hardware configured to perform the functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other, software should be broadly understood to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc.

[0036] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium, or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the aforementioned types, or any other medium that can be used to store computer executable code in the form of instructions or data structures and can be accessed by a computer.

[0037] Figure 1 1 is a diagram showing 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)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and a 5G core (5GC) 190. The base station 102 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 includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0038] In certain aspects, one or more of the UEs 104 may include a scheduling configuration component 140 configured to manage uplink communications during configured grant periods. The scheduling configuration component 140 may include a buffer status component 142 for determining whether the UE 104 has any data to transmit during a configured grant opportunity assigned to the UE by the base station 102. The scheduling configuration component 140 may include a message generation component 144 for generating a no data indication based on a determination that the UE transmission buffer fails to include any data for transmission during the configured grant opportunity assigned to the UE. The scheduling configuration component 140 may include an uplink resource selection component 146 for determining, via the transceiver 502 (see Figure 5 ) sends a no data indication to the base station to prevent the base station from allocating additional resources to the UE for retransmission.

[0039] A base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may be connected to the EPC 160 via a backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) may be connected to the 5GC 190 via a backhaul link 184. The base station 102 may perform one or more of the following functions, among other functions: transmission of user data, wireless 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 device tracking, RAN information management (RIM), paging, positioning, and warning messaging. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 / 5GC 190) via a backhaul link 134 (eg, an X2 interface). The backhaul link 134 may be wired or wireless.

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

[0041] Certain 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 various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0042] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152, for example, in a 5 GHz or other similar unlicensed spectrum via a communication link 154. When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0043] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell base station 102' can use NR technology and use the same (e.g., 5 GHz) unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' using NR in the unlicensed spectrum can expand the coverage of the access network or increase the capacity of the access network.

[0044] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, may operate in one or more frequency bands within the electromagnetic spectrum. The electromagnetic spectrum is often subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with the band names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes occur in FR2, although unlike the extremely high frequency (EHF) band (30GHz-300GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the "millimeter wave" (mmW) band in documents and articles.

[0045] In the case of the above aspects, unless otherwise explicitly stated, it should be understood that the terms "sub-6 GHz" and the like used herein can broadly represent frequencies less than 6 GHz, within FR1, or including mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that the terms "millimeter wave" and the like used herein can broadly represent frequencies including mid-band frequencies, within FR2, or within the EHF band. Communications using mmW / near mmW radio frequency bands have extremely high path loss and short distances. The mmW base station 180 can use beamforming 182 with the UE 110 to compensate for the path loss and short distance.

[0046] 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 communicate 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. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted 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 the IP service 176. The IP service 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 that broadcasts a specific service, and may be responsible for session association (start / stop) and collecting eMBMS-related billing information.

[0047] 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 communicate with unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.

[0048] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), or some other appropriate term. Base station 102 provides an access point to EPC 160 or 5GC 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electronic meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, 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 handheld device, a user agent, a mobile client, a client, or some other suitable terminology.

[0049] Figure 2A FIG200 is a diagram showing an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram showing an example of DL channels within a 5G / NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram showing an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure can be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to DL or UL, or the 5G / NR frame structure can be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are used for both DL and UL. Figure 2A , 2CIn the example provided, the 5G / NR frame structure is assumed to be TDD, with subframe 4 configured with slot format 28 (mostly DL), and subframe 3 configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is used flexibly between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with a slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). It should be noted that the following description also applies to the 5G / NR frame structure of TDD.

[0050] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Depending on the slot configuration, each time slot may include 7 or 14 symbols. For slot configuration 0, each time slot may include 14 symbols, and for slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiplexing (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots in a subframe is based on the slot configuration and parameter set. For slot configuration 0, different parameter sets μ0 to 5 allow 1, 2, 4, 8, 16 and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4 and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframes. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15kKz, where μ is parameter set 0-5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D An example is provided for slot configuration 0 with 14 symbols per slot, parameter set μ=0 and 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is approximately 66.7 μs.

[0051] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) that extends to 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0052] like Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration). x , where x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0053] Figure 2B An example of each DL channel within a subframe of a frame is shown. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE includes nine RE groups (REGs), and each REG includes four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) not sent over the PBCH, and paging messages.

[0054] like Figure 2CAs shown, some of the REs carry DM-RS for channel estimation on the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. Although not shown, the UE can send a sounding reference signal (SRS). The SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0055] Figure 2D An example of each UL channel within a subframe of a frame is shown. The PUCCH may be located as indicated in a configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0056] Figure 3A 300 is an example message diagram between a base station 102 and a UE 104 for indicating that the UE 104 has no data to transmit during a scheduling configuration and / or a configured grant period to prevent the base station 102 from scheduling retransmission resources. In one example, the UE 104 may send an indication that no data is being transmitted in at least a portion of the allocated configured grant and / or the scheduling configuration. Although the following examples show resource allocations and / or "no data" indications associated with one or more configured grants, aspects of the present disclosure may also include resource allocations and / or "no data" indications during a scheduling configuration period.

[0057] To this end, the time resources 305 for each configured grant opportunity for each UE 104 can be divided into multiple parts: a first time period 310 for sending an indication of whether the UE 104 has data to send and a second time period 315 for sending data on the PUSCH (if available) within the same configured grant period. In this way, if the UE 104 has data to send, the UE 104 can send the PUSCH, and if there is no data to send, send a "no data" indication.

[0058] For example, Figure 3AAs shown, the time resources of the first configured authorization opportunity (or period) 305-a associated with the first UE 104-a (UE1) can be divided into a first time period 310-a for sending a no data indicator if the first UE 104-a determines that there is no data waiting for transmission in the transmission buffer, and a second time period 315-b when the first UE 104-a has data to send. In the example shown, since the first UE 104-a indicates that the first UE 104-a does not intend to send any data to the base station 102, the first UE 104-a can send a no data indication 320 during the first time period 310-a of the first configured authorization opportunity 305-a. In this way, the first UE 104-a can omit sending any data during the second time period 315-b (the dotted line shows the lack of transmission). By sending the no data indicator 310-a, the base station 102 can be prevented from mistakenly believing that the data from the first UE 104-a is lost in transmission, and scheduling additional resources that may be wasted for retransmission.

[0059] However, in the example shown, the second UE 104-b may have data to send. Thus, during a second configured authorization opportunity 305-b associated with the second UE 104-b (UE2), the second UE 104-b may send the data on the PUSCH 325 during a second time period 315-b of the second configured authorization opportunity 305-b (the dashed line of the no data indicator 310 indicates that the no data indicator is not sent for UE2). Similarly, for the third UE 104-c, based on the determination that the third UE 104-c has data to send, the data 330 associated with the third UE 104-c may also be sent during the second time period 315-c of the third configured authorization opportunity 305-c.

[0060] It should be understood that the time resource of each configured grant opportunity 305 may not be TDM. In fact, in some cases, if PUSCH 315 is transmitted, it may partially or completely overlap in time / frequency with the region where no data indicator 310 is transmitted. In addition, it should be understood that no data indicator 310 may not necessarily use all REs of an OFDM symbol. Instead, the no data indicator may be transmitted on one or more REs in one or more OFDM symbols.

[0061] Figure 3BFIG. 350 is another example message between base station 102 and UE 104 for indicating that UE 104 has no data to send during a configured grant period to prevent base station 102 from scheduling retransmission resources. In an alternative example, the no data indication may be sent on resources shared by multiple UEs. In other words, each UE may not need dedicated resources for sending no data indications to the base station to save signaling overhead. For example, Figure 3B As shown by the dashed lines of the PUSCH in FIG. 3 (see elements 355 and 365), the first UE 104-a (UE1) and the third UE 104-c (UE3) do not have any data to send. In contrast, only the second UE 104-b (UE2) has data 360 to send to the UE during the configured grant opportunity.

[0062] In such an implementation, the first UE 104-a (UE1) and the third UE 104-c (UE3) can select resources randomly or according to the order of PUSCH opportunities sensed to have no energy to send no data indications (e.g., send no data indicators 370 and 375 for UE1 and UE3). If the UE 104 selects resources randomly, the base station 102 can use a pseudo-omni-directional beam to receive potential indicators from unknown UEs. In contrast, if the UE selects resources based on sensed energy, the base station can predict the UE in the same manner on each resource and prepare the corresponding receiver beam to receive the indication with improved link quality.

[0063] It should also be appreciated that in some cases, no data indications may be aligned across different cells to prevent interference with PUSCH transmissions from neighboring cells. As such, the durations for no data indications may be exchanged and coordinated by the base station between multiple cells so that each cell may schedule uplink data transmissions that are rate matched around the no data indicator durations of neighboring cells to avoid interference.

[0064] In a further example, the no data indication may be an invalid blank packet or alternatively a "null packet" (e.g., a packet that contains no actual data is sent) to prevent the base station from allocating additional resources for retransmission. In such a case, the packet may be one or both of a buffer status report (BSR) or a power headroom report (PHR). For example, if the BSR value indicates that there is data in the buffer, the UE may send a BSR, otherwise a PHR. This may be accomplished by explicitly setting the BSR / PHR trigger configuration parameters so that the report is always sent, or by bypassing specific conditions for the BSR / PHR reporting rules for these IIOT / CG configurations. Finally, it should be understood that the base station may switch between the multiple types of configurations discussed above based in part on load factors (e.g., the percentage of time the UE has data to send).

[0065] In some implementations, the no data indication in the uplink may be packaged into the PUSCH as a separate medium access control (MAC) control element (CE).

[0066] In some aspects of the present disclosure, transmission of a "no data" indication by a UE may occur before (eg, a scheduling configuration period) the grant of resources, simultaneously (at least partially) with the grant of resources, and / or after the grant of resources.

[0067] In other aspects, the transmission of the "no data" indication may indicate to the UE that no data has been, is being, or will be sent by the UE to the BS. For example, the UE may send the "no data" indication before resources have been allocated by the BS to the UE to inform the BS that the UE will not send any data to the BS. In another example, the UE may send the "no data" indication while resources are being allocated by the BS to the UE. In some examples, the UE may send the "no data" indication after one or more resources have been allocated by the BS. In response, the BS may reserve, reallocate, and / or deny the resources allocated to the UE.

[0068] Figure 4 4 is a flow chart illustrating an example method 400 for sending a no data indication to a base station to prevent reallocation of additional resources in a configured grant. The method 400 may be performed by a UE 104 including a scheduling configuration component 140 and its subcomponents. The method 400 may include communications with one or more base stations 102.

[0069] At block 410, method 400 may include determining whether the UE has any data to send during a configured grant opportunity assigned to the UE by the base station. In one aspect, for example, the UE 104, processor 512, and / or modem 514 may execute a buffer status component 142 to receive an indication of whether the UE has any data waiting to be transmitted to the base station in a current configured grant time interval. Thus, the UE 104, processor 512, and / or modem 514 executing the scheduling configuration component 140 and / or the buffer status component 142, or one of its subcomponents, may define a component for determining whether the UE 104 has any data to send during a configured grant opportunity assigned to the UE 104 by the base station 102.

[0070] At block 420, method 400 may include generating a no data indication based on a determination that the UE does not have any data for transmission during a configured authorization opportunity. In one aspect, for example, the UE 104, the processor 512, and / or the modem 514 may execute a message generation component 144 to generate an indication for sending to a base station that identifies whether the UE has any data to send during a configured authorization opportunity. In some examples, the no data indication may be a blank packet sent to the base station to prevent the base station from allocating additional resources. The blank packet may include one or both of a BSR or a PHR. Thus, the UE 104, the processor 512, and / or the modem 514 that executes the scheduling configuration component 140 and / or the message generation component 144 or one of its subcomponents may define a component for generating a no data indication based on a determination that the UE does not have any data for transmission during a configured authorization opportunity.

[0071] At block 430, method 400 may include sending a no data indication to a base station. In one aspect, for example, UE 104, processor 512, modem 514, and / or transceiver 502 may execute uplink resource selection component 146 to send a no data indication message generated by UE 104 to base station 102. In certain implementations, UE 104 may send a no data indication to BS 102 to prevent BS 102 from allocating additional resources to UE 104 for retransmission. In some examples, the configured grant opportunity may include a first time period for UE 104 to send an indication of whether the UE has any data to send and a second time period for sending data on PUSCH if UE 104 has data to send. In other examples, the no data indicator and PUSCH may partially overlap in one or both of time or frequency within the region of the configured grant opportunity. To this end, in some aspects, when there is no data to send, UE 104 may send a no data indication during the configured grant opportunity (e.g., during the first time period). However, if UE 104 determines that there is data to be sent, then UE 104 can send data in PUSCH during the second time period. In this case, when there is data to be sent, UE 104 can decide not to send any indication during the first time period, or alternatively, UE 104 can send a message indicating that UE 104 will send a message later. In some cases, the no data indication can be sent using less than all available resource elements in the OFDM symbol. Thus, the processor 512, transceiver 502 and / or modem 514 that executes the scheduling configuration component 140 and / or the uplink resource selection component 146 or one of its subcomponents can define a component for sending a no data indication to the base station.

[0072] For example, at sub-block 432, block 430 optionally includes selecting an uplink resource from a plurality of available resources allocated to the plurality of UEs and / or sending a no-data indication using the selected uplink resource. For example, uplink resource selection component 146 may be configured to randomly select a resource allocated to any one of the plurality of UEs to send an indication that first UE 104 is not transmitting data during a configured grant opportunity associated with the first UE. The plurality of available resources allocated to the plurality of UEs may be allocated for transmission of no-data indications and / or other uplink transmissions of data and / or control information.

[0073] As another example, at sub-block 434, block 430 optionally includes selecting uplink resources to send a no-data indication based at least in part on an order of PUSCH opportunities sensed to have no energy and / or sending a no-data indication using the selected uplink resources.

[0074] As another example, at sub-block 436, block 430 optionally includes aligning the timing of sending a no data indication in the first cell to the base station with the timing of uplink communication in at least one second cell. For example, the timing duration for sending the no data indicator can be aligned across different neighboring cells so that a transmission from one cell does not interfere with a transmission of a PUSCH in a neighboring cell. Thus, the duration for the no data indicator can be exchanged between cells so that each cell can schedule uplink data transmission that is rate matched around the no data indicator duration of the neighboring cell to avoid interference.

[0075] refer to Figure 5 , an example of an implementation of the UE 104 may include components, some of which have been described above, and also include components such as one or more processors 512 and memory 516 and transceiver 502 that can operate in conjunction with modem 514 and communicate via one or more buses 544, and a scheduling configuration component 140 to implement one or more functions described herein regarding sending a no data indication to a base station when the UE does not have any data to send during a configured grant opportunity. In addition, one or more processors 512, modem 514, memory 516, transceiver 502, RF front end 588 and one or more antennas 565 can be configured to support voice and / or data calls (simultaneously or non-simultaneously) in one or more radio access technologies. Antenna 565 may include one or more antennas, antenna elements and / or antenna arrays.

[0076] In one aspect, the one or more processors 512 may include a modem 514 using one or more modem processors. The functions associated with the scheduling configuration component 140 may be included in the modem 514 and / or the processor 512, and in one aspect, may be performed by a single processor, while in other aspects, different ones of the functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 512 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with the transceiver 502. In other aspects, some of the features of the one or more processors 512 and / or the modem 514 associated with the scheduling configuration component 140 may be performed by the transceiver 502.

[0077] Likewise, the memory 516 can be configured to store data used herein and / or local versions of one or more of the applications 575, the scheduling configuration component 140, and / or its subcomponents executed by the at least one processor 512. The memory 516 can include any type of computer-readable medium usable by a computer or the at least one processor 512, such as random access memory (RAM), read-only memory (ROM), tape, disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, the memory 516 can be a non-transitory computer-readable storage medium storing one or more computer-executable codes that define one or more of the scheduling configuration component 140 and / or its subcomponents and / or data associated therewith when the UE 104 is operating the at least one processor 512 to execute the scheduling configuration component 140 and / or its one or more subcomponents.

[0078] The transceiver 502 may include at least one receiver 506 and at least one transmitter 508. The receiver 506 may include hardware, firmware, and / or software code executable by a processor for receiving data, the code including instructions and stored in a memory (e.g., a computer-readable medium). The receiver 506 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 506 may receive signals transmitted by at least one base station 102. Additionally, the receiver 506 may process such received signals and may also obtain measurements of the signals, such as but not limited to Ec / Io, SNR, RSRP, RSSI, etc. The transmitter 508 may include hardware, firmware, and / or software code executable by a processor for sending data, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 508 may include, but are not limited to, an RF transmitter.

[0079] In addition, in an aspect, the UE 104 may include an RF front end 588 that may be operable to communicate with the one or more antennas 565 and the transceiver 502 to receive and transmit wireless transmissions, such as wireless communications transmitted by at least one base station 102 or wireless communications transmitted by the UE 104. The RF front end 588 may be connected to the one or more antennas 565 and may include one or more low noise amplifiers (LNAs) 590, one or more switches 592, one or more power amplifiers (PAs) 598, and one or more filters 596 to transmit and receive RF signals.

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

[0081] In addition, for example, one or more PAs 598 can be used by the RF front end 588 to amplify the signal of the RF output at a desired output power level. In one aspect, each PA 598 can have a specified minimum and maximum gain value. In one aspect, the RF front end 588 can use one or more switches 592 to select a specific PA 598 and its specified gain value based on the desired gain value of a particular application.

[0082] Likewise, for example, one or more filters 596 can be used by the RF front end 588 to filter received signals to obtain input RF signals. Similarly, in one aspect, for example, each filter 596 can be used to filter the output from the corresponding PA 598 to generate an output signal for transmission. In one aspect, each filter 596 can be connected to a specific LNA 590 and / or PA 598. In one aspect, the RF front end 588 can use one or more switches 592 to select a transmit or receive path using a specified filter 596, LNA 590, and / or PA 598 based on a configuration specified by the transceiver 502 and / or the processor 512.

[0083] As such, the transceiver 502 may be configured to transmit and receive wireless signals via the RF front end 588 via the one or more antennas 565. In an aspect, the transceiver 502 may be tuned to operate at a specified frequency so that the UE 104 may communicate with, for example, 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 514 may configure the transceiver 502 to operate at a specified frequency and power level based on, for example, a UE configuration of the UE 54 and a communication protocol used by the modem 514.

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

[0085] refer to Figure 6 , an example of an implementation of the base station 102 may include components, some of which have been described above, and also include components such as one or more processors 612 and memory 616 and transceiver 602 that can operate in conjunction with modem 614 and communicate via one or more buses 644, and a communication component 620 to implement one or more functions described herein related to receiving a no data indication from a UE when the UE does not have any data to send during a configured authorization opportunity. The base station 102 may include a resource component 622 that manages resources scheduled and / or allocated to one or more UEs in a communication network. In addition, the one or more processors 612, modem 614, memory 616, transceiver 602, RF front end 688 and one or more antennas 666 can be configured to support voice and / or data calls (simultaneously or non-simultaneously) in one or more radio access technologies. The antenna 666 may include one or more antennas, antenna elements and / or antenna arrays.

[0086] In one aspect, the one or more processors 612 may include a modem 614 using one or more modem processors. The functions associated with the communication component 620 and / or the resource component 622 may be included in the modem 614 and / or the processor 612, and in one aspect, may be performed by a single processor, while in other aspects, different ones of the functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 612 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with the transceiver 602. In other aspects, some of the features of the one or more processors 612 and / or the modem 614 associated with the communication component 620 and / or the resource component 622 may be performed by the transceiver 602.

[0087] Likewise, the memory 616 may be configured to store data used herein and / or local versions of one or more of the applications 675, the communication component 620, and / or the resource component 622, and / or subcomponents thereof executed by the at least one processor 612. The memory 616 may include any type of computer-readable medium usable by a computer or the at least one processor 612, such as a random access memory (RAM), a read-only memory (ROM), a tape, a disk, an optical disk, a volatile memory, a non-volatile memory, and any combination thereof. In one aspect, for example, the memory 616 may be a non-transitory computer-readable storage medium storing one or more computer-executable codes that define one or more of the communication component 620, the resource component 622, and / or subcomponents thereof and / or data associated therewith when the base station 102 is operating the at least one processor 612 to execute the communication component 620, the resource component 622, and / or one or more subcomponents thereof.

[0088] The transceiver 602 may include at least one receiver 606 and at least one transmitter 608. The receiver 606 may include hardware, firmware, and / or software code executable by a processor for receiving data, the code including instructions and stored in a memory (e.g., a computer-readable medium). The receiver 606 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 606 may receive a signal transmitted by at least one UE 104. Additionally, the receiver 606 may process such received signals and may also obtain measurements of the signals, such as but not limited to Ec / Io, SNR, RSRP, RSSI, etc. The transmitter 608 may include hardware, firmware, and / or software code executable by a processor for transmitting data, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 608 may include, but are not limited to, an RF transmitter.

[0089] In addition, in an aspect, the base station 102 may include an RF front end 688 that may be operable to communicate with one or more antennas 666 and the transceiver 602 to receive and transmit wireless transmissions, such as wireless communications transmitted by at least one base station 102 or wireless communications transmitted by the UE 104. The RF front end 688 may be connected to the one or more antennas 666 and may include one or more low noise amplifiers (LNAs) 690, one or more switches 692, one or more power amplifiers (PAs) 698, and one or more filters 696 to transmit and receive RF signals.

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

[0091] In addition, for example, one or more PAs 698 can be used by the RF front end 688 to amplify the signal of the RF output at a desired output power level. In one aspect, each PA 698 can have a specified minimum and maximum gain value. In one aspect, the RF front end 688 can use one or more switches 692 to select a specific PA 698 and its specified gain value based on the desired gain value for a particular application.

[0092] Likewise, for example, one or more filters 696 can be used by the RF front end 688 to filter received signals to obtain input RF signals. Similarly, in one aspect, for example, each filter 696 can be used to filter the output from the corresponding PA 698 to generate an output signal for transmission. In one aspect, each filter 696 can be connected to a specific LNA 690 and / or PA 698. In one aspect, the RF front end 688 can use one or more switches 692 to select a transmit or receive path using a specified filter 696, LNA 690, and / or PA 698 based on a configuration specified by the transceiver 602 and / or the processor 612.

[0093] As such, the transceiver 602 may be configured to transmit and receive wireless signals via the RF front end 688 via one or more antennas 666. In an aspect, the transceiver 602 may be tuned to operate at a specified frequency so that the base station 102 can communicate with, for example, one or more UEs 104. In an aspect, the modem 614 may configure the transceiver 602 to operate at a specified frequency and power level based on, for example, the base station configuration of the base station 102 and the communication protocol used by the modem 614.

[0094] In one aspect, the modem 614 can be a multi-band-multi-mode modem that can process digital data and communicate with the transceiver 602 so that the digital data is sent and received using the transceiver 602. In one aspect, the modem 614 can be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, the modem 614 can be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 614 can control one or more components of the base station 102 (e.g., RF front end 688, transceiver 602) to enable the transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, the modem configuration can be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration can be based on base station configuration information associated with the base station 102.

[0095] Figure 7 700 is a flow chart illustrating an example method 700 of receiving a no data indication by a base station to prevent allocation of resources associated with a configured grant. The method 700 may be performed by a base station 102 including a communication component 620 and / or a resource component 622 and subcomponents thereof. The method 700 may include communication with one or more UEs 104.

[0096] At block 710, method 700 optionally allocates resources associated with the transmission of uplink information to a user equipment (UE). In one aspect, for example, base station 102, processor 612, and / or modem 614 may execute resource component 622 of base station 102 to allocate resources associated with the transmission of uplink information of UE 104 to UE 104. In some variants, base station 102 may schedule resources to UE 104 for uplink information transmission. In some implementations, one or more of processor 612, modem 614, resource component 622, and / or subcomponents may define a component for allocating resources associated with the transmission of uplink information of UE 104 to UE 104.

[0097] At block 720, the method 700 may receive a no-data indication from the UE. For example, the antenna 666, RF front end 688, transceiver 602, receiver 606, processor 612, modem 614, and / or communication component 620 of the base station 102 may receive a no-data indication from the UE 104. The base station 102 may receive the no-data indication before, during, or after scheduling resources, allocating resources, and / or sending an indication of allocated resources. In some implementations, the RF front end 688 may receive an electrical signal converted from an electromagnetic signal. The RF front end 688 may filter and / or amplify the electrical signal. The transceiver 602 or the receiver 606 may convert the electrical signal into a digital signal and send the digital signal to the communication component 620. In some implementations, the antenna 666, RF front end 688, transceiver 602, receiver, processor 612, modem 614, and / or communication component 620 of the base station 102 may define a component for receiving a no-data indication from the UE 104.

[0098] At block 730, the method 700 may withdraw resources allocated to the UE in response to receiving the no data indication. In one aspect, for example, the base station 102, the processor 612, and / or the modem 614 may execute the resource component 622 of the base station 102 to withdraw resources allocated to the UE 104. In some variations, at block 732, the base station 102 may avoid allocating resources to the UE 104. In some variations, at block 734, the base station 102 may reallocate resources. For example, the base station 102 may terminate scheduling of resources after receiving the no data indication. In another example, the base station 102 may withdraw resources allocated to the UE 104. In some examples, the base station 102 may reallocate resources for the UE 104 for another transmission / reception not associated with the no data indication, or reallocate resources to another UE 104. In some implementations, one or more of the processor 612, the modem 614, the resource component 622, and / or the subcomponents may define a means for withdrawing resources allocated to the UE in response to receiving the no data indication.

[0099] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flow chart is a schematic diagram of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of the blocks in the process / flow chart can be rearranged. In addition, some blocks can be combined or omitted. The attached method claims present the elements of each block in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0100] The previous description is provided to enable those skilled in the art to implement the various aspects described herein. It will be apparent to the art that various modifications to these aspects will be apparent, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are granted a complete scope consistent with the language claims, wherein unless explicitly stated, the elements referred to in the singular are not intended to represent "one and only one", but to refer to "one or more". The word "exemplary" used herein means "used as an example, instance, or schematic". Any aspect described herein as "exemplary" need not be interpreted as being preferred or beneficial over other aspects. Unless otherwise explicitly stated, the term "some" refers to one or more. Such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / C, and may include the plural number of A, the plural number of B or the plural number of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be just A, just B, just C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure are or will become known to those skilled in the art, are expressly incorporated herein by reference, and are intended to be included in the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly listed in the claims. The words "module," "mechanism," "element," "device," and the like may not be replacements for the word "component." Thus, claim elements should not be interpreted as parts plus functions unless the element is expressly listed using the phrase "component for..."

[0101] Some further example implementations

[0102] An example method for wireless communication by a user equipment (UE), comprising: determining whether the UE has any data to send during a configured authorization opportunity assigned to the UE by a base station; generating a no data indication based on the determination that the UE transmit buffer does not include any data to send during the configured authorization opportunity assigned to the UE; and sending the no data indication to the base station to prevent the base station from allocating additional resources to the UE for retransmission.

[0103] According to the above example method, the configured grant opportunity includes a first time period for the UE to send an indication of whether the UE has any data to send and a second time period for sending data on a physical uplink shared channel (PUSCH) if the UE has data to send.

[0104] According to any of the above example methods, wherein the no data indicator and the PUSCH partially overlap in one or both of time or frequency within a region of configured grant occasions.

[0105] According to any of the above example methods, wherein no data is indicated to be sent using fewer than all available resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

[0106] According to any one of the above exemplary methods, sending a no data indication to the base station comprises: selecting an uplink resource from a plurality of available resources allocated to a plurality of UEs to send the no data indication.

[0107] According to any of the above example methods, wherein sending the no data indication to the base station comprises: selecting uplink resources to send the no data indication based on an order of physical uplink shared channel (PUSCH) opportunities sensed to have no energy.

[0108] According to any one of the above exemplary methods, sending the no data indication to the base station comprises: aligning the timing of sending the no data indication to the base station in the first cell with the timing of uplink communication in at least one second cell.

[0109] According to any one of the above exemplary methods, wherein the no data indication is a blank packet sent to the base station to prevent the base station from allocating additional resources.

[0110] According to any of the above example methods, wherein the blank packet includes one or both of a buffer status report (BSR) or a power headroom report (PHR).

[0111] According to any of the above example methods, wherein the no data indication is encapsulated as a medium access control (MAC) control element (CE) in a physical uplink shared channel (PUSCH).

[0112] An example user equipment (UE) includes: a memory storing computer-executable instructions; and a processor communicatively coupled to the memory, the processor configured to execute the instructions to: determine whether the UE has any data to send during a configured authorization opportunity assigned to the UE by a base station; generate a no data indication based on a determination that a UE transmission buffer fails to include any data for transmission during the configured authorization opportunity assigned to the UE; and send the no data indication to the base station to prevent the base station from allocating additional resources to the UE for retransmission.

[0113] According to the above example UE, the configured grant occasions include a first time period for the UE to send an indication of whether the UE has any data to send and a second time period for sending data on a physical uplink shared channel (PUSCH) if the UE has data to send.

[0114] According to any of the above example UEs, wherein the no data indicator and the PUSCH partially overlap within a region of configured grant opportunities in one or both of time or frequency.

[0115] According to any of the above example UEs, wherein the no data indication is sent without using all available resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

[0116] According to any one of the above exemplary UEs, sending a no-data indication to a base station comprises: selecting an uplink resource from a plurality of available resources allocated to a plurality of UEs to send the no-data indication.

[0117] According to any of the above example UEs, the instruction for sending a no data indication to the base station is further configured to be executed by the processor to: select uplink resources to send a no data indication based on the order of physical uplink shared channel (PUSCH) opportunities sensed to have no energy.

[0118] According to any of the above example UEs, the instruction for sending a no data indication to the base station is further configured to be executed by the processor to: align the timing of sending the no data indication to the base station in the first cell with the timing of uplink communication in at least one second cell.

[0119] According to any one of the above exemplary UEs, the no data indication is a blank packet sent to the base station to prevent the base station from allocating additional resources.

[0120] According to any of the above example UEs, wherein the blank packet includes one or both of a buffer status report (BSR) or a power headroom report (PHR).

[0121] An example non-transitory computer-readable medium storing computer-executable instructions, including instructions for: determining whether a user equipment (UE) has any data to send during a configured grant opportunity assigned to the UE by a base station; generating a no-data indication based on a determination that a UE transmit buffer fails to include any data for transmission during the configured grant opportunity assigned to the UE; and sending the no-data indication to the base station to prevent the base station from allocating additional resources to the UE for retransmission.

[0122] According to the above example non-transitory computer-readable medium, the configured grant opportunity includes a first time period for the UE to send an indication of whether the UE has any data to send and a second time period for sending data on a physical uplink shared channel (PUSCH) if the UE has data to send.

[0123] According to any of the above example non-transitory computer readable media, wherein the no data indicator and the PUSCH partially overlap in one or both of time or frequency within a region of configured grant opportunities.

[0124] According to any of the above example non-transitory computer readable media, wherein no data is indicated to be sent using less than all available resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

[0125] According to any of the above exemplary non-transitory computer-readable media, the instructions for sending a no-data indication to a base station further include instructions for: selecting an uplink resource from a plurality of available resources allocated to a plurality of UEs to send the no-data indication.

[0126] According to any of the above example non-transitory computer-readable media, the instructions for sending a no data indication to a base station also include instructions for: selecting uplink resources to send a no data indication based on an order of physical uplink shared channel (PUSCH) opportunities that are sensed to have no energy.

[0127] According to any of the above example non-transitory computer-readable media, the instructions for sending a no data indication to the base station are further configured to be executed by the processor to: align the timing of sending the no data indication to the base station in the first cell with the timing of uplink communication in at least one second cell.

[0128] According to any of the above example non-transitory computer readable media, wherein the no data indication is a blank packet sent to the base station to prevent the base station from allocating additional resources.

[0129] According to any of the above example non-transitory computer readable media, wherein the blank packet includes one or both of a buffer status report (BSR) or a power headroom report (PHR).

[0130] An example apparatus for wireless communications includes: a component for determining whether a user equipment (UE) has any data to send during a configured grant opportunity assigned to the UE by a base station; a component for generating a no data indication based on a determination that a UE transmission buffer fails to include any data for transmission during the configured grant opportunity assigned to the UE; and a component for sending the no data indication to the base station to prevent the base station from allocating additional resources to the UE for retransmission.

[0131] According to the above example apparatus, the configured grant opportunity includes a first time period for the UE to send an indication of whether the UE has any data to send and a second time period for sending data on a physical uplink shared channel (PUSCH) if the UE has data to send.

[0132] According to any of the above example apparatus, wherein the no data indicator and the PUSCH partially overlap in one or both of time or frequency within a region of configured grant occasions.

[0133] According to any of the above example apparatus, wherein the no data indication is sent using less than all available resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

[0134] According to any one of the above example apparatuses, the means for sending a no data indication to a base station further comprises: a means for selecting an uplink resource from a plurality of available resources allocated to a plurality of UEs to send the no data indication.

[0135] According to any of the above example apparatuses, the means for sending a no data indication to a base station further comprises instructions for: selecting uplink resources to send a no data indication means based on an order of physical uplink shared channel (PUSCH) opportunities sensed to have no energy.

[0136] According to any of the above example apparatuses, the means for sending a no data indication to the base station is further configured to be executed by the processor to: align the timing of sending the no data indication to the base station in the first cell with the timing of uplink communication in at least one second cell.

[0137] According to any of the above example apparatus, wherein the no data indication is a blank packet sent to the base station to prevent the base station from allocating additional resources.

[0138] According to any of the above example apparatus, wherein the blank packet includes one or both of a buffer status report (BSR) or a power headroom report (PHR).

Claims

1. A method for wireless communication by a user equipment UE, comprising: determining whether the UE has any data to send during a configured grant opportunity allocated to the UE by a base station; generating a no data indication based on a determination that the UE does not have any data for transmission during the configured grant opportunity; Based on the order of physical uplink shared channel (PUSCH) opportunities that are sensed to have no energy, select uplink resources for sending the no data indication; and send the no data indication to the base station, wherein the no data indication is sent on the PUSCH using the uplink resources selected based on the order of PUSCH opportunities that are sensed to have no energy, and at least partially overlaps with the resources within the area of ​​the configured authorization opportunities in one or both of time or frequency, wherein the no data indication is an invalid blank packet that prevents the base station from allocating additional resources to the UE for retransmission.

2. The method according to claim 1, wherein: The configured grant occasions include a first time period for the UE to send the no data indication and a second time period for sending data on the PUSCH when the UE has data to send.

3. The method according to claim 1, wherein: The no data indication is sent using fewer than all available resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

4. The method according to claim 1, wherein: Sending the no data indication to the base station further includes: selecting an uplink resource from a plurality of available resources allocated to a plurality of UEs; and The no data indication is sent using the selected uplink resource.

5. The method according to claim 1, wherein: Sending the no data indication to the base station further includes: The timing of sending the no data indication to the base station in the first cell is aligned with the timing of uplink communication in at least one second cell.

6. The method according to claim 1, wherein: The no data indication is configured to prevent the base station from allocating one or more additional resources to the UE.

7. The method according to claim 1, wherein: The no data indication includes at least in part a buffer status report BSR, a power headroom report PHR, or both.

8. The method according to claim 1, wherein: The no data indication is sent as a medium access control MAC control element CE on the PUSCH.

9. The method of claim 1, further comprising, before sending the no data indication to the base station, randomly selecting uplink resources to send the no data indication.

10. A user equipment UE, comprising: Transceiver; a memory storing computer executable instructions; as well as a processor communicatively coupled to the memory and the transceiver and configured to execute the instructions to: determining whether the UE has any data to send during a configured grant opportunity allocated to the UE by a base station; generating a no data indication based on a determination that the UE does not have any data for transmission during the configured grant opportunity; selecting an uplink resource for sending the no data indication based on an order of physical uplink shared channel (PUSCH) opportunities that are sensed to have no energy; as well as The no data indication is sent, via the transceiver, to the base station using the selected uplink resources, wherein the no data indication is sent on a PUSCH and at least partially overlaps with resources within the region of the configured grant opportunities in one or both of time or frequency, wherein the no data indication is an invalid blank packet that prevents the base station from allocating additional resources to the UE for retransmission.

11. The UE according to claim 10, wherein: The configured grant occasions include a first time period for the UE to send the no data indication and a second time period for sending data on the PUSCH when the UE has data to send.

12. The UE according to claim 10, wherein: The no data indication is sent using fewer than all available resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

13. The UE according to claim 10, wherein: Sending the no data indication to the base station further includes: selecting an uplink resource from a plurality of available resources allocated to a plurality of UEs; and The no data indication is sent using the selected uplink resource.

14. The UE according to claim 10, wherein: Sending the no data indication to the base station further includes: The timing of sending the no data indication to the base station in the first cell is aligned with the timing of uplink communication in at least one second cell.

15. The UE according to claim 10, wherein: The no data indication is configured to prevent the base station from allocating one or more additional resources to the UE.

16. The UE according to claim 10, wherein: The no data indication includes at least in part a buffer status report BSR, a power headroom report PHR, or both.

17. A non-transitory computer-readable medium storing computer-executable instructions, comprising instructions for: determining whether a user equipment UE has any data to send during a configured grant opportunity allocated by a base station to the UE; generating a no data indication based on a determination that the UE does not have any data for transmission during the configured grant opportunity; selecting an uplink resource for sending the no data indication based on an order of physical uplink shared channel (PUSCH) opportunities that are sensed to have no energy; as well as The no data indication is sent to the base station using the selected uplink resources, wherein the no data indication is sent on the PUSCH and at least partially overlaps with the resources within the region of the configured grant opportunities in one or both of time or frequency, wherein the no data indication is an invalid blank packet that prevents the base station from allocating additional resources to the UE for retransmission.

18. The non-transitory computer-readable medium of claim 17, wherein the configured grant occasions include a first time period for the UE to send the no data indication and a second time period for sending data on the PUSCH when the UE has data to send.

19. An apparatus for wireless communication, comprising: means for determining whether a user equipment UE has any data to send during a configured grant opportunity allocated by a base station to said UE; means for generating a no data indication based on a determination that the UE does not have any data for transmission during the configured grant opportunity; means for selecting uplink resources for transmitting the no data indication based on an order of physical uplink shared channel (PUSCH) opportunities sensed to be without energy; as well as Means for sending the no data indication to the base station using the selected uplink resources, wherein the no data indication is sent on a PUSCH and at least partially overlaps with resources within the region of the configured grant opportunities in one or both of time or frequency, wherein the no data indication is an invalid blank packet.

20. The device according to claim 19, wherein: The configured grant occasions include a first time period for the UE to send the no data indication and a second time period for sending data on the PUSCH when the UE has data to send.

21. The device according to claim 19, wherein: The no data indication is sent using fewer than all available resource elements in an orthogonal frequency division multiplexing (OFDM) symbol.

22. The device according to claim 19, wherein: The means for sending the no data indication to the base station further comprises: means for selecting uplink resources from a plurality of available resources allocated to a plurality of UEs; and Means for sending the no data indication using the selected uplink resources.

23. The device according to claim 19, wherein: The means for sending the no data indication to the base station further comprises: Means for aligning the timing of sending the no data indication to the base station in the first cell with the timing of uplink communication in at least one second cell.

24. The device according to claim 19, wherein: The no data indication is configured to prevent the base station from allocating one or more additional resources to the UE.

25. The device according to claim 19, wherein: The no data indication includes at least in part a buffer status report BSR, a power headroom report PHR, or both.

Images