Management of single-shot HARQ-ACK codebooks along with HARQ-ACK codebooks with set priority levels

Abstract

To provide an apparatus and a method for configuring and managing hybrid automatic repeat request (HARQ)-acknowledgment (ACK) feedback codebooks for use in wireless communication systems.SOLUTION: HARQ-ACK codebooks include priority-based HARQ-ACK codebooks of differing priorities and one-shot HARQ-ACK codebooks. A wireless communication device may be configured to obtain a set of HARQ-ACK codebooks that include priority-based HARQ-ACK codebooks of differing priorities and a separate one-shot HARQ-ACK codebook. The wireless communication device may further be configured to process first and second physical uplink channels on the basis of the priority of the first physical uplink channel and the priority of the second physical uplink channel, where one of the two physical uplink channels includes the one-shot HARQ-ACK codebook, and with the processing performed in combination with the use of the priority-based HARQ-ACK codebooks.SELECTED DRAWING: Figure 18

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims priority to pending non-provisional application No. 17 / 355,070, filed with the U.S. Patent and Trademark Office on June 22, 2021, and provisional application No. 63 / 043,725, filed with the U.S. Patent and Trademark Office on June 24, 2020, and is assigned to the assignee of the present application, and is expressly incorporated herein by reference as if fully set forth below in its entirety and for all applicable purposes.

[0002] The techniques described herein relate generally to wireless communication systems, and more particularly to wireless communication using Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) feedback processing. [Background technology]

[0003] As demand for higher data rates and improved reliability grows, wireless network operators continue to develop mechanisms to maximize throughput and minimize delay. One such mechanism is the Hybrid Automatic Repeat Request (HARQ) process, which may combine both forward error correction (FEC) and automatic repeat request (ARQ) to correct errors in received packets. FEC adds redundancy (parity bits) to the transmitted data to allow a certain amount of incorrectly received bits to be corrected at the receiver. When a packet arrives with more errors than can be corrected using FEC, an ARQ process is initiated to request a retransmission of the packet from the sender.

[0004] Typically, HARQ uses a stop-and-wait (SAW) protocol, where the transmitting entity waits to receive an acknowledgement (ACK) or negative acknowledgement (NACK) from the receiving entity before sending another packet or retransmitting the same packet. Each HARQ process is identified by a unique HARQ process identifier (ID). Summary of the Invention [Means for solving the problem]

[0005] The following presents a summary of one or more aspects of the present disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the disclosure, and is not intended to identify key or critical elements of any or all aspects of the disclosure or to delineate the scope of any or all aspects of the disclosure. Its purpose is to present some concepts of one or more aspects of the disclosure as a prelude to the more detailed description that is presented later.

[0006] In one example, a wireless communication device is provided that includes a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory are configured to: process multiple hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebooks, where the HARQ-ACK codebooks include priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks; and process first and second physical uplink channels based at least in part on a priority of a first uplink channel and a priority of a second uplink channel, where one of the first and second physical uplink channels contains the one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0007] In another example, a method for wireless communications is provided for use by a wireless device in a communications network, the method including: obtaining multiple HARQ-ACK codebooks including a priority-based HARQ-ACK codebook of different priorities and a separate one-shot HARQ-ACK codebook; and processing first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0008] In another example, an apparatus is provided for use in a wireless communication device of a wireless communication network, the apparatus including: means for configuring a plurality of HARQ-ACK codebooks, the HARQ-ACK codebooks including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks; and means for processing first and second physical uplink channels based at least in part on a priority of a first uplink channel and a priority of a second uplink channel, one of the first and second physical uplink channels containing the one-shot HARQ-ACK codebook, the processing being performed in combination with use of the priority-based HARQ-ACK codebook.

[0009] In another example, an article of manufacture for use by a wireless communication device of a wireless communication network is provided, the article including a computer-readable medium having stored thereon instructions executable by one or more processors of the wireless communication device to: configure multiple HARQ-ACK codebooks, the HARQ-ACK codebooks including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks; and process first and second physical uplink channels based at least in part on a priority of the first uplink channel and a priority of the second uplink channel, wherein one of the first and second physical uplink channels contains the one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic diagram of a wireless communication system according to some aspects. [Figure 2] FIG. 1 is a conceptual diagram of an example radio access network in accordance with some aspects. [Figure 3] FIG. 1 illustrates an example frame structure for use within a radio access network, in accordance with some aspects. [Figure 4] FIG. 1 illustrates an example of low-priority and high-priority codebook processing, according to some aspects. [Figure 5] FIG. 1 illustrates an example of deleting or multiplexing overlapping channels, according to some aspects. [Figure 6] 1 is a flowchart illustrating a wireless communication method for use by a wireless communication device to assign priorities to physical uplink (UL) channels, according to some aspects. [Figure 7]10 is a flowchart illustrating another wireless communication method for use by a wireless communication device to assign priorities to physical UL channels, according to some aspects. [Figure 8] 10 is a flowchart illustrating another wireless communication method for use by a wireless communication device to assign priorities to physical UL channels, according to some aspects. [Figure 9] 1 is a flowchart illustrating a wireless communication method for use by a wireless communication device to assign priorities to physical UL channels, according to some aspects. [Figure 10] 1 is a flowchart illustrating a wireless communication method for use by a wireless communication device to multiplex physical UL channels, according to some aspects. [Figure 11] 1 is a flowchart illustrating a wireless communication method for use by a wireless communication device to apply a one-shot HARQ-ACK feedback configuration to two HARQ-ACK codebooks, according to some aspects. [Figure 12] 10 is a flowchart illustrating another wireless communication method for use by a wireless communication device to apply a one-shot HARQ-ACK feedback configuration to a HARQ-ACK codebook, in accordance with some aspects. [Figure 13] 1 is a flowchart illustrating a wireless communication method for use by a wireless communication device to insert NACK values ​​into empty bit positions in a codebook, according to some aspects. [Figure 14] 10 is a flowchart illustrating another wireless communication method for use by a wireless communication device to insert NACK values ​​into empty bit positions in a codebook, in accordance with some aspects. [Figure 15] 1 is a flowchart illustrating a wireless communication method for use by a wireless communication device to configure transport block (TB) level ACK / NACK reporting, according to some aspects. [Figure 16] FIG. 1 is a block diagram illustrating an example of a hardware implementation for a scheduling entity, in accordance with some aspects. [Figure 17] FIG. 1 is a block diagram illustrating an example of a hardware implementation for a scheduled entity, in accordance with some aspects. [Figure 18] 1 is a flowchart illustrating a wireless communication method for use by a wireless communication device when a one-shot HARQ-ACK codebook is used, according to some aspects. [Figure 19] FIG. 1 is a block diagram illustrating an example of a hardware implementation for a base station, in accordance with some aspects. [Figure 20] FIG. 1 is a block diagram illustrating an example of a hardware implementation for a UE, in accordance with some aspects. [Figure 21] 2 is a block diagram illustrating exemplary components of a processor of a UE, in accordance with some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0011] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0012] Although aspects and embodiments are described herein by illustrating several examples, those skilled in the art will understand that additional implementations and use cases may arise in many different configurations and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, embodiments and / or applications may arise via integrated chip embodiments and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). Some examples may or may not be directed to a particular use case or application, but a wide variety of applicability of the described innovations may arise. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and practice of the claimed and described embodiments. For example, transmitting and receiving wireless signals necessarily involves several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) It is contemplated that the innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed deployments, end-user devices, etc., of various sizes, shapes, and configurations.

[0013] Aspects of the present disclosure provide for managing the use and coexistence of multiple hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebooks (e.g., Type 1 or Type 2 codebooks) of different priorities in conjunction with a Type 3 (single-shot) HARQ-ACK codebook within a wireless communication standard, such as the 3rd Generation Partnership Project (3GPP®) New Radio (NR) standard (often referred to as 5G). For example, a wireless communication device (e.g., user equipment (UE)) may be configured to configure multiple HARQ-ACK codebooks. The HARQ-ACK codebooks may include priority-based HARQ-ACK codebooks of different priorities and one-shot HARQ-ACK codebooks. The UE may be further configured to process first and second physical uplink channels while prioritizing the use of the one-shot HARQ-ACK codebook in combination with the use of priority-based HARQ-ACK codebooks of different priorities. Illustrative examples are described herein, and these procedures are performed by a UE (or other scheduled entity) in communication with a base station (such as a gNB or other scheduling entity). The operation of the base station is also illustrated and described, and block diagrams illustrating example base stations (or other scheduling entities) are provided.

[0014] Before describing these and other techniques in detail, an overview of wireless communication systems employing HARQ-ACK feedback is provided. However, it should be noted that the various concepts presented throughout this disclosure may be implemented across a wide range of telecommunications systems, network architectures, and communication standards.

[0015] The various concepts presented throughout this disclosure may be implemented across a wide range of telecommunications systems, network architectures, and communication standards. Referring now to FIG. 1 , various aspects of the present disclosure are illustrated with respect to a wireless communication system 100, by way of illustrative and not limiting example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By virtue of the wireless communication system 100, the UE 106 may be enabled to engage in data communications with an external data network 110, such as, but not limited to, the Internet.

[0016] The RAN 104 may implement any suitable wireless communication technology or technologies for providing radio access to the UEs 106. As one example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) standard, often referred to as 5G. As another example, the RAN 104 may operate in a mix of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, often referred to as LTE. 3GPP refers to this mixed RAN as Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of this disclosure.

[0017] As shown, the RAN 104 includes multiple base stations 108. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from UEs. In different technologies, standards, or contexts, a base station may be variously referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), enhanced service set (ESS), access point (AP), Node B (NB), eNode B (eNB), gNode B (gNB), transmit / receive point (TRP), or some other suitable terminology. In some examples, a base station may include two or more TRPs, which may or may not be collocated. Each TRP may communicate at the same or different carrier frequencies within the same or different frequency bands. In examples where the RAN 104 operates according to both the LTE standard and the 5G NR standard, one of the base stations may be an LTE base station and another may be a 5G NR base station.

[0018] Also shown is a radio access network 104 supporting wireless communication for multiple mobile devices. A mobile device may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or some other suitable terminology. A UE may be a device that provides access to network services to a user.

[0019] Within this document, a "mobile" device does not necessarily have the capability to move and may be stationary. The term mobile device or mobile equipment generally refers to a diverse range of devices and technologies. A UE may include several hardware structural components sized, shaped, and configured to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, and the like, electrically coupled to one another. For example, some non-limiting examples of mobile devices include mobiles, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide range of embedded systems, e.g., those supporting the "Internet of Things" (IoT). In addition, the mobile device may be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multicopter, a quadcopter, a remote control device, a consumer and / or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. In addition, the mobile device may be a home audio, video, and / or multimedia device, an appliance, a vending machine, an intelligent lighting, a home security system, a digital home device or a smart home device, such as a smart meter. In addition, the mobile device may be a smart energy device, a security device, a solar panel or solar array, a city infrastructure device (e.g., a smart grid) that controls power, lighting, water, industrial automation and enterprise devices, a logistics controller, agricultural equipment, etc. Still further, the mobile device may provide support for connected medicine or telemedicine, i.e., remote healthcare.Telehealth devices may include telehealth monitoring devices and telehealth management devices, whose communications may be given preferential treatment or priority access over other types of information, for example, with respect to priority access for the transport of critical service data and / or associated QoS for the transport of critical service data.

[0020] Wireless communications between the RAN 104 and the UEs 106 may be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UEs 106) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to point-to-multipoint transmissions originating at a base station (e.g., base station 108). Another way to describe the scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink may refer to point-to-point transmissions originating from a UE (e.g., UE 106).

[0021] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station 108) allocates resources for communication between some or all devices and equipment within its coverage area or cell. As described further below within this disclosure, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communication, a UE 106, which may be a scheduled entity, may utilize resources allocated by the scheduling entity 108.

[0022] The base station 108 is not the only entity that can function as a scheduling entity. That is, in some examples, a UE can function as a scheduling entity, i.e., a scheduling resource for one or more scheduled entities (e.g., one or more other UEs). As described further below, a UE can communicate directly with other UEs in a peer-to-peer manner and / or in a relay configuration.

