Techniques for multiplexing uplink control information - Patents.com

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may monitor one or more semi-persistent scheduling (SPS) transmissions according to one or more SPS configurations. The UE may generate a set of feedback bits associated with the SPS transmission, where the feedback bits are scheduled for transmission to a network entity in a first set of uplink symbols. The UE may receive control signaling that changes availability of the first set of uplink symbols for transmission of the set of feedback bits, and then delay the set of feedback bits to a second set of uplink symbols. The UE may determine whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols, transmit at least a portion of the set of feedback bits in the second set of uplink symbols, and communicate according to the determination.

Description

[Technical field]

[0001] This patent application claims the benefit of Greek Patent Application No. 20210100231, entitled “TECHNIQUES FOR MULTIPLEXING UPLINK CONTROL INFORMATION” by DIMOU et al., filed on April 6, 2021, and assigned to the assignee of this application, PUCCH225-c.

[0002] The following relates to wireless communications, including techniques for multiplexing uplink control information. [Background technology]

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and the like. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes 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 Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple-access communication system may include one or more base stations (or other network entities) or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may in some cases be known as user equipment (UE).

[0004] In some wireless communication systems, a UE may be configured to transmit feedback based on monitoring transmissions from one or more semi-persistent scheduling (SPS) configurations. However, in some situations, conflicting transmissions make it difficult to transmit the feedback. Summary of the Invention [Means for solving the problem]

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for multiplexing uplink control information. Generally, the described techniques enable a user equipment (UE) to multiplex existing delayed and non-delayed uplink control information (UCI) bits in the same slot. The UE may monitor semi-persistent scheduling (SPS) transmissions from a network entity. Based on the monitoring, the UE may generate SPS feedback bits (e.g., positive acknowledgement (ACK) or negative ACK (NACK) bits) scheduled for transmission to the network entity in a first set of uplink symbols (e.g., a first slot format). In some cases, a collision may occur during transmission when a physical uplink control channel (PUCCH) carrying the SPS feedback bits partially overlaps with a downlink symbol. Due to the collision, the UE may delay transmission of the feedback bits to a second set of uplink symbols (e.g., a second slot format) to avoid the collision.

[0006] In some cases, the second set of uplink symbols may already carry existing non-delayed UCI bits, and the UE may multiplex the delayed SPS feedback bits and the non-delayed UCI bits in the target slot for transmission. For example, the candidate target slot may not accommodate the non-delayed UCI bits and the delayed feedback bits if it already has existing non-delayed UCI bits (e.g., the combined size of the feedback bits and UCI bits may be larger than the allocation size of the second set of uplink symbols). In some cases, the UE may cancel (e.g., drop) the transmission of some or all of the UCI bits, or check the next slot to transmit all the collided UCI bits and feedback bits, or a combination thereof. In some examples, the UE may decide to transmit at least a portion of the feedback in the second set of uplink symbols.

[0007] A method for wireless communication in a UE is described that may include monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations, generating a set of feedback bits associated with the one or more semi-persistent scheduled transmissions, where the set of feedback bits are scheduled for transmission to a network entity in a first set of uplink symbols, receiving control signaling modifying availability of the first set of uplink symbols for transmitting the set of feedback bits, delaying transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling, determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols, transmitting at least a portion of the set of feedback bits in the second set of uplink symbols in accordance with the determination, and communicating with the network entity in accordance with the determination.

[0008] An apparatus for wireless communication in a UE is described. The apparatus includes at least one processor and a memory (e.g., operatively, communicatively, functionally, electronically, or electrically) coupled to the at least one processor, the memory storing instructions executable by the at least one processor, the instructions may cause the apparatus or UE to: monitor one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations; generate a set of feedback bits associated with the one or more semi-persistent scheduled transmissions, where the set of feedback bits are scheduled for transmission to a network entity in a first set of uplink symbols; receive control signaling modifying availability of the first set of uplink symbols for transmitting the set of feedback bits; delay transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling; determine whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols; transmit at least a portion of the set of feedback bits in the second set of uplink symbols in accordance with the determination; and communicate with the network entity in accordance with the determination.

[0009] Another apparatus for wireless communication in a UE is described. The apparatus may include means for monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations, means for generating a set of feedback bits associated with the one or more semi-persistent scheduled transmissions, where the set of feedback bits are scheduled for transmission to a network entity in a first set of uplink symbols, means for receiving control signaling modifying availability of the first set of uplink symbols for transmitting the set of feedback bits, means for delaying transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling, means for determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols, means for transmitting at least a portion of the set of feedback bits in the second set of uplink symbols in accordance with the determination, and means for communicating with the network entity in accordance with the determination.

[0010] A non-transitory computer-readable medium storing code for wireless communication in a UE is described, the code including instructions that may be executable by at least one processor to: monitor one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations; generate a set of feedback bits associated with the one or more semi-persistent scheduled transmissions, where the set of feedback bits are scheduled for transmission to a network entity in a first set of uplink symbols; receive control signaling modifying availability of the first set of uplink symbols for transmitting the set of feedback bits, delay transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling, determine whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols, transmit at least a portion of the set of feedback bits in the second set of uplink symbols in accordance with the determination, and communicate with the network entity in accordance with the determination.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that a size of the set of feedback bits may be greater than a size of an allocation in the second set of uplink symbols for transmission of the set of feedback bits, where determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols may be based on determining that a size of the set of feedback bits may be greater than a size of the allocation in the second set of uplink symbols.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for delaying transmission of the set of feedback bits to the third set of uplink symbols based on the size of the allocation.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting at least a portion of the set of feedback bits in a second set of uplink symbols based on the size of the allocation.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for generating a set of uplink control information bits scheduled for transmission to the network entity in a second set of uplink symbols, where determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols may be based on generating the set of uplink control information bits.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in a second set of uplink symbols based on generating the set of uplink control information bits.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that a size of the set of feedback bits and the set of uplink control information bits may be greater than a size of an allocation in the second set of uplink symbols for transmission of the set of feedback bits and the set of uplink control information bits, and refraining from transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based on determining that a size of the set of feedback bits and the set of uplink control information bits may be greater than the size of the allocation, where communicating with a network entity includes the operations, features, means, or instructions.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for delaying transmission of the set of feedback bits and the set of uplink control information bits to a third set of uplink symbols based on the size of the allocation.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols may be based on a type of the set of uplink control information bits.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting a set of uplink control information bits in the second set of uplink symbols and delaying transmission of the set of feedback bits to the third set of uplink symbols based on generating the set of uplink control information bits.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting at least a portion of the set of feedback bits in a second set of uplink symbols according to the determination, and delaying transmission of the set of uplink control information bits to a third set of uplink symbols based on transmitting at least a portion of the set of feedback bits in the second set of uplink symbols.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for generating compressed feedback bits based on generating the set of feedback bits, where the compressed feedback bits are associated with at least a portion of the set of feedback bits, and transmitting the compressed feedback bits in a second set of uplink symbols based on generating the set of uplink control information bits.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that the second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols, and refraining from transmitting at least a portion of the set of feedback bits in the second set of uplink symbols based on the number of slots, where communicating with a network entity includes the refraining.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each slot of a certain number of slots includes an uplink symbol, a flexible symbol, or both, and the flexible symbol may be configured for transmitting an uplink transmission or a downlink transmission.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining an order of a set of feedback bits in a feedback codebook for transmission in a second set of uplink symbols, where determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on an order of the set of feedback bits in the feedback codebook.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining to transmit at least a portion of the set of feedback bits in a second set of uplink symbols based on an order of the set of feedback bits in a feedback codebook, where the feedback codebook is a first type feedback codebook or a second type feedback codebook that includes a concatenation of a set of feedback codebooks associated with the first set of uplink symbols.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the concatenation of the sets of feedback codebooks is based on a temporal ordering of the sets of feedback codebooks.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for generating a feedback codebook based on a set of indices associated with the serving cell, one or more semi-persistent scheduling configurations, a first set of uplink symbols, and a second set of uplink symbols, and determining to transmit at least a portion of the set of feedback bits in the second set of uplink symbols in accordance with the generated feedback codebook.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for generating a set of uplink control information bits and a feedback codebook scheduled for transmission to the network entity in a second set of uplink symbols, where determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on generating the set of uplink control information bits and the feedback codebook, where the feedback codebook is a first type feedback codebook or a second type feedback codebook that includes a concatenation of a set of feedback codebooks associated with the first set of uplink symbols; and transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based on generating the set of uplink control information bits and in accordance with the feedback codebook.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for delaying transmission of the set of feedback bits to a third set of uplink symbols, where an allocation in the third set of uplink symbols for transmitting the set of feedback bits overlaps with one or more scheduled downlink transmissions and an offset between the allocation and the one or more scheduled downlink transmissions meets a threshold.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for refraining from transmitting at least a portion of the set of feedback bits in a third set of uplink symbols based on one or more scheduled downlink transmissions, where communicating with a network entity includes said refraining.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for delaying transmission of the set of feedback bits to a third set of uplink symbols, where an allocation in the third set of uplink symbols includes the second set of feedback bits for the DG, and refraining from transmitting at least a portion of the set of feedback bits in the third set of uplink symbols based on the delay.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for delaying transmission of a set of feedback bits to a third set of uplink symbols, where the set of feedback bits is associated with an uplink DG and the allocation in the third set of uplink symbols includes the second set of feedback bits associated with a downlink DG.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that an allocation of the third set of uplink symbols does not overlap with symbols corresponding to the control resource set, and delaying transmission of the set of feedback bits to the third set of uplink symbols based on the determining.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that a size of the set of feedback bits may be greater than a size of an allocation in the second set of uplink symbols for transmission of the set of feedback bits, wherein determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on determining that a size of the set of feedback bits is greater than a size of an allocation in the second set of uplink symbols.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that the second set of uplink symbols occurs after a certain number of symbols from the first set of uplink symbols, and refraining from transmitting at least a portion of the set of feedback bits in the second set of uplink symbols based on the number of symbols, where communicating with a network entity includes the refraining.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining a respective priority associated with each feedback bit of the set of feedback bits, and transmitting at least a portion of the set of feedback bits in a second set of uplink symbols in accordance with determining the respective priority.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling indicates that the first set of uplink symbols partially overlaps with the set of downlink symbols, the set of synchronization signal block symbols, or both. [Brief description of the drawings]

[0038] [Figure 1] FIG. 1 illustrates an example of a wireless communication system that supports techniques for multiplexing uplink control information, according to aspects of the present disclosure. [Diagram 2] FIG. 1 illustrates an example of a wireless communication system that supports techniques for multiplexing uplink control information, according to aspects of the present disclosure. [Diagram 3] FIG. 1 illustrates an example of a transmission scheme supporting techniques for multiplexing uplink control information, according to aspects of the present disclosure. [Figure 4]FIG. 1 illustrates an example of a process flow supporting a technique for multiplexing uplink control information, according to an aspect of the disclosure. [Diagram 5] 1 is a block diagram of a device that supports techniques for multiplexing uplink control information according to an aspect of the disclosure. [Figure 6] 1 is a block diagram of a device that supports techniques for multiplexing uplink control information according to an aspect of the disclosure. [Figure 7] FIG. 1 is a block diagram of a communications manager supporting techniques for multiplexing uplink control information according to an aspect of the disclosure. [Figure 8] FIG. 1 is a diagram of a system including devices that support techniques for multiplexing uplink control information according to an aspect of the disclosure. [Figure 9] 1 is a flowchart illustrating a method for supporting a technique for multiplexing uplink control information according to an aspect of the disclosure. [Figure 10] 1 is a flowchart illustrating a method for supporting a technique for multiplexing uplink control information according to an aspect of the disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0039] In some wireless communication systems, a user equipment (UE) may be configured to monitor semi-persistent scheduling (SPS) transmissions from a network entity. The UE may transmit feedback bits (e.g., hybrid automatic repeat request (HARQ) acknowledgment (ACK) or negative ACK (NACK) associated with the SPS transmission using a physical uplink control channel (PUCCH) according to an SPS configuration). Although the techniques herein are described in the context of SPS HARQ ACK / NACK bits, it should be understood that the techniques may be applied to transmissions of other feedback bits, such as channel control information (CSI) and other uplink control information (USI).

[0040] In some cases, the feedback bits may conflict (e.g., collide) with downlink symbols from a network entity. For example, the network entity may transmit control signaling indicating that resources for transmitting the feedback bits are configured for downlink transmission and therefore are no longer available for uplink symbol transmission (e.g., feedback). In some cases, the UE may delay the PUCCH to the next slot that may accommodate PUCCH resources. In some cases, the UE may check the candidate target slot for carrying the delayed PUCCH for multiple colliding SPS PUCCH transmissions. The target slot may not accommodate PUCCH resources carrying SPS feedback bits from all colliding SPS PUCCH transmissions. In some other cases, the candidate target slot may already be carrying existing non-delayed UCI bits for transmission, and the candidate target slot may not have capacity to carry PUCCH for the sum of the existing UCI bits and the SPS feedback bits from the colliding SPS PUCCH transmissions. It may be advantageous for the UE to determine whether to skip the candidate target slot and check the availability of the next slot, or to transmit some of the existing UCI bits or the collided SPS feedback bits in the candidate target slot.

[0041] Techniques are described herein that support multiplexing mixed existing delayed and non-delayed UCI bits in the same slot. The UE may monitor SPS transmissions from a network entity. The UE may generate SPS feedback bits (e.g., ACK / NACK bits) scheduled for transmission to the network entity in a first set of uplink symbols based on the monitoring. In some cases, a collision may occur during transmission when a PUCCH carrying the SPS feedback bits at least partially overlaps with a downlink symbol (e.g., an RRC configured downlink symbol). Due to the collision, the UE may delay transmission of the feedback bits to a second set of uplink symbols (e.g., a second slot format) to avoid the collision.

[0042] In some cases, the second set of uplink symbols may already carry existing non-delayed UCI bits, and the UE may multiplex the delayed SPS feedback bits and the non-delayed UCI bits in the target slot for transmission. For example, the candidate target slot may not accommodate the non-delayed UCI bits and the delayed feedback bits if it already has existing non-delayed UCI bits (e.g., the combined size of the feedback bits and UCI bits may be larger than the allocation size of the second set of uplink symbols). In some cases, the UE may cancel (e.g., drop) the transmission of some or all of the UCI bits, or check the next slot to transmit all the collided UCI bits and feedback bits, or a combination thereof. In some examples, the UE may decide to transmit at least a portion of the feedback in the second set of uplink symbols.

