Full duplex considerations for configuration grant transmission occasion

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. User equipment (UE) can receive control messages indicating full-duplex (FD) related resources allocated for one or more uplink shared channel messages and corresponding to a set of uplink transmission opportunities within a time period configured by a configuration grant (CG). The UE can transmit uplink control information (UCI) messages using at least one of the uplink transmission opportunities according to the CG configuration. These UCI messages include an indication of the number of unused uplink transmission opportunities. The indication can exclude one or more invalid uplink transmission opportunities based on conflicts between one or more downlink messages or monitored opportunities and one or more uplink shared channel messages. The UE can transmit one or more acknowledgment (ACK) or negative acknowledgment (NACK) messages based on an identifier used to exclude invalid uplink transmission opportunities.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 409,285, filed January 10, 2024, entitled “FULL-DUPLEX CONSIDERATIONS FOR CONFIGURED GRANT TRANSMISSION OCCASIONS”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following pertains to wireless communication, including full-duplex (FD) considerations for the timing of configuration grant (CG) transmission (TO). Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting full-duplex (FD) considerations for Configuration Grant (CG) Transmission Timing (TO). One or more Invalid Uplink Transmission Timings (UTOs) can be defined for FD communications, including Subband Full-Duplex (SBFD). For example, a User Equipment (UE) can consider UTOs (including CG Physical Uplink Shared Channel (PUSCH) TOs that at least partially overlap with one or more downlink messages as invalid. Based on identifying invalid UTOs, the UE can send UTO Uplink Control Information (UTO-UCI) that indicates one or more unused (e.g., skipped, reserved) UTOs and excludes invalid UTOs. For example, the UE can avoid using one or more bits of the UTO-UCI that would otherwise be used to indicate invalid UTOs, which reduces message size and improves system efficiency. The UE can also exclude invalid UTOs when determining feedback identifiers (IDs) (such as those used for Hybrid Automatic Repeat Request (HARQ) ID calculation), which improves the efficiency of HARQ ID management. In some cases, a UTO may be considered invalid due to conflicts with the Physical Downlink Control Channel (PDCCH) monitoring timing, with the Search Space Set (SSS), or with the Tracking Reference Signal (TRS), and may be further determined based on the message priority, periodicity, or time offset threshold of the conflict.

[0006] A method for wireless communication by a UE is described. The method may include: receiving a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more full-duplex resources; and, according to the CG configuration, transmitting a UCI message using at least one UTO from the set of multiple UTOs, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0007] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code (e.g., instructions) and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code (e.g., instructions) to cause the UE to: receive a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more FD resources; and, according to the CG configuration, transmit a UCI message using at least one UTO from the set of multiple UTOs, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict based on one or more downlink messages with one or more uplink shared channel messages associated with one or more FD resources.

[0008] Another UE for wireless communication is described. The UE may include components for receiving a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more FD resources; and components for transmitting a UCI message using at least one UTO from the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more FD resources; and, according to the CG configuration, transmit a UCI message using at least one UTO from the set of multiple UTOs, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0010] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for sending one or more acknowledgment or negative acknowledgment messages based on an identifier based on a first uplink shared channel timing of a first UTO in a set of multiple UTOs, wherein the identifier may also be based on the number of unused UTOs excluded from the indication.

[0011] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for: transmitting one or more second uplink shared channel messages during one or more valid UTOs in a set of multiple UTOs, as configured by the CG; and receiving one or more downlink messages during one or more invalid UTOs.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the UCI message may be multiplexed with each of one or more second uplink shared channel messages that may be transmitted during one or more valid UTOs.

[0013] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for receiving a semi-static indication of the priority of each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages, wherein one or more invalid UTOs may be excluded based on the fact that the uplink shared channel message in one or more uplink shared channel messages has a first priority and the downlink message in one or more downlink messages has a second priority higher than the first priority.

[0014] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for receiving dynamic indications of priority for each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages, wherein one or more invalid UTOs may be excluded based on a duration that satisfies a threshold duration between the end of receiving the dynamic indication and the start time for sending a UCI message.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more invalid UTOs can be excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and a downlink control channel monitoring timing associated with one or more FD resources.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more invalid UTOs may be excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and one or more SSSs associated with one or more FD resources.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more invalid UTOs may be excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and one or more TRSs associated with one or more FD resources.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more invalid UTOs may be excluded based on a first periodicity associated with one or more uplink shared channel messages and a second periodicity associated with one or more downlink messages.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the UCI message includes a bitmap comprising: one or more first bits indicating a first subset of a set of multiple UTOs including the number of unused UTOs; and one or more second bits indicating a second subset of a set of multiple UTOs including the number of used UTOs.

[0020] A method for wireless communication by a network entity is described. The method may include: outputting a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more FD resources; and obtaining a UCI message during at least one UTO in the set of multiple UTOs, according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0021] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code (e.g., instructions) and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code (e.g., instructions) to cause the network entity to: output a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more FD resources; and, according to the CG configuration, obtain a UCI message during at least one UTO in the set of multiple UTOs, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict based on one or more downlink messages with one or more uplink shared channel messages associated with one or more FD resources.

[0022] Another network entity for wireless communication is described. This network entity may include: components for outputting a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more FD resources; and components for obtaining a UCI message during at least one UTO in the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0023] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by a CG, wherein the set of multiple resources includes one or more FD resources; and, according to the CG configuration, obtain a UCI message during at least one UTO in the set of multiple UTOs, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict based on one or more downlink messages with one or more uplink shared channel messages associated with one or more FD resources.

[0024] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining one or more acknowledgment or negative acknowledgment messages based on an identifier based on a first uplink shared channel timing of a first UTO in a set of multiple UTOs, wherein the identifier may also be based on the number of unused UTOs excluded from the indication.

[0025] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining one or more second uplink shared channel messages during one or more valid UTOs in a set of multiple UTOs according to CG configuration; and outputting one or more downlink messages during one or more invalid UTOs.

