Reutilization of skips in uplink configuration grants to improve uplink coverage

By re-utilizing the skip mechanism in uplink configuration authorization in wireless communication systems, the problem of insufficient uplink coverage is solved, and more efficient resource utilization and wider coverage are achieved.

CN119731977APending Publication Date: 2025-03-28QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380053679.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-07-21
Filing Date
2023-06-26
Publication Date
2025-03-28

AI Technical Summary

Technical Problem

The existing wireless communication systems have shortcomings in uplink coverage, especially in the case of insufficient resource utilization and insufficient coverage.

Method used

By repurposing a skip mechanism in uplink configuration authorization between user equipment (UE) and network nodes, the configuration authorization uplink communication is sent to the network node in periodic uplink configuration authorization timing in conjunction with determining that the amount of data in the uplink buffer does not meet the threshold, at least in part, based on one or more previous configuration authorization uplink communications.

Benefits of technology

Improved uplink coverage, improved resource utilization efficiency, reduced network service delay, and enhanced decoding capabilities of previous uplink communications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119731977A_ABST
    Figure CN119731977A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for periodic uplink configuration grant opportunities. The UE may send a configuration grant uplink communication to the network node in an uplink configuration grant occasion of the periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications in conjunction with determining that the amount of data in the uplink buffer does not meet a threshold. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 814,023, filed on July 21, 2022, entitled “REPURPOSING SKIPPING INUPLINK CONFIGURED GRANT TO IMPROVE UPLINK COVERAGE,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for reusing skipping in uplink configuration grants (UL-CGs) to improve uplink coverage. Background Art

[0004] 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 that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: receive an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant occasion. The one or more processors may be configured to: in conjunction with determining that an amount of data in an uplink buffer does not satisfy a threshold, send a configuration grant uplink communication to the network node in an uplink configuration grant occasion in a periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: send an uplink configuration grant configuration to a UE, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant occasion. The one or more processors may be configured to: receive a configuration grant uplink communication from the UE in an uplink configuration grant occasion in a periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: receiving an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant occasion. The method may include: in conjunction with determining that an amount of data in an uplink buffer does not satisfy a threshold, sending a configuration grant uplink communication to the network node in an uplink configuration grant occasion in the periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include: sending an uplink configuration grant configuration to a UE, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant occasion. The method may include: receiving a configuration grant uplink communication from the UE in an uplink configuration grant occasion in the periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity. The instruction set, when executed by one or more processors of the UE, may cause the UE to: in conjunction with determining that an amount of data in an uplink buffer does not satisfy a threshold, send a configuration grant uplink communication to the network node in an uplink configuration grant opportunity in a periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to: send an uplink configuration grant configuration to a UE, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity. The instruction set, when executed by one or more processors of the network node, may cause the network node to: receive a configuration grant uplink communication from the UE in an uplink configuration grant opportunity in a periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant occasion. The apparatus may include: means for sending a configuration grant uplink communication to the network node in an uplink configuration grant occasion in the periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications in conjunction with determining that an amount of data in an uplink buffer does not satisfy a threshold.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for sending an uplink configuration grant configuration to a UE, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant occasion. The apparatus may include: means for receiving a configuration grant uplink communication from the UE in an uplink configuration grant occasion in the periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications.

[0015] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of uplink configuration grant (UL-CG) communication according to the present disclosure.

[0023] Figures 5 to 9 is a diagram illustrating an example associated with reusing skipping in UL-CG to improve uplink coverage according to the present disclosure.

[0024] Fig.10is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0025] Fig.11 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0026] Figure 12 to Figure 13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a 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.

[0029] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0030] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). For another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0031] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0032] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile network node 110 (e.g., a mobile network node).

[0033] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. Thus, a single device may include more than one base station.

[0034] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0035] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul link or a wired backhaul link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0037] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0038] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0039] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0040] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as a “below 6 GHz” band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0042] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0043] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may: receive an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity; and send a configuration grant uplink communication to the network node in an uplink configuration grant opportunity in a periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications in conjunction with determining that the amount of data in the uplink buffer does not satisfy a threshold. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0045] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: send an uplink configuration grant configuration to the UE, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity; and receive a configuration grant uplink communication from the UE in an uplink configuration grant opportunity in the periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0046] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0047] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0048] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0050] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0051] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0052] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform operations described herein (eg, with reference to Figures 5 to 13 ) any aspects of any of the methods described.

[0053] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 5 to 13 ) any aspects of any of the methods described.

[0054] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the may perform one or more techniques associated with reusing skipping in uplink configuration grants to improve uplink coverage, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 of and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0055] In some aspects, a UE (e.g., UE 120) includes: a component for receiving an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity; and / or a component for sending a configuration grant uplink communication to the network node in an uplink configuration grant opportunity in a periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications in conjunction with determining that the amount of data in the uplink buffer does not meet a threshold. The components for the UE to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0056] In some aspects, a network node (e.g., network node 110) includes: a component for sending an uplink configuration grant configuration to a UE, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity; and / or a component for receiving a configuration grant uplink communication from the UE in an uplink configuration grant opportunity in a periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications. In some aspects, the components for the network node to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0057] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0058] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0059] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or components in a variety of ways. In a 5GNR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment may be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality may be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0060] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0061] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0062] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0063] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0064] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0065] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0066] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions based on functional splits (e.g., functional splits defined by 3GPP) such as lower layer functional splits, or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0067] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0068] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0069] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0070] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0071] Figure 4 4 is a diagram illustrating an example of an uplink configuration grant (UL-CG) communication according to the present disclosure. The configuration grant (CG) communication may include periodic uplink communications configured for the UE so that the network node does not need to transmit a separate downlink control information (DCI) to schedule each uplink communication, thereby saving signaling overhead.