[0043] Certain aspects of the subject matter described herein may be implemented to realize one or more advantages. The described techniques may support improvements in multiplexing UCI by reducing signaling overhead and power usage. The UE may reduce the number of collisions by delaying colliding SPS feedback based on different channel conditions, and may more efficiently utilize available resources and improve user experience by prioritizing based on transmissions based on uplink symbol availability. Thus, the supported techniques may include improved network operation and, in some examples, may increase network efficiency, among other benefits.

[0044] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to transmission schemes, process flows, apparatus diagrams, system diagrams and flowcharts relating to techniques for multiplexing uplink control information.

[0045] 1 illustrates an example of a wireless communication system 100 supporting techniques for multiplexing uplink control information according to aspects of the disclosure. 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 LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0046] The network entities 105 may be distributed throughout a geographic area to form the wireless communication system 100 and may be devices of different forms or with different capabilities. The network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each network entity 105 may provide a coverage area 110 over which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entities 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.

[0047] The UEs 115 may be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be fixed or mobile or both at different times. The UEs 115 may be devices of different forms or with different capabilities. Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 network entities 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown in FIG. 1. As described herein, the nodes of the wireless communication system 100 may be referred to as network nodes or wireless nodes, and may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, each node may be a UE 115. As another example, the node may be a network entity 105. As another example, the first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In yet other aspects of this example, the first, second, and third nodes may differ relative to these examples. Similarly, references to a UE 115, a network entity 105, an apparatus, a device, a computing system, etc. may include disclosure of the UE 115, the network entity 105, the apparatus, the device, the computing system, etc. being a node.For example, a disclosure that the UE 115 is configured to receive information from the network entity 105 also discloses that the first node is configured to receive information from the second node.

[0048] In some examples, the network entities 105 may communicate with the core network 130, with each other, or both. For example, the network entities 105 may communicate with the core network 130 over one or more backhaul communication links 120 (e.g., according to an S1, N2, N3, or other interface protocol). In some examples, the network entities 105 may communicate with each other over the backhaul communication links 120 (e.g., according to an X2, Xn, or other interface protocol), either directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other over midhaul communication links (e.g., according to a midhaul interface protocol) or over fronthaul communication links (e.g., according to a fronthaul interface protocol), or any combination thereof. The backhaul communications link 120, the midhaul communications link, or the fronthaul communications link may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), among other examples or various combinations.

[0049] The one or more network entities 105 described herein may include or may be referred to as a network entity (e.g., a base transceiver station, a radio network entity, an access point, a radio transceiver, a Node B, an eNode B (eNB), a Next Generation Node B or Giga-Node B (either of which may be referred to as a gNB), a Next Generation eNB (ng-eNB), a Home Node B, a Home eNode B, or other suitable terminology). The network entity 105 may be implemented in an aggregated or monolithic network entity architecture, or alternatively, in a disaggregated network entity architecture. For example, the network entity 105 may include one or more of a central unit (CU), a distributed unit, a radio unit (RU), a radio access network (RAN) intelligent controller (RIC) (e.g., a near real-time RIC (near RT RIC)), a non-real-time RIC (non-RT RIC), a service management orchestration (SMO) system, or any combination thereof. An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit / receive point (TRP). One or more components of the network entity 105 of a disaggregated RAN may be co-located, or one or more components of the network entity 105 may be located in distributed locations.

[0050] The division of functionality among the CU, DU, and RU may be flexible and support different functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) depending on which functions are performed in the CU, DU, or RU. For example, a functional division of a protocol stack may be used between the CU and DU, whereby the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some examples, the CU may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Aggregation Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, which may host lower protocol layers such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, field access control (MAC) layer) functions and signaling, each of which may be at least partially controlled by the CU. Additionally or alternatively, a functional division of the protocol stack may be used between the DU and the RU, whereby the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some cases, the functional division between the CU and the DU or between the DU and the RU may be within a protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU). The CU may be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions.A CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and a DU may be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some examples, a midhaul or fronthaul communication link may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by the respective network entities 105 communicating over such communication links.

[0051] A wireless communication system (e.g., wireless communication system 100), infrastructure, and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connectivity and provide an integrated access backhaul (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 nodes) may be partially controlled by each other. One or more IAB nodes may be referred to as donor entities or IAB donors. One or more DUs (e.g., one or more RUs) may be partially controlled by a CU associated with a donor network entity 105 (e.g., donor network entity). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes) via supported access and backhaul links (e.g., backhaul communication link 120). An IAB node may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU of the associated IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115 or may share the same antennas of the IAB node that are used for access via the DU of the IAB node. In some examples, the IAB node may include a DU that supports additional communication links with additional entities (e.g., the IAB node, the UE 115) in the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes or components of the IAB node) may be configured to operate in accordance with the techniques described herein.

[0052] The UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, and a "device" may be referred to as a unit, a station, a terminal, or a client, among others. The UE 115 may be a cellular phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, an MP3 player, or a video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) device based on GPS (Global Positioning System), Beidou, GLONASS, or Galileo, or a ground-based device), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, a smart clothing, a smart grocery, a smart home ... The UE 115 may also include or be referred to as a personal electronic device such as a smart device, a smart camera, a smart phone, a smart device ...

[0053] The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may act as relays, as shown in FIG. 1, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay network entities, among others.

[0054] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion (e.g., a bandwidth portion (BWP)) of a radio frequency spectrum band that operates 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 collection signaling (e.g., synchronization signals, system information), control signaling that coordinates operation on the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0055] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have collection or control signaling to coordinate operation with respect to other carriers. A carrier may be associated with a frequency channel (e.g., evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be arranged according to a channel raster for discovery by the UE 115. A carrier may operate in a standalone mode, where initial collection and connection may be made by the UE 115 over the carrier, or the carrier may operate in a non-standalone mode, where connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0056] The communication links 125 shown in the wireless communication system 100 may include uplink transmissions from the UE 115 to the network entity 105 or downlink transmissions from the network entity 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode).

[0057] A carrier may be associated with a particular bandwidth of the radio frequency 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 of several determined bandwidths for a carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 Megahertz (MHz)). The devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth or may be configurable to support communication over one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports simultaneous communication over a carrier associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate over a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

[0058] A signal waveform transmitted on a carrier may be composed of multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing are 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 coding rate of the modulation scheme, or both). Thus, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE 115. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with the UE 115.

[0059] One or more numerologies for a carrier may be supported, where the numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communication for the UE 115 may be limited to one or more active BWPs.

[0060] The time interval for the network entity 105 or the UE 115 may be, for example, T s =1 / (Δf max N f ) seconds, or expressed in multiples of a base time unit, where Δf max may represent the maximum supported subcarrier spacing, and Nf may represent the maximum supported discrete Fourier transform (DFT) size. The communication resource time intervals may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0061] Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into several slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on the subcarrier spacing. Each slot may include several symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may be further divided into multiple minislots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the frequency band of operation.

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

[0063] The physical channels may be multiplexed on the carriers according to various techniques. The physical control channels and the physical data channels may be multiplexed on the downlink carriers using, for example, one or more of a time division multiplexing (TDM), a frequency division multiplexing (FDM), or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (core set)) for the physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESET) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates at one or more aggregation levels located in a cascaded manner. The aggregation level for the control channel candidates may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a particular UE 115 .

[0064] Each network entity 105 may provide communication coverage via one or more cells, e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with the network entity 105 (e.g., on a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) to distinguish neighboring cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion (e.g., a sector) of a geographic coverage area 110 in which the logical communication entity operates. Such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include, among others, a building, a subset of a building, or an outside space between or overlapping with the geographic coverage area 110.

[0065] A macro cell generally covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 115 subscribing to the service of a network provider supporting the macro cell. A small cell may be associated with a lower power network entity 105 compared to a macro cell, and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 subscribing to the service of a network provider, or may provide restricted access to UEs 115 that have an association with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with a user in a home or office). A network entity 105 may support one or more cells and may support communication on one or more cells using one or more component carriers.

[0066] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, Narrowband IoT (NB-IoT), enhanced Mobile Broadband (eMBB)) that may provide access to different types of devices.

[0067] In some examples, the network entities 105 may be mobile and therefore may provide communication coverage to moving geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same network entity 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include heterogeneous networks, for example, where different types of network entities 105 provide coverage to various geographic coverage areas 110 using the same or different radio access technologies.

[0068] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 may have similar frame timing and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing and transmissions from different network entities 105 may not be aligned in time, in some examples. The techniques described herein may be used for either synchronous or asynchronous operation.

[0069] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or with network entities 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that incorporate sensors or meters to measure or capture information and relay that information to a central server or application program that utilizes such information or presents the information to a human interacting with the application program. Some UEs 115 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 geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing. In an aspect, the techniques disclosed herein may be applicable to MTC UEs or IoT UEs. MTC UE or IoT UE may include MTC / Enhanced MTC (eMTC also called CAT-M, Cat M1) UE, NB-IoT (also called CAT NB1) UE, and other types of UE. eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), and mMTC (massive MTC), and NB-IoT may include eNB-IoT (enhanced NB-IoT), and FeNB-IoT (further enhanced NB-IoT).

[0070] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and the like. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless network, e.g., a wireless local area network (WLAN), such as a Wi-Fi (i.e., Institute of Electrical and Electronics Engineers (IEEE) 802.11) network, may include an access point (AP) that may communicate with one or more wireless or mobile devices. The AP may be coupled to a network, such as the Internet, and may enable mobile devices to communicate over the network (or communicate with other devices coupled to the access point). A wireless device may communicate bidirectionally with a network device. For example, in a WLAN, a device may communicate with an associated AP via a downlink (e.g., a communication link from the AP to the device) and an uplink (e.g., a communication link from the device to the AP). A wireless personal area network (PAN), which may include a Bluetooth connection, may provide short-range wireless connectivity between two or more paired wireless devices. For example, a wireless device such as a cellular phone may utilize wireless PAN communications to exchange information such as audio signals with a wireless headset. Components within a wireless communication system may be coupled (e.g., operatively, communicatively, functionally, electronically, and / or electrically) with one another.

[0071] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception, but not simultaneous transmission and reception). In some examples, the half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power saving deep sleep mode when not engaged in active communication, operating over a limited bandwidth (e.g., in accordance with narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured for operation 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 guard band of the carrier, or outside of the carrier.

[0072] The wireless communication system 100 may be configured to support ultra-reliable or low latency communications, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency communications (URLLC) or mission-critical communications. The UE 115 may be designed to support ultra-reliable, low latency, or critical functions (e.g., mission-critical functionality). Ultra-reliable communications may include private or group communications and may be supported by one or more mission-critical services, such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functionality may include service prioritization, and the mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, mission-critical, and ultra-reliable low latency may be used interchangeably herein.

[0073] In some examples, the UE 115 may also be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) protocol or a D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of the network entity 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the network entity 105 or may not otherwise be able to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to every other UE 115 in the group. In some examples, the network entity 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without the involvement of the network entity 105.

[0074] In some systems, the D2D communication link 135 may be an example of a communication channel between vehicles (e.g., UE 115), such as a sidelink communication channel. In some examples, the vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. The vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicles in the V2X system may communicate with roadside infrastructure, such as roadside units, and / or with a network via one or more network nodes (e.g., network entity 105) using vehicle-to-network (V2N) communication.

[0075] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an Evolved Packet Core (EPC) or 5G Core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), or a User Plane Function (UPF)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 associated with the core network 130. User IP packets may be forwarded through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entities may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0076] Some of the network devices, such as the network entity 105, may include subcomponents, such as the access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with the UE 115 through one or more other access network transmitting entities 145, which may be referred to as a radio head, a smart radio head, or a transmit / receive point (TRP). Each access network transmitting entity 145 may include one or more antenna panels. In some configurations, various functions of each access network entity 140 or network entity 105 may be distributed across various network devices (e.g., radio heads and ANCs) or integrated into a single network device (e.g., the network entity 105).

[0077] The wireless communication system 100 may operate using one or more frequency bands, for example, in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, the waves may penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using lower frequencies and longer waves in the short wave (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0078] The wireless communication system 100 may also operate in the super high frequency (SHF) region, also known as the centimeter band, using a frequency band from 3 GHz to 30 GHz, or in the extremely high frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105, and the EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate the use of antenna arrays within the devices. However, propagation of EHF transmissions may experience more atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of bands across these frequency regions may vary by country or regulatory body.

[0079] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may utilize Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, the network entity 105 and devices such as the UE 115 may employ carrier sensing for contention detection and avoidance. In some examples, operation in the unlicensed spectrum may be based on a carrier aggregation configuration in conjunction with a component carrier operating in the licensed spectrum (e.g., LAA). Operation in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0080] The network entity 105 or UE 115 may be equipped with multiple antennas that may be used to utilize techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, one or more network entity antennas or antenna arrays may be located together in an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located in various geographic locations. The network entity 105 may have an antenna array with several rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support radio frequency beamforming for signals transmitted through the antenna ports.

[0081] The network entity 105 or UE 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may be transmitted by a transmitting device, for example, 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 bits related to the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). The different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0082] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array are subject to constructive interference, while other signals are subject to destructive interference. Adjustment of signals communicated through antenna elements may include a transmitting or receiving device applying an amplitude offset, a phase offset, or both, to signals carried through an antenna element associated with the device. The adjustment associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or to some other orientation).

[0083] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform a beamforming operation for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by the network entity 105 multiple times in different directions. For example, the network entity 105 may transmit signals according to different beamforming weight sets associated with different directions of transmission. The transmissions in different beam directions may be used (e.g., by a transmitting device such as the network entity 105 or by a receiving device such as the UE 115) to identify beam directions for later transmissions or receptions by the network entity 105.

[0084] Some signals, such as data signals associated with a particular receiving device, may be transmitted by the network entity 105 in a single beam direction (e.g., a direction associated with a receiving device, such as the UE 115). In some examples, a beam direction associated with a transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, the UE 115 may receive one or more of the signals transmitted in different directions by the network entity 105 and may report to the network entity 105 an indication of the signal that the UE 115 received with the highest signal quality or possibly an acceptable signal quality.

[0085] In some examples, transmission by a device (e.g., by the network entity 105 or the UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from the network entity 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. The network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). These techniques are described with reference to signals transmitted by the network entity 105 in one or more directions, although the UE 115 may employ similar techniques for transmitting a signal multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal in a single direction (e.g., to transmit data to a receiving device).