[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a UCI message may be multiplexed with each of one or more second uplink shared channel messages that may be obtained during one or more valid UTOs.

[0027] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a semi-static indication of the priority of each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages, wherein one or more invalid UTOs may be excluded based on the fact that the uplink shared channel message in one or more uplink shared channel messages has a first priority and the downlink message in one or more downlink messages has a second priority higher than the first priority.

[0028] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a dynamic indication of priority for each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages, wherein one or more invalid UTOs may be excluded based on a duration that satisfies a threshold duration associated with the downlink message and UCI message in one or more downlink messages.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more invalid UTOs can be excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and a downlink control channel monitoring timing associated with one or more FD resources.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more invalid UTOs may be excluded based on a conflict between one or more uplink shared channel messages and one or more SSSs associated with one or more FD resources.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more invalid UTOs can be excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and one or more TRS associated with one or more FD resources.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, one or more invalid UTOs may be excluded based on a first periodicity associated with one or more uplink shared channel messages and a second periodicity associated with one or more downlink messages.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a UCI message includes a bitmap comprising: one or more first bits indicating a first subset of a set of multiple UTOs, including the number of unused UTOs; and one or more second bits indicating a second subset of a set of multiple UTOs, including the number of used UTOs. Attached Figure Description

[0034] Figure 1 An example of a wireless communication system that supports full-duplex (FD) considerations for configuration grant (CG) transmission timing (TO) according to one or more aspects of this disclosure is shown.

[0035] Figure 2 Examples of wireless communication systems supporting FD considerations for CG TO are shown according to one or more aspects of this disclosure.

[0036] Figure 3 An example of a resource allocation diagram supporting FD considerations for CG TO is shown, according to one or more aspects of this disclosure.

[0037] Figure 4 An example of a process flow supporting FD considerations for CG TO is shown in accordance with one or more aspects of this disclosure.

[0038] Figure 5 and Figure 6 A block diagram of a device supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown.

[0039] Figure 7 A block diagram of a communication manager supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown.

[0040] Figure 8 A diagram is shown of a system including a device supporting FD considerations for CG TO, according to one or more aspects of this disclosure.

[0041] Figure 9 and Figure 10 A block diagram of a device supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown.

[0042] Figure 11 A block diagram of a communication manager supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown.

[0043] Figure 12 A diagram is shown of a system including a device supporting FD considerations for CG TO, according to one or more aspects of this disclosure.

[0044] Figures 13 to 15 A flowchart illustrating a method for supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. Detailed Implementation

[0045] Network entities may indicate multiple uplink transmit opportunities (UTOs) for use during the configuration grant (CG) period. For example, a network entity may configure a UE using multiple CGPUSCH transmit opportunities (TOs) for sending Physical Uplink Shared Channel (PUSCH) messages. In some cases, a UE may send an uplink control information (UCI) message indicating one or more UTOs that the UE is not using (e.g., skipping). This UCI may be referred to as UTO-UCI and may, for example, enable enhanced resource utilization in the network by implementing the reallocation of unused resources. In some examples, the UE and network entities may identify conflicts between signaling that could invalidate some UTOs. In such cases, invalid UTOs may not be indicated via UTO-UCI, and therefore the UE may not use the additional bits in the UCI associated with invalid UTOs, thereby reducing the UCI size and increasing throughput.

[0046] Some wireless communication systems support full-duplex (FD) communication. For example, one or more wireless devices (e.g., network entities, UEs) can use FD communication technologies (such as subband full-duplex (SBFD) communication, in-band full-duplex (IBFD) communication, etc.) to communicate with other wireless devices. In such cases, the wireless devices can simultaneously receive and transmit signaling via one or more FD resources (e.g., FD time slots). The wireless devices can operate using FD communication within a subband of a component carrier (CC) (e.g., a single CC with frequency subbands defined for uplink and downlink communication) or across corresponding CCs (e.g., a first set of one or more CCs for uplink communication and a second set of one or more CCs for downlink communication). However, in some cases, conflicts between uplink and downlink signaling may be introduced in FD communication. For example, in SBFD, a network entity may support simultaneous transmission and reception with a half-duplex (HD) UE using uplink and downlink subbands, and in some cases, the UE may experience conflicts between uplink and downlink messages. While UEs and network entities may include conflict resolution rules for SBFDs, such devices may lack protocols and rules for identifying invalid UTOs in SBFDs. Therefore, conventional techniques may cause UEs to indicate invalid UTOs via UTO-UCI, which can lead to excessive resource usage (e.g., unnecessarily including additional bits in the UTO-UCI) and reduced system efficiency.

[0047] As described herein, the network can define invalid UTOs for SBFD. For example, a UE can consider a UTO that overlaps with one or more downlink messages (e.g., CG-PUSCH TO) invalid and can remove bits from the UCI (e.g., UTO-UCI) that would otherwise indicate such timing to include additional information or reduce message size. Furthermore, the UE can exclude invalid timings when determining feedback identifiers (IDs) (such as those used for Hybrid Automatic Repeat Request (HARQ) ID calculations), which improves the efficiency of HARQ ID management. The UE can consider a UTO invalid due to conflicts with Physical Downlink Control Channel (PDCCH) monitoring timings, conflicts with Search Space Sets (SSS), or conflicts with Tracking Reference Signals (TRS). The validity of a UTO in SBFD can also be defined based on the conflicting message priority, periodicity, or persistence. The UE and network entities can also define invalid and valid UTOs based on a timing offset threshold between the indication and transmission of the UCI.

[0048] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated by signaling diagrams, resource allocation diagrams, and process flows relating to FD considerations for CGTO, and are described with reference to these diagrams. The various aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to FD considerations for CGTO, and are described with reference to these diagrams.

[0049] Figure 1 An example of a wireless communication system 100 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0050] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0051] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0052] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0053] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0054] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0055] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0056] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0057] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0058] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support FD considerations for CG TO as described herein. For example, some operations described as being performed by UE115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0059] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0060] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0061] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0062] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0063] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0064] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0065] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0066] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0067] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0068] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0069] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more SSSs, and each SSS can include one or more control channel candidates arranged in a cascaded manner with one or more aggregation levels. The aggregation level of the control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. SSS may include a common SSS configured to transmit control information to multiple UEs 115 and a UE-specific SSS configured to transmit control information to a specific UE 115.

[0070] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0071] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0072] Some UE 115s (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0073] Some UE 115s can be configured to operate in a reduced power consumption mode, such as HD communication (e.g., a mode that supports unidirectional communication via transmission or reception but not concurrent transmission and reception). In some examples, HD communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0074] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0075] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0076] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0077] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0078] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0079] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0080] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0081] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0082] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0083] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0084] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0085] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0086] As described herein, wireless communication system 100 may support protocols involving invalid UTOs defined for SBFD communication. For example, UE 115 may determine that one or more PUSCH TOs at least partially overlap with one or more downlink messages or monitoring opportunities, and UE 115 may remove bits in the UCI sent to network entity 105 that would otherwise be used to indicate such invalid opportunities. UE 115 may, for example, include additional information in place of the removed bits, or may reduce the message size. Furthermore, UE 115 may exclude such invalid opportunities when determining the feedback ID (e.g., HARQ ID).

[0087] Figure 2 An example of a wireless communication system 200 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. Wireless communication system 200 may be implemented or can be implemented to implement aspects of wireless communication system 100. For example, wireless communication system 200 may exemplify signaling between UE 115-a and network entity 105-a, the UE and the network entity may represent as regarding Figure 1 The UE 115 and network entity 105 are described. UE 115-a and network entity 105-a can also communicate using uplink communication link 205 and downlink communication link 210, which can be examples of communication link 125. In some examples, wireless communication system 200 can support the exclusion of invalid UTOs during UCI message transmission and HARQ ID determination in SBFD communication as described herein.

[0088] In some examples, UE 115-a and network entity 105-a may support communication during CG cycle 215-a based on a previously configured setup. For example, UE 115-a may receive control message 235-a (e.g., a semi-static message) indicating resources for the CG, including four UTOs (e.g., CG-PUSCH TO) 220-a, 220-b, 220-c, and 220-d within CG cycle 215-a. Message 225-a (e.g., a control message, corresponding to a PUCCH message) may be based on a previous RRC information element (IE) (e.g., ConfiguredGrantConfig) that defines the periodicity, timers, resources, and other parameters for the CG. In some cases, multiple UTOs may be allocated in each CG cycle for each service (e.g., uplink service, downlink service) cycle used by UE 115-a. For example, UTOs 220-a to 220-d can be used to send message 225, which could be an example of a data burst for uplink traffic of extended reality (XR) video, such as augmented reality (AR) video or virtual reality (VR) video. The start of CG cycle 215-a can also be aligned with the corresponding data generation cycle. Pre-configured CG resources allow UE115-a to reduce uplink transmission latency compared to resource requests based on scheduling requests (SRs) and buffer status reports (BSRs), resulting in relatively high uplink data rates and low-latency periodic traffic. For example, after data arrives at UE115-a's uplink data buffer, UE115-a can immediately begin sending PUSCH messages during UTOs 220-a to 220-d without additional overhead signaling. In some examples, if a CG includes multiple CG-PUSCH TOs, the CG may be referred to as a multi-PUSCH CG.

[0089] UE 115-a can also support indicating UTOs not used in uplink data transmission via UCI (e.g., UTO-UCI), allowing network entity 105-a to reallocate unused resources to other UEs 115. For example, UE 115-a may determine that data (e.g., AR service via PUSCH) is being transmitted in UTOs 220-a, 220-b, and 220-c, but there may not be enough data to be transmitted in UTO 220-d. UE 115-a can send a bitmap in the UCI indicating that UTOs 220-a through 220-c are used and UTO 220-d is not used. In some examples, network entity 105-a may configure UE 115-a to send a UCI indicating an unused UTO, and in some cases, UE 115-a may be configured to send a UCI for each used UTO in each sent message 225 of CG cycle 215-a (e.g., multiplexed with each sent message or as part of that message).

