Minimum offset value for unused transmission opportunity indication

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive offset information associated with a minimum offset between a scheduling grant and a corresponding physical uplink shared channel communication. The UE may transmit an indication of an unused transmission opportunity (TO) based, at least in part, on a time duration between an uplink TO and an unused TO being equal to or greater than a minimum offset for the indication. Numerous other aspects are described.

Description

Background Technology

[0001] All aspects of this disclosure relate to wireless communication, and to techniques and apparatus for indicating unused transmission opportunities.

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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 issued by the 3rd Generation Partnership Project (3GPP).

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

[0004] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0005] Some aspects described herein relate to a method for wireless communication performed at a user equipment (UE). The method may include receiving offset information associated with a minimum offset between scheduling-granted and corresponding Physical Uplink Shared Channel (PUSCH) communication. The method may include transmitting the indication, at least in part, based on the time duration between the uplink TO and the unused TO being equal to or greater than the minimum offset.

[0006] Some aspects described herein relate to a method for performing wireless communication at a network entity. This method may include generating offset information associated with a minimum offset between scheduling permission and the corresponding PUSCH communication, and associated with the UE determining an indication to transmit an unused TO. This method may include transmitting the offset information.

[0007] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive offset information associated with a minimum offset between a scheduling grant and the corresponding PUSCH communication. The one or more processors may be configured to cause the UE to transmit an indication at least in part based on the time duration between the uplink TO and the unused TO being equal to or greater than the minimum offset. In some aspects, the one or more processors may be configured individually or collectively to perform the operation.

[0008] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be configured to generate offset information associated with a minimum offset between a scheduling grant and the corresponding PUSCH communication, and with an indication of an unused TO. The one or more processors may be configured to cause the network entity to transmit the offset information. In some aspects, the one or more processors may be configured individually or collectively to perform operations.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive offset information associated with a minimum offset between a scheduling grant and the corresponding PUSCH communication. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit an indication at least in part based on the time duration between the uplink TO and the unused TO being equal to or greater than the minimum offset.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. When executed by one or more processors of the network entity, this set of instructions enables the network entity to generate offset information associated with a minimum offset between scheduling permission and the corresponding PUSCH communication, and associated with the UE determining an indication to transmit an unused TO. When executed by one or more processors of the network entity, this set of instructions enables the network entity to transmit the offset information.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving offset information associated with a minimum offset between a scheduling grant and the corresponding PUSCH communication. The apparatus may also include components for transmitting an indication, at least in part, based on the time duration between the uplink TO and the unused TO being equal to or greater than the minimum offset.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for generating offset information associated with a minimum offset between scheduling permission and corresponding PUSCH communication, and for determining, in conjunction with another device, an indication to transmit an unused TO. The apparatus may include components for transmitting the offset information.

[0013] The general categories include, as fully described with reference to the accompanying drawings and description and illustrated in the accompanying drawings and description, methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems.

[0014] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims. Attached Figure Description

[0015] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined 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 drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

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

[0017] Figure 2 This 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.

[0018] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0019] Figure 4 This is a diagram illustrating an example of uplink configuration permission (CG) communication according to this disclosure.

[0020] Figure 5 This is a diagram illustrating an example of an unused transmission opportunity (TO) according to this disclosure.

[0021] Figure 6 This is a diagram illustrating an example of a TO not used according to the instructions of this disclosure.

[0022] Figure 7 This is a diagram illustrating an example of a timeline for indicating unused TOs according to this disclosure.

[0023] Figure 8 This is a diagram illustrating an example of how offset information is associated with an unused TO according to this disclosure.

[0024] Figure 9This is a diagram illustrating an example of updated offset information and updated thresholds according to this disclosure.

[0025] Figure 10 This is a diagram illustrating an example procedure performed by a UE according to this disclosure, for example.

[0026] Figure 11 This is a diagram illustrating an example process performed by a network entity, for example, according to this disclosure.

[0027] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure.

[0028] Figure 13 The diagram illustrates an example of a specific implementation of the code and circuitry for a device according to this disclosure.

[0029] Figure 14 This is a diagram illustrating an example of a hardware implementation of a device for employing a processing system according to the present disclosure.

[0030] Figure 15 This is a diagram of an example device for wireless communication according to the present disclosure.

[0031] Figure 16 This is a diagram illustrating an example of a hardware implementation of a device for employing a processing system according to the present disclosure.

[0032] Figure 17 The diagram illustrates an example of a specific implementation of the code and circuitry for a device according to this disclosure. Detailed Implementation

[0033] In some examples, resources for uplink communication performed by the User Equipment (UE) can be granted by configuration. Such resources are referred to as “configuration grants” (CG). For example, Physical Uplink Shared Channel (PUSCH) communication in CG grants (also known as CG-PUSCH Transmission Timing (TO)) can include periodic uplink communication, allowing network entities to save signaling overhead by not needing to transmit separate downlink control information (DCI) to schedule each uplink communication. Using CG scheduling, more resources can be allocated than are required for the transmission of uplink communication. In some examples, the UE can skip one or more TOs to save power. If one or more TOs are skipped (“unused”), the UE can indicate the unused one or more TOs in the uplink control information (UCI). TOs that are not skipped and can be used are considered “unused.” This is because, according to one or more examples, unskipped resources are not always used.

[0034] In one example, another UE may or may not be able to use an unused TO. The UE expects a certain amount of time to process the scheduling grant from the network entity and prepare to use the scheduling grant for uplink transmission. This amount of time may be referred to as the offset (or K2). If another UE wants to use an unused TO, the time duration between the uplink slot (where the UCI indicates the unused TO) and the actual unused TO (e.g., D The time interval can be no less than K2. If K2 is equal to or greater than K2... D If K2 is less than 1, there will not be enough time to reallocate the unused TO to another UE. Therefore, the indication in the UCI will be a waste of signaling resources. D This allows sufficient time to reallocate unused TOs. In other words, the indication in the UCI will be early enough for network entities to reallocate unused TOs to another UE. This resource reallocation saves signaling resources and reduces latency. However, the UE may not have information about whether it will receive an indication for an unused TO in time so that it can be used by another UE. Without this information, signaling resources may be wasted.

[0035] Based on the various aspects described herein, network entities can provide UEs with offset information associated with a minimum offset of K2, which will provide sufficient time to reallocate unused TOs. K2 corresponds to the UE's ability to process and use scheduling-granted capabilities; however, in one or more examples, there may be multiple UEs with different capabilities or K2s. The minimum offset of K2 may include a minimum value of K2 or a time amount for the time duration between the uplink slot (where the UCI indicates an unused TO) and the actual unused TO (e.g., ...). D The offset information can be compared to the minimum offset of K2. In some aspects, the offset information from the network entity to the UE may include multiple offset candidates (e.g., a K2 candidate for each UE), and the UE can select an offset candidate for K2 from these multiple candidates. If the network entity provides the UE with offset information indicating the minimum offset for K2, the UE can determine that K2 is greater than the minimum offset and will not send an indication for an unused TO. If K2 is less than or equal to... D In this way, the UE can send an indication of an unused TO, because another UE can use the unused TO, and the network entity has enough time to schedule the other UE to use the unused TO. In this way, if the unused TO can be reallocated to another UE, signaling resources are saved, and by sending an indication of an unused TO that will not be used, signaling resources are not wasted.

[0036] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0037] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0038] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0039] Figure 1This 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., LTE) network, etc. 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), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated 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). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among 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)).

[0040] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or 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. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0041] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0042] In some aspects, the term "base station" or "network node" may refer to an aggregated 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, "base station" or "network node" may refer to a CU, DU, 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 network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that 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 can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device may include more than one base station.

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