[0086] A receiving device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals, such as synchronization signals, reference signals, beam selection signals, or other control signals, from the network entity 105. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array, or by processing the received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as "listening" with different receive configurations or receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned to a beam direction determined based on listening with different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or possibly acceptable signal quality based on listening with multiple beam directions).

[0087] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate on logical channels. The Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may establish, configure, and maintain an RRC connection between the UE 115 and the network entity 105 or core network 130, which supports radio bearers for user plane data. In the physical layer, the transport channels may be mapped to physical channels.

[0088] The UE 115 and the network entity 105 may support retransmission of data to increase the likelihood of successful reception of the data. HARQ feedback is one technique for increasing the likelihood that data is accurately received over the communication link 125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which the device may provide HARQ feedback in a particular slot for data received in a previous symbol in that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0089] In some examples, the UE 115 may multiplex the mixed existing delayed and non-delayed UCI bits in the same slot. The UE 115 may monitor SPS transmissions from the network entity 105. The UE 115 may generate SPS feedback bits (e.g., ACK / NACK bits) scheduled for transmission to the network entity 105 in a first set of uplink symbols based on the monitoring. In some cases, a collision may occur during transmission when the PUCCH carrying the SPS feedback bits at least partially overlaps with a downlink symbol (e.g., an RRC configured downlink symbol). Due to the collision, the UE 115 may delay transmission of the feedback bits to a second set of uplink symbols (e.g., a second slot format) to avoid the collision.

[0090] In some cases, the second set of uplink symbols may already carry existing non-delayed UCI bits, and the UE 115 may multiplex the delayed SPS feedback bits and the non-delayed UCI bits in the target slot for transmission. For example, the candidate target slot may not accommodate the non-delayed UCI bits and the delayed feedback bits if it already has existing non-delayed UCI bits (e.g., the combined size of the feedback bits and UCI bits may be larger than the allocation size of the second set of uplink symbols). In some cases, the UE 115 may cancel (e.g., drop) the transmission of some or all of the UCI bits, or check the next slot to transmit all the collided UCI bits and feedback bits, or a combination thereof. In some examples, the UE 115 may determine to transmit at least a portion of the feedback in the second set of uplink symbols.

[0091] 2 illustrates an example of a wireless communication system 200 supporting techniques for multiplexing uplink control information in accordance with aspects of the disclosure. In some examples, the wireless communication system 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a network entity 105-a and a UE 115-a, which may be examples of corresponding devices described with reference to FIG.

[0092] In some examples, the network entity 105-a and the UE 115-a may communicate over a communication link 205 within a coverage area 110-a of the network entity 105-a. The UE 115-a may monitor SPS transmissions (e.g., from the network entity 105-a), for example, in the PDSCH 220 according to one or more SPS configurations. The UE 115-a may generate SPS feedback bits (e.g., ACK / NACK bits) scheduled for transmission to the network entity 105-a in a first slot format 210 based on the monitoring. The first slot format 210 may include a duration of K1 symbols 250-a, which may separate the PDSCH 220 and the corresponding PUCCH 225-a.

[0093] In some cases, such as the second slot format 215, the PUCCH 225-b may conflict (e.g., collide) with downlink symbols from the network entity 105-a. For example, the network entity 105-a may transmit control signaling (e.g., RRC signaling) indicating that resources for transmitting the PUCCH 225-b are configured for downlink transmission and therefore are no longer available for uplink transmission. Due to the collision, the UE 115-a may delay the SPS ACK / NACK bits scheduled for transmission in the PUCCH 225-b to the earliest slot that can accommodate the SPS ACK / NACK bits. For example, the UE 115-a may check candidate target slots for carrying the delayed PUCCH 225-c for multiple collided SPS PUCCH transmissions, but the candidate target slots may not accommodate PUCCH resources carrying the SPS ACK / NACK bits from all the collided SPS PUCCH transmissions. The UE 115-a may determine whether to skip the candidate target slot and check the next slot or transmit some of the collided SPS ACK / NACK bits on the candidate target slot. In some other cases, the candidate target slot may already carry existing non-delayed UCI bits for transmission, and thus the candidate target slot may not have capacity to carry PUCCH for the sum of the existing UCI bits and the / NACK bits from the collided SPS PUCCH transmission. It may be advantageous for the UE 115-a to determine whether to skip the candidate target slot and check the availability of the next slot or transmit some of the existing UCI bits or the collided SPS ACK / NACK bits in the candidate target slot.

[0094] In some examples, the UE 115-a may multiplex the mixed existing delayed and non-delayed UCI bits in the same slot. After a collision between the PUCCH 225-b and one or more downlink symbols, the UE 115-a may delay the transmission of the SPS ACK / NACK bits scheduled for transmission in the PUCCH 225-b. For example, the second slot format 215 may include a duration of K1 symbols 250-b, which may separate the PDSCH 220 and the corresponding PUCCH 225-b. In some cases, the second slot format 215 may already carry existing non-delayed UCI bits to be transmitted in the PUCCH 225-c, and the UE 115-a may multiplex the mixed delayed SPS ACK / NACK bits and non-delayed UCI bits in the target slot for transmission in the PUCCH 225-c. In some examples, if the candidate target slot already has existing non-delayed UCI bits, the candidate target slot may not accommodate a combination of non-delayed UCI bits and delayed SPS ACK / NACK bits. That is, the size of the set of SPS ACK / NACK bits and UCI bit combinations may be larger than the allocation size of uplink symbols in the PUCCH 225-c. In some cases, the UE 115-a may cancel (e.g., drop) some or all of the UCI bits or SPS ACK / NACK bits in the PUCCH 225-c, or may continue to check the next slot (not shown) for transmitting all collided UCI bits and SPS ACK / NACK bits, or combinations thereof. In some examples, the UE 115-a may determine to transmit at least some of the SPS ACK / NACK bits in the PUCCH 225-c.

[0095] In some examples, the UE 115-a may determine to transmit at least a portion of the delayed SPS ACK / NACK bits in the PUCCH 225-c based on one or more channel conditions. In some examples, the SPS ACK / NACK bits from multiple collided PUCCHs 225 may be delayed to the same new PUCCH 225 (e.g., delayed PUCCH 225-c). The new codebook in the new PUCCH 225 may be a concatenation of the individual codebooks from the original collided PUCCHs 225, for example, based on the time ordering of the PUCCHs 225. For SPS ACK / NACK delay, the delayed SPS ACK / NACK bits from two or more initial PUCCH slots may be delayed together to the target slot. In some cases, when a candidate target slot does not have existing non-delayed UCI bits, if the target slot cannot accommodate the selected PUCCH 225 for all the collided ACK / NACK bits, the UE 115-a may not transmit the collided ACK / NACK bits in that target slot and may continue to check the next candidate slot for transmitting all of the collided ACK / NACK bits.

[0096] In some cases, if an existing non-delayed ACK / NACK bit exists in the target slot, both the collided SPS ACK / NACK bit and the existing ACK / NACK bit may be transmitted in the same PUCCH 225. The new codebook in the PUCCH 225 may be a concatenation of the codebook for the existing ACK / NACK bit and the codebook from the original colliding PUCCH transmission. In some cases, if an existing non-delayed ACK / NACK bit for SPS exists in the target slot, the UE 115-a may drop all of the existing ACK / NACK bits and the collided SPS ACK / NACK bits without further delay if the slot cannot accommodate the PUCCH 225 selected for both the existing ACK / NACK bit and the collided SPS ACK / NACK bit. In some examples, the UE 115-a may not transmit an ACK / NACK bit in that target slot, may consider all existing ACK / NACK bits and the collided ACK / NACK bits as collided ACK / NACK bits, and may continue to check the next candidate slot for transmitting all unexpired collided ACK / NACK bits.

[0097] In some cases, the UE 115-a may not retransmit the collided SPS ACK / NACK bits after a certain number of slots from the end of the slot in the PUCCH 225 where the collision occurred. In some examples, the number of slots may be configured per SPS configuration. In some cases, the UE 115-a may or may not tolerate a partial delay of the SPS ACK / NACK bits. In some cases, the network entity 105-a may indicate via a DCI that only a portion of the collided SPS ACK / NACK bits in the collided PUCCH may be delayed. In some cases, the UE 115-a may not support a delay of only a portion of the SPS ACK / NACK bits in the collided PUCCH 225. In some cases, if the delayed SPS ACK / NACK and the dynamic grant (DG) ACK / NACK are in the same target slot, the UE 115-a may multiplex both the SPS ACK / NACK and the DG ACK / NACK on the same PUCCH 225 indicated by the PUCCH reception indicator (PRI). In the SPS ACK / NACK delay, if the delayed SPS ACK / NACK does not need to be sent after the target PUCCH slot determination, the delayed SPS ACK / NACK bit may be dropped.

[0098] In some cases, a collision for delay purposes may occur when the PUCCH 225-b carrying the SPS ACK / NACK bits overlaps with one or more RRC configured downlink symbols, or one or more RRC configured flexible symbols that are signal synchronization block (SSB) symbols or CORESET (e.g., CORESET0) symbols. If the PUCCH overlaps with an RRC configured flexible symbol other than an SSB symbol or a CORESET (e.g., CORESET0) symbol, the PUCCH transmission may follow existing rules when the RRC configured flexible symbol is further modified by a dynamic slot format indication (SFI). In some cases, the UE 115-a may not expect the collided PUCCH 225 for delay purposes to also carry an ACK / NACK bit for the DG. In other words, if the DG PDSCH and the associated DG PUCCH (e.g., DG ACK / NACK bit) are in a given slot, the DCI may allocate sufficient resources for the new ACK / NACK bit and the SPS ACK / NACK bit.

[0099] In some cases, the collided SPS ACK / NACK bits may be delayed to the target slot if the corresponding selected PUCCH resource (e.g., PUCCH 225-c) is included in an RRC configured uplink symbol. In some cases, the collided SPS ACK / NACK bits may be delayed to the target slot if the corresponding selected PUCCH resource (e.g., PUCCH 225-c) is included in one or more RRC configured downlink symbols, or one or more RRC configured flexible symbols that are SSB symbols or CORESET (e.g., CORESET0) symbols. For example, in the SPS ACK / NACK delay, to determine valid symbols in the initial and target slots, collisions with symbols indicated by parameters for semi-static downlink symbols, SSB, and CORESET (e.g., CORESET0) may be considered invalid and indicate no symbols for uplink transmission. In some cases, if the collided PUCCH 225 carries ACK / NACK bits for PDSCH 220 configured according to both DG and SPS configurations, the SPS ACK / NACK delay rule may be applied to both the DG and SPS ACK / NACK bits. In some cases, if the selected PUCCH carrying the delayed ACK / NACK bit overlaps with a downlink transmission scheduled by DCI or DG in the target slot, or overlaps with a downlink or flexible symbol indicated by DCI format 2_0, the UE 115-a may drop the delayed ACK / NACK bit without further delay. Thus, with SPS ACK / NACK delay, if the UE 115-a cannot transmit the delayed SPS ACK / NACK after the target slot determination, the UE 115-a may drop the delayed SPS ACK / NACK bit.

[0100] 3 illustrates an example of a transmission scheme 300 supporting a technique for multiplexing uplink control information according to an aspect of the disclosure. In some examples, the transmission scheme 300 may implement or be implemented by aspects of the wireless communication systems 100 and 200. For example, the transmission scheme 300 may illustrate communication between a network entity 105-b and a UE 115-b, which may be examples of corresponding devices described with reference to FIG. 1 and FIG. 2. In some cases, the UE 115-b may implement a technique for multiplexing uplink control information to determine how to transmit delayed SPS feedback in a set of uplink symbols in accordance with the transmission scheme 300.

[0101] In some examples, the network entity 105-b and the UE 115-b may communicate via a communication link (e.g., the communication link 205 described with reference to FIG. 2). The UE 115-b may be configured to monitor SPS transmissions from the network entity 105-b. For example, the network entity 105-b may transmit an SPS PDSCH 305-a with a first SPS configuration, sometimes referred to as SPS config 1, and an SPS PDSCH 305-b with a second SPS configuration, sometimes referred to as SPS config 2. In some cases, the UE 115-b may transmit SPS feedback (e.g., SPS ACK / NACK bits) for each SPS PDSCH 305 via a corresponding PUCCH 315. In some cases, the SPS ACK / NACK bits may conflict (e.g., collide) with downlink symbols from the network entity 105-b. For example, the collided SPS ACK / NACK bits may be carried on the collided PUCCH 315-a (e.g., for SPS config 1) or the collided PUCCH 315-b (e.g., SPS config 2). The network entity 105-b may transmit control signaling (e.g., RRC signaling) indicating that the resources for transmitting the PUCCHs 315-a and 315-b are configured for downlink transmission and therefore are no longer available for uplink symbol transmission. In some cases, the UE 115-b may delay the SPS ACK / NACK to the earliest slot that can accommodate the PUCCH 315. The UE 115-b may check every slot after the slot containing the original collided PUCCH 315 until the UE 115-b finds the first slot that can accommodate the same PUCCH resource as the collided PUCCH resource.

[0102] In some cases, the UE 115-b may check a candidate target slot (e.g., target slot 325) for carrying a delayed PUCCH for multiple collided SPS PUCCH transmissions 315. The target slot 325 may not accommodate a PUCCH 315 carrying SPS ACK / NACK bits from all collided SPS PUCCH transmissions 315. For example, two SPS PUCCH transmissions, such as collided PUCCH 315-a and collided PUCCH 315-b, may collide with a downlink symbol in a corresponding slot, and the UE 115-b may check the target slot 325 (e.g., a mixed uplink and downlink slot) for a potential delayed PUCCH for carrying the total number of SPS ACK / NACK bits from both collided SPS PUCCHs 315. In some cases, when a PUCCH list (sometimes referred to as "SPS-PUCCH-AN-List-r16") is configured, the UE 115-b may select a PUCCH resource from the list based on the sum of collided ACK / NACK bits. However, the selected PUCCH resource with a starting symbol and a certain number of symbols or resource blocks (RBs) may not fit into the available uplink symbols 320 in the target slot 325. It may be advantageous for the UE 115-b to determine whether to skip the target slot 325 and check the availability of the next slot. In some examples, the network entity 105-b may not ensure that the PUCCH resource selected based on the total payload including all delayed ACK / NACK bits and potential existing non-delayed UCI bits can fit into the available uplink symbols 320 of the target slot 325.