[0090] An invalid UTO can be defined for the technology and UTO-UCI associated with multiple UTOs (e.g., multiple PUSCH CGs). For example, for unpaired spectrum (e.g., in TDD), UE 115-a and network entity 105-a may determine that a CG PUSCH TO is invalid if the timing conflicts with one or more downlink symbols indicated by one or more provided parameters (e.g., by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided). Additionally or alternatively, network entity 105-a and UE 115-a may determine that a timing is invalid if a CG PUSCH TO conflicts with one or more symbols of a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block (SSB), where the index may be provided by a second parameter (e.g., by ssb-PositionsInBurst). Such conflicts may also include conflicts with Synchronization Signal (SSB) blocks used for inter-cell multiple TRP communications. In some cases, dynamic conflicts and cancellations of CG PUSCH can be disregarded in invalid CG PUSCH TO determination. In some examples, UE 115-a may not indicate skipping such opportunities because these opportunities are unusable anyway and are known to both the UE and the network entity. For example, invalid UTO states (e.g., used or unused) can be excluded from UTO-UCI to reduce UTO-UCI payload size. Furthermore, invalid opportunities can be excluded from HARQ ID determination to improve the efficiency of HARQ ID management.

[0091] UE 115-a and network entity 105-a may also support SBFD communication. For example, network entity 105-a may support one or more subbands (of a frequency band) for uplink communication and one or more subbands for one or more downlink communication, and may use different subbands to simultaneously receive and transmit messages. In contrast, UE 115-a may be an HDUE and may determine whether to transmit or receive in one or more SBFD symbols based on dynamic scheduling (e.g., monitoring PDCCH candidates) or semi-static signaling (e.g., from network entity 105-a). In some cases, UE 115-a may receive RRC messages (e.g., including CG configuration) indicating the use of default uplink or downlink behavior. Because UE 115-a is aware of and able to communicate with network entity 105-a that supports FD and SBFD communication, UE 115-a may be referred to as an FD-capable UE or an SBFD-aware UE, or similar terms. For example, after establishing a connection with the network (e.g., moving to an RRC connection state or mode), UE 115-a is aware of the SBFD and TDD configurations supported at network entity 105-a. In some examples, UE 115-a and network entity 105-a may support SBFD in XR applications to improve coverage and reduce uplink latency.

[0092] SBFD communication can lead to additional conflicts in communication at HD UE 115-a. For example, one or more SBFD symbols transmitted for uplink in one or more schedules may overlap with one or more symbols transmitted for downlink in one or more schedules. In some cases, uplink and downlink conflict handling rules can be defined (or indicated via configuration messages) at UE 115-a for SBFD to allow UE 115-a to decide whether to transmit or receive. For example, UE 115-a can be configured to prioritize PDCCH monitoring timing and TRS over semi-static PUSCH message transmission when PDCCH monitoring timing, TRS, and semi-static PUSCH message transmission conflict in SBFD communication. However, some UEs and network entities may lack definitions, rules, or protocols for invalidating UTOs in SBFD (e.g., based on such conflict handling).

[0093] As described herein, UE 115-a may determine that one or more UTOs are invalid for SBFD communication. For example, UE 115-a may send a UCI message 230-a indicating the number of unused UTOs (e.g., UTO 220-d) that can exclude one or more invalid UTOs 220 to facilitate additional information or reduce the size of the UCI. In some examples, UE 115-a may invalidate UTO 220-b based on a conflict between message 225-b and a scheduled semi-static downlink message (such as a TRS or PDCCH monitoring timing). UE 115-a may also determine the HARQ ID based on (e.g., using) UTO 220-a (e.g., a first configured CG-PUSCH TO, whether valid or invalid) and based on UTOs 220-b and 220-d (e.g., a subsequent valid CG-PUSCH TO) but excluding invalid UTO 220-c. For example, UE 115-a may send an ACK or NACK message 240-a (e.g., HARQ-ACK) based on the HARQ ID, wherein UE 115-a may not indicate that the HARQ ID (e.g., process number) is not incremented for such invalid occasions. Additionally or alternatively, UE 115-a may receive one or more indications (such as indication 245-a), which may include updates to one or more conflict handling rules (e.g., updates due to priority, indication of the priority of the update, indication of other handling rules).

[0094] Figure 3 An example of a resource allocation diagram 300 for a wireless communication system supporting FD considerations for CG TO, according to one or more aspects of this disclosure, is shown. Resource allocation diagram 300 may be implemented or can be implemented to realize aspects of wireless communication system 100 and wireless communication system 200. For example, resource allocation diagram 300 may illustrate an example resource allocation for message passing between UE 115-a and network entity 105-a in SBFD communication, wherein network entity 105-a and UE 115-a may be configured with subband 340-a for uplink communication and subbands 340-b and 340-c for downlink communication. Figure 3 In the illustrated example, UCI 330-a (e.g., a UCI message) may instruct UTOs 320-a, 320-b, 320-c, and 320-d for sending one or more uplink messages 325 within a CG period 315-a of the CG configuration. The CG period 315-a may lie between a period for downlink signaling and a period for uplink signaling. As described herein, UE115-a may support identifying invalid UTOs in SBFD resources.

[0095] In some examples, for UE 115-a (e.g., a UE aware of SBFD), UTO 320 in the SBFD symbol (e.g., CG-PUSCH TO, the TO for sending PUSCH) may be considered invalid due to conflicts with one or more downlink messages or monitoring opportunities (including PDCCH monitoring opportunities), SSS, and TRS. For example, UE 115-a may have a downlink message 342-a (or monitoring opportunity) scheduled during one or more symbols of UTO 320-b, wherein downlink message 342-a may be any of a PDCCH monitoring opportunity (e.g., for receiving one or more PDCCH messages), SSS, or TRS. UE 115-a may also have an uplink message 325-b (e.g., CG-PUSCH) scheduled during one or more symbols of UTO 320-b, wherein the symbols of downlink message 342-a may, for example, at time 350 at least partially overlap with those symbols of uplink message 325-b. Based on this overlap, UE 115-a can determine that UTO 320-b is invalid.

[0096] In some examples, UE 115 may send a UCI based on invalid timings. For example, the UTO-UCI window for the indication of UCI 330-a may have a bitmap size of three timings following the first UTO 320-a (e.g., corresponding to the sizes of the remaining UTOs 320-b, 320-c, and 320-d). However, due to a conflict with downlink message 342-a, the indication may not span UTO 320-b and uplink message 325-b. For example, UCI 330-a may indicate a bitmap of [1, 1] to indicate the last two UTOs, while excluding bits for invalid UTO 320-b. In some examples, UCI 330-a may indicate a value of "0" for any unused UTO 320. In some examples, UE 115-a may transmit UCI 330-a in each uplink message 325 sent during the used timing of UTO 320-a, 320-c, and 320-d. Furthermore, UE 115-a may transmit UCI 330-a in the first UTO 320-a of CG cycle 315-a (e.g., together with uplink message 325-a), regardless of whether the first timing is valid or invalid. In some aspects, for SBFD UEs (e.g., SBFD-UEs), following CG-PUSCH TO... Invalid TOs can be excluded, where the UE does not send CG-PUSCH due to a conflict between CG-PUSCH and PDCCH monitoring timing, SSS or TRS, or any combination thereof. By excluding such TOs, the UE can use spare bits to indicate skipping valid timings or reduce the size of the bitmap for RRC configuration, which can increase communication throughput.

[0097] Additionally or alternatively, the HARQ ID can be determined for the first configured UTO and subsequent valid UTOs within the CG cycle, but not for invalid UTOs. For example, UE 115-a can determine ID 335-a, such as a HARQ ID, based on incrementing the valid UTO 320 (e.g., CG PUSCH TO) after the first configured UTO 320-a in CG cycle 315-a. For example, the HARQ ID can be incremented according to [0, -, 1, 2], where "-" can indicate skipping the ID increment due to a conflict in UTO 320-b. In some aspects, when a certain number of slots (e.g., nrofSlots_InCGperiod) are configured for a Type 1 CG or Type 2 CG, the HARQ process ID for the Kth valid configuration PUSCH grant (e.g., 1 < K ≤ nrofSlots_InCGperiod) is determined, excluding invalid configuration PUSCH grants that were not sent due to conflicts between PUSCH and PDCCH monitoring timing, SSS, or TRS. Such exclusion improves HARQ ID management (e.g., for XR UEs in SBFD) while maintaining reduced latency by using multiple UTOs per CG cycle.