[0044] The wireless network 100 can be a heterogeneous network, comprising 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 effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

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

[0046] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), 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 smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or 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, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

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

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

[0049] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary device to communicate with each other). 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.

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., by frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz–300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0051] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands for these IF bands as the frequency range designation FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] Considering the examples above, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0053] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive offset information associated with a minimum offset between scheduling permission and the corresponding PUSCH communication. The communication manager 140 may transmit the indication at least in part based on the time duration between the uplink TO used for the indication of the unused TO and the unused TO being equal to or greater than the minimum offset. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0054] In some aspects, network entities (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may generate offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication, and associated with the UE determining an indication to transmit an unused TO. The communication manager 150 may transmit the offset information. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0055] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0056] Figure 2 This is a diagram illustrating an example 200 of communication between a network node 110 and 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 One antenna ( T ≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R One antenna ( R ≥1). Network node 110 of Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component that facilitates communication with UE 120 or another network node. Some network node 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0057] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and can provide data symbols for UE 120. Transmitting processor 220 can 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. Transmitting processor 220 can 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 signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can transmit a set of output symbol streams (e.g., T Each output symbol stream is provided to a corresponding set of modems 232 (e.g., ...). TEach modem 232a to 232t can be used to process a corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. For example, each output symbol stream can be provided to a modulator component (MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t can be connected via a corresponding set of antennas 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., ...). T (One downlink signal).

[0058] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can transmit a set of received signals (e.g., R The received signals are provided to a group of modems 254 (e.g., R Each modem 254 (shown as modems 254a to 254r) may be used. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to 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 can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0060] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include 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., or may 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 (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements and / or be coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a )

[0061] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can 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 network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein.

[0062] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes 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 aspects of any of the methods described herein.

[0063] The controller / processor of the network entity (e.g., controller / processor 240 of network node 110), the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with the minimum offset value used for indicating unused TOs, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 10 Process 1000 Figure 11 The operation of process 1100 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code 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 storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). Figure 10 Process 1000 Figure 11The operation of process 1100 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0064] In some aspects, the UE (e.g., UE 120) includes components for receiving offset information associated with a minimum offset between scheduling permission and the corresponding PUSCH communication; and / or components for transmitting the indication at least in part based on the time duration between the uplink TO and the unused TO being equal to or greater than the minimum offset. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0065] In some aspects, the network entity (e.g., the network entity) includes components for generating offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication and associated with the UE determining an indication to transmit an unused TO; and / or components for transmitting the offset information. In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0066] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0067] In some respects, a single processor can perform all the functions described as being performed by that one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, a first group(s) of the one or more processors can perform a first function described as being performed by that one or more processors, and a second group(s) of the one or more processors can perform a second function described as being performed by that one or more processors. The first group and the second group of processors can be the same group of processors or can be different groups of processors. The reference to "one or more processors" should be understood as referring to a combination of functions. Figure 2 Any one or more processors described. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with... Figure 2 The memory described. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0068] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0069] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can 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 combinations thereof).

[0070] Aggregated base stations (e.g., aggregated network nodes) 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 cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0071] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0072] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as 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 a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0073] Each unit in the clusters (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cluster, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other clusters via transmission media. In some examples, each unit in the cluster may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more units in other clusters, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more units in other clusters, or both.

[0074] In some aspects, the CU 310 can host one or more higher-level 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 can be implemented using an interface configured to signal to other control functions managed by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0075] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by 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 configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

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

[0077] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the 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-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with the hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0078] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0079] In some implementations, to generate AI / ML models 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. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0080] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0081] Figure 4 This is a diagram illustrating example 400 of uplink CG communication according to this disclosure.

[0082] In some aspects, Physical Resource Blocks (PRBs) for uplink communication can be dynamically granted, such as using Scheduling Requests (SRs) or Buffer Status Reports (BSRs). When a UE has data to be processed in its buffer, the UE can first send an SR on the Physical Uplink Control Channel (PUCCH) to request radio resources in the uplink. Using periodic BSR reports, the network entity can know the available buffers at the UE. The network entity then sends an Uplink Grant DCI. The DCI specifies the allocated resources for the UE to transmit communication on the PUSCH.

[0083] Alternatively, PRBs for uplink communications can be granted based on configuration. For example, CG communications may include periodic uplink communications configured for the UE, so that network entities do not need to transmit separate DCIs to schedule each uplink communication, thereby saving signaling overhead.

[0084] As shown in Example 400, a UE (e.g., UE 120) may be configured with a CG configuration for CG communication. For example, the UE may receive the CG configuration via an RRC message sent by a network entity (e.g., network node 110). The CG configuration may indicate the periodicity of resource allocation and resource allocation repetition associated with CG uplink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain), thereby causing the periodic repetition of scheduling CG opportunities 405 for the UE. In some examples, the CG configuration may identify resource pools or multiple resource pools available for the UE to use for uplink transmission. The CG configuration may configure contention-free CG communication (e.g., where resources are dedicated to the UE for uplink transmission) or contention-based CG communication (e.g., where the UE contends for access to a channel in the configured resource allocation, such as through a channel access procedure or a channel sensing procedure).

[0085] The network entity may additionally send a CG activation DCI to the UE to activate the CG configuration for the UE (e.g., for a type 2 CG configuration). The network entity may indicate communication parameters, such as MCS, RB allocation, and / or antenna port, in the CG activation DCI for CG PUSCH communication to be transmitted in scheduled CG times 405 (405a to 405h). The UE may begin transmission in CG times 405 at least in part based on receiving the CG activation DCI. For example, starting from the next scheduled CG times 405 after receiving the CG activation DCI, the UE may transmit PUSCH communication in scheduled CG times 405 using the communication parameters indicated in the CG activation DCI. The UE may avoid transmitting in the configured CG times 405 before receiving the CG activation DCI.

[0086] A network entity may send a CG reactivation DCI to the UE to change the communication parameters used for future CG PUSCH communications. Based at least in part on the receipt of the CG reactivation DCI, the UE may begin transmitting during scheduled CG timing 405 using the communication parameters (e.g., MCS, RB allocation, and / or antenna port) indicated in the CG reactivation DCI. For example, starting from the next scheduled CG timing 405 after receiving the CG reactivation DCI, the UE may transmit future PUSCH communications during scheduled CG timing 405 based at least in part on the communication parameters indicated in the CG reactivation DCI.