[0072] As shown in example 400, the UE may be configured with a UL-CG configuration for CG communication. For example, the UE may receive the UL-CG configuration via an RRC message sent by a network node. The UL-CG configuration may indicate resource allocations associated with CG uplink communications (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations are repeated, such that scheduled UL-CG opportunities 405 for the UE occur periodically. In some examples, the UL-CG configuration may identify a resource pool or multiple resource pools available to the UE for uplink transmissions. The UL-CG configuration may configure contention-free CG communication (e.g., where time and / or frequency resources are dedicated to the UE for transmitting uplink communications) or contention-based CG communication (e.g., where the UE contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).

[0073] The UE may be configured to have a type of UL-CG that does not require DCI activation or a type of UL-CG that requires DCI activation. In the case where the UE is configured to have a type of UL-CG that requires DCI activation, the network node may send a UL-CG activation DCI to the UE to activate the UL-CG configuration for the UE. In this case, the network node may indicate communication parameters such as MCS, resource block (RB) allocation and / or antenna port in the CG activation DCI for the CG physical uplink shared channel (PUSCH) communication to be sent in the scheduled UL-CG opportunity 405. The UE may start sending in the UL-CG opportunity 405 based at least in part on receiving the UL-CG activation DCI. For example, starting with the next scheduled UL-CG opportunity 405 after receiving the UL-CG activation DCI, the UE may send PUSCH communication in the scheduled UL-CG opportunity 405 using the communication parameters indicated in the UL-CG activation DCI. In the case where the UE is configured to have a type of UL-CG that requires DCI activation, the UE may suppress sending in the configured UL-CG opportunity 405 before receiving the UL-CG activation DCI. In a case where the UE is configured with a type of UL-CG that does not require DCI activation, the UE may start sending PUSCH communications in the next scheduled UL-CG opportunity after receiving the UL-CG configuration.

[0074] In each scheduled UL-CG opportunity 405, if the UE has uplink data to send, the UE may send CG uplink communications in the UL-CG opportunity 405 using resources identified by the UL-CG configuration. As shown in figure numeral 410, in some examples, the UE may perform UL-CG skipping for the scheduled UL-CG opportunity 405. UL-CG skipping is a feature that enables the UE to skip sending CG-granted uplink communications in the scheduled UL-CG opportunity 405 in a case where the UE's uplink buffer is empty (or the amount of data in the uplink buffer is less than a threshold). That is, when the UE does not have uplink data to send (e.g., the uplink buffer is empty or the amount of data in the uplink buffer is less than a threshold), the UE may skip the scheduled UL-CG opportunity 405 using UL-CG skipping. In this case, the UE may not indicate to the network node that the UE is performing UL-CG skipping, and the network node may attempt to decode the PUSCH resources configured for the scheduled opportunity 405.

[0075] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.

[0076] Some techniques and apparatus described herein enable reuse of scheduled UL-CG opportunities in which the UE may use UL-CG skipping to improve the uplink coverage of the UE. In some aspects, in conjunction with determining that the amount of data in the uplink buffer does not meet a threshold, the UE may send a CG uplink communication based at least in part on one or more previous CG uplink communications to a network node in a UL-CG opportunity. For example, the UE may send a repetition of the latest CG uplink communication sent in the last CG uplink opportunity before the UL-CG uplink opportunity in a UL-CG opportunity, or the UE may send parity bits associated with previous CG uplink communications sent in multiple latest UL-CG opportunities before an uplink configuration grant opportunity in a UL-CG opportunity. In a UL-CG opportunity, sending a repetition of a previous CG uplink communication or parity bits associated with multiple previous CG uplink communications may increase the likelihood that a network node will be able to decode one or more previous CG uplink communications sent by the UE in one or more previous UL-CG opportunities. Thus, uplink coverage of the UE may be improved and network service latency may be reduced.

[0077] In some aspects, the UE may send an indication to the network node indicating whether a CG uplink communication sent in a UL-CG opportunity is a new data transmission or a transmission for improving uplink coverage (e.g., a CG uplink communication based at least in part on one or more previous CG uplink communications). Thus, confusion about whether the CG uplink communication is to be decoded as a new data transmission or to be used to improve uplink coverage (e.g., to be used to improve decoding of one or more previous CG uplink communications) may be avoided at the network node.

[0078] Figure 5 is a diagram illustrating an example 500 associated with reusing skipping in UL-CG to improve uplink coverage according to the present disclosure. Figure 5 As shown, example 500 includes communications between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0079] In some aspects, such as Figure 5As shown, and indicated by reference numeral 505, the network node 110 may send a UL-CG configuration to the UE 120. The UE 120 may receive the UL-CG configuration sent by the network node 110. For example, the UE 120 may receive the UL-CG configuration via an RRC message sent by the network node 110. The UL-CG configuration may identify resources (e.g., time and frequency resources) used for periodic UL-CG opportunities. For example, the UL-CG configuration may indicate resource allocations associated with CG uplink communications (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations are repeated, so that UL-CG opportunities for the UE are periodically repeated. In some aspects, the UL-CG configuration may indicate a configuration of the type of UL-CG that requires DCI activation. In some aspects, the UL-CG configuration may indicate a configuration of the type of UL-CG that does not require activation. In some aspects, the UL-CG configuration may include an indication of a repetition factor that configures multiple repetition instances in each of the periodic UL-CG opportunities. The number of repetition instances corresponds to the number of times the CG uplink communication is to be repeated in a UL-CG opportunity.

[0080] like Figure 5 As further shown, and indicated by reference numeral 510, in some aspects, the network node 110 may send, and the UE 120 may receive, a UL-CG activation DCI indicating activation of a UL-CG configuration. For example, in the case where the UL-CG configuration indicates a configuration of a type of UL-CG requiring DCI activation, the network node 110 may send the UL-CG activation DCI to the UE 120 to activate the UL-CG configuration. In this case, periodic UL-CG opportunities may be activated for the UE 120 based at least in part on the UE 120 receiving the UL-CG activation DCI.

[0081] In some aspects, in the case where the UL-CG configuration indicates a configuration of a type of UL-CG that does not require DCI activation, the network node 110 may not send a UL-CG activation DCI to the UE 120. In this case, periodic UL-CG opportunities may be activated for the UE 120 based at least in part on the UE 120 receiving the UL-CG configuration but not receiving the UL-CG activation DCI.

[0082] like Figure 5As further shown, and indicated by reference numeral 515, UE 120 may determine whether UE 120 has data to send in a UL-CG opportunity. In some aspects, UE 120 may determine whether the amount of data in an uplink buffer of UE 120 satisfies (e.g., is greater than or equal to) a threshold at a time associated with the UL-CG opportunity. In the case where the amount of data in the uplink buffer satisfies (e.g., is greater than or equal to) the threshold, UE 120 may determine that UE 120 has data to send in a UL-CG opportunity. In the case where the amount of data in the uplink buffer does not satisfy (e.g., is less than) the threshold, UE 120 may determine that UE 120 does not have data to send in a UL-CG opportunity. For example, in the case where the data in the uplink buffer does not satisfy the threshold, the uplink buffer of UE 120 may be empty, or the uplink buffer of UE 120 may include only a small number of bits that are not suitable for resources to be sent in a UL-CG opportunity (e.g., will not effectively fill the resources). UE 120 may perform a determination for each of the periodically occurring UL-CG opportunities whether UE 120 has data to send.

[0083] like Figure 5 As further shown, and indicated by reference numeral 520, in conjunction with determining that UE 120 has data to be sent in a UL-CG opportunity, UE 120 may send a CG uplink communication including the data (e.g., data in an uplink buffer of UE 120) in the UL-CG opportunity. For example, in conjunction with determining that the amount of data in the uplink buffer satisfies (e.g., is greater than or equal to) a threshold, UE 120 may send a CG uplink communication including data from the uplink buffer (e.g., new data not included in a previous uplink communication) in the UL-CG opportunity. For the amount of data in the uplink buffer that satisfies (e.g., is greater than or equal to) the threshold, UE 120 may send a corresponding CG uplink communication including the new data (e.g., data from the uplink buffer) in each of the periodically occurring UL-CG opportunities. The network node 110 may receive the CG uplink communication sent in such UL-CG opportunities, and the network node 110 may decode (or attempt to decode) the CG uplink communication.

[0084] like Figure 5As further shown, and indicated by reference numeral 525, in some aspects, in conjunction with determining that UE 120 does not have data to send in a UL-CG opportunity, UE 120 may send a UL-CG uplink communication in a UL-CG opportunity that is based at least in part on one or more previously configured authorized uplink communications. For example, in some aspects, in conjunction with determining that an amount of data in an uplink buffer does not satisfy (e.g., is less than) a threshold, UE 120 may send a CG uplink communication to network node 110 in a UL-CG opportunity that is based at least in part on one or more previous CG uplink communications sent by UE 120 in one or more previous UL-CG opportunities. The CG uplink communication based at least in part on one or more previous CG uplink communications may be a transmission for improving uplink coverage. In some aspects, determining that the amount of data in the uplink buffer does not satisfy a threshold may correspond to a condition associated with UL-CG skipping, and UE 120 may send a transmission for improved uplink coverage (e.g., a CG uplink communication based at least in part on one or more previous CG uplink communications) in a UL-CG opportunity rather than in a skipped UL-CG opportunity.

[0085] The network node 110 may receive a CG uplink communication based at least in part on one or more previous CG uplink communications in a UL-CG opportunity. The network node 110 may use the CG uplink communication based at least in part on one or more previous CG uplink communications to improve the decoding of the one or more previous CG uplink communications. For example, the network node 110 may attempt to decode the one or more previous CG uplink communications based at least in part on a combination of information included in the one or more previous CG uplink communications and information included in the CG uplink communication based at least in part on one or more previous CG uplink communications. In some aspects, the network node 110 may decode at least one previous CG uplink communication of the one or more previous CG uplink communications based at least in part on a CG uplink communication received in a UL-CG opportunity (e.g., a CG uplink communication based at least in part on one or more previous CG uplink communications).

[0086] In some aspects, in conjunction with determining that the amount of data in the uplink buffer does not satisfy the threshold and determining that the power headroom of the UE 120 satisfies the power threshold, the UE 120 may send a CG uplink communication in the UL-CG opportunity that is based at least in part on one or more previous CG uplink communications. For example, when the UE 120 determines that the UE 120 does not have data to send in the UL-CG opportunity (e.g., the amount of data in the uplink buffer does not satisfy the threshold), the UE 120 may then determine whether the power headroom satisfies (e.g., is greater than or equal to) the power threshold. The power headroom of the UE 120 indicates how much transmit power is available for use by the UE 120 in addition to the power used by the current transmission. In some aspects, the UE 120 may report the power headroom to the network node 110 in a power headroom report (PHR). In some aspects, in the case where the UE 120 determines that the amount of data in the uplink buffer does not meet the threshold and the UE 120 determines that the power headroom meets the power threshold, the UE 120 may send a transmission for improving uplink coverage (e.g., a CG uplink communication based at least in part on one or more previous CG uplink communications) in the UL-CG opportunity. In some aspects, in the case where the UE 120 determines that the amount of data in the uplink buffer does not meet the threshold and the UE 120 determines that the power headroom does not meet the power threshold, the UE 120 may skip sending CG uplink communications in the UL-CG opportunity. In this way, when the UE 120 has sufficient power (e.g., the power headroom meets the power threshold), the UE 120 may utilize the UL-CG opportunities for which the UE 120 does not have data to send to improve uplink coverage. When the UE 120 does not have sufficient power (e.g., the power headroom does not meet the power threshold), the UE 120 may save power by reverting to UL-CG skipping in the UL-CG for which the UE 120 does not have data to send.

[0087] In some aspects, a CG uplink communication based at least in part on one or more previous CG uplink communications may be a repetition of a previous CG uplink communication sent in a previous UL-CG opportunity. For example, in conjunction with determining that the UE 120 does not have data to be sent in a UL-CG opportunity (e.g., the amount of data in the uplink buffer does not meet a threshold), the UE 120 may send a repetition of a previous CG uplink communication sent in a last UL-CG grant opportunity before an uplink configuration grant opportunity in a UL-CG opportunity. In this case, instead of skipping the UL-CG opportunity, the UE 120 may repeat the transmission of the latest CG uplink communication sent in the most recent previous UL-CG opportunity. This may increase the likelihood that the network node 110 successfully decodes a previous CG uplink communication sent in the most recent previous UL-CG opportunity. For example, the network node 110 may receive a repetition of a previous CG uplink communication, and the network node 110 may decode the previous CG uplink communication based at least in part on the previous CG uplink communication and the repetition of the CG uplink communication.

[0088] In some aspects, a CG uplink communication based at least in part on one or more previous CG uplink communications may be a CG uplink communication that includes additional parity bits associated with multiple previous CG uplink communications sent in a previous UL-CG opportunity. For example, in conjunction with determining that UE 120 does not have data to send in a UL-CG opportunity (e.g., the amount of data in the uplink buffer does not meet a threshold), UE 120 may send in a UL-CG opportunity parity bits associated with previous CG uplink communications sent in a number (X) of the most recent UL-CG opportunities before the UL-CG opportunity. The parity bits associated with the previous CG uplink communication may include a set of bits generated from information bits included in the previous CG uplink communication, the set of bits providing a representation of all or a subset of the information bits included in the previous CG uplink communication. For example, the parity bits associated with the previous CG uplink communication may be a set of bits obtained by combining multiple information bits included in the previous CG uplink communication using an exclusive OR (XOR) operator or another operator. In some aspects, the number of parity bits associated with each of X previous CG uplink communications may be based at least in part on X and at least in part on the resources configured for each UL-CG opportunity (e.g., the size of the resources configured for CG uplink communications in each UL-CG opportunity).

[0089] In some aspects, the network node 110 may receive parity bits associated with X previous CG uplink communications, and the parity bits associated with the previous CG uplink communications may increase the likelihood that the network node 110 successfully decodes the information bits of the previous CG uplink communications. For example, in some aspects, the network node 110 may decode one or more information bits that were not successfully decoded in the previous CG uplink communication based at least in part on the parity bits associated with the previous CG uplink communication and the one or more information bits that were successfully decoded in the previous CG uplink communication.

[0090] In some aspects, the network node 110 may send and the UE 120 may receive an indication of X (e.g., the number of latest UL-CG opportunities whose parity bits are to be included in the CG uplink communication). In some aspects, X may be an RRC configured for the UE 120. For example, the indication of X may be included in the UL-CG configuration. Additionally or alternatively, X may be indicated via a medium access control (MAC) control element (MAC-CE) or a DCI. In some aspects, X may be based at least in part on one or more configuration parameters included in the UL-CG configuration. In some aspects, X may be based at least in part on an RRC mapping between the values ​​of one or more configuration parameters in the UL-CG configuration and the value of X (e.g., included in the UL-CG configuration). For example, X may be implicitly indicated by an RRC mapping between different values ​​of the periodicity of the UL-CG occasions and different values ​​of X. In this case, the UE 120 may determine the value of X based at least in part on the periodicity indicated in the UL-CG configuration according to the RRC mapping.

[0091] In some aspects, the behavior of the UE 120 in UL-CG opportunities in which the UE 120 does not have data to send may be based at least in part on an indication sent by the network node 110 and received by the UE 120. For example, the indication may be sent to the UE 120 via an RRC message (e.g., in a UL-CG configuration), a MAC-CE, or a DCI (e.g., a dynamic indication). In some aspects, the indication may indicate whether the UE 120 is to send a transmission for improving uplink coverage in the UL-CG opportunities in which the UE 120 does not have data to send, or whether the UE 120 is to perform UL-CG skipping. In some aspects, the indication may indicate the type of transmission to be sent by the UE 120 in the UL-CG opportunities in which the UE 120 does not have data to send for improving uplink coverage (e.g., a repetition of a previous CG uplink communication or a parity bit associated with X previous CG uplink communications).

[0092] In some aspects, the behavior of the UE 120 in UL-CG opportunities in which the UE 120 does not have data to send may be based at least in part on one or more configuration parameters included in the UL-CG configuration. In some aspects, the behavior of the UE 120 in UL-CG opportunities in which the UE 120 does not have data to send may be implicitly indicated based at least in part on an RRC mapping between different UE behaviors and different values ​​of one or more configuration parameters included in the UL-CG configuration (e.g., included in the UL-CG configuration). In this case, the different UE behaviors may include one or more types of transmissions for improving uplink coverage and / or UL-CG skipping. For example, the one or more types of transmissions for improving uplink coverage may include repetitions of previous CG uplink communications and / or parity bits associated with X previous CG uplink communications, where X has one or more values. In some aspects, the RRC mapping may indicate a mapping between different values ​​of the periodicity of the UL-CG opportunities and different UE behaviors. For example, in this case, in a UL-CG opportunity in which UE 120 does not have data to send, UE 120 may send a repetition of a previous CG uplink communication, UE 120 may send parity bits associated with X previous CG uplink communications (e.g., where X has one or more values), or UE 120 may perform UL-CG skipping based at least in part on UE behavior corresponding to a periodicity indicated in the UL-CG configuration.

[0093] In a case where the UL-CG configuration indicates a repetition factor that configures multiple repetition instances in each UL-CG opportunity, the UE 120 may repeat the transmission of a CG uplink communication including data from an uplink buffer (e.g., a new data transmission) in each of the multiple repetition instances in the UL-CG opportunity. In some aspects, in a case where the UL-CG configuration indicates a repetition factor that configures multiple repetition instances in each UL-CG opportunity, the UE 120 may send multiple repetitions of a previous CG uplink communication sent in the latest preceding UL-CG opportunity in the multiple repetition instances in the UL-CG opportunity. For example, the UE 120 may repeatedly send repetitions of the same previous CG uplink communication (e.g., a CG uplink communication sent in a previous UL-CG opportunity) in each of the multiple repetition instances in the UL-CG opportunity. In some aspects, in a case where the UL-CG configuration indicates a repetition factor that configures multiple repetition instances in each UL-CG opportunity, the UE 120 may send repetitions of multiple previous CG uplink communications sent in multiple UL-CG opportunities before the UL-CG opportunity in multiple repetition instances in the UL-CG opportunity. For example, in a case where N repetition instances are configured in each UL-CG opportunity, UE 120 may send in each of the N repetition instances in the UL-CG opportunity a repetition of a previous CG uplink communication sent in a corresponding one of the latest N UL-CG opportunities prior to the UL-CG opportunity.

[0094] In some aspects, UE 120 may send, and network node 110 may receive, an indication of whether a CG uplink opportunity includes a new data transmission (e.g., a CG uplink communication including data from an uplink buffer of UE 120) or a transmission for improving uplink coverage (e.g., a CG uplink communication based at least in part on one or more previous CG uplink communications). Additionally or alternatively, the indication may indicate the type of transmission for improving uplink coverage. For example, in some aspects, the indication may indicate whether the CG uplink opportunity includes a new data transmission (e.g., a CG uplink communication including data from an uplink buffer of UE 120), a repetition of a previous CG uplink communication, or a parity bit associated with the number (X) of previous CG uplink communications. In some aspects, the indication may be included in CG uplink control information (CG-UCI) sent in a UL-CG opportunity. For example, the CG-UCI may include a dedicated bit for indicating whether the corresponding CG uplink communication in the UL-CG opportunity includes new data, a repetition of a previous CG uplink communication, or a parity bit associated with the number (X) of previous CG uplink communications. In some aspects, the indication may be included in the payload of a CG uplink communication, a directly granted PUSCH communication, or a directly granted physical uplink control channel (PUCCH) communication. In this case, the indication may indicate a grant identifier (ID) associated with the UL-CG opportunity to which the indication applies.

[0095] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0096] Figure 6 600 is a diagram illustrating an example associated with reusing skipping in UL-CG to improve uplink coverage according to the present disclosure. Example 600 includes CG uplink communication in periodic UL-CG opportunities. Figure 6 As shown, the UE may send a first CG uplink communication (CG1) in the first UL-CG opportunity. The UE may send a second CG uplink communication (CG2) in the second UL-CG opportunity. The UE may send a third CG uplink communication (CG3) in the third UL-CG opportunity. The UE may send a fourth CG uplink communication (CG2) in the fourth UL-CG opportunity. The UE may send a fifth CG uplink communication (CG5) in the sixth UL-CG opportunity.