[0023] 1 , the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106 (e.g., one or more UEs 106). Generally, the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 (e.g., one or more UEs 106) to the scheduling entity 108. Meanwhile, the scheduled entity 106 (e.g., UE 106) is a node or device that receives downlink control information 114, including, but not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network, such as the scheduling entity 108.

[0024] Additionally, uplink and / or downlink control information and / or traffic information may be transmitted on a waveform that may be time-divided into frames, subframes, slots, and / or symbols. As used herein, a symbol may refer to a unit of time that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexed (OFDM) waveform. A slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame. Within this disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, with each frame consisting of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing a waveform may be utilized, and the various time divisions of the waveform may have any suitable time lengths.

[0025] In general, the base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communications system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnection between each base station 108. Various types of backhaul interfaces may be utilized, such as a direct physical connection, a virtual network, etc., using any suitable transport network.

[0026] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured in accordance with a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured in accordance with 4G evolved packet core (EPC), or any other suitable standard or configuration.

[0027] 2, by way of example and not limitation, a schematic illustration of a RAN 200 is provided. In some examples, the RAN 200 may be the same as the RAN 104 described above and shown in FIG.

[0028] The geographic area covered by the RAN 200 may be divided into cellular regions (cells) that can be uniquely identified by user equipment (UE) based on an identification broadcast from an access point or base station. Figure 2 shows cells 202, 204, 206, and 208, each of which may include one or more sectors (not shown). A sector is a subarea of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified by a single logical identification belonging to that sector. In a sectorized cell, multiple sectors within the cell may be formed by a group of antennas, each antenna responsible for communication with UEs in a portion of the cell.

[0029] Various base station arrangements may be utilized. For example, in FIG. 2, two base stations, base station 210 and base station 212, are shown in cells 202 and 204. A third base station, base station 214, is shown controlling a remote radio head (RRD) 216 in cell 206. That is, the base station may have an integrated antenna or may be connected to the antenna or RRH 216 by a feeder cable. In the example shown, cells 202, 204, and 206 may be referred to as macrocells because base stations 210, 212, and 214 support cells having large sizes. Additionally, base station 218 is shown in cell 208, which may overlap with one or more macrocells. In this example, because base station 218 supports a cell that is relatively small in size, cell 208 may be referred to as a small cell (e.g., a microcell, picocell, femtocell, home base station, home NodeB, home eNodeB, etc.). Cell sizing may be performed according to system design and component constraints.

[0030] It should be understood that the radio access network 200 may include any number of wireless base stations and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. The base stations 210, 212, 214, 218 provide wireless access points to a core network for any number of mobile devices. In some examples, the base stations 210, 212, 214, and / or 218 may be the same as the base station / scheduling entity 108 described above and shown in FIG. 1.

[0031] 2 further includes an unmanned aerial vehicle (UAV) 220, which may be a drone or quadcopter. The UAV 220 may be configured to function as a base station, or more particularly, as a mobile base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of a mobile base station, such as the UAV 220.

[0032] Within the RAN 200, cells may include UEs that may be in communication with one or more sectors of each cell. Additionally, each base station 210, 212, 214, and 218 may be configured to provide an access point to the core network 102 (see FIG. 1) for all UEs within their respective cell. For example, UEs 222 and 224 may be in communication with base station 210, UEs 226 and 228 may be in communication with base station 212, UEs 230 and 232 may be in communication with base station 214 via RRH 216, UE 234 may be in communication with base station 218, and UE 236 may be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as or similar to the UE / scheduled entity 106 described above and shown in FIG. 1. In some examples, the UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, the UAV 220 may operate within the cell 202 by communicating with the base station 210.

[0033] In a further aspect of the RAN 200, sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station. Sidelink communications may be utilized, for example, in device-to-device (D2D), peer-to-peer (P2P), vehicle-to-vehicle (V2V) networks, and / or vehicle-to-everything (V2X) networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communications through a base station. In some examples, the UEs 238, 240, and 242 may each function as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate sidelink signals 237 therebetween without relying on scheduling or control information from a base station. In another example, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may communicate sidelink signals 227 over a direct link (sidelink) without conducting that communication through the base station 212. In this example, the base station 212 may allocate resources to the UEs 226 and 228 for sidelink communication.

[0034] In the RAN 200, the ability of a UE to communicate while moving, regardless of its location, is called mobility. Various physical channels between the UE and the RAN are generally set up, maintained, and released under the control of an Access and Mobility Management Function (AMF, not shown, part of the core network 102 in FIG. 1). In some scenarios, the AMF may include a Security Context Management Function (SCMF) and a Security Anchor Function (SEAF), which performs authentication. The SCMF can manage security contexts, in whole or in part, for both control plane and user plane functionality.

[0035] In some examples, the RAN 200 may enable mobility and handover (i.e., transfer of a UE's connection from one wireless channel to another). For example, during a call with a scheduling entity or at any other time, a UE may monitor various parameters of signals from its serving cell as well as various parameters of neighboring cells. Depending on the quality of the parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may undertake a handoff or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 (shown as a vehicle, although any suitable form of UE may be used) may move from a geographical area corresponding to its serving cell 202 to a geographical area corresponding to a neighboring cell 206. When the signal strength or quality from a neighbor cell 206 exceeds that of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this condition to its serving base station 210. In response, the UE 224 may receive a handover command, and the UE may undergo a handover to the cell 206.

[0036] In order for transmissions over the radio access network 200 to obtain a low block error rate (BLER) while still achieving very high data rates, channel coding may be used. That is, wireless communications may generally utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is broken down into coded code blocks (CBs), and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. Exploiting this redundancy in the coded information message can improve the reliability of the message and allow for the correction of any bit errors that may occur due to noise.

[0037] In the initial 5G NR standard, user data traffic is coded using quasi-cyclic low-density parity-check (LDPC) coding with two different base graphs, one of which is used for large code blocks and / or high coding rates, and the other is used otherwise. Control information and the physical broadcast channel (PBCH) are coded using polar coding based on nested sequences. Puncturing, shortening, and repetition are used for rate matching for at least some of the channels.

[0038] However, those skilled in the art will understand that aspects of the present disclosure may be implemented utilizing any suitable channel codes. Various implementations of the scheduling entity and the scheduled entity may include suitable hardware and capabilities (e.g., encoders, decoders, and / or codecs) for utilizing one or more of the channel codes for wireless communications.

[0039] However, even with the best error correction codes, if the communication channel experiences a very large amount of noise or suffers from deep fades or other problems, the bit error rate may exceed the rate that can be compensated for. Therefore, many wireless communication networks utilize hybrid automatic repeat request (HARQ) schemes to further improve data reliability. In an HARQ algorithm, a transmitting device (e.g., a base station or UE) may retransmit a code block (e.g., encoded using a convolutional code or a block code) if the first transmission is not correctly decoded at the receiving device. To facilitate this process, the transmitted encoded code block may include a cyclic redundancy check (CRC) portion, a checksum, or any other suitable mechanism known to those skilled in the art for determining whether the encoded code block is properly decoded at the receiving device. If the received encoded code block is properly decoded, the receiving device may transmit an acknowledgement (ACK) to inform the transmitting device that no retransmission is necessary. However, if the received encoded code block is not properly decoded, the receiving device may transmit a negative acknowledgement (NACK) to request a retransmission. Generally, a limited number of retransmissions will be performed until the transmission attempt is terminated. Many existing networks limit the HARQ algorithm to four retransmissions, however, any suitable retransmission limit may be utilized in networks within the scope of this disclosure.

[0040] The air interface in the radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR standard provides multiple access for UL transmissions from the UEs 222 and 224 to the base station 210, and multiplexing for DL ​​transmissions from the base station 210 to one or more UEs 222 and 224, utilizing Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP). Additionally, for UL transmissions, the 5G NR standard provides support for Discrete Fourier Transform Spread OFDM (DFT-s-OFDM) with CP (also referred to as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and may be performed using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes. Furthermore, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be performed using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0041] The air interface in the radio access network 200 may further utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link in which both endpoints can communicate with each other in both directions. Full duplex means that both endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint can send information to the other at a time. Half duplex emulation is frequently implemented for wireless links using time division duplexing (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, a channel is dedicated to transmission in one direction, while at other times the channel is dedicated to transmission in the other direction, in which case the direction may change very rapidly, e.g., several times per slot. In wireless links, full duplex channels generally rely on physical separation of the transmitter and receiver and suitable interference cancellation techniques. Full duplex emulation is frequently implemented for wireless links by using frequency division duplexing (FDD) or spatial division duplexing (SDD). In FDD, transmissions in different directions may operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented in an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur in different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full duplex (SBFD), also known as flexible duplex.

[0042] Various aspects of the present disclosure will be described with reference to the OFDM waveform shown generally in Figure 3. Those skilled in the art will understand that various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be understood that the same principles may also be applied to SC-FDMA waveforms.

[0043] 3, an expanded view of an exemplary subframe 302 is shown illustrating an OFDM resource grid. However, as one skilled in the art will readily appreciate, the PHY transmission structure for any particular application may differ from the example described herein depending on any number of factors, where time is horizontal in units of OFDM symbols and frequency is vertical in units of subcarriers.

[0044] The resource grid 304 may be used to roughly represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding number of resource grids 304 may be available for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE, which is 1 subcarrier by 1 symbol, is the smallest individual portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation employed in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or resource block (RB) 308, which includes any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB, such as RB 308, corresponds entirely to a single direction of communication (either transmit or receive for a given device).

[0045] A set of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth part (BWP). A set of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission generally involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Thus, the UE generally uses only a subset of the resource grid 304. In some examples, an RB may be the smallest unit of resource that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme chosen for the air interface, the higher the UE's data rate. RBs may be scheduled by a base station (e.g., gNB, eNB, etc.) or may be self-scheduled by a UE implementing D2D sidelink communication.

[0046] In this figure, the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302, with several subcarriers shown above and below the RB 308. In a given implementation, the subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, while in this figure the RB 308 is shown as occupying less than the entire duration of the subframe 302, this is just one possible example.

[0047] Each 1 ms subframe 302 may consist of one or more adjacent slots. In the example shown in FIG. 3, one subframe 302 includes four slots 310 as an illustrative example. In some examples, a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include minislots, sometimes referred to as shortened transmission time intervals (TTIs), which have a shorter duration (e.g., 1 to 3 OFDM symbols). Minislots or shortened transmission time intervals (TTIs) may be transmitted occupying resources scheduled for an ongoing slot transmission for the same or a different UE, as the case may be. Any number of resource blocks may be utilized within a subframe or slot.

[0048] An expanded view of one of the slots 310 shows the slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry a control channel, and the data region 314 may carry a data channel. Of course, a slot may include all DL, all UL, or at least one DL portion and at least one UL portion. The structure shown in FIG. 3 is merely exemplary in nature, and different slot structures may be utilized and may include one or more of each of the control and data regions.

[0049] 3, various REs 306 within the RB 308 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 306 within the RB 308 may also carry pilot or reference signals. These pilot or reference signals may enable a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control channel and / or data channel within the RB 308.

[0050] In some examples, slot 310 may be utilized for broadcast or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to a point-to-multipoint transmission by one device (e.g., a base station, UE, or other similar device) to other devices, where a broadcast communication is delivered to all devices, while a multicast communication is delivered to multiple intended receiving devices. Unicast communications may refer to a point-to-point transmission by one device to a single other device.

[0051] In one example of cellular communication over a cellular carrier over a Uu interface, for DL ​​transmissions, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., in the control region 312) to one or more scheduled entities (e.g., UEs) for carrying DL control information, including one or more DL control channels, such as a physical downlink control channel (PDCCH). The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or allocation of REs for DL ​​and UL transmissions. The PDCCH may further carry HARQ feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those skilled in the art, and the integrity of a packet transmission may be checked at the receiving end for accuracy using any suitable integrity checking mechanism, such as, for example, a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, otherwise a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.

[0052] The base station may further allocate one or more REs 306 (e.g., in the control region 312 or the data region 314) to carry other DL signals such as a demodulation reference signal (DMRS), a phase tracking reference signal (PT-RS), a channel state information (CSI) reference signal (CSI-RS), and a synchronization signal block (SSB). The SSBs may be broadcast at regular intervals based on a periodicity (e.g., 5, 10, 20, 40, 80, or 160 ms). The SSBs include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell ID (PCI) of the cell.