[0087] In some situations, such as when a network entity needs to override scheduled CG communication for higher priority communication, the network entity may send a CG Cancel DCI to the UE to temporarily cancel or disable one or more subsequent CG timings 405 for that UE. A CG Cancel DCI may disable only one subsequent CG timing 405 or subsequent... N CG timing 405 (of which N(It is an integer). It refers to one or more of the following after CG eliminates DCI (e.g., N One CG timing 405 after receiving CG cancellation DCI can remain active. At least in part based on receiving CG cancellation DCI, the UE can avoid one or more (e.g., ...) CG timing 405 after receiving CG cancellation DCI. N The CG cancellation DCI is transmitted in a subsequent CG timing 405 of the UE, as shown in Example 400. The CG cancellation DCI is transmitted in a subsequent CG timing 405 of the UE. N After a CG opportunity, the UE can automatically resume transmission in the scheduled CG opportunity 405.

[0088] A network entity may send a CG release DCI to the UE to disable the CG configuration used by the UE. The UE may stop transmitting during scheduled CG timing 405, at least in part, based on receiving the CG release DCI. For example, the UE may avoid transmitting during any scheduled CG timing 405 until it receives another CG activation DCI from the network entity. However, a CG cancellation DCI may disable only one subsequent CG timing 405 or N subsequent CG timings 405, while a CG release DCI disables all subsequent CG timings 405 for a given CG configuration used by the UE until that given CG configuration is reactivated by a new CG activation DCI.

[0089] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0090] Figure 5 This is a diagram illustrating an example 500 of an unused TO according to this disclosure.

[0091] In the example, CG-PUSCH scheduling works well for traffic with strict latency expectations, such as XR gaming traffic, cloud gaming traffic, etc. Depending on one aspect, a network entity (e.g., a gNB) can assign multiple CG-PUSCH opportunities (also referred to herein as “CG opportunities” or “transmission opportunities” (TOs)) to a UE for upcoming PUSCH data, including for large and variable XR video frames. Example 500 illustrates a slot pattern with uplink (U) slots, which are CG-PUSCH TOs scheduled (assigned) for the UE, such as TO 502, TO 504, TO 506, and TO 508. TO 502, TO 504, TO 506, and TO 508 can be part of a CG cycle. Because SR and BSR are not required before PUSCH data transmission, the network entity may not know the exact uplink payload size (e.g., for transport block (TB) 510) and how many CG-PUSCH TOs the UE will use for PUSCH transmission. There may be a mismatch between the allocated TOs 502-508 and the expected resources required to transmit TB 510. If the allocated TOs 502-508 are too few for the upcoming TB 510, the UE will use more resources, and latency will increase. If the allocated TOs 502-508 are too many for the upcoming TB 510, some TOs will be wasted.

[0092] If one or more CG-PUSCH TOs are skipped, the UE can indicate the skipped TOs (e.g., TOs 506 and TOs 508) in UCI (or Media Access Control Element (MAC CE)) 512. When an uplink XR video frame arrives for transmission from the upper layer at the UE, the UE knows the video frame size and therefore the number of TOs required to transmit the video frame. The UE can determine how many TOs to skip. Skipped TOs can be considered "unused," therefore TOs 506 and TOs 508 are indicated in... Figure 5TOs 506 and 508 are shown as unused. TOs that are not skipped and can be used are considered "unused." Because unused TOs may still not be used (due to traffic or scheduling reasons), a TO may not be explicitly "used." Therefore, such unused TOs can be considered "unused." That is, "unused" TOs may or may not be used. Therefore, the UCI can indicate which TOs are used and which are unused. Indicating unused TOs to network entities can reduce blind detection by network entities and allow network entities to reallocate unused PUSCH resources. According to one or more examples, the UCI can explicitly indicate TOs that are not unused and can derive unused TOs (unused TOs are those remaining after removing non-unused TOs). Similarly, the UCI can explicitly indicate unused TOs and can derive non-unused TOs (non-unused TOs are those remaining after removing unused TOs). In summary, the UE can have different ways of indicating which TOs are used and which are unused.

[0093] It should be noted that in one or more examples, a "not unused" TO can also be referred to as a "used" TO. In either case, if there is no uplink data to transmit, the UE is allowed not to send PUSCH communication. Indication of "used" TOs (e.g., UCI or MAC 512) can help network entities reduce blind detection work for overlapping TOs.

[0094] If unused TOs exist, the UE can indicate the unused TOs to the network entity via UCI or MAC CE 502. For example, UCI or MAC CE 502 can indicate unused TOs 504 and 506. Each TO can be identified using a CG timing ID (e.g., an index or other identifier). In some aspects, the UCI indicating an unused TO (e.g., for XR traffic) can be a legacy CG-UCI or a new UCI. The UCI can indicate a TO that is the last one that is not unused or the first of a plurality of consecutive unused TOs. The UCI can indicate that a plurality of consecutive TOs are unused based on a start timing and length (timing ID numbers may be consecutive or may not be consecutive). If the position of a bit in the bitmap is mapped to a timing ID of a configured TO, the UCI can include bits in the bitmap indicating whether a TO is unused. If a value is mapped to a timing ID, the UCI can include a code point value indicating that one or more TOs are unused. Example 500 shows that an unused TO 506 can have a timing ID 514, and an unused TO 508 can have a timing ID 516. In some respects, code point 518 or bitmap 520 in UCI or MAC CE 512 can be mapped to timing ID 514 and timing ID 516.

[0095] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0096] Figure 6 This is a diagram illustrating example 600 of a TO that is not used according to the instructions of this disclosure.

[0097] Example 600 illustrates multiple CG cycles in which XR traffic is to be transmitted. In the first CG cycle, the XR traffic can use all allocated TOs. In the second CG cycle, the XR traffic may not use all allocated TOs. UCI 602 can indicate unused TO 604. In the third CG cycle, the XR traffic may use only half of the TOs, and UCI 606 can indicate unused TOs 608 and 610. The network entity can receive the UCI and reassign the unused TOs 608 and 610 to another UE to avoid wasting resources.

[0098] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0099] Figure 7These are illustrations of examples 700 and 720 illustrating timelines for indicating unused TOs according to this disclosure.

[0100] Example 700 illustrates the uplink timeslot for the UCI used to indicate an unused TO. There is a time interval between the uplink timeslot for UCI 704 indicating an unused TO 706 (as determined by...). D (Shown 702). There is also an offset (shown as K2 708) between scheduling grant 710 and the corresponding PUSCH 712 scheduled by grant 710. If K2 708 is equal to or greater than... D 702, as shown in Example 700, indicates that there is insufficient time to reallocate unused TO 706. The indication in UCI 704 would be a waste of signaling resources. If K2 708 is less than... D As shown in Example 720, there is sufficient time to reallocate the unused TO 706. The indication in UCI 704 is timely, allowing the network entity to reallocate the unused TO 706 to another UE, which saves signaling resources and reduces latency. It should be noted that the determination can be based at least in part on K2 708 being equal to or greater than... D 702 or only K2 708 greater than D 702. Accordingly, it can be determined, at least in part, that K2 708 is exactly less than D 702 or less than or equal to D 702. Under no circumstances does the UE have information about whether indicating an unused TO is beneficial or a waste of signaling resources.

[0101] Based on the various aspects described herein, network entities can provide the UE with offset information associated with the minimum offset of K2 708, which will provide sufficient time to reallocate unused TOs. In some aspects, the offset information can indicate the minimum offset of K2 708. In some aspects, the offset information can include multiple offset candidates (e.g., K2 candidates for each UE), and the UE can select an offset candidate for K2 708 from the multiple offset candidates. If the network entity provides offset information for the minimum offset of K2, the UE can determine that K2 708 is greater than the minimum offset and will not send an indication for the unused TO. If K2 708 is less than or equal to... D 702, then the UE can send an indication of an unused TO. In this way, if the unused TO can be reassigned to another UE, signaling resources are saved, and by sending an indication of an unused TO that will not be used, signaling resources are not wasted.

[0102] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0103] Figure 8 This is a diagram illustrating an example 800 associated with offset information used to indicate an unused TO according to this disclosure. For example... Figure 8 As shown, network entity 810 (e.g., network node 110) and UE 820 (e.g., UE 120) can communicate with each other via a wireless network (e.g., wireless network 100). Network entity 810 can also communicate with UE 825 and UE 830.

[0104] As shown by reference numeral 835 in the attached figure, UEs 820, UE 825, and UE 830 can send capability information for the minimum offset for K2 (the time between scheduling permission and the corresponding PUSCH communication). That is, the capability information of the respective UE can indicate the offset capability, which network entity 810 can use to determine the minimum offset for K2 for the UE. The offset capability can indicate the minimum offset for K2 or a parameter used to derive the minimum offset. Network entity 810 can receive capability information from multiple UEs. Each UE (e.g., UE 825, UE 830) can have different capabilities and therefore different minimum offsets. If no other UE has a minimum offset that would allow the reallocation of unused TOs, it may be of no benefit for UE 820 to send an indication of unused TOs to network entity 810. However, if there is at least one other UE (e.g., UE 830) with a minimum offset for K2 that would allow the reallocation of unused TOs, it is beneficial for UE 820 to send an indication of unused TOs to network entity 810. Network entity 810 can schedule UE 830 to use UE 820's unused TO.