[0103] In some cases, the target slot 325 may already carry existing non-delayed UCI bits for transmission, and thus the target slot 325 may not have the capacity to carry a PUCCH for the sum of the existing UCI bits and the SPS ACK / NACK bits from the collided PUCCH 315. For example, the target slot 325 may be instructed to transmit the existing non-delayed SPS ACK / NACK bits in the third PUCCH (e.g., for SPS config 3). In some cases, if a PUCCH list SPS-PUCCH-AN-List-r16 is configured, the UE 115-b may select a PUCCH resource from the list based on the total payload of the existing ACK / NACK bits and the collided ACK / NACK bits. However, the selected PUCCH 315 at the corresponding time and frequency location may not fit into the available uplink symbols 320 in the target slot 325.

[0104] In some cases, in addition to transmitting a non-delayed ACK / NACK bit for the third SPS PUCCH (e.g., for SPS config 3), the target slot 325 may be instructed to transmit an existing non-delayed ACK / NACK bit for the downlink DG 310. The UE 115-b may select a PUCCH resource based on the PRI in the downlink control information (DCI) of the DG 310 and the total payload of the existing ACK / NACK bits and the collided SPS ACK / NACK bits. However, the selected PUCCH 315 at the corresponding time and frequency location may not fit into the available uplink symbols 320 in the target slot 325. Therefore, it may be advantageous for the UE 115-b to determine whether it may skip the target slot 325 and check the availability of the next slot, or transmit some of the existing UCI bits or the collided SPS ACK / NACK bits in the target slot 325. In some examples, the network entity 105-b may not ensure that the PUCCH resource selected based on the total payload including all delayed SPS ACK / NACK bits and potential existing non-delayed UCI bits can fit into an available uplink symbol of a candidate slot (e.g., uplink symbol 320 of target slot 325).

[0105] In some examples, the UE 115-b may multiplex the mixed existing delayed and non-delayed UCI bits in the same slot. The UE 115-b may monitor one or more SPS transmissions in the SPS PDSCH 305 based on some SPS configurations. In some cases, the UE 115-b may generate SPS feedback associated with the SPS transmission and schedule the feedback to be transmitted to the network entity 105-a in a first set of uplink symbols (e.g., in the PUCCH 315). In some cases, the UE 115-b may receive control signaling from the network entity 105-b that changes the availability of a first slot format for transmitting feedback. That is, the SPS ACK / NACK bits may conflict (e.g., collide) with downlink symbols from the network entity 105-b. For example, the network entity 105-b may transmit control signaling (e.g., RRC signaling) indicating that resources for transmitting the SPS ACK / NACK bits are configured for downlink transmissions and therefore are no longer available for uplink transmissions (e.g., PUCCH 315). Due to the collision, the UE 115-a may delay transmission of the SPS ACK / NACK bits to a second set of uplink symbols, such as the uplink symbols 320 in the target slot 325, to avoid the collision. In some examples, the UE 115-b may determine to transmit at least a portion of the SPS ACK / NACK bits in the uplink symbols 320.

[0106] In some cases, collisions may occur when the PUCCH 315 carrying the SPS ACK / NACK bits overlaps partially or completely with a combination of downlink symbol types including one or more RRC configured downlink symbols, one or more RRC configured flexible symbols that are SSB symbols or CORESETs (e.g., CORESET0), one or more downlink symbols dynamically indicated by the DCI (e.g., DCI format 2_0 that may include a dynamic SFI), one or more downlink transmissions dynamically scheduled by the DCI including at least a CSI reference signal (CSI-RS) and the SPS PDSCH 305, and one or more RRC configured flexible symbols under a combination of one or more conditions. For example, a symbol may include one or more RRC configured flexible symbols without any condition.

[0107] In some cases, the symbol may include any one or more RRC configuration flexible symbols when the network entity 105-b may not indicate uplink transmission on the RRC configuration flexible symbols if at least the UE 115-b does not receive DCI format 2_0 that provides a slot format for the symbol. In some cases, the fact that uplink transmission on these symbols is not indicated may be due to the network entity 105-b refraining from configuring an RRC flag (e.g., enableConfiguredUL). In some cases, the symbol may include one or more RRC configuration flexible symbols within a quantity X symbols from a downlink symbol indicated by the latest RRC or DCI. Here, X may represent a switch time from uplink to downlink. In some cases, X may be indicated by the network entity 105-a (e.g., via RRC signaling, MAC-CE, or DCI), X may be based on UE capabilities, or X may be fixed (e.g., X=1 for FR1 and X=2 for FR2). In some cases, any one or more of the RRC configuration flexible symbols may be different from the random access channel (RACH) occasion symbols. In some cases, the UE 115-b may partially or fully cancel the SPS ACK / NACK based on an indication (e.g., a cancellation indicator) from the network entity 105-b. For example, the offset between the DCI scheduling downlink transmission and the PUCCH 315 for the SPS ACK / NACK may be equal to or greater than a threshold for the UE 115-b to cancel (e.g., drop) the PUCCH. In some cases, the UE 115-b may apply these techniques to SPS ACK / NACK bits and UCI bits that have the same uplink physical layer (PHY) priority (e.g., high or low).

[0108] In some examples, after a collision occurs, the UE 115-b may search for candidate slots for transmitting the collided SPS ACK / NACK bits. The UE may determine a candidate slot that can accommodate all or a portion of the collided SPS ACK / NACK bits, such as the target slot 325, starting from the next slot after the collision, where the determination may be made if the corresponding selected PUCCH resources for retransmitting all or a portion of the collided SPS ACK / NACK bits in the target slot 325 do not overlap with a combination of symbol types in the target slot 325. The symbol types may include one or more RRC configured downlink symbols, one or more RRC configured flexible symbols that are SSB symbols, one or more downlink symbols dynamically indicated by the DCI (e.g., DCI format 2_0 that may include a dynamic SFI), one or more downlink transmissions dynamically scheduled by the DCI including at least the CSI-RS and the SPS PDSCH 305, and one or more RRC configured flexible symbols under a combination of one or more conditions. For example, the symbols may include one or more RRC configuration flexible symbols without any condition. In some examples, the UE 115-b may determine the target slot 325 based on a total ACK / NACK payload size, including delayed and non-delayed ACK / NACK information, if any, for the target slot 325.

[0109] In some cases, the symbol may include any one or more RRC configuration flexible symbols when the network entity 105-b may not indicate uplink transmission on the RRC configuration flexible symbols if at least the UE 115-b does not receive DCI format 2_0 that provides a slot format for the symbol. In some cases, the fact that uplink transmission on these symbols is not indicated may be due to the network entity 105-b refraining from configuring an RRC flag (e.g., enableConfiguredUL). In some cases, the symbol may include one or more RRC configuration flexible symbols within a certain quantity X symbols from the downlink symbol indicated by the latest RRC or DCI. Here, X may represent a switch time from uplink to downlink. In some cases, X may be indicated by the network entity 105-a (e.g., via RRC signaling, MAC-CE, or DCI), X may be based on the UE capabilities, or X may be fixed (e.g., X=1 for FR1 and X=2 for FR2). In some cases, any one or more of the RRC configuration flexible symbols may be different from the random access channel (RACH) occasion symbols. In some cases, the target slot 325 may include up to 14 uplink symbols 320. In some cases, the UE 115-b may apply these techniques to SPS ACK / NACK bits and UCI bits that have the same uplink physical layer (PHY) priority (e.g., high or low).

[0110] In some cases, the target slot 325 may not accommodate the selected PUCCH 315 for all the collided SPS ACK / NACK bits. For example, the target slot 325 may include a limited number of uplink symbols 320. The UE 115-b may multiplex the mixed delayed UCI bits and the existing UCI bits using one of several options when the PUCCH list SPS-PUCCH-AN-List-r16 is configured. In some cases, the UE 115-b may not transmit the collided SPS ACK / NACK bits in the target slot 325 and may continue to check the next slot for transmitting all the collided SPS ACK / NACK bits. In some cases, if the target slot 325 can accommodate the selected PUCCH 315 for a first quantity (e.g., quantity X) of collided SPS ACK / NACK bits, the UE 115-b may transmit those collided bits. For example, the UE 115-b may search for the maximum X by starting with X=1 and possibly increasing X, and continue to check the next slot for transmitting the remaining collided SPS ACK / NACK bits.

[0111] In another example, the UE 115-b may start with X equal to the total number of collided bits and search for the largest X by possibly decreasing X, and the UE 115-b may continue to check the next slot for transmitting the remaining collided SPS ACK / NACK bits. In some cases, if the target slot 325 can accommodate X of all collided SPS ACK / NACK PUCCHs 315 for the PUCCH 315 selected for the collided SPS ACK / NACK bits, the UE 115-b may transmit those collided bits using the target slot 325. For example, the UE 115-b may search for a set of X PUCCHs 315 that maximizes the total PUCCH payload, and the UE 115-b may continue to check the next slot for transmitting the remaining collided SPS ACK / NACK bits. In some cases, the UE 115-b may search for X PUCCHs 315 by increasing from the first X=1 collided PUCCHs 315 to the X that maximizes the payload. In some cases, the UE 115-b may search for X PUCCHs 315 by decreasing from X=total number of collided PUCCHs 315 to the X that maximizes the payload. In some cases, the UE 115-b may apply these techniques to ACK / NACK and UCI bits that have the same uplink physical layer (PHY) priority (e.g., high or low).

[0112] In some examples, the target slot 325 may already have existing non-delayed UCI bits to transmit, such as the SPS PDSCH 305-c (e.g., for SPS config 3) and ACK / NACK bits for the DG 310, which may include a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH). The target slot 325 may not accommodate the selected PUCCH 315 for the sum of all existing UCI bits and the collided SPS ACK / NACK bits, and the UE 115-b may multiplex the mixed bits according to some options. In some cases, the UE 115-b may not transmit the existing UCI bits or the collided SPS ACK / NACK bits in the target slot 325. The UE 115-b may consider all existing UCI bits and the collided SPS ACK / NACK bits as collided UCI bits and may therefore continue to check the next slot for transmitting all the collided UCI bits. Additionally or alternatively, the UE 115-b may consider the original collided SPS ACK / NACK bits as the collided SPS ACK / NACK bits and drop the existing UCI bits. Thus, the UE 115-b may continue to check the next slot for transmitting all the collided SPS ACK / NACK bits. In some cases, the UE 115-b may consider the sum of the original collided SPS ACK / NACK bits and the existing ACK / NACK bits (e.g., associated with the SPS PDSCH 305-c) as the collided SPS ACK / NACK bits, while dropping the other existing UCI bits. Thus, the UE 115-b may continue to check the next slot for transmitting all the collided SPS ACK / NACK bits. In some cases, the UE 115-b may drop all the existing UCI bits and the collided SPS ACK / NACK bits when the corresponding selected PUCCH resource may not fit into the target slot 325 where the existing UCI bits are also present.Thus, if there is a certain number of ACK / NACK bits to include in the target slot 325 and the new PDSCH resource allocation is not the resources for transmitting the new SPS ACK / NACK bits and the delayed SPS ACK / NACK bits, the UE 115-a may drop both the new SPS ACK / NACK bits and the delayed SPS ACK / NACK bits.

[0113] In some cases, when searching for a target slot for retransmitting the collided SPS ACK / NACK bits, the UE 115-b may skip the target slot 325 with the existing non-delayed UCI bits transmitted in the target slot 325. The UE 115-b may transmit the existing UCI bits in the target slot 325 based on the existing rules and continue to check the next slot for transmitting all or a portion of the collided SPS ACK / NACK bits. In some cases, the UE 115-b may determine separate PUCCH resources for the collided SPS ACK / NACK bits and the existing UCI bits in the target slot 325. For example, the UE 115-b may select a first PDSCH resource based on the payload of all or a portion of the collided SPS ACK / NACK bits and may select a second PUCCH resource based on the total payload of the existing UCI bits. In some cases, when both PUCCH resources overlap in time or frequency, one of the two PUCCH resources may be transmitted based on a priority option (e.g., when at least two PUCCH transmissions have the same uplink PHY priority). In some examples, the UE 115-b may transmit a PUCCH 315 carrying an existing UCI bit or a collided SPS ACK / NACK bit. In some examples, the UE 115-b may transmit a PUCCH 315 based on a UCI type. For example, the UE 115-b may first transmit an ACK / NACK, then a scheduling request (SR), then a high priority CSI, and then a low priority CSI. In some examples, the UE 115 may transmit a PUCCH 315 based on a PUCCH position. For example, the UE 115-b may transmit a PUCCH 315 based on the PUCCH 315 arriving earlier or later.

[0114] In some cases, the UE 115-b may transmit the sum of the existing UCI bits and a portion of the collided SPS ACK / NACK bits in the target slot 325. In some cases, the UE 115-b may determine a PUCCH resource based on the total payload of the existing UCI bits. In addition to the existing UCI bits, the UE 115-b may carry as many collided SPS ACK / NACK bits as possible using the remaining bits that the PUCCH resource can accommodate. For example, PUCCH format 0 and format 1 may carry up to 2 bits, while PUCCH formats 2, 3, and 4 may carry up to 1706 bits. In some cases, the UE 115-b may determine a PUCCH resource based on the total payload of the sum of the existing UCI bits and a certain number (e.g., X) of compressed bits based on all the collided SPS ACK / NACK bits. For example, the PUCCH resource may be determined where X=1 and 1 compression bit for all collided SPS ACK / NACK bits is equal to a logical “AND” operation (e.g., the compression bit for a NACK is 0 if the collided ACK / NACK bits for the NACK are 0).

[0115] In some cases, the UE 115-b may determine the PUCCH resource based on the total payload of the existing UCI bits plus the first X collided SPS ACK / NACK bits. For example, the UE 115-b may start with X=1, search for the largest X by possibly increasing X, and continue to check the next slot for transmitting the remaining collided SPS ACK / NACK bits. In another example, the UE 115-b may start with X=total number of collided bits, search for the largest X by possibly decreasing X, and the UE 115-b may continue to check the next slot for transmitting the remaining collided SPS ACK / NACK bits. In some cases, the UE 115-b may determine the PUCCH resource based on the total payload of the existing UCI bits plus the first X collided SPS ACK / NACK bits in the PUCCH 315. The UE 115-b may search for a set of X PUCCHs 315 that maximizes the total PUCCH payload, and the UE 115-b may continue to check the next slot for transmitting the remaining collided SPS ACK / NACK bits. In some cases, the UE 115-b may search for X PUCCHs 315 by increasing from the first X=1 collided PUCCH 315 to the X that maximizes the payload. In some cases, the UE 115-b may search for X PUCCHs 315 by decreasing from X=total number of collided PUCCHs 315 to the X that maximizes the payload. In some cases, the UE 115-b may apply these techniques to SPS ACK / NACK and UCI bits that have the same uplink physical layer (PHY) priority (e.g., high or low). Thus, with an SPS ACK / NACK delay, the UE 115-a may determine the target slot 325 as the next PUCCH slot in which a PUCCH resource is considered valid or is dynamically indicated (eg, from a PUCCH-ResourceSet).The UE 115-b may determine the target slot 325 based on the total ACK / NACK payload size, including the delayed ACK / NACK information and non-delayed SPS ACK / NACK information (eg, if such information exists) of the target slot 325.