[0053] The PBCH in the SSB may further include a Master Information Block (MIB) containing various system information along with parameters for decoding the System Information Block (SIB). For example, the SIB may be System Information Type 1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink numerology), system frame number, PDCCH Control Resource Set (CORESET) configuration (e.g., PDCCH CORESET0), cell barred indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also transmit other system information (OSI).

[0054] For UL transmissions, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to convey UL control information (UCI) to a scheduling entity, including one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding an uplink data transmission. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request for the scheduling entity to schedule an uplink transmission. Here, in response to the SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI), which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF), such as a CSI report, or any other suitable UCI.

[0055] In addition to control information, one or more REs 306 (e.g., in the data region 314) may be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as a Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions or a Physical Uplink Shared Channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 in the data region 314 may be configured to carry other signals, such as one or more SIBs and a DMRS.

[0056] In the example of sidelink communication on a sidelink carrier via a PC5 interface, the control field 312 of the slot 310 may include a physical sidelink control channel (PSCCH) containing sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a V2X or other sidelink device) toward a set of one or more other receiving sidelink devices. The data field 314 of the slot 310 may include a physical sidelink shared channel (PSSCH) containing sidelink data traffic transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier by the transmitting sidelink device via the SCI. Other information may also be transmitted on various REs 306 within the slot 310. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device within a physical sidelink feedback channel (PSFCH) within the slot 310. Additionally, one or more reference signals, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS), may be transmitted within the slot 310.

[0057] The physical channels described above are generally multiplexed and mapped to transport channels for handling at the Medium Access Control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBs), which may correspond to the number of bits of information, may be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0058] Those skilled in the art will recognize that the channels or carriers described above in connection with Figures 1-3 are not necessarily all of the channels or carriers that may be utilized between a scheduling entity and a scheduled entity, and that other channels or carriers, such as other traffic channels, control channels, and feedback channels, may be utilized in addition to those illustrated.

[0059] Turning now to HARQ-ACK feedback, in at least some wireless communication standards, such as Release 16 of 3GPP NR, a UE may be configured with multiple (up to two) priority-based HARQ-ACK codebooks with associated priorities. The term priority-based is used herein to distinguish these codebooks from one-shot codebooks, described in more detail below, which contain HARQ-ACK feedback for all HARQ processes regardless of priority and therefore may not be directly priority-based. Each codebook contains information bits for encoding or indicating a particular HARQ acknowledgment; for example, a codebook is a particular bit string. A UE may be configured with up to two HARQ-ACK codebooks via a radio resource control (RRC) parameter, pdsch-HARQ-ACK-CodebookList. References herein to parameters such as pdsch-HARQ-ACK-CodebookList refer to parameters defined in 3GPP TS 38.213, Release 16, and related documents. The codebook types may be the same or different for the configured HARQ-ACK codebooks, for example, one may be Type 1 (semi-static) and the other Type 2 (dynamic), or both may be Type 2, etc.

[0060] The priority indicator field in the DCI (DL DCI format 1_1 or 1_2) indicates which codebook should be used to report the HARQ-ACK corresponding to the PDSCH scheduled by the DCI. If no priority is provided (e.g., the priority field is not configured for the DCI or DCI format 1_0 is used), the system takes priority 0 (lower priority). For HARQ-ACK corresponding to semi-persistent scheduling (SPS), the priority is RRC configured as part of the SPS configuration. PUCCH resources for HARQ-ACK codebooks are configured separately, and the PUCCH resource indicator (PRI) field in the DCI with a given priority indicates one PUCCH resource among the corresponding PUCCH resources. Further information on physical layer procedures for control can be found in 3GPP TS 38.213, Release 16, Physical Layer Procedures for Control.

[0061] 4 illustrates, at a high level, the separate processing of low-priority and high-priority codebooks in accordance with some aspects. Briefly, for a low-priority example 400 (e.g., priority=0), a first DCI 402 schedules a PDSCH 404, which is associated with a first HARQ-ACK codebook 406 of the PUCCH. In the low-priority example 400, a second DCI 408 schedules a PDSCH 410, which is also associated with the first HARQ-ACK codebook 406. For a high-priority example 412 (e.g., priority=1), a third DCI 414 schedules a PDSCH 416, which is associated with a second, different HARQ-ACK codebook 418 of the PUCCH.

[0062] As far as the elimination of overlapping physical channels is concerned, in Release 16, if two different UL channels with different priorities overlap in time, the lower priority channel is eliminated and the higher priority channel is transmitted. If the channels have the same priority, the UE multiplexes a PUCCH with another PUCCH or multiplexes a PUCCH with a PUSCH. If the channels have different priorities, the lower priority channel is eliminated. A high priority UL channel can be a PUCCH with HARQ-ACK or a PUCCH with SR, or a PUSCH (dynamic or configured grant). A low priority channel can be a PUCCH with HARQ-ACK, a PUCCH with SR, a PUCCH with CSI, or a PUSCH (dynamic or configured grant). As far as priority indication is concerned, for a PUCCH with HARQ-ACK, the priority can be specified as described above via DCI. For a PUCCH with SR, the priority is specified in the RRC configuration. For PUCCH with CSI, a low priority is assigned (e.g., there is no high priority in that particular case). For dynamic PUSCH, the priority is given in the DCI scheduling PUSCH (DCI formats 0_1, 0_2). For configuration grant PUSCH, the priority is given in the RRC as part of the CG configuration.

[0063] 5 illustrates an example 500 of deleting or multiplexing 502 overlapping channels according to some aspects. In the deletion case 500, a low priority PUCCH / PUSCH 504 is deleted if it overlaps in time with a high priority PUCCH / PUSCH 506. In the multiplexing case 502, a PUCCH 508 is time multiplexed with a PUCCH / PUSCH 510 if the PUCCH 508 and the PUCCH / PUSCH 510 overlap in time and have the same priority.

[0064] Turning now to the "one-shot" (or Type 3) codebook in Release 16, one-shot HARQ-ACK feedback allows the gNB to request feedback of HARQ-ACK codebooks for all configured DL HARQ processes for all configured component carriers (CCs) configured for the UE. One-shot feedback may be configurable with a semi-static codebook, a non-enhanced dynamic HARQ codebook, and an enhanced dynamic codebook. Both non-enhanced and enhanced dynamic codebooks are generally referred to herein as dynamic codebooks. If the UE is provided with pdsch-HARQ-ACK-OneShotFeedback, the codebook is configured in RRC. If the UE is triggered to report both one-shot and other semi-static or dynamic HARQ-ACK feedback in the same slot, the UE reports only one-shot feedback under Release 16. Essentially, one-shot feedback "replaces" whatever was originally requested to be reported. The request is carried within DCI 1_1. That is, when the UE is provided with pdsch-HARQ-ACK-OneShotFeedback, one bit in DCI 1_1 (the "One-Shot HARQ-ACK Request" field) is set. The UE determines the PUCCH, PUCCH resource indicator (PRI), and transmit power control (TPC) for one-shot HARQ-ACK feedback from K1, where K1 is the offset between the DL slot where data is scheduled on the PDSCH and the UL slot where ACK / NACK feedback for the scheduled PDSCH data needs to be sent. According to the procedures of the Release 15 3GPP NR standard, the feedback can be piggybacked on the PUSCH. Note that the DL DCI can either schedule the PDSCH or not. For example, a value of 1 in the frequency domain resource allocation field indicates that the DCI cannot schedule the PDSCH.Otherwise, the DCI schedules the PDSCH and simultaneously requests one-shot feedback for all HARQ processes.

[0065] Under Release 16, a new data indicator (NDI) may be configured to be part of the one-shot HARQ feedback. NDI is transmitted within the DCI and is utilized to indicate the first transmission of a transport block. When NDI is configured, the latest NDI value detected by the UE is reported along with the HARQ-ACK for the corresponding HARQ process ID. If there is no previous NDI value for the HARQ process, the UE assumes NDI=0. When NDI is not configured, no NDI value is reported along with the HARQ-ACK for the corresponding PDSCH. The UE is expected to reset the HARQ-ACK state (such as discontinuous transmission (DTX) or NACK) for a HARQ process ID when feedback is reported for the same HARQ process ID in the previous feedback. For higher HARQ efficiency, when a transport block (TB) contains multiple code blocks, the code blocks may be grouped into a code block group (CBG). The CBG-based HARQ-ACK or the TB-based HARQ-ACK may be configured to be part of the one-shot HARQ feedback for a CC configured with a CBG.

[0066] In the following, various techniques are described that allow combining features of (a) a priority-based HARQ-ACK codebook corresponding to two different priorities (e.g., UL channels with lower priority can be dropped in case of collision, or UL channels are multiplexed in case of equal priority) and (b) a one-shot (Type 3) HARQ-ACK codebook. As mentioned above, the one-shot codebook contains HARQ-ACKs for all HARQ processes, and priorities are typically not distinguished. The following techniques also provide for setting priorities for physical UL channels, such as the PUCCH, and selectively dropping overlapping channels (e.g., in an environment where one channel has a higher priority) or selectively multiplexing overlapping channels (e.g., in an environment where channels have equal priority).

[0067] FIG. 6 is a flowchart illustrating an example process 600 that may be performed by a UE or other scheduled entity to assign priorities to physical uplink (UL) channels, according to some aspects. Briefly, in this example, the priority of a physical UL channel with one-shot HARQ-ACK feedback is fixed at high priority, regardless of the DCI / priority indicator field in the DCI that triggered the physical UL channel with one-shot feedback. The high priority is used, at least in part, because one-shot feedback is a fallback mechanism. Thus, when one-shot feedback is required, one-shot feedback must be reported. In block 602, the UE determines a priority for a first physical UL channel, such as a PUCCH. In block 604, the UE receives a DCI that triggers a second physical UL channel that requests the use of a one-shot HARQ-ACK codebook. In block 606, the UE assigns high priority to the second physical UL channel that requests the use of a one-shot HARQ-ACK codebook, regardless of the priority indicator field in the DCI that triggered the second physical UL channel. In block 608, the UE either drops the first physical UL channel if the first physical UL channel has a low priority (because the second physical UL channel has a high priority) or multiplexes the first and second UL channels if the first and second UL channels have high priority.

[0068] FIG. 7 is a flowchart illustrating an example process 700 that may be performed by a UE or other scheduled entity to assign priorities to physical UL channels, according to some aspects. In this example, if the DCI that requested one-shot feedback includes a priority indicator field, the priority is set by the field. Otherwise, the priority is assumed to be high (or, in other examples, it is assumed to be low, depending on the system-wide configuration). Similar to the procedure of FIG. 6, the UE determines a priority for a first physical UL channel (block 702). The UE then receives a DCI that triggers a second physical UL channel requesting the use of a one-shot HARQ-ACK feedback codebook (block 704). In block 706, the UE determines whether the DCI includes an indication of priority. If a priority is indicated in the DCI, the UE proceeds to decision block 708, and in block 710, the UE assigns a priority to the second physical UL channel based on the indicated priority. For example, if the indicated priority is high, a high priority is assigned to the second physical UL channel. If the indicated priority is low, a low priority is assigned to the second physical UL channel. On the other hand, if a priority is not indicated in the DCI that triggered the second physical UL channel, processing instead proceeds to block 712, where the UE assigns a priority to the second physical UL channel by assuming either a high priority or a low priority (e.g., based on a predetermined system configuration). For example, if an overall standard (which specifies the behavior of the UE and other components in a wireless communication system) indicates that a high priority should be taken in this scenario, the second physical UL channel is assigned a high priority. Conversely, if an overall standard (e.g., a 3GPP New Radio standard or specification) indicates that a low priority should be taken in this scenario, the second physical UL channel is assigned a low priority.

[0069] Thereafter, in block 714, the UE either drops the first UL channel if the first UL channel has a lower priority compared to the second UL channel, or drops the second UL channel if the second UL channel has a lower priority compared to the first UL channel, or multiplexes the first and second UL channels if the first and second UL channels have equal priority (e.g., both high or both low).