[0105] In some respects, as indicated by reference numeral 840, network entity 810 may send a quantity threshold. Network entity 810 may send the quantity threshold in an RRC message. The quantity threshold may include the number of UEs that meet a threshold for the minimum offset against K2. For example, if too few UEs meet the minimum offset threshold, the probability that another UE can use an unused TO may be low, and indicating an unused TO may be a waste of signaling resources. If there are many UEs that can use an unused TO (meeting the minimum offset threshold), then indicating an unused TO will not be a waste of signaling resources because the probability that the unused TO will be reassigned to another UE is high. Network entity 810 may send the quantity threshold in a MAC CE. Network entity 810 may send the quantity threshold in a DCI.

[0106] As shown by reference numeral 845 in the attached figure, network entity 810 can send offset information associated with the minimum offset for K2. Transmitting component 810 can send offset information in an RRC message. Network entity 810 can send offset information in a MAC CE. Network entity 810 can send offset information in a DCI. When network entity 810 configures UE 820 for multiple PUSCH communications, network entity 810 can send offset information. The offset information can be associated with the configuration allowed by the PUSCH configuration.

[0107] In some aspects, the offset information can indicate the minimum offset for K2. Alternatively, in some aspects, the offset information can include multiple offset candidates for multiple UEs. For example, the offset information can include multiple K2 candidates, where each K2 candidate is for a UE among multiple UEs. As shown by reference numeral 850, if the offset information includes multiple offset candidates, UE 820 can select the minimum offset for K2 from the offset candidates. For example, UE 820 can select the maximum value among the offset candidates as the minimum offset for K2. UE 820 can select the minimum value among the offset candidates as the minimum offset for K2. UE 820 can select the average value among the offset candidates as the minimum offset for K2.

[0108] UE 820 can determine that a future TO will not be used. This determination can be based at least in part on the amount of traffic to be transmitted, traffic conditions, channel conditions, and / or the state of UE 820. In some aspects, UE 820 can base its determination at least in part on the time duration between the indicated uplink TO and the unused TO (e.g., D A minimum offset (e.g., K2) is used to send an indication of an unused TO. As shown in Figure 855, if K2 is less than or equal to... D Then UE 820 can send an indication of unused TO. Alternatively, as shown by reference numeral 860 in the attached figure, if K2 is greater than D Then UE 820 can avoid sending instructions for unused TOs.

[0109] In some respects, UE 820 may further transmit indications of unused TOs based at least in part on the number of UEs meeting a quantity threshold. The number of UEs may also be based at least in part on meeting another threshold (e.g., minimum offset capability, where K2 for a UE is less than a certain threshold). DIf the number of UEs meets a number threshold (e.g., the number of UEs is equal to or greater than the number threshold), UE 820 can send indications for unused TOs (or multiple unused TOs). If the number of UEs does not meet the number threshold, UE 820 can avoid sending indications for unused TOs. By using offset information notified by the capabilities of other UEs, UE 820 can avoid sending indications for unused TOs that will not be used. Therefore, signaling resources are saved.

[0110] In some aspects, when network entity 810 configures UE 820 for multi-PUSCH CG, network entity 810 can indicate offset candidates to UE 820 using RRC signaling, and the number threshold can be pre-configured using DCI. In some aspects, for Type 2 CG-PUSCH scheduling (periodic RRC configuration of CG), when network entity 810 triggers UE 820 for multi-PUSCH CG, network entity 810 can indicate offset candidates to UE 820 using MAC CE, and the number threshold can be pre-configured using MAC CE or DCI. In some aspects, for Type 2 CG-PUSCH scheduling, when network entity 810 triggers UE 820 for multi-PUSCH CG, network entity 810 can indicate the minimum offset relative to K2 to UE 820 using MAC CE or DCI.

[0111] As shown by reference numeral 865 in the attached figure, network entity 810 may (e.g., via RRC signaling) send an updated quantity threshold. The updated quantity threshold may include more or fewer UEs than the existing quantity threshold. As shown by reference numeral 870 in the attached figure, network entity 810 may send updated offset information. The updated offset information may indicate a new minimum offset for K2 or different offset candidates for the minimum offset.

[0112] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0113] Figure 9 This is an example diagram 900 illustrating the updated offset information and updated threshold according to this disclosure.

[0114] If more UEs attach to the cell, more K2 candidates will emerge. In some respects, network entity 810 can send updated offset information to UE 820 in an intermediate downlink time slot. For example, network entity 810 can configure UE 820 with offset information and a quantity threshold at downlink time slot 902. The offset information can include updated K2 candidates. The offset information can indicate the minimum offset for the updated K2.

[0115] At downlink slot 904, network entity 810 may send updated offset information (e.g., K2 candidate, minimum offset) to UE 820 via RRC signaling. Network entity 810 may also send updated quantity thresholds to UE 820 (e.g., via RRC signaling) to override previously configured quantity thresholds.

[0116] In some respects, network entity 810 can send updated offset information to UE 820 via MAC CE. Network entity 810 can also send updated quantity thresholds to UE 820 via MAC CE or DCI in intermediate downlink time slots.

[0117] In some aspects, network entity 810 may send offset information and / or updated offset information in the Wake-up Signal (WUS). The WUS may be a low-power WUS designed to be received by a low-power radio device that uses less power than the primary radio device and / or operates in a power-saving mode. The WUS may wake up UE 820, causing UE 820 to use more radio components or operate the primary radio device. In some aspects, network entity 810 may send quantity thresholds and / or updated quantity thresholds in the WUS.

[0118] In some respects, network entity 810 may send multiple K2 candidates with corresponding indices (e.g., in an index table) to UE 820 (e.g., via RRC signaling, MAC CE, or DCI) or configure the UE with the multiple K2 candidates. Network entity 810 may send the index of one of the multiple K2 candidates as the minimum offset for K2. Network entity 810 may send the index in WUS. For example, index 1 may indicate that the minimum offset for K2 will be the offset for the first K2 candidate for the first UE, index 2 may indicate that the minimum offset for K2 will be the offset for the second K2 candidate for the second UE, index 3 may indicate that the minimum offset for K2 will be the offset for the third K2 candidate for the third UE, and so on.

[0119] In some respects, network entity 810 may send multiple K2 candidates and a corresponding number of UEs to UE 820 (e.g., via RRC signaling, MAC CE, DCI, low-power WUS) or configure the UE with multiple K2 candidates and a corresponding number of UEs. The K2 candidate values ​​and the number of UEs with the same K2 value may be stored in a data structure (such as an index table). Network entity 810 may send the index of one of the multiple K2 candidates as a minimum offset for K2. At any given time, network entity 810 may have accurate information about the K2 values ​​of all attached UEs and how many UEs have the same K2 value.

[0120] Network entity 810 can send an indication of whether the number of UEs with the same K2 value is increasing or decreasing. Network entity 810 can indicate an instantaneous change in the number of UEs with the same K2 value via MAC CE, DCI, or low-power WUS. For example, if one or more UEs are attached to network entity 810 and their K2 value is K2_0, then network entity 810 indicates... X = X +1. If a UE with K2_0 is transferred to another cell, network entity 810 indicates... X = X -1.