[0116] In some examples, the UE 115-b may delay the collided SPS ACK / NACK bits or PUCCH 315 for a maximum duration. In some cases, the UE 115-b may delay the collided SPS ACK / NACK bits or all ACK / NACK bits in the same HARQ ACK transmission including the collided bits after a duration from the end of the slot where the collision occurred for the PUCCH including the collided SPS ACK / NACK bits. The duration may be a certain number (e.g., X) of slots or symbols and may be configured per SPS configuration. In some cases, the UE 115-b may not retransmit the collided SPS ACK / NACK bits after X slots with one or more uplink or flexible symbols per slot from the end of the slot where the SPS ACK / NACK PUCCH collision occurred. In some cases, the UE 115-b may not retransmit the collided bits after X uplink or flexible symbols from the end of the slot where the SPS ACK / NACK PUCCH collision occurred. Thus, the SPS ACK / NACK delay may define a limit on the maximum delay of the SPS ACK / NACK. In some cases, the X uplink symbols and flexible symbols may be pre-configured or indicated by the network entity 105-b (e.g., via DCI, MAC control element (MAC-CE), or RRC signaling) and may be common or different for the SPS ACK / NACK bits in different collided PUCCH transmissions 315. The collided PUCCH transmissions 315 may have the same uplink PHY priority or different uplink PHY priority. In some cases, the uplink symbols and flexible symbols may also be RRC configured or dynamically indicated by DCI format 2_0 (e.g., in a dynamic SFI). In some cases, the UE 115-b may apply these techniques to SPS ACK / NACK bits and UCI bits that have the same uplink physical layer (PHY) priority (e.g., high or low).

[0117] In some cases, the target slot 325 may not accommodate the selected PUCCH 315 for all the collided SPS ACK / NACK bits, and the collided SPS ACK / NACK bits may also have different uplink PHY priorities. In some cases, at least when the PUCCH list SPS-PUCCH-AN-List-r16 is configured, the UE 115-b may not transmit the collided SPS ACK / NACK bits in the target slot 325 and may continue to check the next slot for transmitting all the collided SPS ACK / NACK bits. In some cases, the UE 115-b may transmit as many high-priority collided SPS ACK / NACK bits in the target slot 325 as possible. In some cases, the UE 115-b may not transmit low-priority collided SPS ACK / NACK bits in the target slot 325. The loading may be in the order of the collided PUCCH 315 or collided ACK / NACK bits, and the UE 115-b may check the next slot for transmitting the remaining high priority collided ACK / NACK bits and all low priority collided ACK / NACK bits. In some cases, the UE 115-b may transmit as many high priority collided ACK / NACK bits as possible. If the slot can accommodate more bits, the UE 115-b may transmit as many low priority collided ACK / NACK bits as possible. The low priority SPS ACK / NACK bits may be compressed to fewer bits (e.g., one compressed bit may be equal to a logical "AND" operation for all low priority SPS ACK / NACK bits).

[0118] In some examples, the target slot 325 may already have existing non-delayed UCI bits to be transmitted, the target slot 325 may not accommodate the selected PUCCH 315 for the sum of all existing UCI bits and the collided ACK / NACK bits, and the collided SPS ACK / NACK bits may each have a different uplink PHY priority. In some cases, the UE 115-b may not transmit the existing UCI bits or the collided SPS ACK / NACK bits in the target slot 325, and the UE 115-b may continue to check the next slot for transmitting all existing UCI bits and the collided SPS ACK / NACK bits. In some examples, the UE 115-b may not transmit the existing UCI bits and the collided SPS ACK / NACK bits of high priority in the target slot 325 as many as possible. In some examples, the UE 115-b may not transmit the collided SPS ACK / NACK bits of low priority in the target slot 325. The loading may be in the order of existing UCI bits, then the collided PUCCH, or existing UCI bits, then the collided SPS ACK / NACK bits, or first the collided SPS ACK / NACK bits, then the existing UCI bits. The UE 115-b may check all of the remaining high priority bits and low priority bits. In some cases, the UE 115-b may transmit as many of the high priority collided ACK / NACK bits as possible. If the target slot 325 can accommodate more bits, the UE 115-b may transmit as many of the low priority collided SPS ACK / NACK bits as possible. In some cases, the low priority ACK / NACK bits may be compressed into fewer bits.

[0119] In some cases, the SPS ACK / NACK bits originally carried in multiple colliding PUCCHs 315 may be retransmitted in the same new PUCCH 315 in the order of the collided SPS ACK / NACK bits in the ACK / NACK codebook carried by the new PUCCH. In some examples, the SPS ACK / NACK bits from multiple colliding PUCCHs 315 may not be retransmitted in the same new PUCCH 315. For example, the ACK / NACK bits from a single colliding PUCCH 315 (e.g., the ACK / NACK bits from the earliest or latest colliding PUCCH 315) may be retransmitted in the new PUCCH. In some cases, the SPS ACK / NACK bits from multiple colliding PUCCHs 315 may be retransmitted in the same new PUCCH 315. In some cases, the codebook may be a concatenation of the individual codebooks originally associated with the colliding PUCCHs 315. The concatenation may be based on the order (e.g., in time) of the colliding PUCCHs 315. For example, a new codebook may be formed as the codebook from the first collided PUCCH 315, followed by the codebook from the second collided PUCCH 315, followed by the codebook from the third collided PUCCH 315, and so on up to the last collided PUCCH 315. In some cases, this technique may be applied to different codebook types (e.g., a type 1 codebook or a type 2 codebook).

[0120] In some examples, the new codebook may be configured based on similar rules for the existing Type 1 codebook configuration. In some cases, one or more bit positions in the new codebook from the SPS ACK / NACK bits from the collided PUCCH 315 may be determined by the time distance (e.g., K1 value) between the SPS PDSCH 305 associated with the collided PUCCH 315 and the new PUCCH 315. This may mean that the collided SPS ACK / NACK bits for the SPS PDSCH 305 may not be included in the new codebook if the K1 to the new PUCCH 315 for that SPS occasion is not included in the configured K1 set. In some cases, for Type 2 codebooks, the new codebook may be a concatenation of a transport block (TB)-based sub-codebook and a code block group (CBG)-based sub-codebook. For example, the new codebook may be a concatenation of the individual TB or CBG sub-codebooks from those collided PUCCHs 315, respectively. Thus, in an SPS ACK / NACK delay, delayed SPS ACK / NACK bits from two or more initial PUCCH slots may be delayed together to the target slot 325. In some cases, the delayed SPS ACK / NACK bits may be appended to an initial HARQ bit or codebook (e.g., Type 1 or Type 2) in the target slot 325.

[0121] In some cases, the new PUCCH 315 may carry only SPS ACK / NACK bits, and the new codebook carried in the new PUCCH 315 may be configured in a given order. In some cases, the UE 115-b may first check each component carrier (CC) in an ordered CC identifier (ID) list (e.g., from the lowest configured CC ID to the highest configured CC ID). For a given CC ID, the UE 115-b may check each SPS configuration ID in the ordered SPS configuration ID list (e.g., from the lowest configured SPS configuration ID to the highest configured SPS configuration ID). For a given SPS configuration ID, the UE 115-b may check whether there is at least one SPS PDSCH 305 with a corresponding PUCCH 315 carrying a corresponding SPS ACK / NACK bit that has a collision with the SPS ACK / NACK bit and has a corresponding maximum delay deadline that has not yet been reached. If this case exists, the UE 115-b may add SPS ACK / NACK bits for up to each such SPS PDSCH 305 to the new codebook based on the time ordering of at least one such SPS PDSCH 305 (e.g., the SPS ACK / NACK bits for the SPS PDSCH 305 in the earliest downlink slot may be added first). In some cases, to generate the new codebook, the UE 115-b may first loop through all such SPS PDSCHs 305 along with the PUCCHs 315 that had collisions for a given SPS configuration ID, then loop through all SPS configuration IDs in a given CC ID, then loop through all CC IDs.

[0122] In some cases, the SPS ACK / NACK bits originally carried in at least one collided PUCCH 315, as well as the existing non-delayed UCI bits, may be retransmitted in the same new PUCCH 315 in the order of the collided SPS ACK / NACK bits and the existing UCI bits in the ACK / NACK codebook carried by the new PUCCH 315. In some cases, the SPS ACK / NACK bits and the existing UCI bits from one or more collided PUCCHs 315 may not be retransmitted in the same new PUCCH. Thus, the SPS ACK / NACK bits and the existing UCI bits from one or more collided PUCCHs 315 may not be retransmitted in the same new PUCCH. For example, a rule may select either the collided SPS ACK / NACK bits or the existing UCI bits for that PUCCH 315. In some cases, the existing UCI bits may be restricted to only one or more UCI types, which may include any combination of ACK / NACK bits, CSI reports, and SRs. In some cases, SPS ACK / NACK bits and some types of existing UCI bits from one or more collided PUCCHs 315 may not be transmitted in the same PUCCH 315. In some cases, the PUCCH 315 may carry a type 1 ACK / NACK codebook, which may be a concatenation of a codebook from existing ACK / NACK bits and one or more individual codebooks originally carried in one or more collided PUCCHs 315. The concatenation order may be based on a rule. For example, a codebook from a collided PUCCH 315 may be appended to a codebook from existing ACK / NACK bits, or a codebook from existing ACK / NACK bits may be appended to a codebook from a collided PUCCH 315.

[0123] In some examples, the codebook may be configured based on similar rules for existing Type 1 codebook configurations. In some cases, one or more bit positions in the new codebook for SPS ACK / NACK bits from the collided PUCCH 315 may be determined by the time distance (e.g., K1 value) between the SPS PDSCH 305 associated with that collided PUCCH 315 and the new PDSCH 315. In some cases, the bit position in the new codebook for each existing ACK / NACK bit may be determined by K1 between the SPS PDSCH 305 associated with that existing ACK / NACK bit and the new PUCCH 315. In some cases, the codebook may be a concatenation of the individual codebooks originally associated with the collided PUCCH 315. The concatenation may be based on the ordering (e.g., in time) of the collided PUCCHs 315. For example, the new codebook may be formed as the codebook from the first collided PUCCH 315, followed by the codebook from the second collided PUCCH 315, followed by the codebook from the third collided PUCCH 315, and so on up to the last collided PUCCH 315. In some cases, this technique may be applied to different codebook types (e.g., Type 1 codebook or Type 2 codebook). In some cases, for Type 2 codebook, the new codebook may be a concatenation of TB-based sub-codebook and CBG-based sub-codebook. For example, the new codebook may be a concatenation of individual TB or CBG sub-codebooks from both the originally existing ACK / NACK bits and the collided PUCCH 315, and the concatenation order may be determined by a rule. In some cases, the delayed SPS ACK / NACK bits may be appended to the initial HARQ bits or codebook (e.g., Type 1 or Type 2) in the target slot 325.

[0124] In some cases, the new PUCCH 315 may carry only SPS ACK / NACK bits, and the new codebook carried in the new PUCCH 315 may be configured in a given order. In some cases, the UE 115-b may first check each component carrier in an ordered CC identifier (ID) list (e.g., from the lowest configured CC ID to the highest configured CC ID). For a given CC ID, the UE 115-b may check each SPS configuration ID in the ordered SPS configuration ID list (e.g., from the lowest configured SPS configuration ID to the highest configured SPS configuration ID). For a given SPS configuration ID, the UE 115-b may check whether there is at least one SPS PDSCH 305 with a corresponding PUCCH 315 carrying a corresponding SPS ACK / NACK bit that has a collision with the SPS ACK / NACK bit and has a corresponding maximum delay deadline that has not yet been reached. If this case exists, the UE 115-b may add SPS ACK / NACK bits up to each such SPS PDSCH 305 based on the time order of at least one such SPS PDSCH 305 to the new codebook (e.g., the SPS ACK / NACK bits for the SPS PDSCH 305 in the earliest downlink slot may be added first). In some cases, to generate the new codebook, the UE 115-b may first loop through all such SPS PDSCHs 305 along with the PUCCHs 315 that had collisions for a given SPS configuration ID, then loop through all SPS configuration IDs in a given CC ID, then loop through all CC IDs. In some cases, the delayed SPS ACK / NACK bits may be appended to an initial HARQ bit or codebook (e.g., Type 1 or Type 2) in the target slot 325.Therefore, for SPS ACK / NACK delay, the bit order of the delayed SPS ACK / NACK information from one or more initial slots in the target slot 325 is based on the SPS ACK / NACK bit order principle (e.g., based on the serving cell index, SPS configuration index, SPS PDSCH slot index).

[0125] In some cases, the collided SPS ACK / NACK bits may be delayed to the target slot 325, and the corresponding selected PUCCH resource does not overlap with one or more RRC configured downlink symbols or RRC configured flexible symbols that are SSB symbols. However, the selected PUCCH resource may overlap with a downlink transmission dynamically scheduled by DCI, including at least CSI-RS and PDSCH, and the offset between the DCI scheduled downlink transmission and the PUCCH for SPS ACK / NACK may be equal to or greater than a processing time threshold for the UE 115-b to cancel (e.g., drop) the PUCCH 315. In some cases, the UE 115-b may drop the delayed SPS ACK / NACK bits in the target slot 325 and may receive a dynamically scheduled downlink transmission. In some cases, the drop may be permanent without further retransmission or delay, or the dropped SPS ACK / NACK bits may be further delayed to a later slot with sufficient resources. In some cases, the UE 115-b may transmit a delayed SPS ACK / NACK bit at the target slot 325 and may not receive a dynamically scheduled downlink transmission. For example, the UE 115-b may drop a delayed SPS ACK / NACK bit if the SPS ACK / NACK delay means that a delayed SPS ACK / NACK decision may not be sent after the target slot 325.