[0070] FIG. 8 is a flowchart illustrating an example process 800 that may be performed by a UE or other scheduled entity for assigning priorities to physical UL channels, according to some aspects. In this example, two or more (plural) DCIs indicate the same physical UL channel and request one-shot HARQ-ACK feedback. The multiple DCIs also include a priority indicator. In one particular example, the priority indicator field of the most recent DCI is used, regardless of whether an earlier DCI indicates the same or a different priority. In another example, if the multiple DCIs indicate different priorities (e.g., at least one indicates a low priority while at least one indicates a high priority), the high priority is assumed. Similar to the procedures of FIGS. 6 and 7, the UE determines a priority for a first physical UL channel (block 802). The UE then receives a DCI triggering a second physical UL channel that requests the use of a one-shot HARQ-ACK feedback codebook (block 804).

[0071] In block 806, the UE receives at least one additional DCI (e.g., a second DCI) requesting the use of a one-shot HARQ-ACK codebook for the second physical UL channel. In block 808, the UE assigns a priority to the second UL channel based on (a) the priority indicated in the most recent DCI, or (b) as a high priority if the DCIs have different priorities. As an example of (a), if the most recent DCI requesting one-shot HARQ-ACK feedback for the second physical UL channel indicates a low priority, a low priority is assigned regardless of the priority of the DCI received in block 804. Conversely, if the most recent DCI indicates a high priority, a high priority is again assigned regardless of the priority of the DCI received in block 804. As an example of (b), if the most recent DCI requesting one-shot HARQ-ACK feedback for the second physical UL channel indicates a low priority, but the DCI received in block 804 indicates a high priority, a high priority is assigned. According to example (b), high priority is assigned as long as at least one DCI has high priority. Low priority is assigned only in the example where all DCIs requesting one-shot HARQ-ACK feedback for the second physical UL channel indicate low priority.

[0072] Thereafter, in block 810, the UE either drops the first UL channel if the first UL channel has a lower priority compared to the second UL channel, or drops the second UL channel if the second UL channel has a lower priority compared to the first UL channel, or multiplexes the first and second UL channels if the first and second UL channels have equal priority (e.g., both high or both low). Whether option (a) or option (b) is used depends, for example, on the applicable wireless communications standard that specifies the operation of the UE and other components in the wireless communications system.

[0073] 9 is a flowchart illustrating an example process 900 that may be performed by a UE or other scheduled entity for assigning priorities to physical UL channels, according to some aspects. In this example, if at least one reported HARQ-ACK bit for a given HARQ process corresponding to a PDSCH scheduled by a DCI has a priority indicator field set to 1 (high priority), then the second physical UL channel (e.g., a PUCCH triggered by a DCI requesting the use of a one-shot HARQ-ACK feedback codebook) is assigned high priority. Otherwise, if all PDSCHs for which HARQ-ACKs are reported in the PUCCH are scheduled by DCIs with priority indicator fields set to 0, then the PUCCH is assigned low priority.

[0074] Similar to the procedure described above, the UE determines a priority for a first physical UL channel (block 902). The UE then receives a DCI triggering a second physical UL channel requesting the use of a one-shot HARQ-ACK feedback codebook (block 904). In block 906, the UE determines whether at least one reported HARQ-ACK bit in the one-shot HARQ-ACK codebook for a given HARQ process corresponding to the PDSCH scheduled by the DCI has a priority indicator set to high priority. If so, a high priority is assigned to the second physical UL channel; otherwise, a low priority is assigned to the second physical UL channel. Thereafter, in block 908, the UE, as previously described, drops the first UL channel if it has a lower priority compared to the second UL channel, drops the second UL channel if it has a lower priority compared to the first UL channel, or multiplexes the first and second UL channels if they have equal priority (e.g., both high or both low).

[0075] 10 is a flowchart illustrating an example process 1000 that may be performed by a UE or other scheduled entity for multiplexing physical UL channels, according to some aspects. In this example, if a PUCCH with one-shot feedback has a high priority, the PUCCH is multiplexed with a low-priority PUSCH (assuming time overlap). That is, rather than eliminating the low-priority PUSCH, the low-priority PUSCH is multiplexed with the high-priority PUSCH. This may be particularly useful because the payload of a one-shot HARQ-ACK is large and the PUSCH may have more available resources. If a PUCCH with one-shot feedback has a low priority, the PUCCH may be multiplexed with a high-priority PUSCH (assuming time overlap). That is, rather than eliminating the low-priority PUSCH, the low-priority PUSCH is multiplexed with the PUSCH of the higher priority. This may be useful because the one-shot feedback includes HARQ-ACKs for all HARQ processes, some of which may be associated with high priority Ultra Reliable Low Latency Communication (URLLC).

[0076] Starting at block 1002 of FIG. 10, the UE determines a priority for a PUCCH with one-shot HARQ-ACK feedback. In block 1004, the UE determines a priority for a PUSCH that overlaps in time with the PUCCH. In block 1006, the UE multiplexes the PUCCH with the overlapping PUSCH if the PUCCH has a high priority and the PUSCH has a low priority. In block 1008, the UE multiplexes the PUCCH with the overlapping PUSCH if the PUCCH has a low priority and the PUSCH has a high priority. Alternatively, although not shown in FIG. 10, the PUCCH and PUSCH may be multiplexed in the same manner if they are of equal priority. (FIG. 10 focuses on a scenario in which UL channels of unequal priority are multiplexed.)

[0077] 11 is a flowchart illustrating an example process 1100 that may be performed by a UE or other scheduled entity to apply one-shot HARQ-ACK feedback configuration to two HARQ-ACK codebooks, according to some aspects. In this example, the UE is provided with two HARQ-ACK codebooks via RRC using pdsch-HARQ-ACK-CodebookList. In particular, in this example, if configured, pdsch-HARQ-ACK-OneShotFeedback applies to both HARQ-ACK codebooks for two priorities. That is, one-shot feedback is configured for either both or neither. For example, semi-static + one-shot feedback is configured for a first priority, and dynamic + one-shot feedback is configured for a second priority.

[0078] Starting at block 1102 of Figure 11, the UE configures, receives, or obtains first and second HARQ-ACK codebooks via RRC (e.g., via pdsch-HARQ-ACK-CodebookList). In block 1104, the UE applies a one-shot HARQ-ACK feedback configuration (e.g., via pdsch-HARQ-ACK-OneShotFeedback) to both the first and second HARQ-ACK codebooks. Thereafter, although not shown in Figure 11, processing may proceed to prioritize overlapping physical UL channels and then eliminate or multiplex the overlapping channels, as previously described.

[0079] FIG. 12 is a flowchart illustrating an example process 1200 that may be performed by a UE or other scheduled entity to apply a one-shot HARQ-ACK feedback configuration to one HARQ-ACK codebook, according to some aspects. The example procedure 1200 may be employed when the UE is provided with two HARQ-ACK codebooks via RRC using pdsch-HARQ-ACK-CodebookList. However, in this example, one-shot feedback is configured separately for two different priorities. In particular, in this example, pdsch-HARQ-ACK-OneShotFeedback is configured separately. For example, dynamic only (no one-shot feedback) is configured for the first priority, and dynamic+one-shot is configured for the second priority. If one-shot feedback is configured for only one of the priorities, the DCI field—One-Shot HARQ-ACK Request—is set to 0 if the priority indicator field in the DCI indicates the other priority.

[0080] Starting at block 1202 of FIG. 12, the UE configures, receives, or obtains first and second HARQ-ACK codebooks via RRC (e.g., via pdsch-HARQ-ACK-CodebookList). In block 1204, the UE applies a first HARQ-ACK feedback configuration to the first HARQ-ACK codebook, where in some examples the first HARQ-ACK is configured for one-shot HARQ-ACK feedback (e.g., via pdsch-HARQ-ACK-OneShotFeedback) and in other examples it is not configured for one-shot HARQ-ACK feedback. In block 1206, the UE applies a second HARQ-ACK feedback configuration to the second HARQ-ACK codebook, where in some examples the second HARQ-ACK is configured for one-shot HARQ-ACK feedback and in other examples it is not configured for one-shot HARQ-ACK feedback. In block 1208, if one-shot feedback is configured for only one of the priorities, the DCI field - One-Shot HARQ-ACK Request - is set to 0 if the priority indicator field in the DCI indicates the other priority. In other words, if one-shot HARQ-ACK feedback is configured for the first priority but not the second, the DCI with the priority indicator field set to the second priority value will include a one-shot HARQ-ACK request field set to zero.