[0121] In some respects, network entity 810 indicates offset information (e.g., minimum offset for K2, multiple K2 values) and / or quantity thresholds to multiple or all UEs with multicast or broadcast modes. Network entity 810 may periodically multicast or broadcast the offset information and / or quantity thresholds to ensure that K2 values ​​are updated regularly. Multicast or broadcasting can save signaling resources and time compared to indicating offset information and / or quantity thresholds individually to each UE. Network entity 810 may use a public DCI (with a specific Radio Network Temporary Identifier (RNTI)) for multicast or broadcasting.

[0122] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0123] Figure 10 This is a diagram illustrating an example procedure 1000 performed by a UE according to this disclosure. Example procedure 1000 is an example in which a UE (e.g., UE 120, UE 820) performs an operation associated with a minimum offset value for an indication of an unused TO.

[0124] like Figure 10 As shown, in some aspects, process 1000 may include receiving offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication (box 1010). For example, the UE (e.g., using...) Figure 12 The communication manager 140 and / or receiving component 1202 depicted above can receive offset information associated with the minimum offset between scheduling grant and corresponding PUSCH communication.

[0125] like Figure 10 Further shown, in some aspects, process 1000 may include transmitting the indication (box 1020) at least in part based on the time duration between the uplink TO and the unused TO being equal to or greater than a minimum offset. For example, the UE (e.g., using...) Figure 12The communication manager 140 and / or the transmitting component 1204 depicted above may transmit the indication at least in part based on the time duration between the uplink TO and the unused TO being equal to or greater than the minimum offset.

[0126] 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 process descriptions elsewhere herein.

[0127] In the first aspect, process 1000 includes transmitting capability information indicating the offset capability of the UE.

[0128] In the second aspect, either alone or in combination with the first aspect, the offset information indicates the minimum offset.

[0129] In a third aspect, receiving offset information, either alone or in combination with one or more of the first and second aspects, includes receiving offset information in an RRC message.

[0130] In the fourth aspect, the offset information is associated with the configuration permitted by the PUSCH configuration, either alone or in combination with one or more of the first to third aspects.

[0131] In the fifth aspect, receiving offset information, either alone or in combination with one or more of the first to fourth aspects, includes receiving offset information in the DCI or MAC CE associated with PUSCH configuration permission.

[0132] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the offset information includes the number of offset candidates associated with multiple UEs, and the process 1000 includes selecting the minimum offset from the offset candidates.

[0133] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, sending an indication of an unused TO includes further sending an indication of an unused TO based at least in part on the number of offset candidates satisfying a quantity threshold.

[0134] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1000 includes receiving a threshold number of data via the first DCI or the first MAC CE.

[0135] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1000 includes receiving an updated quantity threshold via a second DCI or a second MAC CE.

[0136] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 1000 includes a threshold for the number of first RRC messages received.

[0137] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 1000 includes receiving an updated quantity threshold via a second RRC message.

[0138] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1000 includes receiving updated offset information including the number of offset candidates.

[0139] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 1000 includes receiving updated offset information indicating an updated minimum offset.

[0140] In the fourteenth aspect, receiving offset information, either alone or in combination with one or more of the first to thirteenth aspects, includes receiving offset information in WUS.

[0141] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, process 1000 includes receiving updated offset information in WUS.

[0142] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 1000 includes receiving a plurality of offset candidates with corresponding indices via an RRC message or a MAC CE, and receiving offset information includes receiving a WUS including an index corresponding to the offset candidate.

[0143] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 1000 includes receiving a plurality of offset candidates and a number of UEs for each offset candidate, and receiving WUS that increments or decrements the number of UEs for each offset candidate.

[0144] In the eighteenth aspect, receiving offset information, either alone or in combination with one or more of the first to seventeenth aspects, includes receiving offset information in broadcast or multicast.

[0145] although Figure 10 An example box of process 1000 is shown, but in some respects, process 1000 may include... Figure 10 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0146] Figure 11This is a diagram illustrating an example process 1100 performed by a network entity, for example, according to this disclosure. Example process 1100 is an example in which a network entity (e.g., network node 110, network entity 810) performs an operation associated with a minimum offset value for an indication of an unused TO.

[0147] like Figure 11 As shown, in some aspects, process 1100 may include generating offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication, and associated with the UE determining an indication to send an unused TO (box 1110). For example, network entities (e.g., using...) Figure 15 The communication manager 150 and / or offset component 1508 described above can generate offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication and associated with the UE determining an indication to send an unused TO.

[0148] like Figure 11 As further shown, in some aspects, process 1100 may include sending offset information (box 1120). For example, network entities (e.g., using...) Figure 15 The communication manager 150 and / or the transmitting component 1504 depicted above can transmit offset information.

[0149] 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 process descriptions elsewhere herein.

[0150] In the first aspect, process 1100 includes receiving an instruction for an unused TO.

[0151] In a second aspect, either alone or in combination with the first aspect, process 1100 includes receiving capability information indicating the offset capabilities of each of a plurality of UEs, and generating offset information includes generating offset information based at least in part on the capability information of each UE.

[0152] In the third aspect, either alone or in combination with one or more of the first and second aspects, the offset information indicates the minimum offset.

[0153] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the offset information includes the number of offset candidates associated with multiple UEs.

[0154] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1100 includes transmitting a threshold number of UEs associated with the transmission of TO.

[0155] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1100 includes sending an update quantity threshold.

[0156] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1100 includes sending updated offset information.

[0157] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1100 includes sending a plurality of offset candidates with corresponding indices via an RRC message or MAC CE, and sending offset information includes sending a WUS including an index corresponding to the offset candidate.

[0158] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 1100 includes sending a plurality of offset value candidates and a number of UEs for each offset candidate, and sending WUS that increments or decrements the number of UEs for each offset candidate.

[0159] In the tenth aspect, sending offset information, either alone or in combination with one or more of the first to ninth aspects, includes sending offset information in broadcast or multicast.

[0160] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in process 1100 may be executed in parallel.

[0161] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a UE (e.g., UE 120, UE 820), or a UE may include device 1200. In some aspects, device 1200 includes a receiving component 1202 and a transmitting component 1204 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1200 can use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1206 (such as a UE, a base station, or another wireless communication device). As further shown, device 1200 may include a communication manager 140. Communication manager 140 may include an offset component 1208, etc.

[0162] In some respects, device 1200 can be configured to perform the functions described herein. Figures 1 to 9 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 10 Process 1000 Figure 11 The process 1100 or a combination thereof. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

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

[0164] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1206. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1206. In some aspects, 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 device 1206. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1204 may be co-located with the receive component 1202 in a transceiver.

[0165] The receiving component 1202 can receive offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication. The transmitting component 1204 can transmit the indication at least in part based on the time duration between the uplink TO used for indicating an unused TO and the unused TO being equal to or greater than the minimum offset. The offset component 1208 can compare the minimum offset with the time duration. The transmitting component 1204 can transmit capability information indicating the UE's offset capability.

[0166] The receiving component 1202 can receive the quantity threshold via a first DCI or a first MAC CE. The receiving component 1202 can receive an updated quantity threshold via a second DCI or a second MAC CE. The receiving component 1202 can receive the quantity threshold via a first RRC message. The receiving component 1202 can receive an updated quantity threshold via a second RRC message.

[0167] The receiving component 1202 can receive updated offset information including the number of updated offset candidates. The receiving component 1202 can also receive updated offset information indicating the minimum offset for the update. The receiving component 1202 can receive updated offset information in WUS.

[0168] The receiving component 1202 can receive multiple offset candidates with corresponding indices via RRC messages or MAC CE, and the receiving component 1202 can receive WUS including the indices corresponding to the offset candidates. The receiving component 1202 can receive multiple offset candidates and the number of UEs for each offset candidate, and the receiving component 1202 can receive WUS that increments or decrements the number of UEs for each offset candidate.