[0098] In some examples, UE 115-a may receive indication 345-a from network entity 105-a to semi-statically update one or more conflict resolution (e.g., drop) rules. For example, UE 115-a may receive indication 345-a that indicates the timing of CGPUSCH, TRS, SSS, PDCCCH monitoring, and other semi-static signaling, as well as the corresponding priorities of uplink and downlink signaling, and UE 115-a may determine whether a UTO is invalid or valid and drop the UTO based on the indication. In some examples, the indication may indicate prioritization of semi-persistent or persistent message reception, or prioritization of semi-periodic or periodic message reception. Furthermore, the indication may indicate prioritization of signaling based on the periodicity of one or more messages. UE 115-a may also receive dynamic indications (e.g., one or more indications 345-a) to dynamically update conflict resolution rules. In some examples, the indication may be received via MAC-CE, DCI, or another type of signaling.

[0099] Network entity 105-a or UE 115-a may also define a threshold duration 355-a to determine when to invalidate and exclude UTO 320. The threshold duration 355-a may be a time offset threshold (e.g., a minimum time offset threshold, Toffset) between the end of the received indication 345-a (which results in the cancellation of one or more UTOs 320) and the start time used to send UCI 330-a. For example, indication 345-a may cause the cancellation of uplink message 325-b in UTO 320-b because the updated priority indicates a higher priority for downlink message 342-a. If the offset (e.g., difference) in the time domain between the end of indication 345-a and the start of UCI 330-a (e.g., the start of a PUSCH carrying UCI 330-a (e.g., UTO-UCI)) is less than (e.g., shorter in duration than) a threshold, then UCI 330-a may not be affected by the latest updated priority. For example, if the threshold is not met, UE 115-a may not cancel subsequent transmissions and invalidate them due to the update's priority. Otherwise, UCI 330-a may be affected by higher-priority downlink messages and may indicate skipping one or more of the remaining timings. In some examples, the threshold duration 355-a may be based on the PUSCH preparation time. or Additionally or alternatively, UE 115-a may receive dynamic updates to prioritize signaling-related priorities or persistence / periodicity to alter conflict handling (e.g., drop) rules. For example, for a dynamic update in indication 345-a, if a dynamic update is provided earlier than a threshold duration 355-a, UE 115-a may update UTO-UCI (and correspondingly cancel indication CG-PUSCH).

[0100] Figure 4 An example of a process flow 400 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. Process flow 400 may be implemented or can be implemented to implement aspects of wireless communication system 100, wireless communication system 200, and resource allocation diagram 300. For example, process flow 400 may be implemented by UE 115-b and network entity 105-b, which may be as described herein (including references). Figure 1 Example of the corresponding device (to Figure-3).

[0101] In the following description of process flow 400, operations (such as reporting or providing) may be performed in a different order than shown, or operations performed by the example device may be performed in a different order or at different times. Some operations may also be omitted from process flow 400, or other operations may be added to process flow 400. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously or otherwise concurrently.

[0102] At 405, UE 115-b can receive a control message, and network entity 105-b can output (e.g., via a transmitting device of network entity 105-b or a transmitting device coupled to the network entity) the control message, which indicates a set of multiple resources allocated for one or more uplink shared channel messages. In some examples, the set of multiple resources may correspond to a set of multiple uplink transmission opportunities (e.g., UTOs) within a time period configured by the CG. The set of multiple resources may include one or more FD resources.

[0103] At 410, UE 115-b may optionally receive an indication, and network entity 105-b may optionally output the indication. For example, UE 115-b may receive a semi-static indication of the priority of each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages. Additionally or alternatively, UE 115-b may receive a dynamic indication of the priority of each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages.

[0104] At 415, UE 115-b may send a UCI message, and network entity 105-b may receive (e.g., via a receiving device of network entity 105-b or a receiving device coupled to the network entity) the UCI message, which includes an indication of the number of unused UTOs in a set of multiple UTOs. For example, UE 115-b may, according to CG configuration, send a UCI using at least one UTO in the set of multiple UTOs or during at least one UTO in the set of multiple UTOs. In some examples, this indication may exclude one or more invalid UTOs based on conflicts between one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0105] In some examples, based on receiving a semi-static indication at 410, one or more invalid UTOs can be excluded based on the fact that the uplink shared channel message in one or more uplink shared channel messages has a first priority and the downlink message in one or more downlink messages has a second priority higher than the first priority. Additionally or alternatively, based on receiving a dynamic indication at 410, one or more invalid UTOs can be excluded based on a duration that satisfies (e.g., equal to, less than, or exceeds) a threshold duration, which is between the end of receiving the dynamic indication and the start time for sending the UCI message.

[0106] In some examples, one or more invalid UTOs may be excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and one or more downlink control channel monitoring timings associated with one or more FD resources. Additionally or alternatively, one or more invalid UTOs may be excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and one or more SSSs associated with one or more FD resources, and one or more TRSs associated with one or more FD resources, or both. Additionally or alternatively, one or more invalid UTOs may be excluded based on a first periodicity associated with one or more uplink shared channel messages and a second periodicity associated with one or more downlink messages.

[0107] In some examples, a UCI message may include a bitmap. This bitmap may include: one or more first bits indicating a first subset of the set of multiple UTOs, including the number of unused UTOs; and one or more second bits indicating a second subset of the set of multiple UTOs, including the number of used UTOs.

[0108] At 420, UE 115-b may optionally send one or more ACK or NACK messages (e.g., HARQ-ACK / NACK for feedback) based on an identifier (e.g., HARQ process ID), and network entity 105-b may optionally receive the one or more ACK or NACK messages. The identifier may be based on a first uplink shared channel timing of a first UTO in a set corresponding to a plurality of UTOs, and may also be based on the number of unused UTOs excluded from the indication.

[0109] At 425, according to the CG configuration, during one or more valid UTOs in a set of multiple UTOs, UE 115-a may optionally send one or more second uplink shared channel messages, and network entity 105-b may optionally receive the one or more second uplink shared channel messages. In some examples, the UCI message may be multiplexed with each of the one or more second uplink shared channel messages sent during one or more valid UTOs.

[0110] At 430, during one or more invalid UTOs, UE 115-a may optionally receive one or more downlink messages, and network entity 105-b may optionally output the one or more downlink messages.

[0111] Figure 5 A block diagram 500 is shown of a device 505 supporting FD considerations for CG TO according to one or more aspects of this disclosure. Device 505 may be an example of aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0112] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to FD considerations for CG TO). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0113] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to FD considerations for CG TO), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0114] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the FD considerations for CG TO as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0115] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0116] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0117] In some examples, the communication manager 520 may be configured to use a receiver 510, a transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or integrate with the receiver 510, the transmitter 515, or a combination of both to acquire information, output information, or perform various other operations as described herein.

[0118] Communication manager 520 may support wireless communication according to examples disclosed herein. For example, communication manager 520 may be capable of, configured to, or operable to support components for receiving control messages indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of multiple resources includes one or more FD resources. Communication manager 520 may be capable of, configured to, or operable to support components for transmitting a UCI message using at least one UTO from the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict based on one or more downlink messages with one or more uplink shared channel messages associated with one or more FD resources.

[0119] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof, or at least one processor coupled to the receiver, transmitter, communication manager or a combination thereof) can support techniques for reducing processing, lowering power consumption, and more efficiently utilizing communication resources by supporting the exclusion of invalid UTOs in the determination of UTO-UCI and HARQ-ID for SBFD and other FD communications, as well as supporting additional conflict handling rules in SBFD.