[0097] In some aspects, the UE may determine that the UE does not have data to send in the fifth UL-CG opportunity (e.g., the amount of data in the UE's uplink buffer does not meet a threshold). As shown in reference numeral 605, in some aspects, in conjunction with determining that the UE does not have data to send in the fifth UL-CG opportunity, the UE may send a repetition of the CG uplink communication sent in the last UL-CG opportunity before the fifth UL-CG opportunity in the fifth UL-CG opportunity, instead of performing a UL-CG skip for the fifth UL-CG opportunity. In this case, the UE may send a repetition of CG4 in the fifth UL-CG opportunity (e.g., the CG uplink communication sent in the fourth UL-CG opportunity).

[0098] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.

[0099] Figure 7 is a diagram illustrating an example 700 associated with reusing skipping in UL-CG to improve uplink coverage according to the present disclosure. Example 700 includes CG uplink communication in periodic UL-CG opportunities. Figure 7 As shown, the UE may send a first CG uplink communication (CG1) in the first UL-CG opportunity. The UE may send a second CG uplink communication (CG2) in the second UL-CG opportunity. The UE may send a third CG uplink communication (CG3) in the third UL-CG opportunity. The UE may send a fourth CG uplink communication (CG2) in the fourth UL-CG opportunity. The UE may send a fifth CG uplink communication (CG5) in the sixth UL-CG opportunity.

[0100] In some aspects, the UE may determine that the UE does not have data to send in the fifth UL-CG opportunity (e.g., the amount of data in the uplink buffer of the UE does not meet a threshold). As shown in reference numeral 705, in some aspects, in conjunction with determining that the UE does not have data to send in the fifth UL-CG opportunity, the UE may send parity bits associated with previous CG uplink communications in the X most recent UL-CG opportunities before the fifth UL-CG opportunity in the fifth UL-CG opportunity, rather than performing UL-CG skipping for the fifth UL-CG opportunity. Figure 7As shown, in the case where X=3, the UE may send a first group of parity bits 710 associated with CG4 in the fifth UL-CG opportunity (e.g., CG uplink communication sent in the fourth UL-CG opportunity), a second group of parity bits 715 associated with CG3 (e.g., CG uplink communication sent in the third UL-CG opportunity), and a third group of parity bits 720 associated with CG2 (e.g., CG uplink communication sent in the second UL-CG opportunity).

[0101] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.

[0102] Figure 8 800 is a diagram illustrating an example associated with reusing skipping in UL-CG to improve uplink coverage according to the present disclosure. In some aspects, UE behavior in UL-CG opportunities where the UE does not have data to send (e.g., the amount of data in the UE's uplink buffer does not meet a threshold) may be based at least in part on a mapping between different values ​​of one or more configuration parameters in the UL-CG configuration and different UE behaviors. Figure 8 As shown, example 800 includes a mapping between a UL-CG periodicity (e.g., a periodicity of a periodic UL-CG opportunity) and UE behavior in a UL-CG opportunity in which the UE does not have data to send. For example, the mapping between the UL-CG periodicity and the UE behavior can be an RRC mapping, which can be indicated in a UL-CG configuration for the UE.

[0103] like Figure 8As shown, different values ​​of UL-CG periodicity can be mapped to different UE behaviors in UL-CG opportunities in which the UE does not have data to send. As shown in figure numeral 805, a periodicity of one time slot (e.g., sym1X14) maps to a UE behavior of sending additional parity bits for the last six grants (e.g., parity bits associated with the previous CG uplink opportunity sent in the last six UL-CG opportunities). As shown in figure numeral 810, a periodicity of four time slots (e.g., sym4X14) maps to a UE behavior of sending additional parity bits for the last four grants (e.g., parity bits associated with the previous CG uplink opportunity sent in the last four UL-CG opportunities). As shown in figure numeral 815, a periodicity of eight time slots (e.g., sym8X14) maps to a UE behavior of sending additional parity bits for the last two grants (e.g., parity bits associated with the previous CG uplink opportunity sent in the last two UL-CG opportunities). As shown in reference numeral 820, a periodicity of ten time slots (e.g., sym10X14) maps to a UE behavior of repeating a previous CG uplink communication sent in the most recent preceding UL-CG opportunity. As shown in reference numeral 825, a periodicity of twenty time slots (e.g., sym20X14) maps to a UE behavior of skipping UL-CG opportunities in which the UE has no data to send. In some aspects, the UL-CG configuration may indicate a UL-CG periodicity (e.g., the periodicity of a configured periodic UL-CG opportunity), and the UE may perform a UE behavior corresponding to the indicated UL-CG periodicity in UL-CG opportunities in which the UE has no data to send according to the mapping.

[0104] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 Different than described.

[0105] Fig. 9 Diagrams of Examples 900 and 910 associated with reusing skips in UL-CG to improve uplink coverage in accordance with the present disclosure. Examples 900 and 910 include CG uplink communications in periodic UL-CG opportunities. In some aspects, the UL-CG configuration for the UE may indicate a repetition factor that configures multiple repetition instances in each UL-CG opportunity. In Examples 900 and 910, the UE is configured with a repetition factor of three such that each UL-CG opportunity includes three repetition instances for repeating the transmission of the CG uplink communication three times.

[0106] In example 900, the UE may send a first CG uplink communication (CG1) in each of three repetition instances in a first UL-CG opportunity. The UE may send a second CG uplink communication (CG2) in each of three repetition instances in a second UL-CG opportunity. The UE may send a third CG uplink communication (CG3) in each of three repetition instances in a third UL-CG opportunity. The UE may send a fourth CG uplink communication (CG2) in each of three repetition instances in a fourth UL-CG opportunity. The UE may send a fifth CG uplink communication (CG5) in each of three repetition instances in a sixth UL-CG opportunity.

[0107] In some aspects, the UE may determine that the UE does not have data to send in the fifth UL-CG opportunity (e.g., the amount of data in the UE's uplink buffer does not meet a threshold). In some aspects, as shown in figure 905 in example 900, in a case where the UE is configured to have multiple repetition instances and the UE does not have data to send in a UL-CG opportunity (e.g., the fifth UL-CG opportunity), the UE may use all repetition instances in the UL-CG opportunity (e.g., the fifth UL-CG opportunity) to improve coverage of the same previous CG uplink communication (e.g., the CG uplink communication sent in the most recent previous UL-CG configuration). As shown in example 900, the UE may send a repetition of CG4 (e.g., the CG uplink communication sent in the fourth UL-CG opportunity) in each repetition instance of the fifth UL-CG opportunity. In this case, the UE may send three repetitions of CG4 in three repetition instances in the fifth UL-CG opportunity.

[0108] In example 910, the UE may send a first CG uplink communication (CG1) in each of three repetition instances in the first UL-CG opportunity. The UE may send a second CG uplink communication (CG2) in each of three repetition instances in the second UL-CG opportunity. The UE may send a third CG uplink communication (CG3) in each of three repetition instances in the third UL-CG opportunity. The UE may send a fourth CG uplink communication (CG2) in each of three repetition instances in the fourth UL-CG opportunity. The UE may send a fifth CG uplink communication (CG5) in each of three repetition instances in the sixth UL-CG opportunity.

[0109] In some aspects, the UE may determine that the UE does not have data to send in the fifth UL-CG opportunity (e.g., the amount of data in the uplink buffer of the UE does not meet a threshold). In some aspects, as shown in figure 915 in example 910, in a case where the UE is configured to have multiple repetition instances and the UE does not have data to send in a UL-CG opportunity (e.g., the fifth UL-CG opportunity), the UE may use each repetition instance in the UL-CG opportunity (e.g., the fifth UL-CG opportunity) to repeat different previous CG uplink communications. As shown in example 910, the UE may send a repetition of CG2 in the first repetition instance in the fifth UL-CG opportunity, the UE may send a repetition of CG3 in the second repetition instance in the fifth UL-CG opportunity, and the UE may send a repetition of CG4 in the third repetition instance in the fifth UL-CG opportunity. In this case, the UE may send one repetition in three repetition instances in the fifth UL-CG opportunity, each repetition being used for a previous CG communication sent in the last three UL-CG opportunities (e.g., the second, third, and fourth UL-CG opportunities) prior to the fifth UL-CG opportunity.

[0110] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 Different than described.

[0111] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a UE in accordance with the present disclosure. Example process 1000 is an example of operations in which a UE (eg, UE 120) performs skipping in reusing uplink configuration grants to improve uplink coverage.

[0112] like Fig.10 As shown, in some aspects, process 1000 may include: receiving an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for periodic uplink configuration grant opportunities (block 1010). For example, (e.g., using Fig.12 The UE (depicted communications manager 140 and / or receiving component 1202) may: receive an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for periodic uplink configuration grant occasions, as described above.

[0113] like Fig.10As further shown, in some aspects, process 1000 may include, in conjunction with determining that the amount of data in the uplink buffer does not satisfy the threshold, sending a configuration grant uplink communication to the network node in an uplink configuration grant opportunity in a periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications (block 1020). Fig.12 The UE (including the depicted communication manager 140 and / or sending component 1204) may: in combination with determining that the amount of data in the uplink buffer does not meet a threshold, send a configuration authorization uplink communication to a network node in an uplink configuration authorization opportunity in a periodic uplink configuration authorization opportunity based at least in part on one or more previous configuration authorization uplink communications, as described above.

[0114] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0115] In a first aspect, sending a configuration grant uplink communication based at least in part on one or more previous configuration grant uplink communications includes sending, in an uplink configuration grant opportunity, a repetition of a previous configuration grant uplink communication sent in a last uplink configuration grant opportunity before the uplink configuration grant opportunity.

[0116] In a second aspect, alone or in combination with the first aspect, sending a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: in an uplink configuration authorization opportunity, sending parity bits associated with previous configuration authorization uplink communications sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity.

[0117] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes receiving an indication of a number of latest uplink configuration grant opportunities from a network node.

[0118] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the uplink configuration grant configuration includes an indication of a number of latest uplink configuration grant opportunities.

[0119] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the number of latest uplink configuration grant opportunities is based at least in part on one or more configuration parameters included in the uplink configuration grant configuration.

[0120] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the uplink configuration authorization configuration indicates the periodicity of periodic uplink configuration authorization occasions, and the number of latest uplink configuration authorization occasions is at least partially based on the periodicity of the periodic uplink configuration authorization occasions.

[0121] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, an uplink configuration grant configuration indicates a mapping between one or more values ​​of periodicity and one or more numbers of latest uplink configuration grant occasions.

[0122] In an eighth aspect, alone or in combination with one or more of aspects one to seven, sending a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: based at least in part on the periodicity of the periodic uplink configuration authorization occasions indicated in the uplink configuration authorization configuration, sending one of the following in the uplink configuration authorization occasion: a repetition of the previous configuration authorization uplink communication sent in the last uplink configuration authorization occasion before the uplink configuration authorization occasion, or a parity bit associated with the previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization occasions before the uplink configuration authorization occasion.

[0123] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: combining a determination that the amount of data in the uplink buffer does not meet a threshold and a determination that the power margin of the UE meets a power threshold, sending a configuration authorization uplink communication in an uplink configuration authorization opportunity based at least in part on one or more previous configuration authorization uplink communications.

[0124] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, an uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of periodic uplink configuration authorization opportunities, and sending a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes sending multiple repetitions of a previous configuration authorization uplink communication sent in a last uplink configuration authorization opportunity before the uplink configuration authorization opportunity in multiple repetition instances in the uplink configuration authorization opportunity.

[0125] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of the periodic uplink configuration authorization opportunities, and sending the configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: sending repetitions of multiple previous configuration authorization uplink communications sent in multiple uplink configuration authorization opportunities before the uplink configuration authorization opportunity in multiple repetition instances in the uplink configuration authorization opportunity, wherein the repetition of each previous configuration authorization uplink communication in the multiple previous configuration authorization uplink communications is sent in a corresponding repetition instance in the multiple repetition instances in the uplink configuration authorization opportunity.

[0126] In a twelfth aspect, alone or in combination with one or more of aspects 1 to eleven, process 1000 includes: sending an indication to a network node whether a configured authorized uplink opportunity includes new data transmission or a configured authorized uplink communication based at least in part on one or more previously configured authorized uplink communications.

[0127] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, sending a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: sending one of the following in an uplink configuration authorization opportunity: a repetition of a previous configuration authorization uplink communication sent in a last uplink configuration authorization opportunity before the uplink configuration authorization opportunity, or a parity bit associated with a previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity, wherein the indication indicates whether the uplink configuration authorization opportunity includes new data transmission, repetition or a parity bit.

[0128] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the indication is included in configuration grant uplink control information associated with an uplink configuration grant opportunity.

[0129] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the indication is included in a payload of a configuration authorized uplink communication, a direct authorized PUSCH communication or a direct authorized PUCCH communication, and the indication indicates an authorization identifier associated with an uplink configuration authorization opportunity.

[0130] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0131] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a network node, in accordance with the present disclosure. The example process 1100 is an example in which a network node (eg, network node 110) performs operations associated with reusing a skip in an uplink configuration grant to improve uplink coverage.

[0132] like Fig.11 As shown, in some aspects, process 1100 may include: sending an uplink configuration grant configuration to the UE, the uplink configuration grant configuration identifying resources for periodic uplink configuration grant opportunities (block 1110). For example, (e.g., using Fig.13 The depicted communication manager 150 and / or the network node sending component 1304 may: send an uplink configuration grant configuration to the UE, the uplink configuration grant configuration identifying resources for periodic uplink configuration grant occasions, as described above.

[0133] like Fig.11 As further shown, in some aspects, process 1100 may include receiving a configuration grant uplink communication from the UE in an uplink configuration grant opportunity in a periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications (block 1120). Fig.13 The depicted communication manager 150 and / or receiving component 1302) network node may receive a configuration authorization uplink communication from the UE in an uplink configuration authorization occasion in a periodic uplink configuration authorization occasion based at least in part on one or more previous configuration authorization uplink communications, as described above.

[0134] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0135] In a first aspect, process 1100 includes decoding at least one previous configuration grant uplink communication of one or more previous configuration grant uplink communications based at least in part on a configuration grant uplink communication received in an uplink configuration grant opportunity.

[0136] In a second aspect, alone or in combination with the first aspect, receiving a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: in an uplink configuration authorization opportunity, receiving a repetition of a previous configuration authorization uplink communication sent in a last uplink configuration authorization opportunity before the uplink configuration authorization opportunity.

[0137] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: in an uplink configuration authorization opportunity, receiving parity bits associated with previous configuration authorization uplink communications sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity.

[0138] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the process 1100 includes: sending an indication of a number of latest uplink configuration grant opportunities to the UE.

[0139] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the uplink configuration grant configuration includes an indication of a number of latest uplink configuration grant opportunities.

[0140] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the number of latest uplink configuration grant occasions is based at least in part on one or more configuration parameters included in the uplink configuration grant configuration.

[0141] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the uplink configuration authorization configuration indicates the periodicity of periodic uplink configuration authorization occasions, and the number of latest uplink configuration authorization occasions is at least partially based on the periodicity of the periodic uplink configuration authorization occasions.

[0142] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, an uplink configuration grant configuration indicates a mapping between one or more values ​​of periodicity and one or more numbers of latest uplink configuration grant occasions.

[0143] In a ninth aspect, alone or in combination with one or more of aspects one to eight, receiving a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: based at least in part on the periodicity of the periodic uplink configuration authorization occasions indicated in the uplink configuration authorization configuration, receiving one of the following in the uplink configuration authorization occasion: a repetition of a previous configuration authorization uplink communication sent in the last uplink configuration authorization occasion before the uplink configuration authorization occasion, or a parity bit associated with a previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization occasions before the uplink configuration authorization occasion.

[0144] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, an uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of periodic uplink configuration authorization opportunities, and receiving a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes receiving, in multiple repetition instances in the uplink configuration authorization opportunity, multiple repetitions of a previous configuration authorization uplink communication sent in a last uplink configuration authorization opportunity prior to the uplink configuration authorization opportunity.

[0145] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of the periodic uplink configuration authorization opportunities, and receiving the configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: receiving repetitions of multiple previous configuration authorization uplink communications sent in multiple uplink configuration authorization opportunities before the uplink configuration authorization opportunity in multiple repetition instances in the uplink configuration authorization opportunity, wherein the repetition of each previous configuration authorization uplink communication in the multiple previous configuration authorization uplink communications is sent in a corresponding repetition instance in the multiple repetition instances in the uplink configuration authorization opportunity.

[0146] In a twelfth aspect, alone or in combination with one or more of aspects 1 to eleven, process 1100 includes: receiving an indication from the UE whether a configured authorized uplink opportunity includes new data transmission or a configured authorized uplink communication based at least in part on one or more previously configured authorized uplink communications.

[0147] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, receiving a configuration authorization uplink communication based at least in part on one or more previous configuration authorization uplink communications includes: receiving one of the following in an uplink configuration authorization opportunity: a repetition of a previous configuration authorization uplink communication sent in a last uplink configuration authorization opportunity before the uplink configuration authorization opportunity, or a parity bit associated with a previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity, wherein the indication indicates whether the uplink configuration authorization opportunity includes new data transmission, repetition, or a parity bit.

[0148] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the indication is included in configuration grant uplink control information associated with an uplink configuration grant opportunity.

[0149] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the indication is included in a payload of a configuration authorized uplink communication, a direct authorized PUSCH communication or a direct authorized PUCCH communication, and the indication indicates an authorization identifier associated with an uplink configuration authorization opportunity.

[0150] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0151] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE, or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include a determining component 1208, among other things.