[0169] Figure 12 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The set (one or more) components shown are executable and described by Figure 12 Another set of components shown performs one or more functions.

[0170] Figure 13 This is a diagram illustrating an example 1300 of a hardware implementation of an apparatus 1305 employing a processing system 1310 according to the present disclosure. Apparatus 1305 may be a network entity.

[0171] Processing system 1310 can be implemented using a bus architecture typically represented by bus 1315. Bus 1315 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1310 and overall design constraints. Bus 1315 links together various circuits including one or more processors and / or hardware components (represented by processor (or processing circuitry) 1320, illustrated components, and computer-readable medium / memory (or memory circuitry) 1325). Processor 1320 may include multiple processors, such as processor 1320a, memory 1320b, and memory 1320c. Memory 1325 may include multiple memories, such as memory 1325a, memory 1325b, and memory 1325c. Bus 1315 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuitry.

[0172] Processing system 1310 may be coupled to transceiver 1330. Transceiver 1330 is coupled to one or more antennas 1335. Transceiver 1330 provides components for communicating with various other devices via a transmission medium. Transceiver 1330 receives signals from one or more antennas 1335, extracts information from the received signals, and provides the extracted information to processing system 1310 (specifically, receiving component 1202). Furthermore, transceiver 1330 receives information from processing system 1310 (specifically, transmitting component 1204) and generates signals to be applied to one or more antennas 1335, at least in part, based on the received information.

[0173] Processing system 1310 includes a processor 1320 coupled to a computer-readable medium / memory 1325. Processor 1320 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1325. When executed by processor 1320, the software causes processing system 1310 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1325 may also be used to store data manipulated by processor 1320 during software execution. The processing system also includes at least one of the illustrated components. A component may be a software module running in processor 1320, residing in / stored on computer-readable medium / memory 1325, one or more hardware modules coupled to processor 1320, or some combination thereof.

[0174] In some aspects, processing system 1310 may be a component of UE 120 and may include at least one of memory 282, and / or TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In some aspects, apparatus 1305 for wireless communication includes a component that receives offset information associated with a minimum offset between scheduling permission and corresponding PUSCH communication. In some aspects, apparatus 1305 for wireless communication includes a component that transmits an indication at least in part based on the time duration between an uplink TO and an unused TO being equal to or greater than a minimum offset. The aforementioned components may be one or more of the aforementioned components of processing system 1310 of apparatus 1200 and / or apparatus 1305 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 1310 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In one configuration, the aforementioned components may be a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280 configured to perform the functions and / or operations set forth herein.

[0175] Figure 13 This is provided as an example. Other examples can be combined with it. Figure 13 The examples described are different.

[0176] Figure 14 This is a diagram illustrating an example 1400 of a specific implementation of code and circuitry for device 1405 according to the present disclosure. The circuitry may include processing circuitry and memory circuitry. Device 1405 may be a UE, or a UE may include device 1405.

[0177] like Figure 14 As shown, device 1405 may include circuitry (circuit 1420) for receiving offset information associated with the minimum offset between scheduling grant and the corresponding PUSCH communication. For example, circuitry 1420 may enable device 1405 to receive offset information associated with the minimum offset between scheduling grant and the corresponding PUSCH communication.

[0178] like Figure 14 As shown, apparatus 1405 may include code (code 1425) stored in computer-readable medium 1325 for receiving offset information associated with the minimum offset between scheduling grant and corresponding PUSCH communication. For example, when executed by processor 1320, code 1425 may cause processor 1320 to cause transceiver 1330 to receive the offset information associated with the minimum offset between scheduling grant and corresponding PUSCH communication.

[0179] like Figure 14As shown, device 1405 may include circuitry (circuit 1430) for transmitting the indication at least in part based on the time duration between the uplink TO for the indication of an unused TO and the unused TO being equal to or greater than a minimum offset. For example, circuitry 1430 may enable device 1405 to transmit the indication at least in part based on the time duration between the uplink TO for the indication of an unused TO and the unused TO being equal to or greater than a minimum offset.

[0180] like Figure 14 As shown, apparatus 1405 may include code (code 1435) stored in computer-readable medium 1325 for transmitting the indication at least in part based on the time duration between the uplink TO for the indication of the unused TO and the unused TO being equal to or greater than a minimum offset. For example, when executed by processor 1320, code 1435 may cause processor 1320 to cause transceiver 1330 to transmit the indication at least in part based on the time duration between the uplink TO for the indication of the unused TO and the unused TO being equal to or greater than a minimum offset.

[0181] Figure 14 This is provided as an example. Other examples can be combined with it. Figure 14 The examples described are different.

[0182] Figure 15 This is a diagram of an example device 1500 for wireless communication according to the present disclosure. Device 1500 may be a network entity (e.g., network node 110, network entity 810), or a network entity may include device 1500. In some aspects, device 1500 includes a receiving component 1502 and a transmitting component 1504 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1500 can use the receiving component 1502 and the transmitting component 1504 to communicate with another device 1506 (such as a UE, a base station, or another wireless communication device). As further shown, device 1500 may include a communication manager 150. Communication manager 150 may include an offset component 1508, etc.

[0183] In some respects, device 1500 can be configured to perform the functions described herein. Figures 1 to 9 One or more operations described herein. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 11 The process 1100. In some respects, Figure 15 The illustrated device 1500 and / or one or more components may include a combination Figure 2 One or more components of the described network entity. Additionally or alternatively, Figure 15 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0184] Receiver 1502 may receive communications from device 1506, such as reference signals, control information, data communications, or combinations thereof. Receiver 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receiver 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1500. In some aspects, receiver 1502 may include combinations of... Figure 2 The network entity described includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0185] Transmitting component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and provide the generated communications to transmitting component 1504 for transmission to device 1506. In some aspects, transmitting component 1504 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 device 1506. In some aspects, transmitting component 1504 may include combinations of... Figure 2 The described network entity includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, transmit component 1504 may be co-located with receive component 1502 in a transceiver.

[0186] Offset component 1508 can generate offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication, and associated with the UE determining an indication to transmit an unused TO. Transmission component 1504 can transmit the offset information.

[0187] The receiving component 1502 can receive indications of unused TOs. The receiving component 1502 can receive capability information indicating the offset capabilities of each of the multiple UEs, and the offset component 1508 can generate offset information based at least in part on the capability information of each UE.

[0188] The transmitting component 1504 can transmit a threshold number of UEs associated with the transmission of TO. The transmitting component 1504 can also transmit updated threshold numbers.

[0189] The sending component 1504 can send updated offset information. The sending component 1504 can send multiple offset candidates with corresponding indices via RRC messages or MACCE, and the sending component 1504 can send WUS including the indices corresponding to the offset candidates.

[0190] The transmitting component 1504 can transmit multiple offset value candidates and the number of UEs for each offset candidate, and the transmitting component 1504 can transmit WUS that increments or decrements the number of UEs for each offset candidate.

[0191] Figure 15 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 15 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 15 The two or more components shown can be implemented within a single component, or Figure 15 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 The set (one or more) components shown are executable and described by Figure 15 Another set of components shown performs one or more functions.

[0192] Figure 16 This is an illustration of an example 1600 of a hardware implementation of an apparatus 1605 for employing a processing system 1610 according to the present disclosure. Apparatus 1605 may be a network entity.

[0193] Processing system 1610 can be implemented using a bus architecture typically represented by bus 1615. Bus 1615 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1610 and overall design constraints. Bus 1615 links together various circuits including one or more processors and / or hardware components (represented by processor (or processing circuitry) 1620, illustrated components, and computer-readable medium / memory (or memory circuitry) 1625). Processor 1320 may include multiple processors, such as processor 1302a, memory 1320b, and memory 1320c. Memory 1325 may include multiple memories, such as memory 1325a, memory 1325b, and memory 1325c. Bus 1615 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuitry.