[0120] Figure 6 A block diagram 600 is shown of a device 605 supporting FD considerations for CG TO according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0121] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to FD considerations for CG TO). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0122] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to FD considerations for CG TO), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0123] Device 605 or its various components may be examples of parts used to perform various aspects of the FD considerations for CG TO as described herein. For example, communication manager 620 may include resource component 625, UCI component 630, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0124] Communication manager 620 can support wireless communication according to the examples disclosed herein. Resource component 625 is capable of, configured to, or operable to support components for receiving a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of multiple resources includes one or more FD resources. UCI component 630 is capable of, configured to, or operable to support components for transmitting a UCI message using at least one UTO from the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict based on one or more downlink messages with one or more uplink shared channel messages associated with one or more FD resources.

[0125] Figure 7A block diagram 700 is shown of a communication manager 720 supporting FD considerations for CG TO according to one or more aspects of this disclosure. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of FD considerations for CG TO as described herein. For example, the communication manager 720 may include a resource component 725, a UCI component 730, an acknowledgment component 735, a messaging component 740, an instruction component 745, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0126] Communication manager 720 can support wireless communication according to the examples disclosed herein. Resource component 725 is capable of, configured to, or operable to support components for receiving a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of multiple resources includes one or more FD resources. UCI component 730 is capable of, configured to, or operable to support components for transmitting a UCI message using at least one UTO from the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict based on one or more downlink messages with one or more uplink shared channel messages associated with one or more FD resources.

[0127] In some examples, the acknowledgment component 735 is capable of, configured to, or able to operate to support components for sending one or more acknowledgment or negative acknowledgment messages based on an identifier based on a first uplink shared channel timing of a first UTO in a set of multiple UTOs, wherein the identifier is also based on the number of unused UTOs excluded from the indication.

[0128] In some examples, message component 740 is capable of, configured to, or operable to support components for transmitting one or more second uplink shared channel messages during one or more valid UTOs in a set of multiple UTOs, configured according to the CG. In some examples, message component 740 is capable of, configured to, or operable to support components for receiving one or more downlink messages during one or more invalid UTOs.

[0129] In some examples, the UCI message is multiplexed with each of the second uplink shared channel messages in one or more second uplink shared channel messages sent during one or more valid UTOs.

[0130] In some examples, the indicative component 745 is capable of, configured to, or able to operate to support a component for receiving a semi-static indication of the priority of each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages, wherein one or more invalid UTOs are excluded based on the fact that the uplink shared channel message in one or more uplink shared channel messages has a first priority and the downlink message in one or more downlink messages has a second priority higher than the first priority.

[0131] In some examples, the indication component 745 is capable of, configured to, or able to operate to support a component for receiving dynamic indications of priority for each of one or more downlink messages and each of one or more uplink shared channel messages, wherein one or more invalid UTOs are excluded based on a duration that satisfies a threshold duration between the end of receiving the dynamic indication and the start time for sending the UCI message.

[0132] In some examples, one or more invalid UTOs are excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and a downlink control channel monitoring timing associated with one or more FD resources.

[0133] In some examples, one or more invalid UTOs are excluded based on conflicts between one or more uplink shared channel messages and one or more SSSs associated with one or more FD resources.

[0134] In some examples, one or more invalid UTOs are excluded based on conflicts between one or more uplink shared channel messages and one or more TRS associated with one or more FD resources.

[0135] In some examples, one or more invalid UTOs are excluded based on a first periodicity associated with one or more uplink shared channel messages and a second periodicity associated with one or more downlink messages.

[0136] In some examples, the UCI message includes a bitmap comprising: one or more first bits indicating a first subset of the set of multiple UTOs, including the number of unused UTOs; and one or more second bits indicating a second subset of the set of multiple UTOs, including the number of used UTOs.

[0137] Figure 8 A diagram of a system 800 including device 805 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

[0138] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0139] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825 as described herein, or via a wired or wireless link. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0140] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 830 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0141] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., supporting functions or tasks for FD considerations for CG TO). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, at least one processor 840 and at least one memory 830 being configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured to, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0142] Communication manager 820 may support wireless communication according to examples disclosed herein. For example, communication manager 820 may be capable of, configured to, or operable to support components for receiving control messages indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of multiple resources includes one or more FD resources. Communication manager 820 may be capable of, configured to, or operable to support components for transmitting a UCI message using at least one UTO from the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0143] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for reducing latency, lowering power consumption and extending battery life, utilizing communication resources more efficiently, improving the utilization of processing power, and improving the user experience associated with reduced processing by supporting the exclusion of invalid UTOs in the determination of UTO-UCI and HARQ ID for FD communication (including SBFD) and supporting additional conflict handling rules in SBFD.

[0144] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 815, one or more antennas 825, or any combination thereof, or otherwise cooperating with them. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or performed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of the FD considerations for CG TO as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0145] Figure 9A block diagram 900 is shown of a device 905 supporting FD considerations for CG TO according to one or more aspects of this disclosure. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0147] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0148] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the FD considerations for CG TO as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0149] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0150] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0151] In some examples, the communication manager 920 may be configured to use a receiver 910, a transmitter 915, or both, or otherwise cooperate with the receiver, the transmitter, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or integrate with the receiver 910, the transmitter 915, or a combination of both to acquire information, output information, or perform various other operations as described herein.

[0152] Communication manager 920 may support wireless communication according to examples disclosed herein. For example, communication manager 920 may be capable of, configured to, or operable to support components for outputting control messages indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by CG, wherein the set of multiple resources includes one or more FD resources. Communication manager 920 may be capable of, configured to, or operable to support components for obtaining a UCI message during at least one UTO in the set of multiple UTOs according to CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs based on conflicts between one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0153] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., at least one processor controlling receiver 910, transmitter 915, communication manager 920, or combinations thereof, or otherwise coupled to receiver, transmitter, communication manager, or combinations thereof) can support techniques for reducing processing, lowering power consumption, and more efficiently utilizing communication resources by supporting the exclusion of invalid UTOs in UTO-UCI and HARQ-ID determination for SBFD and other FD communications, as well as supporting additional conflict handling rules in SBFD.

[0154] Figure 10 A block diagram 1000 of a device 1005 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0155] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0156] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0157] Device 1005 or its various components may be examples of parts used to perform various aspects of the FD considerations for CG TO as described herein. For example, communication manager 1020 may include resource component 1025, UCI component 1030, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with the receiver, transmitter, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0158] Communication manager 1020 can support wireless communication according to the examples disclosed herein. Resource component 1025 is capable of, configured to, or operable to support components for outputting a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by CG, wherein the set of multiple resources includes one or more FD resources. UCI component 1030 is capable of, configured to, or operable to support components for obtaining a UCI message during at least one UTO in the set of multiple UTOs according to CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict based on one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0159] Figure 11 A block diagram 1100 is shown of a communication manager 1120 supporting FD considerations for CG TO according to one or more aspects of this disclosure. Communication manager 1120 may be an example of aspects of communication manager 920, communication manager 1020, or both as described herein. Communication manager 1120 or its various components may be examples of parts for performing various aspects of FD considerations for CG TO as described herein. For example, communication manager 1120 may include resource component 1125, UCI component 1130, acknowledgment component 1135, messaging component 1140, instruction component 1145, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0160] Communication manager 1120 can support wireless communication according to the examples disclosed herein. Resource component 1125 is capable of, configured to, or operable to support components for outputting a control message indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of multiple resources includes one or more FD resources. UCI component 1130 is capable of, configured to, or operable to support components for obtaining a UCI message during at least one UTO in the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs based on conflicts between one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0161] In some examples, the acknowledgment component 1135 is capable of, configured to, or able to operate to support components for obtaining one or more acknowledgment or negative acknowledgment messages based on an identifier based on a first uplink shared channel timing of a first UTO in a set of multiple UTOs, wherein the identifier is also based on the number of unused UTOs excluded from the indication.

[0162] In some examples, message component 1140 is capable of, configured to, or operable to support components for obtaining one or more second uplink shared channel messages during one or more valid UTOs in a set of multiple UTOs, configured according to the CG. In some examples, message component 1140 is capable of, configured to, or operable to support components for outputting one or more downlink messages during one or more invalid UTOs.

[0163] In some examples, the UCI message is multiplexed with each of the one or more second uplink shared channel messages obtained during one or more valid UTOs.