[0081] Next, focusing on the CBG, the UE (e.g.,

[0082]

number

[0083] The maximum number of CBGs per TB may be configured in a component carrier (CC) / serving cell (by the parameter codeBlockGroupTransmission, which includes the parameter maxCodeBlockGroupsPerTransportBlock, which may be set to 2, 4, 6 or 8 as the maximum number of CBGs per TB, denoted by If so, the UE reports a CBG-based HARQ-ACK (with one bit A / N for each CBG for a given TB). A one-shot (Type 3) codebook may be configured to report a CBG-based HARQ-ACK (e.g., if the RRC parameter pdsch-HARQ-ACK-OneShotFeedbackCBG-r16 is enabled). In the case of two HARQ-ACK codebooks, two different maximum numbers of CBGs per TB are allowed (e.g., by the RRC parameter pdsch-CodeBlockGroupTransmissionList-r16), with two priorities.

[0084]

number

[0085] and

[0086]

number

[0087] It is configured corresponding to: However, for one-shot (Type 3), feedback for all HARQ-IDs is reported within Release 16, regardless of priority as mentioned above. Therefore, a question may arise regarding what maximum number of CBGs per TB to use.

[0088] In the first CBG-based one-shot HARQ-ACK example, the maximum number of CBGs per TB to use is determined as follows:

[0089]

number

[0090] and

[0091]

number

[0092] ), and the UE is configured to report CBG-based HARQ-ACK in the one-shot feedback report, when the UE is requested by DCI to report one-shot feedback, the maximum of the two numbers is selected. That is, the number of HARQ-ACK bits for each TB of the number of HARQ processes for that CC in the one-shot feedback is max{

[0093]

number

[0094] ,

[0095]

number

[0096] In this case, if the actual number of CBGs for a given TB of an HARQ process in a CC is less than the number determined above, the UE generates a NACK for each of the last remaining positions in the codebook.

[0097] 13 is a flowchart illustrating an example process 1300 that may be performed by a UE or other scheduled entity to insert NACK values ​​into empty bit positions in a codebook, according to some aspects. Beginning at block 1302 of procedure 1300, the UE determines first and second maximum numbers of CBGs per TB for first and second priorities for a particular CC, e.g., (

[0098]

number

[0099] and

[0100]

number

[0101] In block 1304, the UE determines whether it has requested to report using one-shot HARQ-ACK feedback. If so, the UE configures, receives, or obtains the larger of the number of HARQ-ACK bits configured for the first priority and the number of HARQ-ACK bits configured for the second priority, e.g., max{

[0102]

number

[0103] ,

[0104]

number

[0105] } bits, set the number of HARQ-ACK bits for each TB for the HARQ process for a particular CC.

[0106] In the second CBG-based one-shot HARQ-ACK example, the maximum number of CBGs per TB to use is determined as follows: The priority indicator field of the DCI requesting one-shot feedback determines the maximum number of CBGs and the number of HARQ-ACK bits for each TB of the number of HARQ processes for that CC in the one-shot feedback. This option again applies when the UE is given two maximum numbers of CBGs per TB in a given CC corresponding to two different priorities, the UE is configured to report CBG-based HARQ-ACK in the one-shot feedback report, and the UE is requested by the DCI to report one-shot feedback. As an example, if the priority indicator field is 0, the first maximum number of CBGs is used, and if the priority indicator field is 1, the second maximum number of CBGs is used. If a TB is initially scheduled with a number of CBGs greater than the maximum number of CBGs determined for the purposes of one-shot (Type 3) HARQ-ACK, the UE generates HARQ-ACK bits for new CBGs that include two or more original CBGs by applying a binary AND operation to the HARQ-ACK information bits corresponding to the original CBGs. (Binary AND yields 0 AND 0 → 0, 0 AND 1 → 0, 1 AND 0 → 0, and 1 AND 1 → 1.)

[0107] 14 is a flowchart illustrating an example process 1400 that may be performed by a UE or other scheduled entity to insert NACK values ​​into empty bit positions in a codebook, according to some aspects. Beginning at block 1402 of procedure 1400, the UE configures, receives, or obtains first and second maximum numbers of CBGs per TB for first and second priorities for a particular component carrier CC. Here, a priority indicator field of a DCI requesting one-shot HARQ-ACK feedback determines the maximum number of CBGs and the number of HARQ-ACK bits for each TB of the number of HARQ processes for that particular CC in the one-shot feedback. At block 1404, if the priority indicator field of the DCI is set to indicate the first priority, the UE uses or selects the first maximum number of CBGs, and if the priority indicator field of the DCI is set to indicate the second priority, the UE uses or possibly selects the second maximum number of CBGs. In block 1406, if the TB was originally scheduled with a number of CBGs greater than either the first or second maximum number of CBGs, the UE generates HARQ-ACK bits for a new CBG that includes two or more original CBGs, where the HARQ-ACK bits are generated by applying a binary AND operation to the HARQ-ACK bits corresponding to the original CBGs.

[0108] In a third CBG-based one-shot HARQ-ACK example, if the maximum number of CBGs for the two priorities are different or only one of the priorities is CBG-based, the UE would only expect to be configured with TB-level A / N reporting for one-shot (e.g., the UE would not expect to be configured with CBG-based feedback for one-shot feedback). In this example, the UE would be configured with TB-level ACK / NACK reporting for one-shot feedback without using CBG-based feedback for one-shot feedback.

[0109] 15 is a flowchart illustrating an example process 1500 that may be performed by a UE or other scheduled entity to configure TB-level ACK / NACK reporting according to some aspects. Beginning at block 1502 of procedure 1500, the UE obtains first and second maximum numbers of CBGs per TB for first and second priorities for a particular CC, or obtains only a single CBG-based priority. At block 1504, the UE determines whether the maximum numbers of CBGs for the two priorities are different, or whether only one is CBG-based. If so (e.g., if the maximum numbers of CBGs for the two priorities are different, or if only one is CBG-based), the UE configures TB-level ACK / NACK reporting for one-shot feedback without using CBG-based feedback for the one-shot feedback.

[0110] FIG. 16 is a block diagram illustrating an example of a hardware implementation for a scheduling entity 1600 employing a processing system 1614 capable of processing HARQ-ACKs, including both priority-based HARQ-ACKs and one-shot HARQ-ACKs, in accordance with some aspects.

[0111] In one example, the scheduling entity 1600 of FIG. 16 may be a base station or gNB shown in any one or more of the other figures (although it may also be a UE).

[0112] The scheduling entity 1600 may be implemented with a processing system 1614 including one or more processors 1604. Examples of processors 1604 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. In various examples, the scheduling entity 1600 may be configured to perform any one or more of the functions described herein. That is, the processor 1604 utilized in the scheduling entity 1600 may be used to implement any one or more of the processes and procedures described elsewhere herein.

[0113] The processor 1604 may, in some cases, be implemented via a baseband chip or a modem chip, while in other implementations, the processor 1604 may include several devices that are separate and distinct from the baseband or modem chip (e.g., in scenarios that may work in cooperation to achieve the examples described herein). As mentioned above, various hardware arrangements and components external to the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0114] In the example of FIG. 16, processing system 1614 may be implemented with a bus architecture, represented generally by bus 1602. Bus 1602 may include any number of interconnected buses and bridges, depending on the particular application and overall design constraints of processing system 1614. Bus 1602 communicatively couples various circuits, including one or more processors (represented generally by processor 1604), memory 1605, and computer-readable media (represented generally by computer-readable media 1606). Bus 1602 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well-known in the art and therefore will not be described further. Bus interface 1608 provides an interface between bus 1602 and transceiver 1610. Transceiver 1610 provides a communication interface or means for communicating with various other devices over a transmission medium. Also, depending on the nature of the device, a user interface 1612 (eg, keypad, display, speaker, microphone, joystick) may be provided.

[0115] In some aspects of the present disclosure, the processor 1604 may include circuitry configured to implement one or more of the base station side functions described elsewhere herein. The processor 1604 may include a priority-based HARQ-ACK processing circuit 1640, a one-shot HARQ-ACK processing circuit 1642, and a UL / DL processing circuit 1644.

[0116] The processor 1604 is responsible for managing the bus 1602 and for general processing, including executing software stored on the computer-readable medium 1606. The software, when executed by the processor 1604, causes the processing system 1614 to perform various functions, described below for any particular apparatus. The computer-readable medium 1606 and memory 1605 may also be used to store data that is manipulated by the processor 1604 when executing software.

[0117] The one or more processors 1604 in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. The software may reside on computer-readable medium 1606. Computer-readable medium 1606 may be a non-transitory computer-readable medium. Non-transitory computer-readable media include, by way of example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable media may also include, by way of example, carrier waves, transmission lines, and any other suitable medium for transmitting software and / or instructions that can be accessed and read by a computer. Computer-readable media 1606 may be within processing system 1614, external to processing system 1614, or distributed across multiple entities, including processing system 1614. The computer-readable medium 1606 may be embodied in a computer program product. By way of example, the computer program product may include the computer-readable medium in packaging materials.Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0118] The computer-readable storage medium 1606 may include software executable by the processor 1604 configured to implement one or more of the functions described elsewhere herein. For example, the computer-readable storage medium 1606 may include code 1652 for priority-based HARQ-ACK processing executable by the priority-based HARQ-ACK processing circuit 1640, code 1654 for one-shot HARQ-ACK processing executable by the one-shot HARQ-ACK processing circuit 1642, and code 1656 for UL / DL processing executable by the UL / DL processing circuit 1644.

[0119] 17 is a block diagram illustrating an example of a hardware implementation for an exemplary scheduled entity 1700 employing a processing system 1714, which may be, for example, a UE. According to various aspects of the disclosure, the elements, or any portion of the elements, or any combination of the elements, may be implemented using a processing system 1714 that includes one or more processors 1704. For example, the scheduled entity 1700 may be a UE as shown in any one or more of the other figures.

[0120] The processing system 1714 may generally be similar to the processing system 1614 shown in FIG. 16 and include the bus interface 1708, bus 1702, memory 1705, processor 1704, computer-readable medium 1706, user interface 1712, and transceiver 1710 (communications interface) similar to those described above; therefore, many of the details of the system architecture will not be described again. The processor 1704 may, in some cases, be implemented via a baseband or modem chip; in other implementations, the processor 1704 may include several devices that are separate and distinct from the baseband or modem chip (e.g., in scenarios that may work in cooperation to achieve the examples described herein). As mentioned above, various hardware arrangements and components external to the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0121] The processor 1704 utilized in the scheduled entity 1700 may be used to implement one or more of the various processes described herein for use by a scheduled entity, such as a UE. In some aspects of the present disclosure, the processor 1704 includes a priority-based HARQ-ACK processing circuit 1740 configured for priority-based HARQ-ACK processing including processing using codebooks of different priorities, a one-shot HARQ-ACK processing circuit 1742 configured for one-shot HARQ-ACK processing including processing one-shot codebooks, and a UL channel priority determination circuit 1744 configured to determine UL channel priorities and to remove or multiplex overlapping channels using the various procedures of Figures 4-16. The processing circuits 1740 and 1742 may include processing circuits configured to obtain and / or configure multiple HARQ-ACK codebooks, including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks according to the various processes shown in Figures 4-16. The circuit 1744 may include processing circuitry configured to process the first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, one of the first and second physical uplink channels including a one-shot HARQ-ACK codebook, and the processing performed in combination with use of the priority-based HARQ-ACK codebook according to various processes shown in Figures 4-16.

[0122] The computer-readable storage medium 1706 may include software executable by the processor 1704 configured to implement one or more of the functions described elsewhere herein. For example, the computer-readable storage medium 1706 may include code 1752 for priority-based HARQ-ACK processing executable by the priority-based HARQ-ACK processing circuit 1740, code 1754 for one-shot-HARQ-ACK processing executable by the one-shot-based HARQ-ACK processing circuit 1742, and code 1756 for determining UL channel priority and for removing or multiplexing overlapping channels executable by the UL channel priority determination circuit 1744 in accordance with the various processes shown in FIGS. 4-16.

[0123] 18 is a flowchart illustrating a wireless communication method 1800 according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some illustrated features may not be necessary for all example implementations. The communication method 1800 may be performed by any of the scheduled entities shown in the figure, such as, for example, a UE, or by other suitably equipped systems, devices, or apparatuses including wireless communication devices.

[0124] At block 1802, the wireless communications device obtains multiple HARQ-ACK codebooks, the multiple HARQ-ACK codebooks including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks. For example, the priority-based HARQ-ACK processing circuit 1640, together with the one-shot HARQ-ACK processing circuit 1642 shown and described above in connection with FIG. 16, may provide means for obtaining the multiple HARQ-ACK codebooks.

[0125] At block 1804, the wireless communications device processes the first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, one of the first and second physical uplink channels including a one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook. For example, the UL / DL processing circuit 1644, along with the priority-based HARQ-ACK processing circuit 1640 and the one-shot HARQ-ACK processing circuit 1642 shown and described above in connection with FIG. 16, may provide means for processing the first and second physical uplink channels.

[0126] In one configuration, an apparatus for wireless communication includes means for performing the methods and processes described above, including the means for communicating described above. In one aspect, the means may be the processor of Figures 16 and 17 configured to perform the functions recited by the means described above. In another aspect, the means may be a circuit or any device configured to perform the functions recited by the means described above.

[0127] FIG. 19 is a block diagram illustrating an example of a hardware implementation for an exemplary base station 1900 (e.g., a gNB or a scheduling entity) employing a processing system 1914. According to various aspects of the present disclosure, elements, or any portion of elements, or any combination of elements, may be implemented using a processing system 1914 including one or more processors 1904. The processing system 1914 may be generally similar to the processing system 1614 shown in FIGS. 16 and 17 and includes a bus interface 1908, a bus 1902, a memory 1905, a processor 1904, a computer-readable medium 1906, a user interface 1912, and a transceiver 1910. The transceiver 1910 provides a communication interface or means for communicating with various other devices over a transmission medium. The transceiver 1910 includes one or more receivers 1911 and one or more transmitters 1913. The receiver 1911 is coupled to a set of antennas 1915. The transceiver 1913 is coupled to the same or different set of antennas 1917. The set of antennas may be used for beamforming. Also, depending on the nature of the device, a user interface 1912 (e.g., keypad, display, speaker, microphone, joystick) may be provided.

[0128] The processor 1904 may, in some cases, be implemented via a baseband chip or a modem chip, while in other implementations, the processor 1904 may include several devices that are separate and distinct from the baseband chip or modem chip (e.g., in scenarios that may work in cooperation to achieve the examples described herein). As mentioned above, various hardware arrangements and components external to the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0129] The processor 1904 utilized within the base station 1900 may be used to implement one or more of the various processes described herein for use by the base station. In some aspects of the present disclosure, the processor 1904 includes a HARQ-ACK codebook management circuit 1940 configured to manage codebooks (e.g., Type 1, Type 2, and One-Shot / Type 3), a physical channel processing circuit 1944, and a DCI processing circuit 1946, the circuits configured to perform functions corresponding to or complementary to various UE-side functions or operations described herein. In this regard, the base station may generate and send signals to configure the UE to provide HARQ feedback for different CORESET groups. Additionally, the base station may configure the UE with one or more codebooks for use to generate one or more feedback messages, such as a priority-based HARQ-ACK codebook (e.g., a dynamic Type 2 HARQ-ACK codebook or a quasi-static Type 1 HARQ-ACK codebook) and / or a one-shot Type 3 HARQ-ACK codebook. The codebooks may be stored in memory 1905.

[0130] The computer-readable storage medium 1906 may include software executable by the processor 1904 configured to implement one or more of the functions described herein. For example, the computer-readable storage medium 1906 may include code 1952 for managing a HARQ-ACK codebook (e.g., Type 1, Type 2, and One-Shot / Type 3) executable by the HARQ-ACK codebook management circuit 1940, code 1956 for physical channel processing executable by the physical channel processing circuit 1944, and code 1958 for DCI processing executable by the DCI processing circuit 1946.

