Multiplexing configuration grant signaling and feedback with different priorities

By allocating time-frequency resources and optimizing the encoding chain in the wireless communication system, the user equipment can realize the effective reuse of ACK feedback and CSI, solve the problem of low signaling and feedback efficiency in the prior art, and improve the system resource utilization and user experience.

CN118975359APending Publication Date: 2024-11-15QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094355.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-22
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

Existing wireless communication systems lack effective resource management and channel multiplexing technologies when supporting multiplexing configurations with different priorities, resulting in inefficiency and waste of resources.

Method used

User equipment (UE) optimizes the transmission of uplink shared channel messages by determining time-frequency resource allocation, and improves signaling and feedback efficiency using coded chains.

Benefits of technology

It improves the transmission efficiency of signaling and feedback, reduces processing and power consumption, optimizes the utilization of communication resources, and enhances the reliability and user experience of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975359A_ABST
    Figure CN118975359A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may determine that time-frequency resources allocated for acknowledgement (ACK) feedback and channel state information (CSI) overlap a periodic resource allocation for an uplink shared channel (e.g., a configuration grant-physical uplink shared channel (CG-PUSCH)). The UE may multiplex uplink control information (UCI) for the uplink shared channel with the ACK feedback, the CSI, or at least some of both on an uplink shared channel message. For example, the UE may use a coding chain that is specified for multiplexing ACK feedback of a priority type of the uplink shared channel message. The UE may transmit the uplink shared channel message after the UE multiplexes the ACK feedback, the CSI, or both with the UCI.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The following generally relates to wireless communications, including multiplexing configuration grant (CG) signaling and feedback with different priorities. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques 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, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses that support multiplexing of configuration grant signaling and feedback with different priorities. For example, the described technology enables a user equipment (UE) to multiplex the uplink shared channel message carrying uplink control information (UCI) with an acknowledgement (ACK) feedback and channel state information (CSI) according to the priority type of the UCI. The UE may determine that the time-frequency resources allocated for the ACK feedback and the CSI overlap with the periodic resource allocation for the uplink shared channel (e.g., configuration grant-physical uplink shared channel (CG-PUSCH)). In some cases, the UE may multiplex the UCI with at least some of the ACK feedback, the CSI, or both on the uplink shared channel message. For example, the UE may use a coding chain that is designated for multiplexing the ACK feedback of the priority type of the uplink shared channel message. After the UE multiplexes the ACK feedback, the CSI, or both with the UCI, the UE may send the uplink shared channel message.

[0004] A method for wireless communication at a UE is described. The method may include: determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type; multiplexing the UCI with at least some of the ACK feedback and CSI on the uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing the ACK feedback of the first priority type with the uplink shared channel message; and sending the uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a configuration grant (CG) uplink shared channel associated with the uplink shared channel message.

[0005] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to: determine that one or more resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type; multiplex the UCI with at least some of the ACK feedback and CSI on the uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing the ACK feedback of the first priority type with the uplink shared channel message; and send the uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type; a component for multiplexing the UCI with at least some of the ACK feedback and CSI on the uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing the ACK feedback of the first priority type with the uplink shared channel message; and a component for sending the uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: determine that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type; multiplex the UCI with at least some of the ACK feedback and CSI on the uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing the ACK feedback of the first priority type with the uplink shared channel message; and send the uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, multiplexing the UCI may include operations, features, components, or instructions for appending the UCI to the ACK feedback of the first priority type of the ACK feedback codebook, the ACK feedback of the first priority type being at least a portion of the ACK feedback multiplexed on the uplink shared channel message.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for multiplexing CSI on the uplink shared channel message using a combination of a second coding chain and a third coding chain, wherein the ACK feedback multiplexed on the uplink shared channel message may completely include the ACK feedback of the first priority type, and wherein the second coding chain and the third coding chain may each be different from the first coding chain.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, multiplexing the CSI may include operations, features, components, or instructions for multiplexing a first portion of the CSI using the second encoding chain and multiplexing a second portion of the CSI using the third encoding chain.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a second priority type of ACK feedback is multiplexed on the uplink shared channel message using a second coding chain, wherein the ACK feedback multiplexed on the uplink shared channel message includes the ACK feedback of the first priority type and the ACK feedback of the second priority type; and a first part of the CSI is multiplexed on the uplink shared channel message using a third coding chain, wherein the CSI includes the first part and the second part.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second portion of the CSI may not be multiplexed on the uplink shared channel message.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first priority type may be a higher priority type than the second priority type.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second priority type is a higher priority type than the first priority type.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, an ACK feedback of a second priority type is multiplexed on the uplink shared channel message using a second coding chain, wherein the ACK feedback multiplexed on the uplink shared channel message may completely include the ACK feedback of the second priority type; and a first part of the CSI is multiplexed on the uplink shared channel message using a third coding chain, wherein the CSI includes the first part and the second part.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, multiplexing the UCI may include operations, features, means, or instructions for appending the UCI to a dummy ACK feedback in an ACK feedback codebook.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second portion of the CSI may not be multiplexed on the uplink shared channel message.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first priority type may be a higher priority type than the second priority type.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second priority type is a higher priority type than the first priority type.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for multiplexing a first portion of the CSI on the uplink shared channel message using a second coding chain, wherein the CSI includes the first portion and the second portion, and multiplexing the second portion of the CSI on the uplink shared channel message using a third coding chain, wherein the UCI may be multiplexed with the CSI but not with the ACK feedback.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI includes a CG-UCI.

[0022] A method for wireless communication at a network entity is described. The method may include: determining that one or more time-frequency resources allocated to a UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority; and receiving the uplink shared channel message with the UCI multiplexed with at least some of the ACK feedback and the CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0023] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: determine that one or more time-frequency resources allocated to a UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority; and receive the uplink shared channel message with the UCI multiplexed with at least some of the ACK feedback and the CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0024] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a means for determining that one or more time-frequency resources allocated to a UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority; and a means for receiving the uplink shared channel message with the UCI multiplexed with at least some of the ACK feedback and the CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0025] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: determine that one or more time-frequency resources allocated to a UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority; and receive the uplink shared channel message with the UCI multiplexed with at least some of the ACK feedback and the CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, based on at least a portion of the ACK feedback having a same priority type as the UCI, the UCI may be encoded using the portion of the ACK feedback.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI includes a CG-UCI. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 and Figure 2 An example of a wireless communication system supporting multiplexing of configuration grant (CG) signaling and feedback with different priorities according to one or more aspects of the present disclosure is illustrated.

[0029] FIG. 3A to FIG. 3C An example of a resource map supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is illustrated.

[0030] Figure 4 An example of a process flow supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is illustrated.

[0031] Figure 5 and Figure 6 A block diagram of a device supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown.

[0032] Figure 7 A block diagram of a communication manager supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown.

[0033] Figure 8 A diagram of a system including a device supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown.

[0034] Fig. 9 and Fig.10 A block diagram of a device supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown.

[0035] Fig.11 A block diagram of a communication manager supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown.

[0036] Fig.12 A diagram of a system including a device supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown.