[0194] Processing system 1610 may be coupled to transceiver 1630. Transceiver 1630 is coupled to one or more antennas 1635. Transceiver 1630 provides components for communicating with various other devices via a transmission medium. Transceiver 1630 receives signals from one or more antennas 1635, extracts information from the received signals, and provides the extracted information to processing system 1610 (specifically, receiving component 1502). Furthermore, transceiver 1630 receives information from processing system 1610 (specifically, transmitting component 1504) and generates signals to be applied to one or more antennas 1635, at least in part, based on the received information.

[0195] Processing system 1610 includes a processor 1620 coupled to a computer-readable medium / memory 1625. Processor 1620 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1625. When executed by processor 1620, the software causes processing system 1610 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1625 may also be used to store data manipulated by processor 1620 during software execution. The processing system also includes at least one of the illustrated components. A component may be a software module running in processor 1620, residing in / stored on computer-readable medium / memory 1625, one or more hardware modules coupled to processor 1620, or some combination thereof.

[0196] In some aspects, processing system 1610 may be a component of base station 110 and may include memory 242 and / or at least one of TX MIMO processor 230, RX processor 238, and / or controller / processor 240. In some aspects, apparatus 1605 for wireless communication includes components for generating offset information associated with a minimum offset between scheduling grant and corresponding PUSCH communication and associated with the UE determining an indication to transmit an unused TO. In some aspects, apparatus 1605 for wireless communication includes components for transmitting offset information. The aforementioned components may be one or more of the aforementioned components of apparatus 1500 and / or processing system 1610 of apparatus 1605 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 1610 may include TX MIMO processor 230, receiver processor 238, and / or controller / processor 240. In one configuration, the aforementioned components may be TX MIMO processor 230, receiver processor 238, and / or controller / processor 240 configured to perform the functions and / or operations stated herein.

[0197] Figure 16 This is provided as an example. Other examples can be combined with it. Figure 16 The examples described are different.

[0198] Figure 17 This is an illustration of example 1700 of a specific implementation of code and circuitry for device 1705 according to the present disclosure. The circuitry may include processing circuitry and memory circuitry. Device 1705 may be a network entity, or a network entity may include device 1705.

[0199] like Figure 17 As shown, apparatus 1705 may include circuitry (circuit 1720) for generating offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication and associated with the UE determining an indication to transmit an unused TO. For example, circuitry 1720 may enable apparatus 1705 to generate offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication and associated with the UE determining an indication to transmit an unused TO.

[0200] like Figure 17As shown, apparatus 1705 may include code (code 1725) stored in computer-readable medium 1625 for generating offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication and associated with the UE determining an indication to send an unused TO. For example, when executed by processor 1620, code 1725 may cause processor 1620 to generate offset information associated with the minimum offset between scheduling permission and the corresponding PUSCH communication and associated with the UE determining an indication to send an unused TO.

[0201] like Figure 17 As shown, device 1705 may include circuitry (circuit 1730) for transmitting offset information. For example, circuitry 1730 enables device 1705 to transmit offset information.

[0202] like Figure 17 As shown, device 1705 may include code (code 1735) stored in computer-readable medium 1625 for transmitting offset information. For example, when executed by processor 1620, code 1735 may cause processor 1620 to cause transceiver 1630 to transmit offset information.

[0203] Figure 17 This is provided as an example. Other examples can be combined with it. Figure 17 The examples described are different.

[0204] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed at a user equipment (UE), the method comprising: receiving offset information associated with a minimum offset between scheduling-granted and corresponding physical uplink shared channel (PUSCH) communication; and transmitting the indication at least in part based on an uplink TO for indicating an unused transmission opportunity (TO) and the unused TO having a time duration equal to or greater than the minimum offset.

[0205] Aspect 2: According to the method of aspect 1, the method further includes sending capability information indicating the offset capability of the UE.

[0206] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the offset information indicates the minimum offset.

[0207] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the offset information includes receiving the offset information in a radio resource control message.

[0208] Aspect 5: According to the method described in aspect 4, the offset information is associated with the configuration granted by the PUSCH configuration.

[0209] Aspect 6: The method according to any one of Aspects 1 to 5, wherein receiving the offset information includes receiving the offset information in downlink control information or media access control control element (MAC CE) associated with PUSCH configuration permission.

[0210] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the offset information includes a number of offset candidates associated with a plurality of UEs, and wherein the method includes selecting the minimum offset from the offset candidates.

[0211] Aspect 8: According to the method of aspect 7, wherein sending the indication to the unused TO includes further sending the indication to the unused TO based at least in part on the number of offset candidates satisfying a number threshold.

[0212] Aspect 9: According to the method of aspect 8, the method further includes receiving the quantity threshold via a first downlink control information (DCI) or a first media access control element (MAC CE).

[0213] Aspect 10: According to the method of aspect 9, the method further includes receiving an updated quantity threshold via a second DCI or a second MAC CE.

[0214] Aspect 11: According to the method of aspect 8, the method further includes receiving the quantity threshold via a first radio resource control (RRC) message.

[0215] Aspect 12: According to the method of aspect 11, the method further includes receiving an updated quantity threshold via a second RRC message.

[0216] Aspect 13: The method according to any one of aspects 1 to 12, the method further includes receiving updated offset information including an updated number of offset candidates.

[0217] Aspect 14: The method according to any one of aspects 1 to 13, the method further comprising receiving updated offset information indicating the minimum offset to be updated.

[0218] Aspect 15: The method according to any one of Aspects 1 to 14, wherein receiving the offset information includes receiving the offset information in a wake-up signal.

[0219] Aspect 16: The method according to any one of aspects 1 to 15, the method further comprising receiving updated offset information in a wake-up signal.

[0220] Aspect 17: The method according to any one of Aspects 1 to 16, the method further comprising receiving a plurality of offset candidates having corresponding indices via a radio resource control message or a media access control element (MAC CE), wherein receiving the offset information includes receiving a wake-up signal including an index corresponding to the offset candidate.

[0221] Aspect 18: The method according to any one of Aspects 1 to 17, the method further comprising receiving a plurality of offset candidates and a number of UEs for each offset candidate, and wherein the method includes receiving a wake-up signal that increments or decrements the number of UEs for the offset candidates.

[0222] Aspect 19: The method according to any one of Aspects 1 to 18, wherein receiving the offset information includes receiving the offset information in a broadcast or multicast.

[0223] Aspect 20: A method for wireless communication performed at a network entity, the method comprising: generating offset information associated with a minimum offset between scheduling permission and corresponding Physical Uplink Shared Channel (PUSCH) communication and associated with a User Equipment (UE) determining an indication to transmit an unused Transmission Timing (TO); and transmitting the offset information.

[0224] Aspect 21: The method according to aspect 20 further includes receiving an indication of the unused TO.

[0225] Aspect 22: The method according to any one of aspects 20 to 21, the method further comprising receiving capability information indicating the offset capability of each of a plurality of UEs, and wherein generating the offset information includes generating the offset information at least in part based on the capability information of each UE.

[0226] Aspect 23: The method according to any one of aspects 20 to 22, wherein the offset information indicates the minimum offset.

[0227] Aspect 24: The method according to any one of Aspects 20 to 23, wherein the offset information includes the number of offset candidates associated with a plurality of UEs.

[0228] Aspect 25: The method according to any one of Aspects 20 to 24, the method further comprising transmitting a threshold number of UEs associated with the transmission of TO.

[0229] Aspect 26: According to the method of aspect 25, the method further includes a threshold for the number of updates to be sent.