[0131] FIG. 20 is a block diagram illustrating an example of a hardware implementation for an exemplary wireless communication device 2000 (e.g., a UE or a scheduled entity) employing a processing system 2014. According to various aspects of the present disclosure, elements, or any portion of elements, or any combination of elements, may be implemented using a processing system 2014 including one or more processors 2004. The processing system 2014 may be generally similar to the processing system 1614 shown in FIGS. 16-17 and 19 and includes a bus interface 2008, a bus 2002, a memory 2005, a processor 2004, a computer-readable medium 2006, a user interface 2012, and a transceiver 2010. The transceiver 2010 provides a communication interface or means for communicating with various other apparatuses over a transmission medium. The transceiver 2010 includes one or more receivers 2011 and one or more transmitters 2013. The receiver 2011 is coupled to a set of antennas 2015. The transceiver 2013 is coupled to the same or different set of antennas 2017. The set of antennas may be used for beamforming. Also, depending on the nature of the device, a user interface 2012 (e.g., keypad, display, speaker, microphone, joystick) may be provided.

[0132] The processor 2004 may, in some cases, be implemented via a baseband or modem chip, while in other implementations, the processor 2004 may include several devices that are separate and distinct from the baseband or modem chip (e.g., in scenarios that may work in cooperation to achieve the examples described herein). As mentioned above, various hardware arrangements and components external to the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0133] The processor 2004 utilized within the wireless communication device 2000 may be used to implement one or more of the various processes described herein for use by a UE. In some aspects of the present disclosure, the processor 2004 includes a HARQ-ACK codebook reception / management circuit 2040 configured to receive / manage codebooks (e.g., Type 1, Type 2, and one-shot / Type 3), a priority-based physical channel processing circuit 2044, and a DCI processing circuit 2046, the circuits configured to perform functions corresponding to or complementary to various base station side functions or operations described herein. For example, the HARQ-ACK codebook reception / management circuit 2040 provides circuitry configured to obtain multiple HARQ-ACK codebooks, the multiple HARQ-ACK codebooks including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks.

[0134] The computer-readable storage medium 2006 may include software executable by the processor 2014 configured to implement one or more of the functions described herein. For example, the computer-readable storage medium 2006 may include code 2052 for receiving / managing an HARQ-ACK codebook (e.g., Type 1, Type 2, and One-Shot / Type 3) executable by the HARQ-ACK codebook receiving / managing circuit 2040, code 2056 for priority-based physical channel processing executable by the priority-based physical channel processing circuit 2044, and code 2058 for DCI processing executable by the DCI processing circuit 2046. The codebooks may be stored in the memory 2005.

[0135] The HARQ-ACK codebook receiving / managing circuit 2040 may be configured to obtain one or more HARQ-ACK codebooks, including priority-based HARQ-ACK codebooks of different priorities and individual one-shot codebooks. The HARQ-ACK codebook receiving / managing circuit 2040 may be configured to obtain the HARQ-ACK codebook by receiving a codebook from a base station or by generating a codebook based on configuration information provided by the base station and / or from information stored in the UE. Additionally or alternatively, the HARQ-ACK codebook receiving / managing circuit 2040 may be referred to as a HARQ-ACK codebook receiving circuit, an obtaining circuit, a determining circuit, or a configuring circuit. The DCI processing circuit 2046 may be configured to receive DCI from a base station, or to obtain or determine DCI, as the case may be. The DCI processing circuit 2046 may alternatively be referred to as a DCI receiving circuit, an obtaining circuit, a determining circuit, or a configuring circuit.

[0136] The priority-based physical channel processing circuit 2044 may be configured to process the first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, where one of the first and second physical uplink channels includes a one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook. In some examples, the priority-based HARQ-ACK codebook includes one or more of a one-shot HARQ-ACK codebook including a Type 1 quasi-static codebook (having first and second priorities, e.g., high and low), a Type 2 dynamic codebook (having first and second priorities, e.g., high and low), and a Type 3 codebook.

[0137] In some aspects, the HARQ-ACK codebook receiving / managing circuit 2040 provides means for obtaining multiple HARQ-ACK codebooks, the multiple HARQ-ACK codebooks including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks. The priority-based physical channel processing circuit 2044 provides means for processing the first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, one of the first and second physical uplink channels including a one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0138] In some aspects, code for HARQ-ACK codebook reception / management 2052 provides instructions executable by one or more processors of a wireless communication device to obtain multiple HARQ-ACK codebooks, the multiple HARQ-ACK codebooks including a priority-based HARQ-ACK codebook of different priorities and a separate one-shot HARQ-ACK codebook. Priority-based physical channel processing code 2056 provides instructions executable by one or more processors of a wireless communication device to process first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, wherein one of the first and second physical uplink channels includes a one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0139] Additional features of the priority-based physical channel processing circuit 2044 for use with one-shot HARQ-ACK feedback are shown in FIG.

[0140] In some aspects, the priority-based physical channel processing circuit 2044 is configured to process the first and second physical uplink channels (along with one of the channels using one-shot HARQ-ACK feedback) by eliminating one of the first and second physical uplink channels when the first and second physical uplink channels overlap in time based on a respective priority of each of the first and second physical uplink channels, as shown in block 2102 of FIG. 21. That is, circuitry is provided for eliminating one of two physical UL channels when two UL channels overlap in time based on a respective priority of the two physical UL channels (when one of the channels uses one-shot HARQ-ACK feedback). See, e.g., FIGS. 5-10.

[0141] In some aspects, the priority-based physical channel processing circuit 2044 is configured to process the first and second physical uplink channels by multiplexing the first and second physical uplink channels when the first and second physical uplink channels overlap in time and are of equal priority, as shown in block 2104 of Figure 21. See, e.g., Figures 7-8. That is, circuitry is provided for multiplexing two physical UL channels when the two UL channels overlap in time and are of equal priority (when one of the channels uses one-shot feedback).

[0142] In some aspects, at least one of the first and second physical uplink channels includes a PUCCH or a PUSCH. See, e.g., FIG. 4.

[0143] In some aspects, the priority-based physical channel processing circuit 2044 is configured to process the first and second physical uplink channels by determining a priority for the first physical uplink channel, receiving (via the DCI processing circuit 2046) a DCI triggering the second physical uplink channel requesting use of a one-shot HARQ-ACK codebook, assigning a priority to the second physical uplink channel, dropping the first physical uplink channel when the first physical uplink channel has a lower priority compared to the second physical uplink channel, dropping the second physical uplink channel when the second physical uplink channel has a lower priority compared to the first physical uplink channel, and multiplexing the first and second physical uplink channels when the first and second physical uplink channels have equal priority. See, for example, FIG. 6.

[0144] In some aspects, as shown by block 2106 of FIG. 21 , the priority-based physical channel processing circuit 2044 is configured to assign a priority to the second physical uplink channel by assigning a high priority to the second physical uplink channel regardless of a priority indicator field of the DCI. That is, a circuit is provided for assigning a priority to a physical UL channel regardless of the DCI. See, e.g., FIG. 6 . In other aspects, as shown by block 2108 of FIG. 21 , the priority-based physical channel processing circuit 2044 is configured to assign a priority to the second physical uplink channel by determining whether the DCI includes an indication of priority, selecting a priority for the second physical uplink channel based on the DCI in response to the DCI including an indication of priority, or selecting a priority for the second physical uplink channel based on a predetermined priority set to either low or high in response to the DCI not including an indication of priority. That is, a circuit is provided for assigning a priority to a physical UL channel based on a DCI having a priority indicator. See, e.g., FIG. 7 .

[0145] In some aspects, as shown by block 2110 of FIG. 21, the priority-based physical channel processing circuit 2044 is further configured to receive (via the DCI processing circuit 2046) an additional DCI for a second physical uplink channel requesting a one-shot HARQ-ACK codebook and including a priority indicator, and to select a priority for the second physical uplink channel based on the priority indicator of the additional DCI. That is, a circuit is provided for assigning priorities to physical UL channels based on the second or additional DCI having a priority indicator. See, e.g., FIG. 8.

[0146] In other aspects, the priority-based physical channel processing circuit 2044 is further configured to receive an additional DCI requesting a one-shot HARQ-ACK codebook and including a priority indicator different from the indication of priority in the DCI, and to select a priority for the second physical uplink channel by assigning a high priority to the second physical uplink channel. See, e.g., FIG. 8.

[0147] In some aspects, the priority-based physical channel processing circuit 2044 is configured to assign a priority to the second physical uplink channel by setting the priority of the second physical uplink channel to high priority when at least one reported HARQ-ACK bit in the one-shot HARQ-ACK codebook for a given HARQ process corresponding to the PDSCH scheduled by the DCI has a priority indicator field set to high priority, and by setting the priority of the second physical uplink channel to low priority when the priority indicator field is set to low priority. See, e.g., FIG. 9.

[0148] In some aspects, at least one of the first and second physical uplink channels is a PUCCH with a one-shot HARQ-ACK codebook, and the other of the first and second physical uplink channels is a PUSCH that overlaps in time with the PUCCH. In that case, the priority-based physical channel processing circuit 2044 may be configured to process the first and second physical uplink channels by multiplexing the PUCCH with the PUSCH when the PUCCH with the one-shot HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority, and by multiplexing the PUCCH with the PUSCH when the PUCCH with the one-shot HARQ-ACK feedback codebook has a low priority and the PUSCH has a high priority. See, for example, FIG. 10 .

[0149] In some aspects, the HARQ-ACK codebook receiving / managing circuit 2040 is further configured to obtain the first and second HARQ-ACK codebooks via an RRC configuration and to provide one-shot HARQ-ACK feedback via the RRC configuration. In such a case, the priority-based physical channel processing circuit 2044 may be configured to apply the one-shot HARQ-ACK feedback configuration to both the first and second HARQ-ACK codebooks, as shown in block 2112 of FIG. 21. See, e.g., FIGs. 11 and 12.

[0150] In some aspects, the priority-based physical channel processing circuit 2044 may be configured to use first and second maximum numbers of CBGs per TB for the respective first and second priorities for a CC, and if so, the priority-based physical channel processing circuit 2044 is further configured to set the number of HARQ-ACK bits for each TB for the one-shot HARQ feedback process for a particular CC based on the maximum value that is the greater of the number of HARQ-ACK bits configured for the first priority and the number of HARQ-ACK bits configured for the second priority, as represented by block 2114 of FIG. 13-15. See, for example, FIG. 13-15.

[0151] Of course, in the above examples, the circuitry contained within the processors of Figures 16-17 and 18-21 is provided by way of example only, and other means for performing the described functions may be included within various aspects of the disclosure, including, but not limited to, instructions stored on a computer-readable storage medium of Figures 16-17 and 18-21, or any other suitable apparatus or means that utilizes the processes and / or algorithms described in any one of the figures, e.g., as described herein in connection with the figures.

[0152] The following provides a summary of an embodiment of the present disclosure.

[0153] 1. A wireless communications device including: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: obtain a plurality of HARQ-ACK codebooks including a priority-based HARQ-ACK codebook and a separate one-shot HARQ-ACK codebook of different priorities; and process first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and wherein the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0154] Example 2: The wireless communication device of Example 1, wherein the priority-based HARQ-ACK codebook is configured as one or more of a Type 1 quasi-static codebook and a Type 2 dynamic codebook, and the one-shot HARQ-ACK codebook is configured as a Type 3 codebook.

[0155] 3. The wireless communications device of any one of embodiments 1 or 2, wherein the processor is further configured to process the first and second physical uplink channels by removing one of the first and second physical uplink channels when the first and second physical uplink channels overlap in time based on a respective priority of each of the first and second physical uplink channels.

[0156] Example 4: The wireless communication device of Example 1 or 2, wherein the processor is further configured to process the first and second physical uplink channels by multiplexing the first and second physical uplink channels when the first and second physical uplink channels overlap in time and are of equal priority.

[0157] Example 5: The wireless communications device of Example 1, 2, 3, or 4, wherein the first and second physical uplink channels include one or more of a PUCCH and a PUSCH.

[0158] 6. The wireless communications device of any one of embodiments 1 to 5, wherein the processor is further configured to process the first and second physical uplink channels by: determining a priority for the first physical uplink channel; receiving a DCI triggering the second physical uplink channel requesting use of a one-shot HARQ-ACK codebook; assigning a priority to the second physical uplink channel; removing the first physical uplink channel when the first physical uplink channel has a lower priority compared to the second physical uplink channel; removing the second physical uplink channel when the second physical uplink channel has a lower priority compared to the first physical uplink channel; and multiplexing the first and second physical uplink channels when the first and second physical uplink channels have equal priority.