[0037] Figures 13 to 16 A flowchart illustrating a method for supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0038] In some wireless communication systems, wireless devices such as user equipment (UE) can use a technique called multiplexing to send multiple information channels simultaneously on the same time-frequency resources. That is, a network entity (e.g., a base station) can schedule multiple uplink transmissions that may conflict on time-frequency resources. Then, according to specified rules, the UE can multiplex the uplink transmissions onto a single channel. For example, the UE can be scheduled to send uplink shared channel transmissions, such as physical uplink shared channel (PUSCH) transmissions, while the UE is scheduled to send feedback messages, such as confirmation (ACK) or negative confirmation (NACK) information and channel state information (CsI). ACK and NACK information can be referred to as A / N feedback, ACK feedback, or feedback information. The UE can follow rules for multiplexing feedback and CSI onto PUSCH. The rules may include encoding different information sets using different coding chains. The rules may specify that ACK feedback is multiplexed onto PUSCH using a specific coding chain (a coding chain associated with ACK feedback coding). The rules may also specify that CSI is multiplexed onto PUSCH using different coding chains. In some examples, the CSI may be divided into two parts, so the rule may specify that the CSI part 1 coding chain is used to encode CSI part 1 and the CSI part 2 coding chain is used to encode CSI part 2. Therefore, three coding chains may be used to multiplex ACK information and CSI onto the PUSCH.

[0039] The UE may be scheduled to send a Configuration Grant (CG) transmission, which is a periodic uplink transmission. The CG-PUSCH message may have associated CG-Uplink Control Information (CG-UCI), which may also be multiplexed with the CG-PUSCH. However, there are no rules for multiplexing CG-UCI, ACK feedback, and CSI with the CG-PUSCH.

[0040] As described herein, the UE may multiplex the CG-UCI with the ACK feedback or feedback information and the CSI on the CG-PUSCH. For example, the UE may encode the CG-UCI (which may be referred to as UCI) using a coding chain for encoding feedback information having the same priority as the UCI. For example, the feedback information may include a high priority or low priority feedback bit. The UCI may also have a high priority or a low priority. Therefore, the UCI may be attached to the feedback codebook and encoded with feedback information matching the priority of the UCI. The UE may reuse the above three coding chains. The highest priority coding chain may be the feedback coding chain. The next coding chain may be the CSI part 1 coding chain. The third coding chain may be the CSI part 2 coding chain. If the feedback information includes both high priority feedback and low priority feedback, the feedback coding chain may be used to encode the high priority feedback information, and the CSI part 1 coding chain may be used to encode the low priority feedback information. This means that the CSI part 2 coding chain may be used to shift and encode the CSI part 1 information, and the CSI part 2 information may be discarded. In this scheme, the UE may encode the UCI using the feedback coding chain or the CSI part 1 coding chain as if the UCI was feedback information of the same priority.

[0041] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further described in the context of resource diagrams and process flows. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to multiplexing CG signaling and feedback with different priorities.

[0042] Figure 1 An example of a wireless communication system 100 that supports multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0043] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0044] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Communicating with other UEs 115 or network entities 105 as shown.

[0045] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) 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, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a 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 network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, reference to UE 115, network entity 105, apparatus, device, or computing system may include disclosure that UE 115, network entity 105, apparatus, device, or computing system is a node. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0046] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other through the backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 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), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

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

[0048] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. RU 170 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 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0049] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and the RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

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

[0051] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of part of a backhaul link).

[0052] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (eg, DU 165) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115.

[0053] For example, the IAB node 104 may be referred to as a parent node supporting child IAB node communications and as a child node associated with the IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, and may directly signal the transmissions to the UE 115. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0054] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support multiplexing of CG signaling and feedback with different priorities as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0055] UE 115 may include or may 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, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as 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, for example, GPS (Global Positioning System), BeiDou, GLONASS, or Galileo, or a ground-based device), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances, or vehicles, meters, netbooks, smartbooks, personal computers, smart devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart wristbands)), drones, robots / robotic devices, vehicles, in-vehicle equipment, meters (e.g., parking meters, electricity meters, gas meters, water meters), monitors, gas pumps, appliances (e.g., kitchen appliances, washing machines, dryers), location tags, medical / health care devices, implants, sensors / actuators, displays, or any other suitable device configured to communicate via wireless or wired media, etc.

[0056] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0057] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) 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 acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "sending," "receiving," or "communicating," when referring to the network entity 105, may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

[0058] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., of the same or different radio access technology).

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

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

[0061] The signal waveform transmitted by the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, 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 refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0062] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. 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 communications of a UE 115 may be constrained to one or more active BWPs.

[0063] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be referred to as T s =1 / (Δf max ·N f ) seconds sampling period, where Δf maxIt can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources 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).

[0064] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of code periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into a plurality of mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0065] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit 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 communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

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

[0067] The 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 to communicate 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) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0068] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (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 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0069] 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.

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

[0071] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) 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 in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0072] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging. In one aspect, the technology disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UE may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UE, NB-IoT (also known as CAT NB 1) 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 (further enhanced eMTC), mMTC (massive MTC), and NB-IoT may include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

[0073] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed with a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is 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 a carrier, or outside a carrier.

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

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

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

[0077] 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 a 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)) for managing 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)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0078] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 kilohertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features that may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0079] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of a spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, RU170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0080] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as network entities 105 and UEs 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on carrier aggregation configurations (e.g., LAA) in conjunction with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

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

[0082] The network entity 105 or the UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. For example, multiple signals may be sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0083] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

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

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

[0086] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send reference signals (e.g., cell-specific reference signals (CRS), CSI reference signals (CSI-RS)), which may be precoded or not precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

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

[0088] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate through logical channels. The MAC layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection for a radio bearer that supports user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, transport channels may be mapped to physical channels.

[0089] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). 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 under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0090] As described herein, UE 115 may multiplex UCI with ACK feedback or feedback information and CSI on a periodic uplink shared channel (e.g., CG-PUSCH). For example, UE 115 may encode UCI using a coding chain for encoding ACK feedback with the same priority as UCI. For example, ACK feedback may include feedback bits of high priority, low priority, or both. UCI may have a high priority or a low priority. Therefore, UCI may be attached to the feedback codebook and encoded with ACK feedback matching the priority of UCI. UE may reuse the above three coding chains. The highest priority coding chain may be the feedback coding chain. The next coding chain may be the CSI part 1 coding chain. The third coding chain may be the CSI part 2 coding chain. If the ACK feedback includes both high priority feedback and low priority feedback, the feedback coding chain may be used to encode the high priority ACK feedback, and the CSI part 1 coding chain may be used to encode the low priority ACK feedback. This means that the CSI part 2 coding chain may be used to shift and encode the CSI part 1 information, and the CSI part 2 information may be discarded. In this scheme, the UE may encode the UCI using the feedback coding chain or the CSI part 1 coding chain as if the UCI was feedback information of the same priority.

[0091] Figure 2 An example of a wireless communication system 200 that supports multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may be implemented or may be implemented to implement aspects of the wireless communication system 100. For example, the wireless communication system 200 illustrates communications between one or more UEs and network entities (such as UE 115-a and network entity 105-a), which may be as described herein (including references). Figure 1) An example of a corresponding device described in the wireless communication system 200. The wireless communication system 200 can support signaling from the UE 115-a, which can be multiplexed using coding chains based on the priority of UCI and feedback in the uplink shared channel.

[0092] In some cases, UE 115-a may communicate with network entity 105-a. For example, UE 115-a may send control information, data, or both to network entity 105-a via uplink communication link 205. UE 115-a may support the simultaneous transmission of multiple information channels on the same time-frequency resources using a technique known as multiplexing. For example, network entity 105-a may schedule uplink transmissions at UE 115-a that may conflict in time-frequency resources, such as in an unlicensed band. In some cases, network entity 105-a may periodically or semi-persistently schedule one or more uplink transmissions, such as via RRC signaling or MAC-CE. Periodic uplink transmissions may be periodic uplink shared channel transmissions, such as CG-PUSCH transmissions, which may include CG-UCI.