[0164] In some examples, the indicative component 1145 is capable of, configured to, or operable to support a component for outputting a semi-static indication of the priority of each downlink message in one or more downlink messages and each uplink shared channel message in one or more uplink shared channel messages, wherein one or more invalid UTOs are excluded based on the fact that the uplink shared channel message in one or more uplink shared channel messages has a first priority and the downlink message in one or more downlink messages has a second priority higher than the first priority.

[0165] In some examples, the indicative component 1145 is capable of, configured to, or able to operate to support a component for outputting a dynamic indication of the priority of each of one or more downlink messages and each of one or more uplink shared channel messages, wherein one or more invalid UTOs are excluded based on a duration that satisfies a threshold duration associated with the dynamic indication and the UCI message.

[0166] In some examples, one or more invalid UTOs are excluded based on a conflict between an uplink shared channel message in one or more uplink shared channel messages and a downlink control channel monitoring timing associated with one or more FD resources.

[0167] In some examples, one or more invalid UTOs are excluded based on conflicts between one or more uplink shared channel messages and one or more SSSs associated with one or more FD resources.

[0168] In some examples, one or more invalid UTOs are excluded based on conflicts between one or more uplink shared channel messages and one or more TRS associated with one or more FD resources.

[0169] In some examples, one or more invalid UTOs are excluded based on a first periodicity associated with one or more uplink shared channel messages and a second periodicity associated with one or more downlink messages.

[0170] In some examples, the UCI message includes a bitmap comprising: one or more first bits indicating a first subset of the set of multiple UTOs, including the number of unused UTOs; and one or more second bits indicating a second subset of the set of multiple UTOs, including the number of used UTOs.

[0171] Figure 12A diagram of a system 1200 including device 1205 supporting FD considerations for CG TO, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and acquisition of communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0172] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1215, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components, or be configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more memory components being operable to: perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both) may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0173] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more processors of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by a processor of at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may also include a BIOS, etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0174] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., supporting functions or tasks for FD considerations for CGTO). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more processors in at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 being configured to perform the various functions described herein. At least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1230) to perform the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or acquire input and process that input to produce, generate, or acquire output. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operable to cause the device 1205 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

[0175] In some examples, bus 1240 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1240 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1205 or between different components of device 1205, which may be co-located or located in different locations (e.g., device 1205 may refer to a system in which one or more of a communication manager 1220, transceiver 1210, at least one memory 1225, code 1230, and at least one processor 1235 may be located in one of the different components or divided between different components).

[0176] In some examples, the communication manager 1220 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1220 can manage the transfer of data communication with client devices (such as one or more UEs 115). In some examples, the communication manager 1220 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1220 may support the X2 interface in LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0177] Communication manager 1220 may support wireless communication according to examples disclosed herein. For example, communication manager 1220 may be capable of, configured to, or operable to support components for outputting control messages indicating a set of multiple resources allocated for one or more uplink shared channel messages, the set of multiple resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of multiple resources includes one or more FD resources. Communication manager 1220 may be capable of, configured to, or operable to support components for obtaining a UCI message during at least one UTO in the set of multiple UTOs according to the CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs based on conflicts between one or more downlink messages and one or more uplink shared channel messages associated with one or more FD resources.

[0178] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for reducing latency, lowering power consumption and extending battery life, utilizing communication resources more efficiently, improving the utilization of processing power, and improving the user experience associated with reduced processing by supporting the exclusion of invalid UTOs in the determination of UTO-UCI and HARQ ID for FD communication (including SBFD) and supporting additional conflict handling rules in SBFD.

[0179] In some examples, the communication manager 1220 may be configured to use a transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof, or otherwise cooperate with the transceiver, the one or more antennas, or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more of at least one processor 1235 to cause device 1205 to perform various aspects of the FD considerations for CG TO as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0180] Figure 13 A flowchart illustrating method 1300 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0181] At 1305, the method may include: receiving a control message indicating a set of resources allocated for one or more uplink shared channel messages, the set of resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of resources includes one or more FD resources. The operation of 1305 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference]. Figure 7 The resource component 725 described is used for execution.

[0182] At 1310, the method may include: transmitting a UCI message using at least one UTO from a set of multiple UTOs, according to a CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more uplink shared channel messages associated with one or more FD resources. The operation of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 7 The UCI component 730 described is used for execution.

[0183] Figure 14 A flowchart illustrating a method 1400 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0184] At 1405, the method may include: receiving a control message indicating a set of resources allocated for one or more uplink shared channel messages, the set of resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of resources includes one or more FD resources. The operation of 1405 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 7 The resource component 725 described is used for execution.

[0185] At 1410, the method may include: transmitting a UCI message using at least one UTO from a set of multiple UTOs, according to a CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more uplink shared channel messages associated with one or more FD resources. The operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 7 The UCI component 730 described is used for execution.

[0186] At 1415, the method may include: sending one or more acknowledgment or negative acknowledgment messages based on an identifier, the identifier being based on a first uplink shared channel timing corresponding to a first UTO in a set of multiple UTOs, wherein the identifier is further based on the number of unused UTOs excluded from the indication. The operation of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference]. Figure 7 The described confirmation component 735 is used for execution.

[0187] Figure 15 A flowchart illustrating a method 1500 supporting FD considerations for CG TO according to one or more aspects of this disclosure is shown. The operation of method 1500 may be implemented by a network entity or its components as described herein. For example, the operation of method 1500 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0188] At 1505, the method may include: outputting a control message indicating a set of resources allocated for one or more uplink shared channel messages, the set of resources corresponding to a set of multiple UTOs within a time period configured by the CG, wherein the set of resources includes one or more FD resources. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference]. Figure 11 The resource component 1125 described is used for execution.

[0189] At 1510, the method may include: obtaining a UCI message during at least one UTO in a set of multiple UTOs, according to a CG configuration, the UCI message including an indication of the number of unused UTOs in the set of multiple UTOs, wherein the indication excludes one or more invalid UTOs that conflict with one or more uplink shared channel messages associated with one or more FD resources. The operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to... Figure 11 The UCI component 1130 described is used to execute this.

[0190] The following provides an overview of the various aspects of this disclosure:

[0191] Aspect 1: A method for wireless communication by a UE, the method comprising: receiving a control message indicating the allocation of a plurality of resources for one or more uplink shared channel messages, the plurality of resources corresponding to a plurality of UTOs within a time period configured by a CG, wherein the plurality of resources includes one or more FD resources; and, according to the CG configuration, transmitting a UCI message using at least one of the plurality of UTOs, the UCI message including an indication of the number of unused UTOs among the plurality of UTOs, wherein the indication excludes one or more invalid UTOs that conflict at least in part based on one or more downlink messages with the one or more uplink shared channel messages associated with one or more FD resources.

[0192] Aspect 2: According to the method of aspect 1, the method further includes: sending one or more acknowledgment or negative acknowledgment messages based on an identifier, the identifier being at least partially based on a first uplink shared channel timing corresponding to a first UTO among the plurality of UTOs, wherein the identifier is also at least partially based on the number of unused UTOs excluded from the indication.

[0193] Aspect 3: The method according to any one of Aspects 1 to 2, further comprising: transmitting one or more second uplink shared channel messages during one or more valid UTOs among the plurality of UTOs, according to the CG configuration; and receiving the one or more downlink messages during the one or more invalid UTOs.

[0194] Aspect 4: According to the method of aspect 3, wherein the UCI message is multiplexed with each of the one or more second uplink shared channel messages transmitted during the one or more valid UTOs.

[0195] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: receiving a semi-static indication of priority for each downlink message in the one or more downlink messages and each uplink shared channel message in the one or more uplink shared channel messages, wherein the one or more invalid UTOs are excluded at least in part based on the fact that the uplink shared channel message in the one or more uplink shared channel messages has a first priority and the downlink message in the one or more downlink messages has a second priority higher than the first priority.

[0196] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: receiving a dynamic indication of priority for each of the one or more downlink messages and each of the one or more uplink shared channel messages, wherein the one or more invalid UTOs are excluded at least in part based on a duration satisfying a threshold duration, the duration being between the end of receiving the dynamic indication and the start time for sending the UCI message.