[0159] Example 7: The wireless communications device of Examples 1, 2, 3, 4, 5, or 6, wherein the processor is further configured to assign a priority to the second physical uplink channel by assigning a high priority to the second physical uplink channel regardless of a priority indicator field of the DCI.

[0160] Example 8: The wireless communications device of Examples 1, 2, 3, 4, 5, or 6, wherein the processor is further configured to assign a priority to the second physical uplink channel by determining whether the DCI includes an indication of priority, selecting a priority for the second physical uplink channel based on the DCI in response to the DCI including an indication of priority, and selecting a priority for the second physical uplink channel based on a predetermined priority set to either low or high in response to the DCI not including an indication of priority.

[0161] Example 9: The wireless communications device of Examples 1, 2, 3, 4, 5, 6, or 8, wherein the processor is further configured to: receive an additional DCI for a second physical uplink channel requesting a one-shot HARQ-ACK codebook and including a priority indicator; and select a priority for the second physical uplink channel based on the priority indicator of the additional DCI.

[0162] Example 10: The wireless communications device of Examples 1, 2, 3, 4, 5, 6, or 8, wherein the processor is further configured to: receive an additional DCI requesting a one-shot HARQ-ACK codebook and including a priority indicator that differs from the indication of priority in the DCI; and select a priority for the second physical uplink channel by assigning a high priority to the second physical uplink channel.

[0163] 11. The wireless communications device of any one of embodiments 1, 2, 3, 4, 5, or 6, wherein the processor is further configured to assign a priority to the second physical uplink channel by setting the priority of the second physical uplink channel to a high priority when at least one reported HARQ-ACK bit in the one-shot HARQ-ACK codebook for a given HARQ process corresponding to a PDSCH scheduled by the DCI has a priority indicator field set to a high priority, and setting the priority of the second physical uplink channel to a low priority when the priority indicator field is set to a low priority.

[0164] Example 12: The wireless communications device of Examples 1, 2, 3, 4, or 5, wherein at least one of the first and second physical uplink channels is a PUCCH with a one-shot HARQ-ACK codebook, and the other of the first and second physical uplink channels is a PUSCH that overlaps in time with the PUCCH, and the processor is further configured to process the first and second physical uplink channels by: multiplexing the PUCCH with the PUSCH when the PUCCH with the one-shot HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority; and multiplexing the PUCCH with the PUSCH when the PUCCH with the one-shot HARQ-ACK feedback codebook has a low priority and the PUSCH has a high priority.

[0165] Example 13: The wireless communications device of Examples 1, 2, 3, 4, or 5, wherein the processor is further configured to obtain the first and second HARQ-ACK codebooks via a radio resource control (RRC) configuration and to provide one-shot HARQ-ACK feedback via the RRC configuration, and wherein the processor is further configured to apply the one-shot HARQ-ACK feedback configuration to both the first and second HARQ-ACK codebooks.

[0166] Example 14: The wireless communication device of Example 1, 2, 3, 4 or 5, wherein the processor is further configured to use first and second maximum numbers of CBGs per TB for respective first and second priorities for the CC, and the processor is further configured to set the number of HARQ-ACK bits for each TB for the one-shot HARQ feedback process for the particular CC based on a maximum value that is the greater of the number of HARQ-ACK bits configured for the first priority and the number of HARQ-ACK bits configured for the second priority.

[0167] Example 15: A method of wireless communication by a wireless device in a communications network, comprising: obtaining a plurality of HARQ-ACK codebooks including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks; and processing first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0168] Example 16: The method of example 15, wherein the priority-based HARQ-ACK codebook includes one or more of a type-1 quasi-static codebook and a type-2 dynamic codebook, and the one-shot HARQ-ACK codebook includes a type-3 codebook.

[0169] Example 17: The method of Example 15 or 16, wherein the step of processing the first and second physical uplink channels further includes the step of removing one of the first and second physical uplink channels when the first and second physical uplink channels overlap in time based on a respective priority of each of the first and second physical uplink channels.

[0170] Example 18: The method of Example 15 or 16, wherein the step of processing the first and second physical uplink channels further includes the step of multiplexing the first and second physical uplink channels when the first and second physical uplink channels overlap in time and are of equal priority.

[0171] Example 19: The method of example 15, 16, 17 or 18, wherein the first and second physical uplink channels include one or more of a PUCCH and a PUSCH.

[0172] Example 20: The method of Examples 15, 16, 17, 18 or 19, wherein the step of processing the first and second physical uplink channels includes the steps of determining a priority for the first physical uplink channel; receiving a DCI triggering the second physical uplink channel requesting use of a one-shot HARQ-ACK codebook; assigning a priority to the second physical uplink channel; removing the first physical uplink channel when the first physical uplink channel has a lower priority compared to the second physical uplink channel, removing the second physical uplink channel when the second physical uplink channel has a lower priority compared to the first physical uplink channel, and multiplexing the first and second physical uplink channels when the first and second physical uplink channels have equal priority.

[0173] Example 21: The method of example 15, 16, 17, 18, 19 or 20, wherein assigning a priority to the second physical uplink channel includes assigning a high priority to the second physical uplink channel regardless of a priority indicator field of the DCI.

[0174] Example 22: The method of Examples 15, 16, 17, 18, 19 or 20, wherein the step of assigning a priority to the second physical uplink channel includes the steps of: determining whether the DCI includes an indication of priority; selecting a priority for the second physical uplink channel based on the DCI in response to the DCI including an indication of priority; and selecting a priority for the second physical uplink channel based on a predetermined priority set to either low or high in response to the DCI not including an indication of priority.

[0175] Example 23: The method of Example 15, 16, 17, 18, 19, 20 or 22, further comprising: receiving an additional DCI for a second physical uplink channel requesting a one-shot HARQ-ACK codebook and including a priority indicator; and selecting a priority for the second physical uplink channel based on the priority indicator of the additional DCI.

[0176] Example 24: The method of Example 15, 16, 17, 18, 19, 20 or 22, further comprising: receiving an additional DCI requesting a one-shot HARQ-ACK codebook and including a priority indicator different from the indication of priority in the DCI; and selecting a priority for the second physical uplink channel by assigning a high priority to the second physical uplink channel.

[0177] Example 25: The method of Examples 15, 16, 17, 18, 19 or 20, wherein the step of assigning a priority to the second physical uplink channel includes: setting the priority of the second physical uplink channel to a high priority when at least one reported HARQ-ACK bit in the one-shot HARQ-ACK codebook for a given HARQ process corresponding to a PDSCH scheduled by the DCI has a priority indicator field set to a high priority; and setting the priority of the second physical uplink channel to a low priority when the priority indicator field is set to a low priority.

[0178] Example 26: The method of Example 15, 16, 17, 18 or 19, wherein at least one of the first or second physical uplink channel is a PUCCH having a one-shot HARQ-ACK codebook, and the other of the first and second physical uplink channels is a PUSCH that overlaps in time with the PUCCH, and the step of processing the first and second physical uplink channels includes the steps of: multiplexing the PUCCH with the PUSCH when the PUCCH with the one-shot HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority; and multiplexing the PUCCH with the PUSCH when the PUCCH with the one-shot HARQ-ACK feedback codebook has a low priority and the PUSCH has a high priority.

[0179] Example 27: The method of Example 15, 16, 17, 18 or 19, further including: obtaining the first and second HARQ-ACK codebooks via an RRC configuration; and applying a one-shot HARQ-ACK feedback configuration to both the first and second HARQ-ACK codebooks using the RRC configuration.

[0180] Example 28: The method of Examples 15, 16, 17, 18 or 19, wherein the wireless device is configured with first and second maximum numbers of CBGs per TB for respective first and second priorities for the CC, and the method further includes setting the number of HARQ-ACK bits for each TB for the one-shot HARQ feedback process for the particular CC based on a maximum value that is the greater of the number of HARQ-ACK bits configured for the first priority and the number of HARQ-ACK bits configured for the second priority.

[0181] Example 29: An apparatus for use in a wireless communications device of a wireless communications network, the apparatus comprising: means for obtaining a plurality of HARQ-ACK codebooks including a priority-based HARQ-ACK codebook of different priorities and a separate one-shot HARQ-ACK codebook; and means for processing first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and wherein the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0182] Example 30: An article of manufacture for use by a wireless communication device of a wireless communication network, the item including a computer-readable medium storing instructions, the instructions being executable by one or more processors of the wireless communication device to: obtain a plurality of HARQ-ACK codebooks, the plurality of HARQ-ACK codebooks including a priority-based HARQ-ACK codebook and a separate one-shot HARQ-ACK codebook of different priorities; and process first and second physical uplink channels based at least in part on a priority of the first physical uplink channel and a priority of the second physical uplink channel, wherein one of the first and second physical uplink channels contains the one-shot HARQ-ACK codebook, and the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

[0183] Several aspects of wireless communication networks have been presented with reference to example implementations. As one skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunications systems, network architectures, and communication standards.

[0184] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as LTE, Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standard, network architecture, and / or communications standard employed will depend on the particular application and the overall design constraints imposed on the system.

[0185] Although aspects and embodiments are described herein by way of illustrating some examples, those skilled in the art will appreciate that additional implementations and use cases may arise in many different configurations and scenarios. Features described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or applications may arise with integrated chip embodiments and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not specifically target a use case or application, a wide assortment of applicability of the described innovations may arise. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, transmitting and receiving wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the features described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, end-user devices, etc., of various sizes, shapes, and configurations.

[0186] Within this disclosure, the word “exemplary” is used to mean “serving as an example, instance, or illustration.” Any implementation or aspect described herein as “exemplary” should not necessarily be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspect” does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term “coupled” is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, object A and object C may still be considered to be coupled to each other even though they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even though the first object is not in direct physical contact with the second object at all. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in this disclosure, and software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in this disclosure, without limitation as to the type of electronic circuit.

[0187] One or more of the components, steps, features, and / or functions shown in FIGS. 1-21 may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additionally, additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. The apparatuses, devices, and / or components shown in FIGS. 1, 2, 16, 18, and 19-21 may be configured to perform one or more of the methods, features, or steps described herein. The algorithms described herein may also be efficiently implemented in software and / or incorporated into hardware. Generally speaking, the various components, steps, features, and / or functions shown in FIGS. 1-21 are not mutually exclusive.

[0188] It is understood that the specific order or hierarchy of steps in the disclosed methods represents example processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented, unless specifically recited herein.

[0189] The above description is provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments. Accordingly, the claims are not limited to the embodiments set forth herein but are to be accorded the widest scope consistent with the language of the claims, and references to elements in the singular are intended to mean "one or more" and not "one and only one," unless expressly stated otherwise. Unless expressly stated otherwise, the term "some" refers to "one or more." A phrase referring to "at least one of" a list of items refers to any combination of those items, including a single element. As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a and b, a and c, b and c, and a, b, and c. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is made available to the public, regardless of whether such disclosure is expressly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase "means for," or, in the case of a method claim, unless the element is recited using the phrase "step for." [Explanation of symbols]