[0093] In some examples, periodic uplink transmission (e.g., CG uplink transmission) may have a first type (type 1) or a second type (type 2) of periodic uplink transmission. For type 1 periodic uplink transmission, the network entity 105-a may send RRC signaling to configure time-frequency domain resource allocation, which resource allocation includes the periodicity of CG resources, the offset of the uplink transmission, the starting symbol, and the length of the uplink shared channel used for the uplink transmission. For type 2 periodic uplink transmission, the network entity 105-a may send RRC signaling to configure the period and number of repetitions of the uplink transmission. The network entity 105-a may then send an activation downlink control information (DCI) message to initiate uplink transmission. In some cases, the network entity 105-a may configure type 1 and type 2 periodic uplink transmissions using multiple allocated time slots (e.g., a starting time slot and a time slot offset in a time slot cycle), multiple continuous uplink shared channels in a time slot, or both to support flexible time domain resource allocation, where a time slot can be a dynamically scheduled unit in the time domain.

[0094] In some examples, UE 115-a may report UCI to network entity 105-a using an uplink shared channel (e.g., PUSCH). UCI may include a HARQ process identifier (ID), a redundancy version ID (RVID), a new data indicator (NDI), channel occupancy time (COT) sharing information, or any combination thereof. In some cases, network entity 105-a may configure UE 115-a to use resources used for periodic uplink transmissions for retransmissions of previous transmissions. In some examples, the network entity may include downlink feedback information (DFI) in a DCI message to UE 115-a to provide feedback (e.g., HARQ A / N) of the uplink shared channel.

[0095] In some examples, the network entity 105-a may schedule the UE 115-a to send periodic uplink transmissions (e.g., CG transmissions), such as an uplink shared channel message 210. The uplink shared channel message 210 may be a CG-PUSCH message with an associated CG-UCI, which may also be multiplexed with the CG-PUSCH. The network entity 105-a may configure the uplink shared channel message 210 so that the UE 115-a may send the uplink shared channel message 210 once per time period 215. The uplink shared channel message 210 may overlap with one or more time-frequency resources of the ACK feedback 220, the CSI 225, or both, as shown in the resource map 230. The CSI 225 may include multiple parts of the CSI message, such as CSI part 1 and CSI part 2. However, the UE 115-a may not know how to multiplex the UCI, ACK feedback 220, and CSI 225 of the uplink shared channel message 210 on the uplink shared channel message 210.

[0096] In some examples, UE 115-a may use one or more coding chains to multiplex information on uplink shared channel message 210. Each coding chain may include a set of steps for multiplexing information. For example, UE 115-a may use a first coding chain to multiplex UCI with feedback information (such as ACK feedback 220). The first coding chain may include coding, rate matching or perforation, and resource element mapping for multiplexing ACK feedback 220 on uplink shared channel message 210. Additionally or alternatively, UE 115-a may use a second coding chain or a third coding chain to multiplex UCI with CSI 225 (such as CSI part 1 and CSI part 2, respectively) on uplink shared channel message 210. The second coding chain and the third coding chain may include coding, rate matching, and resource element mapping of CSI part 1 or CSI part 2 on uplink shared channel message 210, respectively.

[0097] In some examples, at 235, UE 115-a may multiplex the UCI with at least some of ACK feedback 220, CSI 225, or both on uplink shared channel message 210, which will refer to FIG. 3A to FIG. 3C Further detailed description. In some cases, UE 115-a may use one or more of the three coding chains based on the priority type of UCI, ACK feedback 220, CSI 225, or any combination thereof. In some examples, network entity 105-a may send CSI 225 on an uplink control channel (e.g., a physical uplink control channel (PUCCH)). Therefore, UE 115-a may treat CSI 225 as having a low priority type. When CSI 225 on the uplink control channel overlaps with uplink shared channel message 210, UE 115-a may multiplex CSI 225 on uplink shared channel message 210.

[0098] In some examples, UE 115-a may treat the UCI of the priority level (e.g., CG-UCI) as the ACK feedback 220 of the same priority level and jointly encode the UCI with the ACK feedback 220 of the same priority level (e.g., if there is ACK feedback 220). UE 115-a may jointly encode the UCI with the ACK feedback 220 using the first coding chain or the second coding chain for CSI part 1, which will be relative to FIG. 3A to FIG. 3C If the UCI is of high priority type, the UE 115-a may use the first coding chain to multiplex the UCI with the ACK feedback 220 on the uplink shared channel message 210, which will be relative to Figure 3A If the UCI is of low priority type and there is no high priority type UCI or ACK feedback 220, the UE 115-a may use the second coding chain, which will be relative to Figure 3B and Figure 3C If there is no ACK feedback 220, UE 115-a may multiplex UCI with CSI part 1 using the second coding chain.

[0099] In some cases, once the UE 115-a multiplexes the UCI with the ACK feedback 220, the CSI 225, or both, the UE 115-a may send the multiplexed transmission 240 to the network entity 105-a. The multiplexed transmission 240 may include an uplink shared channel message 210 with the multiplexed UCI and at least some of the ACK feedback 220 and the CSI 225.

[0100] Figure 3A , Figure 3B and Figure 3CExamples of resource maps 300-a, 300-b, and 300-c that respectively support multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure are illustrated. In some examples, resource maps 300-a, 300-b, and 300-c may implement aspects of wireless communication system 100 and wireless communication system 200. For example, resource maps 300-a, 300-b, and 300-c may be implemented by a wireless communication system in which a UE may send an uplink shared channel message with multiplexed UCI and at least some ACK feedback and CSI to a network entity, wherein the network entity and the UE may be as described in reference Figure 1 and Figure 2 Examples of corresponding devices described.

[0101] In some examples, the network entity may schedule the UE to send periodic uplink transmissions (e.g., CG transmissions), such as uplink shared channel messages. The uplink shared channel messages may be PUSCH messages, such as PUSCH 305-a, PUSCH 305-b, and PUSCH 305-c. Each PUSCH may have a corresponding UCI (e.g., UCI 310-a, UCI 310-b, and UCI 310-c, respectively), which may also be multiplexed with the PUSCH. The PUSCH may overlap with one or more time-frequency resources of ACK feedback, CSI, or both. CSI 225 may include multiple parts of a CSI message, such as CSI part 1 and CSI part 2. In some examples, PUSCH 305-a may overlap with ACK feedback 315-a, CSI part 1 320-a, CSI part 2 325-a, or any combination thereof. Similarly, PUSCH 305-b may overlap with ACK feedback 315-b, ACK feedback 315-c, CSI part 1320-a, CSI part 2325-a, or any components thereof, and PUSCH 305-a may overlap with ACK feedback 315-d, ACK feedback 315-e, CSI part 1320-a, CSI part 2325-a, or any combination thereof.