[0197] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the one or more invalid UTOs are excluded at least in part based on the conflict between the uplink shared channel message in the one or more uplink shared channel messages and the one or more downlink control channel monitoring timing associated with the one or more FD resources.

[0198] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the one or more invalid UTOs are excluded at least in part based on a conflict between the one or more uplink shared channel messages and one or more SSS associated with the one or more FD resources.

[0199] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the one or more invalid UTOs are excluded at least in part based on a conflict between the one or more uplink shared channel messages and one or more TRS associated with the one or more FD resources.

[0200] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the one or more invalid UTOs are excluded based at least in part on a first periodicity associated with the one or more uplink shared channel messages and a second periodicity associated with the one or more downlink messages.

[0201] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the UCI message includes a bitmap, the bitmap including: one or more first bits, the one or more first bits indicating a first subset of the number of unused UTOs among the plurality of UTOs; and one or more second bits, the one or more second bits indicating a second subset of the number of used UTOs among the plurality of UTOs.

[0202] Aspect 12: A method for wireless communication by a network entity, the method comprising: outputting a control message indicating the allocation of a plurality of resources for one or more uplink shared channel messages, the plurality of resources corresponding to a plurality of UTOs within a time period configured by a CG, wherein the plurality of resources include one or more FD resources; and, according to the CG configuration, obtaining a UCI message during at least one of the plurality of UTOs, the UCI message including an indication of the number of unused UTOs among the plurality of UTOs, wherein the indication excludes one or more invalid UTOs that conflict at least in part based on one or more downlink messages with the one or more uplink shared channel messages associated with one or more FD resources.

[0203] Aspect 13: The method according to aspect 12, the method further comprising: obtaining one or more acknowledgment or negative acknowledgment messages based on an identifier, the identifier being at least partially based on a first uplink shared channel timing corresponding to a first UTO among the plurality of UTOs, wherein the identifier is also at least partially based on the number of unused UTOs excluded from the indication.

[0204] Aspect 14: The method according to any one of Aspects 12 to 13, the method further comprising: obtaining one or more second uplink shared channel messages during one or more valid UTOs among the plurality of UTOs according to the CG configuration; and outputting the one or more downlink messages during the one or more invalid UTOs.

[0205] Aspect 15: The method according to aspect 14, wherein the UCI message is multiplexed with each of the one or more second uplink shared channel messages obtained during the one or more valid UTOs.

[0206] Aspect 16: The method according to any one of Aspects 12 to 15, the method further comprising: outputting a semi-static indication of the priority of each downlink message in the one or more downlink messages and each uplink shared channel message in the one or more uplink shared channel messages, wherein the one or more invalid UTOs are excluded at least in part based on the fact that the uplink shared channel message in the one or more uplink shared channel messages has a first priority and the downlink message in the one or more downlink messages has a second priority higher than the first priority.

[0207] Aspect 17: The method according to any one of Aspects 12 to 16, the method further comprising: outputting a dynamic indication of the priority of each downlink message in the one or more downlink messages and each uplink shared channel message in the one or more uplink shared channel messages, wherein the one or more invalid UTOs are excluded at least in part based on a duration of time that satisfies a threshold duration associated with the downlink message in the one or more downlink messages and the UCI message.

[0208] Aspect 18: The method according to any one of Aspects 12 to 17, wherein the one or more invalid UTOs are excluded at least in part based on the conflict between the uplink shared channel message in the one or more uplink shared channel messages and the one or more downlink control channel monitoring timing associated with the one or more FD resources.

[0209] Aspect 19: The method according to any one of Aspects 12 to 18, wherein the one or more invalid UTOs are excluded at least in part based on a conflict between the one or more uplink shared channel messages and one or more SSS associated with the one or more FD resources.

[0210] Aspect 20: The method according to any one of Aspects 12 to 19, wherein the one or more invalid UTOs are excluded at least in part based on a conflict between the one or more uplink shared channel messages and one or more TRS associated with the one or more FD resources.

[0211] Aspect 21: The method according to any one of Aspects 12 to 20, wherein the one or more invalid UTOs are excluded based at least in part on a first periodicity associated with the one or more uplink shared channel messages and a second periodicity associated with the one or more downlink messages.

[0212] Aspect 22: The method according to any one of Aspects 12 to 21, wherein the UCI message includes a bitmap, the bitmap including: one or more first bits indicating a first subset of the number of unused UTOs among the plurality of UTOs; and one or more second bits indicating a second subset of the number of used UTOs among the plurality of UTOs.

[0213] Aspect 23: A UE (or an apparatus for wireless communication) for performing wireless communication at a UE, the UE (or the apparatus) comprising: one or more memories storing processor-executable code (e.g., instructions); and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code (e.g., instructions) to cause the UE to perform a method according to any one of Aspects 1 to 11.

[0214] Aspect 24: A UE (or device) for wireless communication, the UE (or device) comprising at least one component for performing the method according to any one of aspects 1 to 11.

[0215] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 11.

[0216] Aspect 26: A network entity (or an apparatus for wireless communication at a network entity) for wireless communication, the network entity (or the apparatus) comprising: one or more memories storing processor-executable code (e.g., instructions); and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code (e.g., instructions) to cause the network entity to perform a method according to any one of Aspects 12 to 22.

[0217] Aspect 27: A network entity (or apparatus) for wireless communication, the network entity (or apparatus) comprising at least one component for performing the method according to any one of aspects 12 to 22.

[0218] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 12 to 22.

[0219] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0220] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0221] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0222] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0223] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0224] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0225] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0226] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0227] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0228] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0229] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0230] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more processors; and instructions stored in the one or more memories and executable by the one or more processors singly or collectively to cause the apparatus to: receive a control message indicating a plurality of resources allocated for one or more uplink shared channel messages, the plurality of resources corresponding to a plurality of uplink transmission occasions within a time period of a configured grant configuration, wherein the plurality of resources includes one or more full duplex resources; and transmit, in accordance with the configured grant configuration, an uplink control information message using at least one of the plurality of uplink transmission occasions, the uplink control information message including an indication of a number of unused uplink transmission occasions of the plurality of uplink transmission occasions, wherein the indication excludes one or more invalid uplink transmission occasions based at least in part on a collision between one or more downlink messages and the one or more uplink shared channel messages associated with the one or more full duplex resources.

2. The apparatus of claim 1, wherein, the instructions are further executable by the one or more processors singly or collectively to cause the apparatus to: transmit one or more acknowledgement or negative acknowledgement messages in accordance with an identifier, the identifier based at least in part on a first uplink shared channel occasion corresponding to a first uplink transmission occasion of the plurality of uplink transmission occasions, wherein the identifier is further based at least in part on the number of unused uplink transmission occasions excluded from the indication.

3. The apparatus of claim 1, wherein, the instructions are further executable by the one or more processors singly or collectively to cause the apparatus to: transmit one or more second uplink shared channel messages during one or more valid uplink transmission occasions of the plurality of uplink transmission occasions in accordance with the configured grant configuration; and receive the one or more downlink messages during the one or more invalid uplink transmission occasions.

4. The apparatus of claim 3, wherein, the uplink control information message is multiplexed with each of the one or more second uplink shared channel messages transmitted during the one or more valid uplink transmission occasions.

5. The apparatus of claim 1, wherein, the instructions are further executable by the one or more processors singly or collectively to cause the apparatus to: receive a semi-static indication of a priority of each of the one or more downlink messages and each of the one or more uplink shared channel messages, wherein the one or more invalid uplink transmission occasions are excluded based at least in part on an uplink shared channel message of the one or more uplink shared channel messages having a first priority and a downlink message of the one or more downlink messages having a second priority higher than the first priority.

6. The apparatus of claim 1, wherein, the instructions are further executable by the one or more processors singly or collectively to cause the apparatus to: Receive dynamic indications of priority for each downlink message in the one or more downlink messages and each uplink shared channel message in the one or more uplink shared channel messages, wherein the one or more invalid uplink transmission timings are excluded at least in part based on a duration that meets a threshold duration, the duration being between the end of receiving the dynamic indication and the start time for transmitting the uplink control information message.