[0190] 100 Wireless Communication System 102 Core Network 104 Radio Access Network (RAN) 106 User Equipment (UE) 108 Base Station 110 External Data Network 112 Downlink Traffic 114 Downlink Control Information 116 uplink traffic 118 Uplink Control 120 Backhaul section 200 Radio Access Network (RAN) 202 cells 204 cells 206 cells 208 cells 210 base station 212 Base Station 214 Base Station 216 Remote Radio Head (RRH) 218 Base Station 220 Unmanned Aerial Vehicle (UAV) 222 User Equipment (UE) 224 UE 226 UE 227 Sidelink Signal 228 UE 230 UE 232 UE 234 UE 236 UE 237 Sidelink Signal 238 UE 240 UE 242 UE 302 subframe 304 Resource Grid 306 Resource Element (RE) 308 Resource Blocks (RB) 310 Slots 312 Control Area 314 Data Area 400 Low Priority Example 402 First Downlink Control Information (DCI) 404 Physical Downlink Shared Channel (PDSCH) 406 First Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) Codebook 408 Second DCI 410 PDSCH 412 High Priority Example 414 Third DCI 417 PDSCH 418 Second HARQ-ACK Codebook 500 Delete Example 502 Multiplexing Example 504 Low priority PUCCH / PUSCH504 506 High priority PUCCH / PUSCH 508 Physical Uplink Control Channel (PUCCH) 510 PUCCH / PUSCH 1600 Scheduling Entities 1602 Bus 1604 processor 1605 memory 1606 Computer-readable storage medium, Computer-readable storage medium 1608 bus interface 1610 Transceiver 1612 User Interface 1614 Processing System 1640 Priority-based HARQ-ACK Processing Circuit 1642 One-shot HARQ-ACK processing circuit 1644 UL / DL processing circuit 1652 Code for Priority-Based HARQ-ACK Processing 1654 Code for One-Shot HARQ-ACK Processing 1656 Code for UL / DL Processing 1700 Scheduled Entities 1702 Bus 1704 processor 1705 memory 1706 Computer-readable medium 1708 bus interface 1710 Transceiver 1712 User Interface 1714 Processing System 1740 Priority-based HARQ-ACK processing circuit 1742 One-shot HARQ-ACK processing circuit 1744 UL channel priority determination circuit 1752 Code for priority-based HARQ-ACK processing 1754 Code for One-Shot HARQ-ACK Processing 1756 Code for removing or multiplexing channels 1900 base station 1902 Bus 1904 processor 1905 Memory 1906 Computer-readable medium 1908 bus interface 1910 transceiver 1911 receiver 1912 User Interface 1913 Transmitter 1914 Processing System 1915 Antenna 1917 Antenna Set 1940 HARQ-ACK codebook management circuit 1944 Physical channel processing circuit 1946 DCI processing circuit 1952 Code for HARQ-ACK codebook management 1956 Code for Physical Channel Processing 1958 Code for DCI Processing 2000 Wireless Communication Devices 2002 Bus 2004 processor 2005 Memory 2006 Computer-Readable Medium 2008 Bus Interface 2010 Transceiver 2011 Receiver 2012 User Interface 2013 Transmitter 2014 Processing System 2015 Antenna Set 2020 Antenna Set 2040 HARQ-ACK codebook reception / management circuit 2044 Priority-based physical channel processing circuit 2046 DCI processing circuit 2052 Code for HARQ-ACK codebook reception / management 2056 Code for Priority-Based Physical Channel Processing 2058 Code for DCI Processing Block 2102 2104 Block Block 2106 Block 2108 Block 2110 2112 Block 2114 Block

Claims

1. A transceiver; Memory and a processor communicatively coupled to the transceiver and the memory, the processor comprising: Obtaining multiple hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebooks, including priority-based HARQ-ACK codebooks of different priorities and individual one-shot HARQ-ACK codebooks; and processing the first and second physical uplink channels based at least in part on a priority of a first physical uplink channel and a priority of a second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and wherein the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

2. the priority-based HARQ-ACK codebook is configured as one or more of a Type-1 quasi-static codebook and a Type-2 dynamic codebook; 10. The wireless communication device of claim 1, wherein the one-shot HARQ-ACK codebook is configured as a Type 3 codebook.

3. 10. The wireless communication device of claim 1, wherein the processor is further configured to process the first and second physical uplink channels by removing one of the first and second physical uplink channels when the first and second physical uplink channels overlap in time based on a respective priority of each of the first and second physical uplink channels.

4. 10. The wireless communication device of claim 1, wherein the processor is further configured to process the first and second physical uplink channels by multiplexing the first and second physical uplink channels when the first and second physical uplink channels overlap in time and are of equal priority.

5. 10. The wireless communication device of claim 1, wherein the first and second physical uplink channels comprise one or more of a Physical Uplink Control Channel (PUCCH) and a Physical Uplink Shared Channel (PUSCH).

6. The processor: determining a priority for the first physical uplink channel; receiving downlink control information (DCI) triggering the second physical uplink channel requesting use of the one-shot HARQ-ACK codebook; assigning a priority to the second physical uplink channel; 10. The wireless communication device of claim 1, further configured to process the first and second physical uplink channels by: dropping the first physical uplink channel when the first physical uplink channel has a lower priority compared to the second physical uplink channel; dropping the second physical uplink channel when the second physical uplink channel has a lower priority compared to the first physical uplink channel; and multiplexing the first and second physical uplink channels when the first and second physical uplink channels have equal priority.

7. 7. The wireless communication device of claim 6, wherein the processor is further configured to assign the priority to the second physical uplink channel by assigning a high priority to the second physical uplink channel regardless of a priority indicator field of the DCI.

8. The processor: determining whether the DCI includes an indication of priority; responsive to the DCI including an indication of the priority, selecting the priority for the second physical uplink channel based on the DCI; 7. The wireless communication device of claim 6, further configured to: in response to the DCI not including an indication of the priority, assign the priority to the second physical uplink channel by: selecting the priority for the second physical uplink channel based on a predetermined priority set to either low or high.

9. The processor: receiving an additional DCI for the second physical uplink channel requesting the one-shot HARQ-ACK codebook and including a priority indicator; and selecting the priority for the second physical uplink channel based on the priority indicator of the additional DCI.

10. The processor: receiving an additional DCI requesting the one-shot HARQ-ACK codebook and including a priority indicator different from the indication of priority in the DCI; and selecting the priority for the second physical uplink channel by assigning a high priority to the second physical uplink channel.

11. The processor: setting the priority of the second physical uplink channel to high priority when at least one reported HARQ-ACK bit in the one-shot HARQ-ACK codebook for a given HARQ process corresponding to a physical downlink shared channel (PDSCH) scheduled by the DCI has a priority indicator set to high priority; 7. The wireless communication device of claim 6, further configured to assign the priority to the second physical uplink channel by setting the priority of the second physical uplink channel to low priority when the priority indicator field is set to low priority.

12. At least one of the first and second physical uplink channels is a Physical Uplink Control Channel (PUCCH) having the one-shot HARQ-ACK codebook, and the other of the first and second physical uplink channels is a Physical Uplink Shared Channel (PUSCH) that overlaps in time with the PUCCH; The processor: multiplexing the PUCCH with the PUSCH when the PUCCH having the one-shot HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority; 10. The wireless communication device of claim 1, further configured to process the first and second physical uplink channels by multiplexing the PUCCH with the PUSCH when the PUCCH having the one-shot HARQ-ACK feedback codebook has the low priority and the PUSCH has the high priority.

13. The processor is further configured to obtain first and second HARQ-ACK codebooks via a radio resource control (RRC) configuration and provide one-shot HARQ-ACK feedback via the RRC configuration; 10. The wireless communication device of claim 1, wherein the processor is further configured to apply a one-shot HARQ-ACK feedback configuration to both the first and second HARQ-ACK codebooks.

14. the processor is further configured to use first and second maximum numbers of code block groups (CBGs) per transport block (TB) for respective first and second priorities for a component carrier (CC); 10. The wireless communication device of claim 1, wherein the processor is further configured to set a number of HARQ-ACK bits for each TB for a one-shot HARQ-ACK feedback process for a particular CC based on a maximum value that is a greater of a number of HARQ-ACK bits configured for the first priority and a number of HARQ-ACK bits configured for the second priority.

15. 1. A method of wireless communication by a wireless device in a communication network, comprising: obtaining a plurality of hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebooks, including priority-based HARQ-ACK codebooks of different priorities and individual one-shot HARQ-ACK codebooks; and processing the first and second physical uplink channels based at least in part on a priority of a first physical uplink channel and a priority of a second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and wherein the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

16. the priority-based HARQ-ACK codebook includes one or more of a type-1 quasi-static codebook and a type-2 dynamic codebook; The method of claim 15 , wherein the one-shot HARQ-ACK codebook comprises a Type 3 codebook.

17. 16. The method of claim 15, wherein the step of processing the first and second physical uplink channels further comprises the step of removing one of the first and second physical uplink channels when the first and second physical uplink channels overlap in time based on a respective priority of each of the first and second physical uplink channels.

18. 16. The method of claim 15, wherein the step of processing the first and second physical uplink channels further comprises the step of multiplexing the first and second physical uplink channels when the first and second physical uplink channels overlap in time and are of equal priority.

19. 16. The method of claim 15, wherein the first and second physical uplink channels include one or more of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH).

20. The step of processing the first and second physical uplink channels includes: determining a priority for the first physical uplink channel; receiving downlink control information (DCI) triggering the second physical uplink channel requesting use of the one-shot HARQ-ACK codebook; assigning a priority to the second physical uplink channel; 16. The method of claim 15, comprising: removing the first physical uplink channel when the first physical uplink channel has a lower priority compared to the second physical uplink channel; removing the second physical uplink channel when the second physical uplink channel has a lower priority compared to the first physical uplink channel; and multiplexing the first and second physical uplink channels when the first and second physical uplink channels have equal priority.

21. 21. The method of claim 20, wherein the step of assigning the priority to the second physical uplink channel comprises assigning a high priority to the second physical uplink channel regardless of a priority indicator field of the DCI.

22. The step of assigning the priority to the second physical uplink channel comprises: determining whether the DCI includes an indication of priority; responsive to the DCI including an indication of the priority, selecting the priority for the second physical uplink channel based on the DCI; and in response to the DCI not including an indication of the priority, selecting the priority for the second physical uplink channel based on a predetermined priority set to either low or high.

23. receiving an additional DCI for the second physical uplink channel requesting the one-shot HARQ-ACK codebook and including a priority indicator; and selecting the priority for the second physical uplink channel based on the priority indicator of the additional DCI.

24. receiving an additional DCI requesting the one-shot HARQ-ACK codebook and including a priority indicator different from the indication of priority in the DCI; and selecting the priority for the second physical uplink channel by assigning a high priority to the second physical uplink channel.

25. the step of assigning the priority to the second physical uplink channel comprises: setting the priority of the second physical uplink channel to high priority when at least one reported HARQ-ACK bit in the one-shot HARQ-ACK codebook for a given HARQ process corresponding to a physical downlink shared channel (PDSCH) scheduled by the DCI has a priority indicator set to high priority; and setting the priority of the second physical uplink channel to low priority when the priority indicator field is set to low priority.

26. At least one of the first or second physical uplink channel is a Physical Uplink Control Channel (PUCCH) having a one-shot HARQ-ACK codebook, and the other of the first and second physical uplink channels is a Physical Uplink Shared Channel (PUSCH) that overlaps in time with the PUCCH; The step of processing the first and second physical uplink channels includes: multiplexing the PUCCH with the PUSCH when the PUCCH having the one-shot HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority; and multiplexing the PUCCH with the PUSCH when the PUCCH having the one-shot HARQ-ACK feedback codebook has the low priority and the PUSCH has the high priority.

27. obtaining first and second HARQ-ACK codebooks via a radio resource control (RRC) configuration; and applying the one-shot HARQ-ACK feedback configuration to both the first and second HARQ-ACK codebooks using the RRC configuration.

28. the wireless device is configured with first and second maximum numbers of code block groups (CBGs) per transport block (TB) for respective first and second priorities for a component carrier (CC); 16. The method of claim 15, further comprising: setting a number of HARQ-ACK bits for each TB for a one-shot HARQ-ACK feedback process for a specific CC based on a maximum value that is a larger value of a number of HARQ-ACK bits configured for the first priority and a number of HARQ-ACK bits configured for the second priority.

29. 1. An apparatus for use in a wireless communication device of a wireless communication network, comprising: means for obtaining a plurality of hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebooks, including priority-based HARQ-ACK codebooks of different priorities and separate one-shot HARQ-ACK codebooks; and means for processing the first and second physical uplink channels based at least in part on a priority of a first physical uplink channel and a priority of a second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and wherein the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

30. 1. An article of manufacture for use by a wireless communication device of a wireless communication network, comprising: a computer-readable medium having stored thereon instructions, the instructions being configured to cause one or more processors of the wireless communication device to: Obtaining multiple hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codes including priority-based HARQ-ACK codebooks of different priorities and individual one-shot HARQ-ACK codebooks; and processing the first and second physical uplink channels based at least in part on a priority of a first physical uplink channel and a priority of a second physical uplink channel, wherein one of the first and second physical uplink channels includes the one-shot HARQ-ACK codebook, and wherein the processing is performed in combination with use of the priority-based HARQ-ACK codebook.

Images