[0230] Aspect 27: The method according to any one of aspects 20 to 26, the method further comprising sending updated offset information.

[0231] Aspect 28: The method according to any one of Aspects 20 to 27, the method further comprising transmitting a plurality of offset candidates having corresponding indices via a radio resource control message or a media access control element (MAC CE), wherein transmitting the offset information comprises transmitting a wake-up signal including an index corresponding to the offset candidate.

[0232] Aspect 29: The method according to any one of Aspects 20 to 28, the method further comprising sending a plurality of offset value candidates and a number of UEs for each offset candidate, and wherein the method comprises sending a wake-up signal that increments or decrements the number of UEs for the offset candidates.

[0233] Aspect 30: The method according to any one of Aspects 20 to 29, wherein sending the offset information includes sending the offset information in a broadcast or multicast.

[0234] Aspect 31: 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 the method according to one or more of aspects 1 to 30.

[0235] Aspect 32: An apparatus for wireless communication, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 30.

[0236] Aspect 33: 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 30.

[0237] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 1 to 30.

[0238] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 30.

[0239] Aspect 36: A user equipment (UE) for wireless communication, the user equipment (UE) comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the UE to perform the method according to one or more of aspects 1 to 19.

[0240] Aspect 37: An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, and the one or more processors being configured to cause the UE to: receive offset information associated with a minimum offset between scheduling-granted and corresponding Physical Uplink Shared Channel (PUSCH) communication; and transmit the indication at least in part based on an uplink TO indicating an unused transmission opportunity (TO) and the unused TO having a time duration equal to or greater than the minimum offset.

[0241] Aspect 38: The apparatus according to aspect 37, wherein the one or more processors are individually or jointly configured to cause the UE to: receive offset information associated with a minimum offset between scheduling-granted and corresponding Physical Uplink Shared Channel (PUSCH) communication; and transmit the indication at least in part based on the time duration between the uplink TO for indicating an unused transmission opportunity (TO) and the unused TO being equal to or greater than the minimum offset.

[0242] Aspect 39: A network entity for wireless communication, the network entity comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the network entity to perform the method according to one or more of aspects 20 to 30.

[0243] Aspect 40: An apparatus for wireless communication at a network entity, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network entity to: generate offset information associated with a minimum offset between scheduled and corresponding Physical Uplink Shared Channel (PUSCH) communication and with an indication of unused transmission opportunities (TO); and transmit the offset information.

[0244] Aspect 41: The apparatus according to aspect 40, wherein the one or more processors are individually or jointly configured to cause the network entity to: generate offset information associated with the minimum offset between scheduling permission and corresponding Physical Uplink Shared Channel (PUSCH) communication and associated with an indication of unused transmission opportunities (TO); and transmit the offset information.

[0245] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit all aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various practices.

[0246] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referenced herein to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0247] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0248] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0249] 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 may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase referring to “at least one of” in the list of items means any combination of these items, including 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 having 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).

[0250] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and configured to cause the UE to: receive offset information associated with a minimum offset between a scheduling grant and a corresponding physical uplink shared channel (PUSCH) communication; and transmit an indication of an unused transmission occasion (TO) based at least in part on a time duration between the uplink TO for the indication and the unused TO being equal to or greater than the minimum offset.

2. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to transmit capability information indicating an offset capability of the UE.

3. The apparatus of claim 1, wherein the offset information indicates the minimum offset.

4. The apparatus of claim 1, wherein to receive the offset information, the one or more processors are configured to cause the UE to receive the offset information in a radio resource control message.

5. The apparatus of claim 4, wherein the offset information is associated with a configuration of a PUSCH configuration grant.

6. The apparatus of claim 1, wherein to receive the offset information, the one or more processors are configured to cause the UE to receive the offset information in a downlink control information or medium access control control element (MAC CE) associated with a PUSCH configuration grant.

7. The apparatus of claim 1, wherein the offset information comprises a number of offset candidates associated with a plurality of UEs, and wherein the one or more processors are configured to cause the UE to select the minimum offset from the offset candidates.

8. The apparatus of claim 7, wherein to transmit the indication of the unused TO, the one or more processors are configured to cause the UE to transmit the indication of the unused TO further based at least in part on the number of offset candidates satisfying a number threshold.

9. The apparatus of claim 8, wherein the one or more processors are configured to cause the UE to receive the number threshold via a first downlink control information (DCI) or a first medium access control control element (MAC CE).

10. The apparatus of claim 9, wherein the one or more processors are configured to cause the UE to receive an updated number threshold via a second DCI or a second MAC CE.

11. The apparatus of claim 8, wherein the one or more processors are configured to cause the UE to receive the number threshold via a first radio resource control (RRC) message.

12. The apparatus of claim 11, wherein the one or more processors are configured to cause the UE to receive an updated number threshold via a second RRC message.

13. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to receive updated offset information comprising an updated number of offset candidates.

14. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to receive updated offset information indicating an updated minimum offset.

15. The apparatus of claim 1, wherein to receive the offset information, the one or more processors are configured to cause the UE to receive the offset information in a wake-up signal.

16. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to receive updated offset information in a wake-up signal.

17. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to receive a plurality of offset candidates with corresponding indices via a radio resource control message or a medium access control control element (MAC CE), and wherein to receive the offset information, the one or more processors are configured to receive a wake-up signal comprising an index corresponding to an offset candidate.

18. The apparatus of claim 1, wherein the one or more processors are configured to cause the UE to receive a plurality of offset candidates and a number of UEs for each offset candidate, and wherein the one or more processors are configured to cause the UE to receive a wake-up signal that increments or decrements the number of UEs for an offset candidate.

19. The apparatus of claim 1, wherein to receive the offset information, the one or more processors are configured to cause the UE to receive the offset information in a broadcast or multicast.

20. An apparatus for wireless communication at a network entity, the apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and configured to cause the network entity to: generate offset information associated with a minimum offset between a scheduling grant and a corresponding physical uplink shared channel (PUSCH) communication and associated with an indication of unused transmission occasions (TOs); and transmit the offset information.

21. The apparatus of claim 20, wherein the one or more processors are configured to cause the network entity to receive the indication of the unused TOs.

22. The apparatus of claim 20, wherein the one or more processors are configured to cause the network entity to receive, from each UE of a plurality of UEs, capability information indicating an offset capability of the UE, and wherein to generate the offset information, the one or more processors are configured to generate the offset information based at least in part on the capability information of each UE.

23. The apparatus of claim 20, wherein the offset information indicates the minimum offset.

24. The apparatus of claim 20, wherein the offset information comprises a number of offset candidates associated with a plurality of UEs.

25. The apparatus of claim 20, wherein the one or more processors are configured to cause the network entity to transmit a quantity threshold of UEs associated with transmission of TOs.

26. The apparatus of claim 25, wherein the one or more processors are configured to cause the network entity to transmit an updated quantity threshold.

27. The apparatus of claim 20, wherein the one or more processors are configured to cause the network entity to transmit updated offset information.

28. The apparatus of claim 20, wherein the one or more processors are configured to cause the network entity to transmit, via a radio resource control message or a medium access control control element (MAC CE), a plurality of offset candidates with corresponding indices, and wherein to transmit the offset information, the one or more processors are configured to cause the network entity to transmit a wake-up signal that includes an index corresponding to an offset candidate.

29. The apparatus of claim 20, wherein the one or more processors are configured to cause the network entity to transmit a plurality of offset value candidates and a quantity of UEs for each offset candidate, and wherein the one or more processors are configured to cause the network entity to transmit a wake-up signal that increments or decrements the quantity of UEs for an offset candidate.

30. The apparatus of claim 20, wherein to transmit the offset information, the one or more processors are configured to transmit the offset information in a broadcast or a multicast.

Images