[0152] In some aspects, the apparatus 1200 may be configured to perform Figures 5 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein (such as Fig.10 In some aspects, the apparatus 1200 and / or Fig.12 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0153] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0154] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0155] The receiving component 1202 can receive an uplink configuration grant configuration from the network node, the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity. The sending component 1204 can: in conjunction with determining that the amount of data in the uplink buffer does not satisfy a threshold, send a configuration grant uplink communication to the network node in an uplink configuration grant opportunity in the periodic uplink configuration grant opportunity based at least in part on one or more previous configuration grant uplink communications.

[0156] Determining component 1208 can determine whether the amount of data in the uplink buffer satisfies a threshold.

[0157] Receiving component 1202 can receive, from a network node, an indication of a number of latest uplink configuration grant opportunities.

[0158] Transmitting component 1204 can transmit, to the network node, an indication of whether the configured granted uplink opportunity includes a new data transmission or a configured granted uplink communication based at least in part on one or more prior configured granted uplink communications.

[0159] Fig.12 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.12 Two or more components shown in may be implemented in a single component, or Fig.12 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The assembly of (one or more) components shown in the executable is described as being composed of Fig.12 Another collection of components shown in the figure performs one or more functions.

[0160] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network node, or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include a decoding component 1308, among other things.

[0161] In some aspects, the apparatus 1300 may be configured to perform Figures 5 to 9Additionally or alternatively, the apparatus 1300 may be configured to perform one or more of the processes described herein (such as Fig.11 In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the network node. Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0162] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network node.