[0102] In some examples, the UE may use one or more coding chains to multiplex information on an uplink shared channel message. Each coding chain may include a set of steps for multiplexing information. For example, the UE may use coding chain 330-a or coding chain 330-b to multiplex UCI with feedback information (such as ACK feedback). Coding chain 330-a or coding chain 330-b may include coding, rate matching or perforation, and resource element mapping for multiplexing ACK feedback on an uplink shared channel message. Additionally or alternatively, the UE may use coding chain 330-b or coding chain 330-c to multiplex UCI with CSI (such as, respectively, CSI part 1 and CSI part 2) on an uplink shared channel message. Coding chain 330-b and coding chain 330-c may include coding, rate matching, and resource element mapping of CSI part 1 or CSI part 2 on an uplink shared channel message, respectively.

[0103] The UE may multiplex the UCI with ACK feedback, CSI, or at least some of the two. Figure 3A As shown, the UE may multiplex the ACK feedback 315-a with the UCI 310-a on the PUSCH 305-a to obtain a multiplexed transmission 335-a. Figure 3B and Figure 3C As shown in , the UE may multiplex the ACK feedback 315-b with the UCI 310-b on the PUSCH 305-b to obtain a multiplexed transmission 335-b, and the UE may multiplex the ACK feedback 315-e with the UCI 310-c on the PUSCH 305-c to obtain a multiplexed transmission 335-c.

[0104] In some examples, ACK feedback, UCI, and CSI may each have a priority type, such as high priority or low priority. Figure 3AAs shown in , ACK feedback 315-a may have bits that are entirely priority 340-a, which may be the same priority as UCI 310-a, while CSI portion 1 320-a and CSI portion 2 325-a have priority 340-b. In some cases, priority 340-a may be a high priority and priority 340-b may be a low priority, such that both UCI 310-a and ACK feedback 315-a may be high priority, and CSI portion 1 320-a and CSI portion 2 325-a are low priority. In some other cases, priority 340-a may be a low priority, and priority 340-b may also be a low priority, such that UCI 310-a, ACK feedback 315-a, CSI portion 1 320-a, and CSI portion 2 325-a may all be low priority. In some examples, the UE may treat UCI 310-a as if UCI 310-a is ACK feedback 315-a with the same priority as UCI 310-a. For example, the UE may append UCI 310-a to the end of a feedback codebook (e.g., an A / N codebook) and may jointly encode the ACK feedback 315-a with the UCI 310-a. The UE may multiplex the encoded bits on PUSCH 305-a using coding chain 330-a so that PUSCH 305-a may have the same priority as the multiplexed transmission 335-a (e.g., priority 340-a, which may be a high priority or a low priority). In some examples, the UE may encode CSI part 1 320-a using coding chain 330-b and encode CSI part 2 using coding chain 330-c.

[0105] In some examples, such as Figure 3BAs shown in , ACK feedback 315-b may have a bit of priority 340-a, while a different portion of feedback information (ACK feedback 315-c) may have a different priority (e.g., priority 340-b) than ACK feedback 315-b. ACK feedback 315-b may have the same priority as UCI 310-b, while CSI portion 1 320-b and CSI portion 2 325-b may have the same priority (e.g., priority 340-b) as ACK feedback 315-c. Priority 340-a may be a high priority, and priority 340-b may be a low priority, such that both UCI 310-b and ACK feedback 315-b may be high priority, and ACK feedback 315-c, CSI portion 1 320-b, and CSI portion 2 325-b are low priority. In some examples, the UE may treat UCI 310-b as if UCI 310-b is ACK feedback 315-b having the same priority as UCI 310-b. For example, the UE may append UCI 310-b to the end of a feedback codebook (e.g., A / N codebook) and may jointly encode ACK feedback 315-b with UCI 310-b. The UE may multiplex the encoded bits on PUSCH 305-b using coding chain 330-a so that PUSCH 305-b may have the same priority as the multiplexed transmission 335-b (e.g., priority 340-a, which may be a high priority). In some examples, the UE may encode ACK feedback 315-c using coding chain 330-b and encode CSI part 1 using coding chain 330-c. The UE may discard CSI part 2 325-b.

[0106] In some examples, such as Figure 3CAs shown in , ACK feedback 315-d may have a bit of priority 340-a, while a different portion of feedback information (ACK feedback 315-e) may have a different priority (e.g., priority 340-b) than ACK feedback 315-d. ACK feedback 315-e may have the same priority (e.g., priority 340-b) as UCI 310-c and CSI portion 1 320-c and CSI portion 2 325-c. Priority 340-a may be a high priority and priority 340-b may be a low priority, such that ACK feedback 315-d is a high priority and both UCI 310-c and ACK feedback 315-e are low priorities. In some examples, the UE may treat UCI 310-c as if UCI 310-c is ACK feedback 315-e having the same priority as UCI 310-c. For example, the UE may append UCI 310-c to the end of a feedback codebook (e.g., A / N codebook) and may jointly encode ACK feedback 315-e with UCI 310-c. The UE may multiplex the encoded bits on PUSCH 305-c using coding chain 330-b so that PUSCH 305-b may have the same priority as the multiplexed transmission 335-c (e.g., priority 340-b, which may be a low priority). In some examples, the UE may encode ACK feedback 315-d using coding chain 330-a and encode CSI part 1 using coding chain 330-c. The UE may discard CSI part 2 325-b.

[0107] In some examples, the UE may not be configured to send ACK feedback of the same priority type as the UCI. For example, the UE may have a high priority ACK feedback and a low priority UCI, or a low priority ACK feedback and a high priority UCI. The UE may use one or more dummy bits (e.g., 2 dummy bits) to simulate ACK feedback of the same priority type as the UCI. For example, ACK feedback 315-b, ACK feedback 315-e, or both may be dummy bits. The UE may treat the UCI as ACK feedback of the same priority as the UCI, and may jointly encode the UCI with the dummy bits for the ACK feedback (e.g., using coding chain 330-a or coding chain 330-b). The UE may multiplex the encoded bits on the PUSCH based on the applied coding chain.

[0108] Figure 4An example of a process flow 400 for supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 can implement aspects of the wireless communication system 100, the wireless communication system 200, the resource map 300-a, the resource map 300-b, and the resource map 300-c. The process flow 400 can illustrate an example of UE 115-b sending an uplink shared channel message with UCI multiplexed with ACK feedback and CSI to the network entity 105-b. The network entity 105-b and the UE 115-b can be as described in reference Figure 1 and Figure 2 Examples of network entities 105 and UE 115 described. The following alternative examples may be implemented in which some of the processes are performed in an order different from that described or not performed. In some cases, the processes may include additional features not mentioned below, or further processes may be added.

[0109] At 405, UE 115-b may determine that one or more time-frequency resources allocated to UE 115-b for reporting ACK feedback and CSI overlap with periodic resource allocations for uplink shared channel messages with UCI. The periodic resource allocations may be used for one or more CG-PUSCH messages, and the UCI may be CG-UCI. In some cases, UCI, ACK feedback, and CSI may have defined priority types (e.g., low priority or high priority).

[0110] At 410, UE 115-b may multiplex UCI with at least some of the ACK feedback and CSI on an uplink shared channel message. For example, UE 115-b may use a first coding chain that is designated for multiplexing ACK feedback of the same priority type as UCI on an uplink shared channel message. In some cases, UE 115-b may append UCI to ACK feedback of the same priority type in an ACK feedback codebook. The ACK feedback may include at least a portion of bits of the same priority type as UCI, which are multiplexed on the uplink shared channel message. UE 115-b may multiplex CSI on an uplink shared channel message using a combination of a second coding chain and a third coding chain. For example, if the ACK feedback multiplexed on the uplink shared channel message includes confirmation feedback of the same priority type as UCI (e.g., rather than other priority types), UE 115-b may encode both CSI part 1 and CSI part 2 using the second coding chain and the third coding chain, respectively, as shown in reference Figure 3A In some cases, the second coding strand and the third coding strand may be different from the first coding strand.