[0126] In some examples, if the collided PUCCH 315 carries ACK / NACK bits for DCI scheduled downlink DG 310 in addition to SPS ACK / NACK bits for SPS PDSCH 305, the UE 115-b may clarify whether the SPS ACK / NACK delay rule described herein may be applied. In some cases, the SPS ACK / NACK delay rule may not be applied to the collided PUCCH 315 containing both DG 310 and SPS ACK / NACK bits. The UE 115-b may drop all ACK / NACK bits in the collided PUCCH 315 without a delayed transmission. In some cases, the SPS ACK / NACK delay rule may be applied to all ACK / NACK bits in the collided PUCCH 315 containing both DG 310 and SPS ACK / NACK bits. The UE 115-b may attempt a delayed transmission for all SPS ACK / NACK bits in the collided PUCCH 315. In some cases, SPS ACK / NACK bits from one or more collided PUCCHs 315 and some types of existing UCI bits may be transmitted in the same PUCCH 315, when a new codebook may be constructed by concatenating individual codebooks from the collided PUCCHs 315. In some cases, the PUCCH 315 may carry a type 1 ACK / NACK codebook, which may be a concatenation of a codebook from existing ACK / NACK bits and one or more individual codebooks originally carried in one or more collided PUCCHs 315. The concatenation order may be based on a rule. For example, a codebook from a collided PUCCH 315 may be appended to a codebook from existing ACK / NACK bits, or a codebook from existing ACK / NACK bits may be appended to a codebook from a collided PUCCH 315. In some cases, the SPS ACK / NACK delay rule may be applied only to SPS ACK / NACK bits in a collided PUCCH 315 that contains both DG 310 and SPS ACK / NACK bits.The UE 115-b may attempt deferred transmission for only the SPS ACK / NACK bits in the collided PUCCH 315 with the same codebook configuration as described above.

[0127] In some cases, the UE 115-b may be configured to configure multiple HARQ ACK / NACK codebooks, and the SPS ACK / NACK delay rules described herein may be applied to delayed transmission of colliding SPS ACK / NACK bits associated with the same codebook. That is, colliding SPS ACK / NACK bits belonging to the same codebook may be transmitted together in the same delayed transmission, and the delayed transmission may be determined independently for colliding ACK / NACK bits belonging to different codebooks respectively based on the delay rules. In some cases, each individual codebook may be identified by any combination of several coefficients configured by the network entity 105-b. In some cases, the codebooks may be associated with uplink PHY priorities as high or low (e.g., with corresponding priority IDs of 0 or 1, respectively). In some cases, the codebooks may be associated with TRP IDs in case of multi-TRP operation, and the corresponding TRP IDs (e.g., CORESETPoolIndex) may be 0 or 1. In some cases, a codebook may be associated with a PDSCH group index in case of group-based HARQ-ACK retransmissions (e.g., for a Type 2 codebook), and the PDSCH 220 group indicator may be 0 or 1. For example, a codebook may have high uplink PHY priority, a TRP ID of 0, and a PDSCH group index of 0. In some cases, a codebook may include sub-codebooks, and the sub-codebooks may be multiplexed into the same codebook (e.g., sub-codebooks with PDSCH group indices of 0 and 1 may be multiplexed into the same codebook).

[0128] FIG. 4 illustrates an example of a process flow 400 supporting a technique for multiplexing uplink control information according to an aspect of the disclosure. The process flow 400 may implement or be performed by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-c and the UE 115-c may be examples of the network entity 105 and the UE 115-c described with reference to FIG. 1 and FIG. 2. In the following description of the process flow 400, operations between the network entity 105-c and the UE 115-c may be transmitted in a different order than the example order shown, or operations performed by the network entity 105-c and the UE 115-c may be performed in a different order or at different times. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.

[0129] At 405, the UE 115-c may monitor one or more SPS transmissions according to one or more SPS configurations. For example, the network entity 105-c may transmit a first PDSCH according to a first SPS configuration and transmit a PDSCH according to a second SPS configuration.

[0130] At 410, the UE 115-c may generate a set of feedback bits associated with the SPS transmission, where the set of feedback bits are scheduled for transmission to the network entity 105-c in the first set of uplink symbols. For example, each feedback bit may indicate whether the UE 115-c successfully received the respective SPS transmission based on the monitoring. In some examples, the feedback bits may include ACK / NACK bits or other feedback bits.

[0131] At 415, the UE 115-c may receive control signaling from the network entity 105-c that changes the availability of the first set of uplink symbols for transmission of the set of feedback bits. For example, the network entity 105-c may send control signaling (e.g., RRC signaling) indicating that resources for transmitting the feedback bits are configured for downlink transmission and therefore are no longer available for uplink transmission. Thus, the UE 115-c may determine a collision with the configured downlink symbols.

[0132] At 420, the UE 115-c may delay transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling, e.g., due to a collision, the UE 115-c may delay the SPS ACK / NACK bits to another slot that can accommodate the SPS ACK / NACK bits.

[0133] At 425, the UE 115-c may determine to transmit at least a portion of the set of feedback bits in a second set of uplink symbols. At 430, the UE 115-c may communicate with the network entity 105-c according to the determination. For example, the UE 115-c may determine to transmit at least a portion of the set of feedback bits in the second set of uplink symbols. Operations performed at the UE 115-c and the network entity 105-c may improve resource utilization and, in some examples, may promote network efficiency, among other benefits.

[0134] 5 illustrates a block diagram 500 of a device 505 supporting techniques for multiplexing uplink control information according to an aspect of the disclosure. The device 505 may be an example of an aspect of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0135] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various traffic channels (e.g., control channels, data channels, traffic channels associated with techniques for multiplexing uplink control information). The information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or may utilize a set of multiple antennas.

[0136] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit 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 associated with techniques for multiplexing uplink control information). In some examples, the transmitter 515 may be collocated with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or may utilize a set of multiple antennas.

[0137] The communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be examples of means for implementing various aspects of the techniques for multiplexing uplink control information described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0138] In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or possibly supporting a means for performing the functions described in this disclosure. In some examples, at least one processor and a memory coupled to the at least one processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the at least one processor, instructions stored in the memory). Additionally or alternatively, in some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software). When implemented in code executed by a processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof, may be performed by a general purpose processor, a DSP, a central processing unit (CPU), a graphics processing unit (GPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or possibly supporting a means for performing the functions described in this disclosure).

[0139] A processor may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof).

[0140] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using general purpose processors, DSPs, ASICs, CPUs, GPUs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

[0141] In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to receive information, transmit information, or perform various other operations described herein.

[0142] The communications manager 520 may support wireless communications in a UE according to examples disclosed herein. For example, the communications manager 520 may be configured as, or may possibly support, a means for monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations. The communications manager 520 may be configured as, or may possibly support, a means for generating a set of feedback bits associated with one or more semi-persistent scheduled transmissions, the set of feedback bits being scheduled for transmission to a network entity in a first set of uplink symbols. The communications manager 520 may be configured as, or may possibly support, a means for receiving control signaling that modifies availability of the first set of uplink symbols for transmission of the set of feedback bits. The communications manager 520 may be configured as, or may possibly support, a means for delaying transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling. The communications manager 520 may be configured as, or may possibly support, a means for determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols. Communications manager 520 may be configured as or possibly support a means for communicating with network entities, as determined.

[0143] By including or configuring the communications manager 520 according to examples described herein, the device 505 (e.g., a processor controlling or possibly coupled to the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for multiplexing uplink control information, thereby reducing signaling overhead and power consumption, among other advantages. Delaying colliding SPS feedback based on different channel conditions and reducing the number of collisions may improve resource efficiency and user experience. Thus, the techniques described herein may improve network operation and, in some examples, may promote network efficiency, among other advantages.

[0144] 6 illustrates a block diagram 600 of a device 605 supporting techniques for multiplexing uplink control information according to an aspect of the disclosure. The device 605 may be an example of an aspect of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0145] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various traffic channels (e.g., control channels, data channels, traffic channels associated with techniques for multiplexing uplink control information). The information may be passed on to other components of the device 605. The receiver 610 may use a single antenna or a set of multiple antennas.

[0146] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit 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 associated with techniques for multiplexing uplink control information). In some examples, the transmitter 615 may be collocated with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0147] The device 605, or various components thereof, may be examples of means for implementing various aspects of the techniques for multiplexing uplink control information described herein. For example, the communications manager 620 may include an SPS transmission monitoring component 625, a feedback generating component 630, a control signaling receiving component 635, a feedback delay component 640, a feedback determining component 645, a communications component 650, or any combination thereof. The communications manager 620 may be an example of an aspect of the communications manager 520 described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to receive information, send information, or perform various other operations described herein.

[0148] The communications manager 620 may support wireless communications in the UE according to examples disclosed herein. For example, the SPS transmission monitoring component 625 may be configured as, or in some cases support, a means for monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations. The feedback generation component 630 may be configured as, or in some cases support, a means for generating a set of feedback bits associated with one or more semi-persistent scheduled transmissions, the set of feedback bits being scheduled for transmission to a network entity in a first set of uplink symbols. The control signaling reception component 635 may be configured as, or in some cases support, a means for receiving control signaling that changes the availability of the first set of uplink symbols for transmission of the set of feedback bits. The feedback delay component 640 may be configured as, or in some cases support, a means for delaying transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling. The feedback determination component 645 may be configured as, or in some cases support, a means for determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols. The communications component 650 may be configured as or possibly support a means for communicating with network entities, as determined.

[0149] 7 illustrates a block diagram 700 of a communications manager 720 supporting techniques for multiplexing uplink control information according to aspects of the disclosure. Communications manager 720 may be an example of aspects of communications manager 520, communications manager 620, or both described herein. Communications manager 720, or various components thereof, may be examples of means for implementing various aspects of techniques for multiplexing uplink control information described herein. For example, communications manager 720 may include an SPS transmission monitoring component 725, a feedback generation component 730, a control signaling reception component 735, a feedback delay component 740, a feedback determination component 745, a communications component 750, an uplink control information component 755, or any combination thereof. Each of these components may be in direct or indirect communication with one another (e.g., via one or more buses).

[0150] The communications manager 720 may support wireless communications in the UE according to examples disclosed herein. For example, the SPS transmission monitoring component 725 may be configured as, or in some cases support, a means for monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations. The feedback generation component 730 may be configured as, or in some cases support, a means for generating a set of feedback bits associated with one or more semi-persistent scheduled transmissions, the set of feedback bits being scheduled for transmission to a network entity in a first set of uplink symbols. The control signaling reception component 735 may be configured as, or in some cases support, a means for receiving control signaling that changes the availability of the first set of uplink symbols for transmission of the set of feedback bits. The feedback delay component 740 may be configured as, or in some cases support, a means for delaying transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling. The feedback determination component 745 may be configured as, or in some cases support, a means for determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols. The communications component 750 may be configured as, or may in some cases support, a means for transmitting at least a portion of the set of feedback bits in a second set of uplink symbols in accordance with the determination. The communications component 750 may be configured as, or may in some cases support, a means for communicating with a network entity in accordance with the determination.

[0151] In some examples, the feedback determination component 745 may be configured with, or possibly support, a means for determining that a size of the set of feedback bits is greater than a size of an allocation in the second set of uplink symbols for transmission of the set of feedback bits, and determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on determining that the size of the set of feedback bits is greater than the size of the allocation in the second set of uplink symbols.

[0152] In some examples, the feedback delay component 740 may be configured as, or in some cases support, a means for delaying the transmission of the set of feedback bits to the third set of uplink symbols based on the size of the allocation.

[0153] In some examples, the communications component 750 may be configured as, or in some cases support, a means for transmitting at least a portion of the set of feedback bits in a second set of uplink symbols in accordance with the allocation determination.

[0154] In some examples, the uplink control information component 755 may be configured as, or in some cases support, a means for generating a set of uplink control information bits scheduled for transmission to the network entity in the second set of uplink symbols, and determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on generating the set of uplink control information bits.

[0155] In some examples, communications component 750 may be configured as, or in some cases support, a means for transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in a second set of uplink symbols based on generating the set of uplink control information bits.

[0156] In some examples, the feedback determination component 745 may be configured as, or in some cases support, a means for determining that a size of the set of feedback bits and the set of uplink control information bits is greater than a size of an allocation in the second set of uplink symbols for transmitting the set of feedback bits and the set of uplink control information bits. In some examples, the communication component 750 may be configured as, or in some cases support, a means for refraining from transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based on determining that a size of the set of feedback bits and the set of uplink control information bits is greater than the size of the allocation, and the communication with the network entity includes said refraining.

[0157] In some examples, the feedback delay component 740 may be configured as, or in some cases support, a means for delaying transmission of the set of feedback bits and the set of uplink control information bits to a third set of uplink symbols based on the size of the allocation.

[0158] In some examples, determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on a type of the set of uplink control information bits.

[0159] In some examples, the communications component 750 may be configured as, or in some cases support, a means for transmitting the set of uplink control information bits in the second set of uplink symbols. In some examples, the feedback delay component 740 may be configured as, or in some cases support, a means for delaying transmission of the set of feedback bits to the third set of uplink symbols based on generating the set of uplink control information bits.

[0160] In some examples, the communications component 750 may be configured as, or may otherwise support, a means for transmitting at least a portion of the set of feedback bits in a second set of uplink symbols according to the determination. In some examples, the feedback delay component 740 may be configured as, or may otherwise support, a means for delaying transmission of the set of uplink control information bits to a third set of uplink symbols based on transmitting at least a portion of the set of feedback bits in the second set of uplink symbols.

[0161] In some examples, the feedback delay component 740 may be configured as or may otherwise support a means for generating compressed feedback bits based on generating a set of feedback bits, the compressed feedback bits being associated with at least a portion of the set of feedback bits. In some examples, the communication component 750 may be configured as or may otherwise support a means for transmitting the compressed feedback bits in a second set of uplink symbols based on generating a set of uplink control information bits.

[0162] In some examples, the feedback determination component 745 may be configured with or may support a means for determining that the second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols. In some examples, the communication component 750 may be configured with or may support a means for refraining from transmitting at least a portion of the set of feedback bits in the second set of uplink symbols based on the number of slots, and communicating with the network entity includes said refraining.

[0163] In some examples, each slot of a certain number of slots includes an uplink symbol, a flexible symbol, or both. In some examples, the flexible symbol is configured for transmission of an uplink transmission or a downlink transmission.