[0163] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0164] The transmitting component 1304 can transmit an uplink configuration grant configuration to the UE, the uplink configuration grant configuration identifying resources for the periodic uplink configuration grant occasion. The receiving component 1302 can receive a configuration grant uplink communication from the UE in an uplink configuration grant occasion in the periodic uplink configuration grant occasion based at least in part on one or more previous configuration grant uplink communications.

[0165] Decoding component 1308 can decode at least one previous configuration grant uplink communication of the one or more previous configuration grant uplink communications based at least in part on a configuration grant uplink communication received in an uplink configuration grant opportunity.

[0166] Transmitting component 1304 can transmit an indication of the number of latest uplink configuration grant opportunities to the UE.

[0167] Receiving component 1302 can receive, from the UE, an indication of whether a configured granted uplink opportunity includes a new data transmission or a configured granted uplink communication based at least in part on one or more previously configured granted uplink communications.

[0168] Fig.13 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.13 Two or more components shown in may be implemented in a single component, or Fig.13 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The assembly of (one or more) components shown in the executable is described as being composed of Fig.13 Another collection of components shown in the figure performs one or more functions.

[0169] The following provides an overview of some aspects of the disclosure:

[0170] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an uplink configuration authorization configuration from a network node, the uplink configuration authorization configuration identifying resources for periodic uplink configuration authorization opportunities; and in combination with determining that the amount of data in an uplink buffer does not meet a threshold, at least partially based on one or more previous configuration authorization uplink communications, sending a configuration authorization uplink communication to the network node in an uplink configuration authorization opportunity in the periodic uplink configuration authorization opportunity.