[0111] In some cases, UE 115-b may use the second coding chain to multiplex ACK feedback of a different priority type than UCI on the uplink shared channel message. The ACK feedback multiplexed on the uplink shared channel message may include ACK feedback of the same priority type as UCI and ACK feedback of a different priority type than UCI. UE 115-a may use the third coding chain to multiplex CSI part 1 on the uplink shared channel message. In some cases, UE 115-b may discard CSI part 2 based on multiplexing CSI part 1 using the third coding chain. UCI may have a high priority or a low priority, and ACK feedback may have a high priority, a low priority, or both.

[0112] In some examples, UE 115-b may multiplex ACK feedback of a different priority type than UCI on an uplink shared channel message using a second coding chain. The ACK feedback may include bits of a different priority type (e.g., and not of the same priority type as UCI). UE 115-b may multiplex CSI part 1 on an uplink shared channel message using a third coding chain. In some cases, UE 115-b may multiplex ACK feedback with UCI by appending UCI to a dummy ACK feedback in an ACK feedback codebook. UE 115-b may discard CSI part 2. UCI may have a high priority or a low priority, while ACK feedback may have a high priority, a low priority, or both.

[0113] In some cases, UE 115-b may multiplex CSI part 1 on an uplink shared channel message using a second coding chain and CSI part 2 on an uplink shared channel message using a third coding chain, where UCI is multiplexed with CSI but not with ACK feedback.

[0114] At 415, UE 115-b may send an uplink shared channel message on a CG uplink shared channel (e.g., CG-PUSCH) with the multiplexed UCI and at least some of the ACK feedback and CSI.

[0115] Figure 5 A block diagram 500 of a device 505 supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The device 505 may be an example of various aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0116] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to multiplexing CG signaling and feedback with different priorities, data channels, information channels). The information may be delivered to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0117] The transmitter 515 may provide 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 related to multiplexing CG signaling and feedback with different priorities). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0118] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of multiplexing CG signaling and feedback with different priorities as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0119] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0120] Additionally or alternatively, in some examples, the communication 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 communication management software). If implemented in code executed by a processor, the functionality of the communication 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 CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0121] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0122] According to the examples disclosed herein, the communication manager 520 may support wireless communication at the UE. For example, the communication manager 520 may be configured as or otherwise support a component for determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type. The communication manager 520 may be configured as or otherwise support a component for multiplexing UCI with at least some of the ACK feedback and CSI on an uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing ACK feedback of a first priority type with an uplink shared channel message. The communication manager 520 may be configured as or otherwise support a component for sending an uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0123] By including or configuring the communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof or otherwise coupled thereto) may support techniques for a UE to send an uplink shared channel message with multiplexed UCI and at least some ACK feedback and CSI to a network entity, which may provide reduced processing, reduced power consumption, or more efficient utilization of communication resources.

[0124] Figure 6 A block diagram 600 of a device 605 supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0125] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to multiplexing CG signaling and feedback with different priorities, data channels, information channels). The information may be delivered to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0126] The transmitter 615 may provide 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 related to multiplexing CG signaling and feedback with different priorities). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0127] Device 605 or its various components may be examples of components for performing various aspects of multiplexing CG signaling and feedback with different priorities as described herein. For example, communication manager 620 may include resource component 625, encoding component 630, uplink shared channel component 635, or any combination thereof. Communication manager 620 may be an example of various aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or integrate with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0128] According to the examples disclosed herein, the communication manager 620 may support wireless communication at the UE. The resource component 625 may be configured as or otherwise support a component for determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type. The coding component 630 may be configured as or otherwise support a component for multiplexing UCI with at least some of the ACK feedback and CSI on the uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing ACK feedback of the first priority type with the uplink shared channel message. The uplink shared channel component 635 may be configured as or otherwise support a component for sending an uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0129] Figure 7 A block diagram 700 of a communication manager 720 that supports multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The communication manager 720 can be an example of various aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components can be examples of components for performing various aspects of multiplexing of CG signaling and feedback with different priorities as described herein. For example, the communication manager 720 may include a resource component 725, a coding component 730, an uplink shared channel component 735, an ACK feedback component 740, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0130] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The resource component 725 may be configured as or otherwise support a component for determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type. The coding component 730 may be configured as or otherwise support a component for multiplexing UCI with at least some of the ACK feedback and CSI on the uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing ACK feedback of the first priority type with the uplink shared channel message. The uplink shared channel component 735 may be configured as or otherwise support a component for sending an uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0131] In some examples, to support multiplexing of UCI, ACK feedback component 740 may be configured as or otherwise support means for appending UCI to a first priority type of ACK feedback in an ACK feedback codebook, the first priority type of ACK feedback being at least a portion of ACK feedback multiplexed on an uplink shared channel message.

[0132] In some examples, the encoding component 730 may be configured as or otherwise support a means for multiplexing CSI on an uplink shared channel message using a combination of a second coding chain and a third coding chain, wherein the ACK feedback multiplexed on the uplink shared channel message comprises entirely ACK feedback of a first priority type, and wherein the second coding chain and the third coding chain are each different from the first coding chain.

[0133] In some examples, to support multiplexing CSI, encoding component 730 may be configured as or otherwise support means for multiplexing a first portion of CSI using a second encoding chain. In some examples, to support multiplexing CSI, encoding component 730 may be configured as or otherwise support means for multiplexing a second portion of CSI using a third encoding chain.

[0134] In some examples, the encoding component 730 may be configured as or otherwise support means for multiplexing ACK feedback of a second priority type on an uplink shared channel message using a second coding chain, wherein the ACK feedback multiplexed on the uplink shared channel message includes ACK feedback of a first priority type and ACK feedback of a second priority type. In some examples, the encoding component 730 may be configured as or otherwise support means for multiplexing a first portion of CSI on an uplink shared channel message using a third coding chain, wherein the CSI includes a first portion and a second portion.

[0135] In some examples, the second portion of the CSI is not multiplexed on the uplink shared channel message.

[0136] In some examples, the first priority type is a higher priority type than the second priority type.

[0137] In some examples, the second priority type is a higher priority type than the first priority type.

[0138] In some examples, the encoding component 730 may be configured as or otherwise support means for multiplexing ACK feedback of a second priority type on an uplink shared channel message using a second coding chain, wherein the ACK feedback multiplexed on the uplink shared channel message entirely includes ACK feedback of the second priority type. In some examples, the encoding component 730 may be configured as or otherwise support means for multiplexing a first portion of CSI on an uplink shared channel message using a third coding chain, wherein the CSI includes a first portion and a second portion.

[0139] In some examples, to support multiplexing of UCI, ACK feedback component 740 can be configured as or otherwise support means for appending UCI to dummy ACK feedback in an ACK feedback codebook.

[0140] In some examples, the second portion of the CSI is not multiplexed on the uplink shared channel message.

[0141] In some examples, the first priority type is a higher priority type than the second priority type.

[0142] In some examples, the second priority type is a higher priority type than the first priority type.

[0143] In some examples, the encoding component 730 may be configured as or otherwise support means for multiplexing a first portion of the CSI on an uplink shared channel message using a second coding chain, wherein the CSI includes a first portion and a second portion. In some examples, the encoding component 730 may be configured as or otherwise support means for multiplexing a second portion of the CSI on an uplink shared channel message using a third coding chain, wherein the UCI is multiplexed with the CSI but not multiplexed with the ACK feedback.