[0164] In some examples, the feedback decision component 745 may be configured as, or in some cases support, a means for determining an order of a set of feedback bits in a feedback codebook for transmission in the second set of uplink symbols, and determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on the order of the set of feedback bits in the feedback codebook.

[0165] In some examples, the communications component 750 may be configured with or possibly support a means for determining to transmit at least a portion of the set of feedback bits in a second set of uplink symbols based on an order of the set of feedback bits in a feedback codebook, where the feedback codebook is a first type feedback codebook or a second type feedback codebook that includes a concatenation of the sets of feedback codebooks associated with the first set of uplink symbols. In some examples, the concatenation of the sets of feedback codebooks is based on a temporal order of the sets of feedback codebooks.

[0166] In some examples, the feedback determination component 745 may be configured as, or in some cases support, a means for generating a feedback codebook based on a set of indices associated with the serving cell, one or more semi-persistent scheduling configurations, the first set of uplink symbols, and the second set of uplink symbols. In some examples, the communication component 750 may be configured as, or in some cases support, a means for determining to transmit at least a portion of the set of feedback bits in the second set of uplink symbols according to the generated feedback codebook.

[0167] In some examples, the feedback determination component 745 may be configured as, or may possibly support, a means for generating a set of uplink control information bits and a feedback codebook scheduled for transmission to the network entity in the second set of uplink symbols, and determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols based on generating a set of uplink control information bits and a feedback codebook, the feedback codebook being a first type feedback codebook or a second type feedback codebook that includes a concatenation of the sets of feedback codebooks associated with the first set of uplink symbols. In some examples, the communication component 750 may be configured as, or may possibly support, a means for transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based on generating the set of uplink control information bits and in accordance with the feedback codebook.

[0168] In some examples, the feedback delay component 740 may be configured with, or possibly support, a means for delaying the transmission of the set of feedback bits to a third set of uplink symbols, where an allocation in the third set of uplink symbols for the transmission of the set of feedback bits overlaps with one or more scheduled downlink transmissions, and an offset between the allocation and the one or more scheduled downlink transmissions meets a threshold.

[0169] In some examples, the communications component 750 may be configured with or possibly support a means for refraining from transmitting at least a portion of the set of feedback bits in the third set of uplink symbols based on the overlapping one or more scheduled downlink transmissions, and communicating with the network entity includes said refraining.

[0170] In some examples, the feedback delay component 740 may be configured as, or may possibly support, a means for delaying transmission of the set of feedback bits to a third set of uplink symbols, the allocation in the third set of uplink symbols including the second set of feedback bits for the dynamic grant. In some examples, the communication component 750 may be configured as, or may possibly support, a means for refraining from transmitting at least a portion of the set of feedback bits in the third set of uplink symbols based on the delay.

[0171] In some examples, the feedback delay component 740 may be configured as, or possibly support, a means for delaying transmission of a set of feedback bits to a third set of uplink symbols, where the set of feedback bits is associated with an uplink dynamic grant, and where an allocation in the third set of uplink symbols includes the second set of feedback bits for the downlink dynamic grant.

[0172] In some examples, the feedback determination component 745 may be configured as, or in some cases may support, a means for determining that an allocation of the third set of uplink symbols does not overlap with symbols corresponding to the control resource set. In some examples, the feedback delay component 740 may be configured as, or in some cases may support, a means for delaying transmission of the set of feedback bits to the third set of uplink symbols based on determining.

[0173] In some examples, the feedback determination component 745 may be configured with, or possibly support, a means for determining that a size of the set of feedback bits is greater than a size of an allocation in the second set of uplink symbols for transmission of the set of feedback bits, and determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based on determining that the size of the set of feedback bits is greater than the size of the allocation in the second set of uplink symbols.

[0174] In some examples, the feedback determination component 745 may be configured as or may possibly support a means for determining that the second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols. In some examples, the communication component 750 may be configured as or may possibly support a means for refraining from transmitting at least a portion of the set of feedback bits in the second set of uplink symbols based on the number of symbols, and communicating with the network entity includes said refraining.

[0175] In some examples, the feedback determination component 745 may be configured as or may in some cases support a means for determining a respective priority associated with each feedback bit of the set of feedback bits. In some examples, the communication component 750 may be configured as or may in some cases support a means for transmitting at least a portion of the set of feedback bits in a second set of uplink symbols in accordance with determining the respective priority.

[0176] In some examples, the control signaling indicates that the first set of uplink symbols partially overlaps with the set of downlink symbols, the set of synchronization signal block symbols, or both.

[0177] FIG. 8 illustrates a diagram of a system 800 including a device 805 supporting techniques for multiplexing uplink control information according to an aspect of the disclosure. The device 805 may be an example of or may include components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may wirelessly communicate with one or more network entities 105, a UE 115, or any combination thereof. The device 805 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, and a processor 840. These components may be in electronic communication or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled via one or more buses (e.g., bus 845).

[0178] The I / O controller 810 may manage input and output signals for the device 805. The I / O controller 810 may also manage peripheral devices that are not integrated into the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, the 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, touch screen, or similar device. In some cases, the I / O controller 810 may be implemented as part of a processor, such as the processor 840. In some cases, a user may interact with the device 805 through the I / O controller 810 or through hardware components controlled by the I / O controller 810.

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

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

[0181] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting techniques for combining uplink control information). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to the processor 840, where the processor 840 and the memory 830 are configured to perform various functions described herein.

[0182] The communications manager 820 may support wireless communications in a UE according to examples disclosed herein. For example, the communications manager 820 may be configured as, or may possibly support, a means for monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations. The communications manager 820 may be configured as, or may possibly support, a means for generating a set of feedback bits associated with one or more semi-persistent scheduled transmissions, the set of feedback bits being scheduled for transmission to a network entity in a first set of uplink symbols. The communications manager 820 may be configured as, or may possibly support, a means for receiving control signaling that modifies availability of the first set of uplink symbols for transmission of the set of feedback bits. The communications manager 820 may be configured as, or may possibly support, a means for delaying transmission of the set of feedback bits to a second set of uplink symbols based on receiving the control signaling. The communications manager 820 may be configured as, or may possibly support, a means for determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols. The communications manager 820 may be configured as or possibly support a means for communicating with network entities according to the determinations.

[0183] By including or configuring a communications manager 820 according to examples described herein, the device 805 may support techniques for multiplexing uplink control information, which may reduce signaling overhead and power consumption, among other advantages. Delaying colliding SPS feedback based on different channel conditions and reducing the number of collisions may improve resource efficiency and user experience. Thus, the techniques described herein may improve network operation and, in some examples, may promote network efficiency, among other advantages.

[0184] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is shown as a separate component, in some examples, one or more functions described in connection with the communications manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of the techniques for multiplexing uplink control information described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0185] FIG. 9 illustrates a flowchart illustrating a method 900 supporting a technique for multiplexing uplink control information according to an aspect of the disclosure. The operations of the method 900 may be performed by a UE or components thereof as described herein. For example, the operations of the method 900 may be performed by the UE 115 described with reference to FIGS. 1-8. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0186] At 905, the method may include monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations. The operations of 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by the SPS transmission monitoring component 725 described with reference to FIG.

[0187] At 910, the method may include generating a set of feedback bits associated with one or more semi-persistent scheduled transmissions, the set of feedback bits scheduled for transmission to a network entity in a first set of uplink symbols. The operations of 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed by a feedback generation component 730 described with reference to FIG.

[0188] At 915, the method may include receiving control signaling from a network entity modifying availability of the first set of uplink symbols for transmission of the set of feedback bits. The operations of 915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed by the control signaling receiving component 735 described with reference to FIG.

[0189] At 920, the method may include delaying transmission of the set of feedback bits to a second set of uplink symbols based at least in part on receiving the control signaling. The operations of 920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 920 may be performed by a feedback delay component 740 described with reference to FIG.

[0190] At 925, the method may include determining whether to transmit at least a portion of the set of feedback bits in a second set of uplink symbols. The operations of 925 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 925 may be performed by a feedback determination component 745 described with reference to FIG.

[0191] At 930, the method may include communicating with a network entity in accordance with the determination. The operations of 930 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 930 may be performed by communications component 750 described with reference to FIG.

[0192] FIG. 10 illustrates a flow chart illustrating a method 1000 supporting techniques for multiplexing uplink control information according to aspects of the disclosure. The operations of method 1000 may be performed by a UE or components thereof as described herein. For example, the operations of method 1000 may be performed by the UE 115 described with reference to FIGS. 1-8. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0193] At 1005, the method may include monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations. The operations of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by the SPS transmission monitoring component 725 described with reference to FIG.

[0194] At 1010, the method may include generating a set of feedback bits associated with one or more semi-persistent scheduled transmissions, the set of feedback bits scheduled for transmission to a network entity in a first set of uplink symbols. The operations of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by a feedback generation component 730 described with reference to FIG.

[0195] At 1015, the method may include receiving control signaling from a network entity modifying availability of the first set of uplink symbols for transmission of the set of feedback bits. The operations of 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed by the control signaling receiving component 735 described with reference to FIG.

[0196] At 1020, the method may include delaying transmission of the set of feedback bits to a second set of uplink symbols based at least in part on receiving the control signaling. The operations of 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed by a feedback delay component 740 described with reference to FIG.

[0197] At 1025, the method may include determining whether to transmit at least a portion of the set of feedback bits in a second set of uplink symbols. The operations of 1025 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1025 may be performed by a feedback determination component 745 described with reference to FIG.

[0198] At 1030, the method may include transmitting at least a portion of the set of feedback bits in a second set of uplink symbols according to the determination. The operations of 1030 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1030 may be performed by communications component 750 described with reference to FIG.

[0199] The following provides a summary of aspects of the disclosure.

[0200] Aspect 1: A method of wireless communication in a UE, the method including: monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations; generating a set of feedback bits associated with the one or more semi-persistent scheduled transmissions, where the set of feedback bits are scheduled for transmission to a network entity in a first set of uplink symbols; receiving control signaling modifying availability of the first set of uplink symbols for transmission of the set of feedback bits; delaying transmission of the set of feedback bits to a second set of uplink symbols based at least in part on receiving the control signaling; determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols; transmitting at least a portion of the set of feedback bits in the second set of uplink symbols in accordance with the determination; and communicating with the network entity in accordance with the determination.

[0201] Aspect 2: The method of aspect 1, comprising determining that a size of the set of feedback bits is greater than a size of an allocation in a second set of uplink symbols for transmission of the set of feedback bits, wherein determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based at least in part on determining that the size of the set of feedback bits is greater than the size of the allocation in the second set of uplink symbols.

[0202] Aspect 3: The method of aspect 2, further comprising delaying transmission of the set of feedback bits to a third set of uplink symbols based at least in part on the size of the allocation.

[0203] Aspect 4: The method of any of aspects 3 to 3, further comprising transmitting at least a portion of the set of feedback bits in a second set of uplink symbols based at least in part on the size of the allocation.

[0204] Aspect 5: A method as described in any of aspects 1 to 4, wherein generating a set of uplink control information bits scheduled for transmission to a network entity in a second set of uplink symbols, and determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based at least in part on generating the set of uplink control information bits.

[0205] Aspect 6: The method of aspect 5, further comprising transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in a second set of uplink symbols based at least in part on generating the set of uplink control information bits.

[0206] Aspect 7: The method of any of aspects 5 and 6, further comprising: determining that a size of the set of feedback bits and the set of uplink control information bits is greater than a size of an allocation in the second set of uplink symbols for transmission of the set of feedback bits and the set of uplink control information bits; and refraining from transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based at least in part on determining that a size of the set of feedback bits and the set of uplink control information bits is greater than the size of the allocation, wherein the step of communicating with the network entity includes the refraining step.

[0207] Aspect 8: The method of aspect 7, further comprising delaying transmission of the set of feedback bits and the set of uplink control information bits to a third set of uplink symbols based at least in part on the size of the allocation.

[0208] Aspect 9: The method of any of aspects 5 to 8, wherein determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based at least in part on a type of the set of uplink control information bits.

[0209] Aspect 10: The method of any of aspects 5 to 9, further comprising: transmitting a set of uplink control information bits in a second set of uplink symbols; and delaying transmission of the set of feedback bits to a third set of uplink symbols based at least in part on generating the set of uplink control information bits.

[0210] Aspect 11: The method of any of aspects 5 to 10, further comprising: transmitting at least a portion of the set of feedback bits in a second set of uplink symbols according to the determination; and delaying transmission of the set of uplink control information bits to a third set of uplink symbols based at least in part on transmitting at least a portion of the set of feedback bits in the second set of uplink symbols.

[0211] Aspect 12: The method of any of aspects 5 to 11, further comprising: generating compressed feedback bits based at least in part on generating a set of feedback bits, the compressed feedback bits being associated with at least a portion of the set of feedback bits; and transmitting the compressed feedback bits in a second set of uplink symbols based at least in part on generating a set of uplink control information bits.

[0212] Aspect 13: The method of any of aspects 1 to 12, further comprising: determining that a second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols; and refraining from transmitting at least a portion of the set of feedback bits in the second set of uplink symbols based at least in part on the number of slots, wherein the step of communicating with the network entity includes the refraining step.

[0213] Aspect 14: The method of aspect 13, wherein each slot of the quantity of slots includes an uplink symbol, a flexible symbol, or both, and the flexible symbol is configured for transmission of an uplink transmission or a downlink transmission.

[0214] Aspect 15: A method as described in any of aspects 1 to 14, wherein the step of determining an order of a set of feedback bits in a feedback codebook for transmission in a second set of uplink symbols, wherein determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based at least in part on the order of the set of feedback bits in the feedback codebook.

[0215] Aspect 16: A method as described in any of aspects 1 to 15, determining to transmit at least a portion of the set of feedback bits in a second set of uplink symbols based at least in part on an order of the set of feedback bits in a feedback codebook, the feedback codebook being a first type feedback codebook or a second type feedback codebook that includes a concatenation of multiple feedback codebooks associated with the first set of uplink symbols.

[0216] Aspect 17: The method of aspect 16, wherein the concatenation of the multiple feedback codebooks is based at least in part on a temporal ordering of the multiple feedback codebooks.

[0217] Aspect 18: The method of any of aspects 15 to 17, further comprising: generating a feedback codebook based at least in part on a set of indices associated with the serving cell, the one or more semi-persistent scheduling configurations, the first set of uplink symbols, and the second set of uplink symbols; and determining, in accordance with the generated feedback codebook, to transmit at least a portion of the set of feedback bits in the second set of uplink symbols.