[0171] Aspect 2: A method according to Aspect 1, wherein sending the configuration authorization uplink communication at least partially based on the one or more previous configuration authorization uplink communications includes: sending, in the uplink configuration authorization opportunity, a repetition of the previous configuration authorization uplink communication sent in the last uplink configuration authorization opportunity before the uplink configuration authorization opportunity.

[0172] Aspect 3: A method according to Aspect 1, wherein sending the configuration authorization uplink communication at least partially based on the one or more previous configuration authorization uplink communications includes: sending, in the uplink configuration authorization opportunity, parity bits associated with previous configuration authorization uplink communications sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity.

[0173] Aspect 4: The method according to aspect 3, further comprising: receiving an indication of the number of the latest uplink configuration grant opportunities from the network node.

[0174] Aspect 5: The method according to any one of aspects 3 to 4, wherein the uplink configuration grant configuration includes an indication of the number of the latest uplink configuration grant opportunities.

[0175] Aspect 6: The method according to aspect 3, wherein the number of the latest uplink configuration grant opportunities is based at least in part on one or more configuration parameters included in the uplink configuration grant configuration.

[0176] Aspect 7: A method according to any one of Aspects 3 or 6, wherein the uplink configuration authorization configuration indicates the periodicity of the periodic uplink configuration authorization occasions, and wherein the number of the latest uplink configuration authorization occasions is at least partially based on the periodicity of the periodic uplink configuration authorization occasions.

[0177] Aspect 8: The method according to aspect 7, wherein the uplink configuration grant configuration indicates a mapping between one or more values ​​of the periodicity and one or more numbers of the latest uplink configuration grant occasions.

[0178] Aspect 9: A method according to any one of Aspects 1 to 8, wherein sending the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: sending one of the following items in the uplink configuration authorization opportunity based at least in part on the periodicity of the periodic uplink configuration authorization opportunity indicated in the uplink configuration authorization configuration: a repetition of the previous configuration authorization uplink communication sent in the last uplink configuration authorization opportunity before the uplink configuration authorization opportunity, or a parity bit associated with the previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity.

[0179] Aspect 10: A method according to any one of Aspects 1 to 9, wherein sending the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: combining determining that the amount of data in the uplink buffer does not meet the threshold and determining that the power margin of the UE meets the power threshold, and sending the configuration authorization uplink communication in the uplink configuration authorization opportunity based at least in part on the one or more previous configuration authorization uplink communications.