[0144] In some examples, the UCI includes a CG-UCI.

[0145] Figure 8 A diagram of a system 800 including a device 805 that supports multiplexing CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components thereof. The device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0146] I / O controller 810 can manage input signals and output signals of device 805. I / O controller 810 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor such as processor 840. In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0147] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825 that may be capable of concurrently 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 one or more antennas 825 for transmission, and for demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and the one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or components thereof as described herein.

[0148] 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 cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, the memory 830 may contain a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0149] The processor 840 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, 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 other 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., a memory 830) to enable the device 805 to perform various functions (e.g., functions or tasks that support multiplexing of CG signaling and feedback with different priorities). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0150] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be configured as or otherwise support a component for determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type. The communication manager 820 may be configured as or otherwise support a component for multiplexing UCI with at least some of the ACK feedback and CSI on an uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing ACK feedback of a first priority type with an uplink shared channel message. The communication manager 820 may be configured as or otherwise support a component for sending an uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0151] By including or configuring the communication manager 820 according to the examples described herein, the device 805 can support techniques for a UE to send an uplink shared channel message with multiplexed UCI and at least some ACK feedback and CSI to a network entity, which can improve communication reliability, reduce latency, improve user experience related to reduced processing, reduce power consumption, more efficiently utilize communication resources, improve coordination between devices, extend battery life, or improve utilization of processing power.

[0152] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that can be executed by the processor 840 to cause the device 805 to perform various aspects of multiplexing CG signaling and feedback with different priorities as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0153] Fig. 9A block diagram 900 of a device 905 supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

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

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

[0156] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of multiplexing CG signaling and feedback with different priorities as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0157] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, a GPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described herein. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0158] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0159] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0160] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. For example, the communication manager 920 may be configured as or otherwise support a component for determining that one or more time-frequency resources allocated to a UE for reporting acknowledgment feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority. The communication manager 920 may be configured as or otherwise support a component for receiving an uplink shared channel message with UCI multiplexed with at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0161] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof or otherwise coupled thereto) may support techniques for a UE to send an uplink shared channel message with multiplexed UCI and at least some ACK feedback and CSI to a network entity, which may provide reduced processing, reduced power consumption, or more efficient utilization of communication resources.

[0162] Fig.10 A block diagram 1000 of a device 1005 supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

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

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

[0165] Device 1005 or its various components may be examples of components for performing various aspects of multiplexing CG signaling and feedback with different priorities as described herein. For example, communication manager 1020 may include resource manager 1025, uplink sharing manager 1030, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0166] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The resource manager 1025 may be configured as or otherwise support means for determining that one or more time-frequency resources allocated to a UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority. The uplink shared channel manager 1030 may be configured as or otherwise support means for receiving an uplink shared channel message with UCI multiplexed with at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0167] Fig.11 A block diagram 1100 of a communication manager 1120 supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of multiplexing of CG signaling and feedback with different priorities as described herein. For example, the communication manager 1120 may include a resource manager 1125, an uplink sharing manager 1130, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0168] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The resource manager 1125 may be configured as or otherwise support means for determining that one or more time-frequency resources allocated to a UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority. The uplink shared channel manager 1130 may be configured as or otherwise support means for receiving an uplink shared channel message with UCI multiplexed with at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0169] In some examples, the UCI is encoded with at least a portion of the confirmation feedback based on the portion of the confirmation feedback having the same priority type as the UCI.

[0170] In some examples, the UCI includes a CG-UCI.

[0171] Fig.12 A diagram of a system 1200 including a device 1205 supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0172] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and for demodulating a signal. The transceiver 1210 or transceiver 1210 and one or more antennas 1215 or wired interfaces (where applicable) may be examples of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0173] Memory 1225 may include RAM and ROM. Memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by processor 1235, cause device 1205 to perform various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by processor 1235, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1225 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0174] Processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, a GPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to enable device 1205 to perform various functions (e.g., functions or tasks that support multiplexing of CG signaling and feedback with different priorities). For example, device 1205 or a component of device 1205 may include a processor 1235 and a memory 1225 coupled to processor 1235, the processor 1235 and memory 1225 being configured to perform the various functions described herein. Processor 1235 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1205 (e.g., by executing code 1230).

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

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

[0177] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured as or otherwise support a component for determining that one or more time-frequency resources allocated to a UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority. The communication manager 1220 may be configured as or otherwise support a component for receiving an uplink shared channel message with UCI multiplexed with at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message.

[0178] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 can support techniques for a UE to send an uplink shared channel message with multiplexed UCI and at least some ACK feedback and CSI to a network entity, which can improve communication reliability, reduce latency, improve user experience related to reduced processing, reduce power consumption, more efficiently utilize communication resources, improve coordination between devices, extend battery life, or improve utilization of processing power.

[0179] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1235, the memory 1225, the code 1230, the transceiver 1210, or any combination thereof. For example, the code 1230 may include instructions that can be executed by the processor 1235 to cause the device 1205 to perform various aspects of multiplexing CG signaling and feedback with different priorities as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0180] Fig.13 A flowchart illustrating a method 1300 for supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference Figures 1 to 8 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0181] At 1305, the method may include determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described resource component 725 is executed.

[0182] At 1310, the method may include multiplexing UCI with at least some of the ACK feedback and the CSI on an uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing ACK feedback of a first priority type with the uplink shared channel message. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The encoding component 730 described above is performed.

[0183] At 1315, the method may include sending an uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The described uplink shared channel component 735 is performed.

[0184] Fig.14 A flowchart illustrating a method 1400 for supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0185] At 1405, the method may include determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described resource component 725 is executed.

[0186] At 1410, the method may include multiplexing UCI with at least some of the ACK feedback and the CSI on an uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing ACK feedback of a first priority type with the uplink shared channel message. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 7 The encoding component 730 described above is performed.

[0187] At 1415, the method may include appending the UCI to a first priority type of ACK feedback in the ACK feedback codebook, the first priority type of ACK feedback being at least a portion of the ACK feedback multiplexed on the uplink shared channel message. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 7 The ACK feedback component 740 described above is performed.

[0188] At 1420, the method may include sending an uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The described uplink shared channel component 735 is performed.

[0189] Fig.15 A flowchart illustrating a method 1500 for supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0190] At 1505, the method may include determining that one or more time-frequency resources allocated to the UE for reporting ACK feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with associated UCI, the UCI having a first priority type. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 7 The described resource component 725 is executed.

[0191] At 1510, the method may include multiplexing UCI with at least some of the ACK feedback and the CSI on an uplink shared channel message, the UCI being multiplexed using a first coding chain, the first coding chain being designated for multiplexing ACK feedback of a first priority type with the uplink shared channel message. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 7 The encoding component 730 described above is performed.

[0192] At 1515, the method may include multiplexing ACK feedback of the second priority type on the uplink shared channel message using the second coding chain, wherein the ACK feedback multiplexed on the uplink shared channel message entirely includes ACK feedback of the second priority type. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference Figure 7 The encoding component 730 described above is performed.

[0193] At 1520, the method may include multiplexing a first portion of CSI on an uplink shared channel message using a third coding chain, wherein the CSI includes a first portion and a second portion. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 7 The encoding component 730 described above is performed.