[0218] Aspect 19: The method of any of aspects 1 to 18, further comprising: generating a set of uplink control information bits and a feedback codebook scheduled for transmission to the network entity in a second set of uplink symbols, wherein determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based at least in part on generating the set of uplink control information bits and the feedback codebook, the feedback codebook being a concatenation of a plurality of feedback codebooks associated with the first set of uplink symbols; and transmitting at least a portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based at least in part on generating the set of uplink control information bits and in accordance with the feedback codebook.

[0219] Aspect 20: A method as described in any of aspects 1 to 19, further comprising delaying transmission of a set of feedback bits to a third set of uplink symbols, wherein an allocation in the third set of uplink symbols for transmission of the set of feedback bits overlaps with one or more scheduled downlink transmissions, and an offset between the allocation and the one or more scheduled downlink transmissions satisfies a threshold.

[0220] Aspect 21: The method of aspect 20, comprising: refraining from transmitting at least a portion of a set of feedback bits in a third set of uplink symbols based at least in part on one or more overlapping scheduled downlink transmissions, wherein the step of communicating with the network entity includes the refraining step.

[0221] Aspect 22: A method as described in any of aspects 1 to 21, further comprising: delaying transmission of the set of feedback bits to a third set of uplink symbols, where the allocation in the third set of uplink symbols includes the second set of feedback bits for the DG; and refraining from transmitting at least a portion of the set of feedback bits in the third set of uplink symbols based at least in part on the delaying step.

[0222] Aspect 23: A method as described in any of aspects 1 to 22, comprising delaying transmission of a set of feedback bits to a third set of uplink symbols, the set of feedback bits being associated with an uplink DG, and an allocation in the third set of uplink symbols including the second set of feedback bits for the downlink DG.

[0223] Aspect 24: The method of any of aspects 1 to 23, further comprising: determining that an allocation of a third set of uplink symbols does not overlap with symbols corresponding to the control resource set; and delaying transmission of the set of feedback bits to the third set of uplink symbols based at least in part on the determining step.

[0224] Aspect 25: A method as described in any of aspects 1 to 24, wherein the step of determining that a size of the set of feedback bits is greater than a size of an allocation in a second set of uplink symbols for transmission of the set of feedback bits, wherein the step of determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols is based at least in part on determining that the size of the set of feedback bits is greater than the size of the allocation in the second set of uplink symbols.

[0225] Aspect 26: The method of any of aspects 1 to 25, further comprising: determining that the second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols; and refraining from transmitting at least a portion of the set of feedback bits in the second set of uplink symbols based at least in part on the number of slots, wherein the step of communicating with the network entity includes the refraining step.

[0226] Aspect 27: The method of any of aspects 1 to 26, further comprising: determining a respective priority associated with each feedback bit of the set of feedback bits; and transmitting at least a portion of the set of feedback bits in a second set of uplink symbols in accordance with the determining the respective priority.

[0227] Aspect 28: The method of any of aspects 1 to 27, wherein the control signaling indicates that the first set of uplink symbols overlaps with the set of downlink symbols, the set of synchronization signal block symbols, or both.

[0228] Aspect 29: An apparatus for wireless communication in a UE, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the apparatus or the UE to perform a method as described in any of aspects 1 to 28.

[0229] Aspect 30: An apparatus for wireless communication in a UE, comprising at least one means for performing a method as recited in any of aspects 1 to 28.

[0230] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication in a UE, the code including instructions executable by at least one processor to perform a method as described in any of aspects 1 to 28.

[0231] It should be noted that the methods described herein describe possible implementations, that the acts and steps may be rearranged or otherwise modified, and that other implementations are possible. Additionally, aspects from two or more of these methods may be combined.

[0232] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described as examples, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may be applicable to other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to other systems and radio technologies, including various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and future systems and radio technologies not expressly mentioned herein.

[0233] The information and signals described herein may be represented using any of a wide variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0234] The various example blocks and components described with respect to the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the 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 in conjunction with a DSP core, or any other such configuration).

[0235] The functions described herein may be implemented in hardware, software (e.g., executed by a processor), or any combination thereof. Software shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. When implemented in software executed by a processor, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in different locations, including being distributed such that parts of the functions are implemented in different physical locations.

[0236] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that enables transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed 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, phase-change memory, Compact Disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the 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, the 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, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0237] As used herein, including within the claims, "or" as used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of 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). Also, the phrase "based on" as used herein should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, the phrase "based on" as used herein shall be construed similarly to the phrase "based at least in part on". As used herein, the term "and / or", when used in a list of two or more items, means that any one of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as including components A, B, and / or C, the composition can include only A, only B, only C, A and B in combination, A and C in combination, B and C in combination, or A, B, and C in combination.

[0238] The terms "determine" or "determining" encompass a wide variety of actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determining" can include receiving (such as receiving information), accessing (accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, or other such similar actions.

[0239] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of a second reference label, or other subsequent reference label.

[0240] The description set forth herein with reference to the accompanying drawings describes exemplary configurations and does not necessarily represent all examples that may be implemented or fall within the scope of the claims. As used herein, the term "exemplary" means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purposes of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0241] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the 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 the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0242] 100 Wireless communication system 105, 105-a, 105-b, 105-c Network entities 110, 110-a, 110-b, 110-c Geographic Coverage Area 115, 115-a, 115-b, 115-c UE 120 backhaul communication links 125 Communication Links 130 Core Network 135 Inter-device Communication Links 140 Access Network Entity 145 Access Network Transmission Entity 150 IP Services 200 Wireless Communication System 205 Communication Links 210 First Slot Format 215 Second Slot Format 220 PDSCH 225, 225-a, 225-b, 225-c PUCCH 250, 250-a, 250-b, 250-c symbols 300 Transmission Method 305, 305-a, 305-b, 305-c SPS PDSCH 310 Downlink DG 315, 315a, 315-b, 315-c PUCCH 320 Uplink Symbol 325 Target Slot 400 Process Flow 500 Block Diagram 505 Devices 510 Receiver 515 Transmitter 520 Communications Manager 600 Block Diagram 605 Devices 610 Receiver 615 Transmitter 620 Communications Manager 625 SPS Transmission Monitoring Component 630 Feedback Generation Component 635 Control Signaling Receiving Component 640 Feedback Delay Component 645 Feedback Judgment Component 650 Communication Components 700 Block Diagram 720 Communications Manager 725 SPS Transmission Monitoring Component 730 Feedback Generation Component 735 Control Signaling Receiving Component 740 Feedback Delay Components 745 Feedback Judgment Component 750 Communication Components 755 Uplink Control Information Component 800 Systems 805 Devices 810 I / O Controller 815 Transceiver 820 Communications Manager 825 Antenna 830 Memory 835 Code 840 Processor 845 Bus 900 ways 1000 ways

Claims

1. 1. A method for wireless communication in a user equipment (UE), comprising: monitoring one or more semi-persistent scheduled transmissions according to one or more semi-persistent scheduling configurations; generating a set of feedback bits associated with the one or more semi-persistent scheduled transmissions, the set of feedback bits being scheduled for transmission to a network entity in a first set of uplink symbols; The method comprises: receiving control signaling that modifies availability of the first set of uplink symbols for transmission of the set of feedback bits and determining that a collision occurs between a transmission of a physical uplink control channel (PUCCH) carrying the set of feedback bits; delaying transmission of the set of feedback bits to a second set of uplink symbols based on the collision and based at least in part on receiving the control signaling; determining whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols; transmitting at least the portion of the set of feedback bits in the second set of uplink symbols in accordance with the determination of whether to transmit at least the portion of the set of feedback bits in the second set of uplink symbols; communicating with the network entity according to the determination of whether to transmit at least a portion of the set of feedback bits in the second set of uplink symbols; Characterized by: method.

2. determining that a size of the set of feedback bits is greater than a size of an allocation in the second set of uplink symbols for transmission of the set of feedback bits; 2. The method of claim 1 , wherein determining whether to transmit at least the portion of the set of feedback bits in the second set of uplink symbols is based at least in part on the step of determining that the size of the set of feedback bits is greater than the size of the allocation in the second set of uplink symbols.

3. delaying transmission of the set of feedback bits to a third set of uplink symbols based at least in part on the size of the allocation; or transmitting at least the portion of the set of feedback bits in the second set of uplink symbols based at least in part on the size of the allocation; The method of claim 2, further comprising:

4. generating a set of uplink control information bits scheduled for transmission to the network entity in the second set of uplink symbols; 2. The method of claim 1, wherein the determining whether to transmit at least the portion of the set of feedback bits in the second set of uplink symbols is based at least in part on generating the set of uplink control information bits.

5. transmitting at least the portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based at least in part on generating the set of uplink control information bits; or transmitting at least the portion of the set of feedback bits in the second set of uplink symbols in accordance with the determining; and delaying transmission of the set of uplink control information bits to a third set of uplink symbols based at least in part on transmitting at least the portion of the set of feedback bits in the second set of uplink symbols. or transmitting the set of uplink control information bits in the second set of uplink symbols; and delaying transmission of the set of feedback bits to a third set of uplink symbols based at least in part on generating the set of uplink control information bits.

5. The method of claim 4, further comprising:

6. determining that a size of the set of feedback bits and the set of uplink control information bits is greater than a size of an allocation in the second set of uplink symbols for transmitting the set of feedback bits and the set of uplink control information bits; refraining from transmitting at least the portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based at least in part on determining that the sizes of the set of feedback bits and the set of uplink control information bits are greater than the size of the allocation, wherein the step of communicating with the network entity includes the refraining step; Optionally, delaying transmission of said set of feedback bits and said set of uplink control information bits to a third set of uplink symbols based at least in part on said size of said allocation; Further comprising: The method of claim 4.

7. 5. The method of claim 4, wherein the determining whether to transmit at least the portion of the set of feedback bits in the second set of uplink symbols is based at least in part on a type of the set of uplink control information bits.

8. generating compressed feedback bits based at least in part on generating the set of feedback bits, the compressed feedback bits being associated with at least the portion of the set of feedback bits; 6. The method of claim 5, further comprising: transmitting the compressed feedback bits in the second set of uplink symbols based at least in part on generating the set of uplink control information bits.

9. The method of claim 8, further comprising: determining that the second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols; and refraining from transmitting at least the portion of the set of feedback bits in the second set of uplink symbols based at least in part on the number of symbols, wherein the step of communicating with the network entity includes the refraining step; or determining that the second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols; refraining from transmitting at least the portion of the set of feedback bits in the second set of uplink symbols based at least in part on the quantity of slots, wherein the step of communicating with the network entity includes the refraining step; The method of claim 1, further comprising: determining that the second set of uplink symbols occurs a certain number of slots after the first set of uplink symbols; and refraining from transmitting at least the portion of the set of feedback bits in the second set of uplink symbols based at least in part on the quantity of slots, wherein the step of communicating with the network entity includes the refraining step; each slot of the number of slots includes an uplink symbol, a flexible symbol, or both; the flexible symbol is configured for transmission of an uplink transmission or a downlink transmission; The method of claim 1.

11. 2. The method of claim 1, wherein determining an order of the set of feedback bits in a feedback codebook to be transmitted in the second set of uplink symbols, determining whether to transmit at least the portion of the set of feedback bits in the second set of uplink symbols is based at least in part on the order of the set of feedback bits in the feedback codebook.

12. determining to transmit at least the portion of the set of feedback bits in the second set of uplink symbols based at least in part on the ordering of the set of feedback bits in the feedback codebook, the feedback codebook being a first type feedback codebook or a second type feedback codebook comprising a concatenation of a plurality of feedback codebooks associated with the first set of uplink symbols; Optionally, the concatenation of the plurality of feedback codebooks is based at least in part on a temporal ordering of the plurality of feedback codebooks. The method of claim 11.

13. generating a feedback codebook based at least in part on a set of associated indexes corresponding to a serving cell, the one or more semi-persistent scheduling configurations, the first set of uplink symbols, and the second set of uplink symbols; 12. The method of claim 11, further comprising: determining to transmit at least the portion of the set of feedback bits in the second set of uplink symbols according to the generated feedback codebook.

14. generating a set of uplink control information bits and a feedback codebook scheduled for transmission to the network entity in the second set of uplink symbols, wherein determining whether to transmit at least the portion of the set of feedback bits in the second set of uplink symbols is based at least in part on generating the set of uplink control information bits and the feedback codebook, the feedback codebook being a first type feedback codebook or a second type feedback codebook comprising a concatenation of a plurality of feedback codebooks associated with the first set of uplink symbols; and transmitting at least the portion of the set of feedback bits and the set of uplink control information bits in the second set of uplink symbols based at least in part on generating the set of uplink control information bits and in accordance with the feedback codebook. or determining a respective priority associated with each feedback bit of the set of feedback bits; and transmitting at least the portion of the set of feedback bits in the second set of uplink symbols in accordance with the determining the respective priority. The method of claim 1, further comprising:

15. delaying transmission of the set of feedback bits to a third set of uplink symbols, the allocation in the third set of uplink symbols including a second set of feedback bits for dynamic grants; and refraining from transmitting at least a portion of the set of feedback bits in the third set of uplink symbols based at least in part on the delay. or delaying transmission of the set of feedback bits to a third set of uplink symbols, the set of feedback bits being associated with an uplink dynamic grant, the allocation in the third set of uplink symbols including a second set of feedback bits associated with a downlink dynamic grant; or delaying transmission of the set of feedback bits to a third set of uplink symbols, where an allocation in the third set of uplink symbols for transmission of the set of feedback bits overlaps with one or more scheduled downlink transmissions, and an offset between the allocation and the one or more scheduled downlink transmissions meets a threshold; and, where an offset between the allocation and the one or more scheduled downlink transmissions meets a threshold, optionally refraining from transmitting at least a portion of the set of feedback bits in the third set of uplink symbols based at least in part on the overlapping one or more scheduled downlink transmissions, where the step of communicating with the network entity includes the refraining step. The method of claim 1 further comprising:

16. determining that an allocation of a third set of uplink symbols does not overlap with symbols corresponding to the control resource set; and delaying transmission of the set of feedback bits to a third set of uplink symbols based at least in part on the determination.

17. An apparatus for wireless communication in a user equipment (UE), comprising: At least one processor; and a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor, the instructions causing the UE to perform a method according to any one of claims 1 to 16.

Images