7. The apparatus of claim 1, wherein, The one or more invalid uplink transmission timings are excluded at least in part based on conflicts between the uplink shared channel messages in the one or more uplink shared channel messages and the one or more downlink control channel monitoring timings associated with the one or more full-duplex resources.

8. The apparatus of claim 1, wherein, The one or more invalid uplink transmission timings are excluded at least in part based on conflicts between the uplink shared channel messages in the one or more uplink shared channel messages and one or more SSS associated with the one or more full-duplex resources.

9. The apparatus of claim 1, wherein, The one or more invalid uplink transmission timings are excluded at least in part based on conflicts between the uplink shared channel message in the one or more uplink shared channel messages and one or more tracking reference signals associated with the one or more full-duplex resources.

10. The apparatus of claim 1, wherein, The one or more invalid uplink transmission timings are excluded based at least in part on a first periodicity associated with the one or more uplink shared channel messages and a second periodicity associated with the one or more downlink messages.

11. The apparatus of claim 1, wherein, The uplink control information message includes a bitmap, the bitmap including: one or more first bits, the one or more first bits indicating a first subset of the number of unused uplink transmission opportunities among the plurality of uplink transmission opportunities; and one or more second bits, the one or more second bits indicating a second subset of the number of used uplink transmission opportunities among the plurality of uplink transmission opportunities.

12. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more processors; and Instructions, which are stored in one or more memories and can be executed individually or jointly by the one or more processors, to cause the device to: The output indicates a control message that allocates multiple resources for one or more uplink shared channel messages, the multiple resources corresponding to multiple uplink transmission opportunities within a time period for which the configuration is granted, wherein the multiple resources include one or more full-duplex resources; as well as According to the configuration granted, an uplink control information message is obtained during at least one of the plurality of uplink transmission opportunities, the uplink control information message including an indication of the number of unused uplink transmission opportunities among the plurality of uplink transmission opportunities, wherein the indication excludes one or more invalid uplink transmission opportunities based at least in part on conflicts between one or more downlink messages and one or more uplink shared channel messages associated with the one or more full-duplex resources.

13. The apparatus of claim 12, wherein, The instructions can also be executed individually or jointly by the one or more processors to enable the device to: One or more acknowledgment or negative acknowledgment messages are obtained based on an identifier, the identifier being at least partially based on a first uplink shared channel timing corresponding to a first uplink transmission timing among the plurality of uplink transmission timings, wherein the identifier is also at least partially based on the number of unused uplink transmission timings excluded from the indication.

14. The apparatus of claim 12, wherein, The instructions can also be executed individually or jointly by the one or more processors to enable the device to: According to the configuration granted, one or more second uplink shared channel messages are obtained during one or more valid uplink transmission opportunities among the plurality of uplink transmission opportunities; as well as The one or more downlink messages are output during the one or more invalid uplink transmission periods.

15. The apparatus of claim 14, wherein, The uplink control information message is multiplexed with each of the one or more second uplink shared channel messages obtained during the one or more valid uplink transmission opportunities.

16. The apparatus of claim 12, wherein, The instructions can also be executed individually or jointly by the one or more processors to enable the device to: Output a semi-static indication of the priority of each downlink message in the one or more downlink messages and each uplink shared channel message in the one or more uplink shared channel messages, wherein the one or more invalid uplink transmission timings are excluded at least in part based on the fact that the uplink shared channel message in the one or more uplink shared channel messages has a first priority and the downlink message in the one or more downlink messages has a second priority higher than the first priority.

17. The apparatus of claim 12, wherein, The instructions can also be executed individually or jointly by the one or more processors to enable the device to: Output a dynamic indication of the priority of each downlink message in the one or more downlink messages and each uplink shared channel message in the one or more uplink shared channel messages, wherein the one or more invalid uplink transmission timings are excluded at least in part based on a duration that satisfies a threshold duration associated with the dynamic indication and the uplink control information message.

18. The apparatus of claim 12, wherein, The one or more invalid uplink transmission timings are excluded at least in part based on conflicts between the uplink shared channel messages in the one or more uplink shared channel messages and the one or more downlink control channel monitoring timings associated with the one or more full-duplex resources.

19. The apparatus of claim 12, wherein, The one or more invalid uplink transmission timings are excluded at least in part based on conflicts between the uplink shared channel messages in the one or more uplink shared channel messages and one or more SSS associated with the one or more full-duplex resources.

20. The apparatus of claim 12, wherein, The one or more invalid uplink transmission timings are excluded at least in part based on conflicts between the uplink shared channel message in the one or more uplink shared channel messages and one or more tracking reference signals associated with the one or more full-duplex resources.

21. The apparatus of claim 12, wherein, The one or more invalid uplink transmission timings are excluded based at least in part on a first periodicity associated with the one or more uplink shared channel messages and a second periodicity associated with the one or more downlink messages.

22. The apparatus of claim 12, wherein, The uplink control information message includes a bitmap, the bitmap including: one or more first bits, the one or more first bits indicating a first subset of the number of unused uplink transmission opportunities among the plurality of uplink transmission opportunities; and one or more second bits, the one or more second bits indicating a second subset of the number of used uplink transmission opportunities among the plurality of uplink transmission opportunities.

23. A method for wireless communication by a user equipment (UE), the method comprising: Receive a control message indicating the allocation of multiple resources for one or more uplink shared channel messages, the multiple resources corresponding to multiple uplink transmission opportunities within a configured time period, wherein the multiple resources include one or more full-duplex resources; and According to the configuration granted, at least one of the plurality of uplink transmission opportunities is used to transmit an uplink control information message, the uplink control information message including an indication of the number of unused uplink transmission opportunities among the plurality of uplink transmission opportunities, wherein the indication excludes one or more invalid uplink transmission opportunities that are at least partially based on conflicts between one or more downlink messages and one or more uplink shared channel messages associated with the one or more full-duplex resources.

24. The method according to claim 23, further comprising: One or more acknowledgment or negative acknowledgment messages are sent based on an identifier, the identifier being at least partially based on a first uplink shared channel timing corresponding to a first uplink transmission timing among the plurality of uplink transmission timings, wherein the identifier is also at least partially based on the number of unused uplink transmission timings excluded from the indication.

25. The method according to claim 23, further comprising: According to the configuration granted, one or more second uplink shared channel messages are transmitted during one or more valid uplink transmission opportunities among the plurality of uplink transmission opportunities; as well as Receive the one or more downlink messages during the one or more invalid uplink transmission periods.

26. The method of claim 25, wherein, The uplink control information message is multiplexed with each of the one or more second uplink shared channel messages transmitted during the one or more valid uplink transmission periods.

27. A method for wireless communication by a network entity, the method comprising: Output control messages indicating the allocation of multiple resources for one or more uplink shared channel messages, the multiple resources corresponding to multiple uplink transmission opportunities within a configured time period, wherein the multiple resources include one or more full-duplex resources; and According to the configuration granted, an uplink control information message is obtained during at least one of the plurality of uplink transmission opportunities, the uplink control information message including an indication of the number of unused uplink transmission opportunities among the plurality of uplink transmission opportunities, wherein the indication excludes one or more invalid uplink transmission opportunities based at least in part on conflicts between one or more downlink messages and one or more uplink shared channel messages associated with the one or more full-duplex resources.

28. The method of claim 27, further comprising: One or more acknowledgment or negative acknowledgment messages are obtained based on an identifier, the identifier being at least partially based on a first uplink shared channel timing corresponding to a first uplink transmission timing among the plurality of uplink transmission timings, wherein the identifier is also at least partially based on the number of unused uplink transmission timings excluded from the indication.

29. The method of claim 27, further comprising: According to the configuration granted, one or more second uplink shared channel messages are obtained during one or more valid uplink transmission opportunities among the plurality of uplink transmission opportunities; as well as The one or more downlink messages are output during the one or more invalid uplink transmission periods.

30. The method of claim 29, wherein, The uplink control information message is multiplexed with each of the one or more second uplink shared channel messages obtained during the one or more valid uplink transmission opportunities.

Images