[0194] At 1525, the method may include sending an uplink shared channel message with the multiplexed UCI and at least some of the ACK feedback and CSI on a CG uplink shared channel associated with the uplink shared channel message. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figure 7 The described uplink shared channel component 735 is performed.

[0195] Fig.16 A flowchart illustrating a method 1600 for supporting multiplexing of CG signaling and feedback with different priorities according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference Figures 1 to 4 as well as Figures 9 to 12 The network entity described herein performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0196] At 1605, the method may include determining that one or more time-frequency resources allocated to the UE for reporting confirmation feedback and CSI overlap with a periodic resource allocation for an uplink shared channel message with an associated UCI having a first priority. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The resource manager 1125 described is executed.

[0197] At 1610, the method may include receiving an uplink shared channel message having UCI multiplexed with at least some of the ACK feedback and the CSI on a CG uplink shared channel associated with the uplink shared channel message. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11 The described uplink shared channel manager 1130 is performed.

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

[0199] Aspect 1: A method for wireless communication at a UE, the method comprising: determining that one or more time-frequency resources allocated to the UE for reporting confirmation feedback and channel state information overlap with a periodic resource allocation for an uplink shared channel message having associated uplink control information, the uplink control information having a first priority type; multiplexing the uplink control information with at least some of the confirmation feedback and channel state information on the uplink shared channel message, the uplink control information being multiplexed using a first coding chain, the first coding chain being designated for multiplexing confirmation feedback of the first priority type with the uplink shared channel message; and sending the uplink shared channel message having the multiplexed uplink control information and at least some of the confirmation feedback and channel state information on a configured granted uplink shared channel associated with the uplink shared channel message.

[0200] Aspect 2: A method according to aspect 1, wherein multiplexing the uplink control information includes: appending the uplink control information to the confirmation feedback of the first priority type in the confirmation feedback codebook, and the confirmation feedback of the first priority type is at least a part of the confirmation feedback multiplexed on the uplink shared channel message.

[0201] Aspect 3: According to the method described in Aspect 2, the method further includes: multiplexing the channel state information on the uplink shared channel message using a combination of a second coding chain and a third coding chain, wherein the confirmation feedback multiplexed on the uplink shared channel message completely includes the confirmation feedback of the first priority type, and wherein the second coding chain and the third coding chain are respectively different from the first coding chain.

[0202] Aspect 4: The method according to aspect 3, wherein multiplexing the channel state information comprises: multiplexing a first part of the channel state information using the second coding chain; and multiplexing a second part of the channel state information using the third coding chain.

[0203] Aspect 5: According to the method described in any one of Aspects 2 to 4, the method further includes: using a second coding chain to multiplex confirmation feedback of a second priority type on the uplink shared channel message, wherein the confirmation feedback multiplexed on the uplink shared channel message includes the confirmation feedback of the first priority type and the confirmation feedback of the second priority type; and using a third coding chain to multiplex the first part of the channel state information on the uplink shared channel message, wherein the channel state information includes the first part and the second part.

[0204] Aspect 6: The method according to aspect 5, wherein the second part of the channel state information is not multiplexed on the uplink shared channel message.

[0205] Aspect 7: The method according to any one of aspects 5 to 6, wherein the first priority type is a higher priority type than the second priority type.

[0206] Aspect 8: The method according to any one of aspects 5 to 6, wherein the second priority type is a higher priority type than the first priority type.

[0207] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: using a second coding chain to multiplex confirmation feedback of a second priority type on the uplink shared channel message, wherein the confirmation feedback multiplexed on the uplink shared channel message completely includes the confirmation feedback of the second priority type; and using a third coding chain to multiplex the first part of the channel state information on the uplink shared channel message, wherein the channel state information includes the first part and the second part.

[0208] Aspect 10: The method according to aspect 9, wherein multiplexing the uplink control information comprises: appending the uplink control information to a dummy confirmation feedback in a confirmation feedback codebook.

[0209] Aspect 11: The method according to any one of aspects 9 to 10, wherein the second part of the channel state information is not multiplexed on the uplink shared channel message.

[0210] Aspect 12: The method according to any one of aspects 9 to 11, wherein the first priority type is a higher priority type than the second priority type.

[0211] Aspect 13: The method according to any one of aspects 9 to 11, wherein the second priority type is a higher priority type than the first priority type.

[0212] Aspect 14: According to the method described in any one of Aspects 1 to 13, the method further includes: using a second coding chain to multiplex the first part of the channel state information on the uplink shared channel message, wherein the channel state information includes the first part and the second part; and using a third coding chain to multiplex the second part of the channel state information on the uplink shared channel message, wherein the uplink control information is multiplexed with the channel state information but not multiplexed with the confirmation feedback.

[0213] Aspect 15: The method according to any one of aspects 1 to 14, wherein the uplink control information includes configuration grant-uplink control information.

[0214] Aspect 16: A method for performing wireless communications at a network entity, the method comprising: determining that one or more time-frequency resources allocated to a UE for reporting confirmation feedback and channel state information overlap with a periodic resource allocation for an uplink shared channel message having associated uplink control information, the uplink control information having a first priority; and receiving the uplink shared channel message having the uplink control information multiplexed with at least some of the confirmation feedback and the channel state information on a configured granted uplink shared channel associated with the uplink shared channel message.

[0215] Aspect 17: A method according to aspect 16, wherein the uplink control information is encoded using at least a portion of the confirmation feedback at least in part based on the portion of the confirmation feedback having the same priority type as the uplink control information.

[0216] Aspect 18: A method according to any one of aspects 16 to 17, wherein the uplink control information comprises configuration grant-uplink control information.

[0217] Aspect 19: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 15.

[0218] Aspect 20: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 15.

[0219] Aspect 21: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0220] Aspect 22: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 16 to 18.

[0221] Aspect 23: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one means for performing the method according to any one of aspects 16 to 18.

[0222] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 16 to 18.

[0223] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0224] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to 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 other systems and radio technologies not explicitly mentioned herein, including future systems and radio technologies.

[0225] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0226] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, GPU, 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 in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0227] The functions described herein can be implemented in the form of hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, or functions, whether it is described in software, firmware, middleware, microcode, hardware description language, or other terms. When implemented in software executed by a processor, the function can be stored on a computer-readable medium as one or more instructions or codes, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software, firmware, hard wiring, or any combination thereof executed by a processor. The features that implement the functions can also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0228] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer-readable medium may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change memory, compact disk (CD) ROM or other optical disk storage device, disk storage device or other magnetic storage device, or can be used to carry or store instruction or data structure form of desired program code means and can be accessed by general or special-purpose computer or general or special-purpose processor any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0229] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items can be employed individually, or any combination of two or more of the listed items can be employed. For example, if a composition is described as comprising components A, B, and / or C, the composition can comprise A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.

[0230] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0231] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0232] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The detailed description includes specific details for 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.

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

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: determining that one or more time-frequency resources allocated to the UE for reporting acknowledgment feedback and channel state information overlap with a periodic resource allocation for an uplink shared channel message including associated uplink control information, the uplink control information having a first priority type; multiplexing the uplink control information with at least some of the acknowledgment feedback and channel state information on the uplink shared channel message, the uplink control information being multiplexed using a first coding chain, the first coding chain being designated for multiplexing acknowledgment feedback of the first priority type with the uplink shared channel message; as well as The uplink shared channel message with the multiplexed uplink control information and the at least some of the acknowledgment feedback and channel state information is sent on a configuration grant uplink shared channel associated with the uplink shared channel message.