[0180] Aspect 11: A method according to any one of Aspects 1 to 2 and 9 to 10, wherein the uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of the periodic uplink configuration authorization occasions, and wherein sending the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: sending multiple repetitions of the previous configuration authorization uplink communication sent in the last uplink configuration authorization occasion before the uplink configuration authorization occasion in the multiple repetition instances in the uplink configuration authorization occasion.

[0181] Aspect 12: A method according to any one of Aspects 1 to 2 and 9 to 10, wherein the uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of the periodic uplink configuration authorization opportunities, and wherein sending the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: sending repetitions of multiple previous configuration authorization uplink communications sent in multiple uplink configuration authorization opportunities before the uplink configuration authorization opportunity in the multiple repetition instances in the uplink configuration authorization opportunity, wherein the repetition of each previous configuration authorization uplink communication in the multiple repetition instances is sent in a corresponding repetition instance in the multiple repetition instances in the uplink configuration authorization opportunity.

[0182] Aspect 13: According to the method of Aspects 1 to 12, the method also includes: sending an indication to the network node whether the configuration authorization uplink opportunity includes new data transmission or the configuration authorization uplink communication, at least in part based on the one or more previous configuration authorization uplink communications.

[0183] Aspect 14: A method according to Aspect 13, wherein sending the configuration authorization uplink communication at least partially based on the one or more previous configuration authorization uplink communications includes: sending one of the following items in the uplink configuration authorization opportunity: a repetition of the previous configuration authorization uplink communication sent in the last uplink configuration authorization opportunity before the uplink configuration authorization opportunity, or a parity bit associated with the previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity, wherein the indication indicates whether the uplink configuration authorization opportunity includes the new data transmission, the repetition or the parity bit.

[0184] Aspect 15: The method according to any one of aspects 13 to 14, wherein the indication is included in configuration grant uplink control information associated with the uplink configuration grant opportunity.

[0185] Aspect 16: A method according to any one of Aspects 13 to 14, wherein the indication is included in the payload of a configuration authorized uplink communication, a directly authorized physical uplink shared channel (PUSCH) communication or a directly authorized physical uplink control channel (PUCCH) communication, and wherein the indication indicates an authorization identifier associated with the uplink configuration authorization opportunity.

[0186] Aspect 17: A method of wireless communication performed by a network node, the method comprising: sending an uplink configuration authorization configuration to a user equipment (UE), the uplink configuration authorization configuration identifying resources for periodic uplink configuration authorization opportunities; and receiving a configuration authorization uplink communication from the UE in an uplink configuration authorization opportunity in the periodic uplink configuration authorization opportunity based at least in part on one or more previous configuration authorization uplink communications.

[0187] Aspect 18: According to the method of Aspect 17, the method also includes: decoding at least one previous configuration authorization uplink communication of the one or more previous configuration authorization uplink communications based at least in part on the configuration authorization uplink communication received in the uplink configuration authorization opportunity.

[0188] Aspect 19: A method according to any one of Aspects 17 to 18, wherein receiving the configuration authorization uplink communication at least partially based on the one or more previous configuration authorization uplink communications includes: receiving, in the uplink configuration authorization opportunity, a repetition of the previous configuration authorization uplink communication sent in the last uplink configuration authorization opportunity before the uplink configuration authorization opportunity.

[0189] Aspect 20: A method according to any one of Aspects 17 to 18, wherein receiving the configuration authorization uplink communication at least in part based on the one or more previous configuration authorization uplink communications includes: in the uplink configuration authorization opportunity, receiving parity bits associated with previous configuration authorization uplink communications sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity.

[0190] Aspect 21: According to the method of aspect 20, the method further includes: sending an indication of the number of the latest uplink configuration grant opportunities to the UE.

[0191] Aspect 22: The method according to any one of aspects 20 to 21, wherein the uplink configuration grant configuration comprises an indication of the number of the latest uplink configuration grant opportunities.

[0192] Aspect 23: The method according to aspect 20, wherein the number of the latest uplink configuration grant opportunities is based at least in part on one or more configuration parameters included in the uplink configuration grant configuration.

[0193] Aspect 24: A method according to any one of Aspects 20 or 23, wherein the uplink configuration authorization configuration indicates the periodicity of the periodic uplink configuration authorization occasions, and wherein the number of the latest uplink configuration authorization occasions is at least partially based on the periodicity of the periodic uplink configuration authorization occasions.

[0194] Aspect 25: The method according to aspect 24, wherein the uplink configuration grant configuration indicates a mapping between one or more values ​​of the periodicity and one or more numbers of the latest uplink configuration grant occasions.

[0195] Aspect 26: A method according to any one of Aspects 17 to 25, wherein receiving the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: receiving one of the following items in the uplink configuration authorization opportunity based at least in part on the periodicity of the periodic uplink configuration authorization occasion indicated in the uplink configuration authorization configuration: a repetition of the previous configuration authorization uplink communication sent in the last uplink configuration authorization occasion before the uplink configuration authorization occasion, or a parity bit associated with the previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization occasions before the uplink configuration authorization occasion.

[0196] Aspect 27: A method according to any one of Aspects 17 to 19 and 26, wherein the uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of the periodic uplink configuration authorization occasions, and wherein receiving the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: receiving multiple repetitions of the previous configuration authorization uplink communication sent in the last uplink configuration authorization occasion before the uplink configuration authorization occasion in the multiple repetition instances in the uplink configuration authorization occasion.

[0197] Aspect 28: A method according to any one of Aspects 17 to 19 and 26, wherein the uplink configuration authorization configuration indicates a repetition factor for configuring multiple repetition instances in each of the periodic uplink configuration authorization opportunities, and wherein receiving the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: receiving repetitions of multiple previous configuration authorization uplink communications sent in multiple uplink configuration authorization opportunities before the uplink configuration authorization opportunity in the multiple repetition instances in the uplink configuration authorization opportunity, wherein the repetition of each previous configuration authorization uplink communication in the multiple previous configuration authorization uplink communications is sent in a corresponding repetition instance in the multiple repetition instances in the uplink configuration authorization opportunity.

[0198] Aspect 29: According to the method described in any one of Aspects 17 to 28, the method also includes: receiving an indication from the UE whether the configured authorized uplink opportunity includes new data transmission or the configured authorized uplink communication, at least in part based on the one or more previously configured authorized uplink communications.

[0199] Aspect 30: A method according to Aspect 29, wherein receiving the configuration authorization uplink communication based at least in part on the one or more previous configuration authorization uplink communications includes: receiving one of the following items in the uplink configuration authorization opportunity: a repetition of the previous configuration authorization uplink communication sent in the last uplink configuration authorization opportunity before the uplink configuration authorization opportunity, or a parity bit associated with the previous configuration authorization uplink communication sent in a certain number of latest uplink configuration authorization opportunities before the uplink configuration authorization opportunity, wherein the indication indicates whether the uplink configuration authorization opportunity includes the new data transmission, the repetition or the parity bit.

[0200] Aspect 31: A method according to any one of aspects 29 to 30, wherein the indication is included in configuration grant uplink control information associated with the uplink configuration grant opportunity.

[0201] Aspect 32: A method according to any one of Aspects 29 to 30, wherein the indication is included in the payload of a configuration authorized uplink communication, a directly authorized physical uplink shared channel (PUSCH) communication or a directly authorized physical uplink control channel (PUCCH) communication, and wherein the indication indicates an authorization identifier associated with the uplink configuration authorization opportunity.

[0202] Aspect 33: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 16.

[0203] Aspect 34: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 16.

[0204] Aspect 35: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 16.

[0205] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 16.

[0206] Aspect 37: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 16.

[0207] Aspect 38: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 17 to 32.

[0208] Aspect 39: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 17 to 32.

[0209] Aspect 40: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 17 to 32.

[0210] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 17 to 32.

[0211] Aspect 42: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 17 to 32.

[0212] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0213] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads, processes and / or functions implemented, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0214] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0215] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0216] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for periodic uplink configuration grant opportunities; as well as In conjunction with determining that the amount of data in the uplink buffer does not satisfy a threshold, a configuration grant uplink communication is sent to the network node in an uplink configuration grant opportunity in the periodic uplink configuration grant opportunities based at least in part on one or more previous configuration grant uplink communications.

2. The UE of claim 1 , wherein to send the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: In the uplink configuration grant opportunity, a repetition of a previous configuration grant uplink communication sent in a last uplink configuration grant opportunity before the uplink configuration grant opportunity is sent.