2. The method of claim 1, wherein multiplexing the uplink control information comprises: The uplink control information is appended to the confirmation feedback of the first priority type in the confirmation feedback codebook, wherein the confirmation feedback of the first priority type is at least a part of the confirmation feedback multiplexed on the uplink shared channel message.

3. The method according to claim 2, further comprising: The channel state information is multiplexed on the uplink shared channel message using a combination of a second coding chain and a third coding chain, wherein the confirmation feedback multiplexed on the uplink shared channel message completely includes the confirmation feedback of the first priority type, and wherein the second coding chain and the third coding chain are each different from the first coding chain.

4. The method according to claim 3, wherein multiplexing the channel state information comprises: multiplexing a first portion of the channel state information using the second coding chain; as well as A second portion of the channel state information is multiplexed using the third coding chain.

5. The method according to claim 2, further comprising: multiplexing confirmation feedback of a second priority type on the uplink shared channel message using a second coding chain, wherein the confirmation feedback multiplexed on the uplink shared channel message includes the confirmation feedback of the first priority type and the confirmation feedback of the second priority type; as well as The first part of the channel state information is multiplexed on the uplink shared channel message using a third coding chain, wherein the channel state information includes the first part and the second part.

6. The method of claim 5, wherein the second portion of the channel state information is not multiplexed on the uplink shared channel message. The method of claim 5 , wherein the first priority type is a higher priority type than the second priority type. The method of claim 5 , wherein the second priority type is a higher priority type than the first priority type.

9. The method according to claim 1, further comprising: multiplexing confirmation feedback of a second priority type on the uplink shared channel message using a second coding chain, wherein the confirmation feedback multiplexed on the uplink shared channel message completely includes the confirmation feedback of the second priority type; and multiplexing a first part of the channel state information on the uplink shared channel message using a third coding chain, wherein the channel state information includes the first part and the second part.

10. The method of claim 9, wherein multiplexing the uplink control information comprises: The uplink control information is appended to a dummy acknowledgment feedback in an acknowledgment feedback codebook.

11. The method of claim 9, wherein the second portion of the channel state information is not multiplexed on the uplink shared channel message.

12. The method of claim 9, wherein the first priority type is a higher priority type than the second priority type.

13. The method of claim 9, wherein the second priority type is a higher priority type than the first priority type.

14. The method according to claim 1, further comprising: multiplexing a first portion of the channel state information on the uplink shared channel message using a second coding chain, wherein the channel state information includes the first portion and a second portion; as well as The second portion of the channel state information is multiplexed on the uplink shared channel message using a third coding chain, wherein the uplink control information is multiplexed with the channel state information but not with the acknowledgment feedback.

15. The method of claim 1, wherein the uplink control information comprises configuration grant-uplink control information.

16. A method for wireless communication at a network entity, the method comprising: determining that one or more time-frequency resources allocated to a user equipment (UE) for reporting acknowledgement feedback and channel state information overlap with a periodic resource allocation for an uplink shared channel message including associated uplink control information, the uplink control information having a first priority; as well as The uplink shared channel message having the uplink control information multiplexed with at least some of the acknowledgment feedback and the channel state information is received on a configuration grant uplink shared channel associated with the uplink shared channel message.

17. The method of claim 16, wherein the uplink control information is encoded with at least a portion of the acknowledgment feedback based at least in part on the portion of the acknowledgment feedback having a same priority type as the uplink control information.

18. The method of claim 16, wherein the uplink control information comprises configuration grant-uplink control information.

19. An apparatus for wireless communication at a user equipment (UE), the apparatus 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 UE to: determining that one or more time-frequency resources allocated to the UE for reporting acknowledgment feedback and channel state information overlap with a periodic resource allocation for an uplink shared channel message having associated uplink control information, the uplink control information having a first priority type; multiplexing the uplink control information with at least some of the acknowledgment feedback and channel state information on the uplink shared channel message, the uplink control information being multiplexed using a first coding chain, the first coding chain being designated for multiplexing acknowledgment feedback of the first priority type with the uplink shared channel message; as well as The uplink shared channel message with the multiplexed uplink control information and the at least some of the acknowledgment feedback and channel state information is sent on a configuration grant uplink shared channel associated with the uplink shared channel message.

20. The apparatus of claim 19, wherein the instructions for multiplexing the uplink control information are executable by the at least one processor to cause the UE to: The uplink control information is appended to the confirmation feedback of the first priority type in the confirmation feedback codebook, wherein the confirmation feedback of the first priority type is at least a part of the confirmation feedback multiplexed on the uplink shared channel message.

21. The apparatus of claim 20, wherein the instructions are further executable by the at least one processor to cause the UE to: The channel state information is multiplexed on the uplink shared channel message using a combination of a second coding chain and a third coding chain, wherein the confirmation feedback multiplexed on the uplink shared channel message completely includes the confirmation feedback of the first priority type, and wherein the second coding chain and the third coding chain are each different from the first coding chain.

22. The apparatus of claim 21 , wherein the instructions for multiplexing the channel state information are executable by the at least one processor to cause the UE to: multiplexing a first portion of the channel state information using the second coding chain; and A second portion of the channel state information is multiplexed using the third coding chain.

23. The apparatus of claim 20, wherein the instructions are further executable by the at least one processor to cause the UE to: multiplexing confirmation feedback of a second priority type on the uplink shared channel message using a second coding chain, wherein the confirmation feedback multiplexed on the uplink shared channel message includes the confirmation feedback of the first priority type and the confirmation feedback of the second priority type; and The first part of the channel state information is multiplexed on the uplink shared channel message using a third coding chain, wherein the channel state information includes the first part and the second part.

24. The apparatus of claim 23, wherein the second portion of the channel state information is not multiplexed on the uplink shared channel message.

25. The apparatus of claim 23, wherein the first priority type is a higher priority type than the second priority type.

26. The apparatus of claim 23, wherein the second priority type is a higher priority type than the first priority type.

27. The apparatus of claim 19, wherein the instructions are further executable by the at least one processor to cause the UE to: multiplexing confirmation feedback of a second priority type on the uplink shared channel message using a second coding chain, wherein the confirmation feedback multiplexed on the uplink shared channel message completely includes the confirmation feedback of the second priority type; and multiplexing a first part of the channel state information on the uplink shared channel message using a third coding chain, wherein the channel state information includes the first part and the second part.

28. The apparatus of claim 27, wherein the instructions for multiplexing the uplink control information are executable by the at least one processor to cause the UE to: The uplink control information is appended to a dummy acknowledgment feedback in an acknowledgment feedback codebook.

29. The apparatus of claim 19, wherein the instructions are further executable by the at least one processor to cause the UE to: multiplexing a first portion of the channel state information on the uplink shared channel message using a second coding chain, wherein the channel state information includes the first portion and a second portion; and The second portion of the channel state information is multiplexed on the uplink shared channel message using a third coding chain, wherein the uplink control information is multiplexed with the channel state information but not with the acknowledgment feedback.

30. An apparatus for wireless communication at a network entity, the apparatus 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 network entity to: determining that one or more time-frequency resources allocated to a user equipment (UE) for reporting acknowledgement feedback and channel state information overlap with a periodic resource allocation for an uplink shared channel message having associated uplink control information, the uplink control information having a first priority; as well as The uplink shared channel message having the uplink control information multiplexed with at least some of the acknowledgment feedback and the channel state information is received on a configuration grant uplink shared channel associated with the uplink shared channel message.