3. The UE of claim 1 , wherein to send the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: In the uplink configuration grant opportunity, parity bits associated with previous configuration grant uplink communications sent in a number of most recent uplink configuration grant opportunities prior to the uplink configuration grant opportunity are sent.

4. The UE of claim 3, wherein the one or more processors are further configured to: An indication of the number of grant opportunities for the latest uplink configuration is received from the network node.

5. The UE of claim 3, wherein the uplink configuration grant configuration comprises an indication of the number of the latest uplink configuration grant opportunities.

6. The UE of claim 3, wherein the number of the latest uplink configuration grant occasions is based at least in part on one or more configuration parameters included in the uplink configuration grant configuration.

7. The UE of claim 3, wherein the uplink configuration grant configuration indicates a periodicity of the periodic uplink configuration grant occasions, and wherein the number of the latest uplink configuration grant occasions is based at least in part on the periodicity of the periodic uplink configuration grant occasions.

8. The UE of claim 7, wherein the uplink configuration grant configuration indicates a mapping between one or more values ​​of the periodicity and one or more numbers of the latest uplink configuration grant occasions.

9. The UE of claim 1 , wherein to send the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: At least partially based on the periodicity of the periodic uplink configuration grant occasion indicated in the uplink configuration grant configuration, one of the following items is sent in the uplink configuration grant occasion: a repetition of a previous configuration authorization uplink communication sent in a last uplink configuration grant occasion before the uplink configuration grant occasion, or a parity bit associated with a previous configuration authorization uplink communication sent in a certain number of latest uplink configuration grant occasions before the uplink configuration grant occasion.

10. The UE of claim 1 , wherein to send the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: In combination with determining that the amount of data in the uplink buffer does not meet the threshold and determining that the power headroom of the UE meets the power threshold, the configuration authorization uplink communication is sent in the uplink configuration authorization opportunity based at least in part on the one or more previous configuration authorization uplink communications.

11. The UE of claim 1 , wherein the uplink configuration grant configuration indicates a repetition factor for configuring a plurality of repetition instances in each of the periodic uplink configuration grant occasions, and wherein to send the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: In the plurality of repetitive instances in the uplink configuration grant opportunity, multiple repetitions of a previous configuration grant uplink communication sent in a last uplink configuration grant opportunity before the uplink configuration grant opportunity are sent.

12. The UE of claim 1 , wherein the uplink configuration grant configuration indicates a repetition factor for configuring a plurality of repetition instances in each of the periodic uplink configuration grant occasions, and wherein to send the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: Repetitions of multiple previous configuration authorization uplink communications sent in multiple uplink configuration authorization opportunities before the uplink configuration authorization opportunity are sent in the multiple repetition instances in the uplink configuration authorization opportunity, wherein the repetition of each previous configuration authorization uplink communication in the multiple previous configuration authorization uplink communications is sent in a corresponding repetition instance in the multiple repetition instances in the uplink configuration authorization opportunity.

13. The UE of claim 1, wherein the one or more processors are further configured to: Based at least in part on the one or more previous configured granted uplink communications, an indication is sent to the network node as to whether the configured granted uplink opportunity includes a new data transmission or the configured granted uplink communication.

14. The UE of claim 13, wherein to send the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: Sending one of the following in the uplink configuration grant opportunity: a repetition of a previous configuration grant uplink communication sent in a last uplink configuration grant opportunity before the uplink configuration grant opportunity, or a parity bit associated with a previous configuration grant uplink communication sent in a certain number of latest uplink configuration grant opportunities before the uplink configuration grant opportunity, wherein the indication indicates whether the uplink configuration grant opportunity includes the new data transmission, the repetition or the parity bit.

15. The UE of claim 13, wherein the indication is included in configuration grant uplink control information associated with the uplink configuration grant opportunity.

16. A UE according to claim 13, wherein the indication is included in a payload of a configuration-granted uplink communication, a directly granted physical uplink shared channel (PUSCH) communication, or a directly granted physical uplink control channel (PUCCH) communication, and wherein the indication indicates an authorization identifier associated with the uplink configuration authorization opportunity.

17. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: sending an uplink configuration grant configuration to a user equipment (UE), the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity; as well as A configuration grant uplink communication is received from the UE in an uplink configuration grant occasion in the periodic uplink configuration grant occasions based at least in part on one or more previous configuration grant uplink communications.

18. The network node of claim 17, wherein the one or more processors are further configured to: At least one previous configuration grant uplink communication of the one or more previous configuration grant uplink communications is decoded based at least in part on the configuration grant uplink communication received in the uplink configuration grant opportunity.

19. The network node of claim 17, wherein to receive the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: In the uplink configuration grant opportunity, a repetition of a previous configuration grant uplink communication sent in a last uplink configuration grant opportunity before the uplink configuration grant opportunity is received.

20. The network node of claim 17, wherein to receive the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: In the uplink configuration grant opportunity, parity bits associated with previous configuration grant uplink communications sent in a number of most recent uplink configuration grant opportunities prior to the uplink configuration grant opportunity are received.

21. The network node of claim 17, wherein the uplink configuration grant configuration indicates a repetition factor for configuring a plurality of repetition instances in each of the periodic uplink configuration grant occasions, and wherein to receive the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: In the plurality of repetitive instances in the uplink configuration grant opportunity, a plurality of repetitions of a previous configuration grant uplink communication sent in a last uplink configuration grant opportunity prior to the uplink configuration grant opportunity are received.

22. The network node of claim 17, wherein the uplink configuration grant configuration indicates a repetition factor for configuring a plurality of repetition instances in each of the periodic uplink configuration grant occasions, and wherein to receive the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications, the one or more processors are configured to: Repetitions of multiple previous configuration authorization uplink communications sent in multiple uplink configuration authorization opportunities before the uplink configuration authorization opportunity are received in the multiple repetition instances in the uplink configuration authorization opportunity, wherein the repetition of each previous configuration authorization uplink communication in the multiple previous configuration authorization uplink communications is sent in a corresponding repetition instance in the multiple repetition instances in the uplink configuration authorization opportunity.

23. The network node of claim 17, wherein the one or more processors are further configured to: Based at least in part on the one or more previously configured granted uplink communications, an indication is received from the UE as to whether the configured granted uplink opportunity includes a new data transmission or the configured granted uplink communication.

24. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an uplink configuration grant configuration from a network node, the uplink configuration grant configuration identifying resources for periodic uplink configuration grant opportunities; as well as In conjunction with determining that the amount of data in the uplink buffer does not satisfy a threshold, a configuration grant uplink communication is sent to the network node in an uplink configuration grant opportunity in the periodic uplink configuration grant opportunities based at least in part on one or more previous configuration grant uplink communications.

25. The method of claim 24, wherein sending the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications comprises: In the uplink configuration grant opportunity, a repetition of a previous configuration grant uplink communication sent in a last uplink configuration grant opportunity before the uplink configuration grant opportunity is sent.

26. The method of claim 24, wherein sending the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications comprises: In the uplink configuration grant opportunity, parity bits associated with previous configuration grant uplink communications sent in a number of most recent uplink configuration grant opportunities prior to the uplink configuration grant opportunity are sent.

27. The method of claim 24, wherein sending the configuration grant uplink communication based at least in part on the one or more previous configuration grant uplink communications comprises: In combination with determining that the amount of data in the uplink buffer does not meet the threshold and determining that the power headroom of the UE meets the power threshold, the configuration authorization uplink communication is sent in the uplink configuration authorization opportunity based at least in part on the one or more previous configuration authorization uplink communications.

28. The method according to claim 24, further comprising: Based at least in part on the one or more previous configured granted uplink communications, an indication is sent to the network node as to whether the configured granted uplink opportunity includes a new data transmission or the configured granted uplink communication.

29. A method of wireless communication performed by a network node, the method comprising: sending an uplink configuration grant configuration to a user equipment (UE), the uplink configuration grant configuration identifying resources for a periodic uplink configuration grant opportunity; as well as A configuration grant uplink communication is received from the UE in an uplink configuration grant occasion in the periodic uplink configuration grant occasions based at least in part on one or more previous configuration grant uplink communications.

30. The method according to claim 29, further comprising: At least one previous configuration grant uplink communication of the one or more previous configuration grant uplink communications is decoded based at least in part on the configuration grant uplink communication received in the uplink configuration grant opportunity.