Management of single HARQ-ACK codebook and HARQ-ACK codebook with set priority level
By using multiple HARQ-ACK codebooks and optimized channel processing strategies in the wireless communication system, the HARQ confirmation feedback management problem in the prior art is solved, channel resource utilization and data transmission efficiency are improved, and wireless communication performance is improved.
Patent Information
- Application Number
- CN202180043822.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-06-22
- Filing Date
- 2021-06-23
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
When existing wireless communication systems process hybrid automatic retransmission request (HARQ) acknowledgement (ACK) feedback, it is difficult to effectively manage physical uplink channels of different priority levels, resulting in waste of channel resources and reduced data transmission efficiency.
Using multiple HARQ-ACK codebooks, including priority-based codebooks and single-time codebooks, optimize the processing of the first and second physical uplink channels by combining the use of different priority codebooks, cancel or replication Use overlapping channels to improve channel utilization.
It improves the utilization rate of channel resources, enhances data transmission efficiency, reduces delay and error rates, and improves the overall performance of wireless communication systems.
Smart Images

Figure CN115812287B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to pending non-provisional serial number 17 / 355,070 filed with the U.S. Patent Office on June 22, 2021, and provisional application serial number 63 / 043,725 filed with the U.S. Patent Office on June 24, 2020, which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field
[0003] Generally speaking, the techniques discussed herein relate to wireless communication systems, and more particularly, the techniques discussed herein relate to wireless communication using a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback process. Background Art
[0004] As the demand for higher data rates and improved reliability increases, wireless network operators continue to develop mechanisms for maximizing throughput and minimizing latency. One such mechanism is the hybrid automatic repeat request (HARQ) process, which can 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 so that a certain amount of erroneously received bits can be corrected at the receiver. If a packet arrives with a higher number of errors than can be corrected using FEC, an ARQ process is initiated to request the sender to retransmit the packet.
[0005] Typically, HARQ uses a stop-and-wait (SAW) protocol in which a transmitting entity waits to receive an acknowledgement (ACK) or negative acknowledgement (NACK) back from a 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
[0006] In order to provide a basic understanding of one or more aspects of the present disclosure, an overview of such aspects is provided below. This overview is not an exhaustive overview of all expected features of the present disclosure, and is not intended to identify the key or important elements of any or all aspects of the present disclosure or to describe the scope of any or all aspects of the present disclosure. Its purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description provided later.
[0007] In one example, a wireless communication device is provided. The wireless communication device includes: a transceiver; a memory; and a processor, which is 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, wherein the HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks with different priorities; and process the first physical uplink channel and the second physical uplink channel based at least in part on the priority of the first physical uplink channel and the priority of the second physical uplink channel, wherein one of the first physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of the priority-based HARQ-ACK codebook.
[0008] In another example, a method for wireless communication for use by a wireless device in a communication network is provided. The method includes: obtaining a plurality of HARQ-ACK codebooks, wherein the plurality of HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks having different priorities; and processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of the priority-based HARQ-ACK codebook.
[0009] In another example, an apparatus for use in a wireless communication device of a wireless communication network is provided. The apparatus includes: a unit for obtaining a plurality of HARQ-ACK codebooks, wherein the HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks having different priorities; and a unit for processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of the priority-based HARQ-ACK codebook.
[0010] In another example, an article for use with a wireless communication device of a wireless communication network is provided. The article includes: a computer-readable medium having instructions stored therein that can be executed by one or more processors of the wireless communication device to perform the following operations: configuring multiple HARQ-ACK codebooks, wherein the HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks with different priorities; and processing the first physical uplink channel and the second physical uplink channel based at least in part on the priority of the first physical uplink channel and the priority of the second physical uplink channel, wherein one of the first physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of the priority-based HARQ-ACK codebook. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 is a schematic diagram of a wireless communication system according to some aspects.
[0012] Figure 2 is a conceptual diagram of an example of a radio access network in accordance with some aspects.
[0013] Figure 3 is a diagram illustrating an example of a frame structure for use in a radio access network in accordance with some aspects.
[0014] Figure 4 is a diagram illustrating an example of low priority and high priority codebook processing according to some aspects.
[0015] Figure 5 is a diagram illustrating an example of eliminating or multiplexing overlapping channels in accordance with some aspects.
[0016] Figure 6 is a flow chart illustrating a wireless communication method for use by a wireless communication device to assign priorities to physical uplink (UL) channels in accordance with some aspects.
[0017] Figure 7 is a flow chart illustrating another wireless communication method for use by a wireless communication device to assign priorities to physical UL channels in accordance with some aspects.
[0018] Figure 8 is a flow chart illustrating another wireless communication method for use by a wireless communication device to assign priorities to physical UL channels in accordance with some aspects.
[0019] Fig. 9 is a flow chart illustrating a wireless communication method for use by a wireless communication device to assign priorities to physical UL channels in accordance with some aspects.
[0020] Fig.10 is a flow chart illustrating a wireless communication method for use by a wireless communication device for multiplexing physical UL channels according to some aspects.
[0021] Fig.11 is a flow chart illustrating a wireless communication method for a wireless communication device to apply a single HARQ-ACK feedback configuration to two HARQ-ACK codebooks according to some aspects.
[0022] Fig.12 is a flow chart illustrating another wireless communication method for a wireless communication device to apply a single HARQ-ACK feedback configuration to a HARQ-ACK codebook according to some aspects.
[0023] Fig.13 is a flow chart illustrating a wireless communication method for use by a wireless communication device to insert NACK values into vacant bit positions in a codebook in accordance with some aspects.
[0024] Fig.14 is a flow chart illustrating another wireless communication method for use by a wireless communication device to insert NACK values into vacant bit positions in a codebook in accordance with some aspects.
[0025] Fig.15 is a flow chart illustrating a wireless communication method for use by a wireless communication device to configure transport block (TB) level ACK / NACK reporting in accordance with some aspects.
[0026] Fig.16 is a block diagram illustrating an example of a hardware implementation for a scheduling entity according to some aspects.
[0027] Fig.17 is a block diagram illustrating an example of a hardware implementation for a scheduled entity according to some aspects.
[0028] Fig.18 is a flow chart illustrating a wireless communication method for use by a wireless communication device when using a single HARQ-ACK codebook in accordance with some aspects.
[0029] Fig.19 is a block diagram illustrating an example of a hardware implementation for a base station according to some aspects.
[0030] Fig. 20 is a block diagram illustrating an example of a hardware implementation for a UE according to some aspects.
[0031] Fig.21 is a block diagram illustrating example components of a processor of a UE according to some aspects. DETAILED DESCRIPTION
[0032] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. In order to provide a comprehensive understanding of each concept, the detailed description includes specific details. 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 blurring such concepts.
[0033] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses can be generated via integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical devices, AI-enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicable scopes for the described innovations. Implementations may have a range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, the 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, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.) It is expected that the innovations described herein can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations.
[0034] Various 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) with different priorities and type 3 (single) HARQ-ACK codebooks in wireless communication standards, such as the third generation partnership project (3GPP) new radio (NR) specifications (commonly referred to as 5G). For example, a wireless communication device (e.g., a user equipment (UE)) may be configured to configure multiple HARQ-ACK codebooks. The HARQ-ACK codebooks may include priority-based HARQ-ACK codebooks and single HARQ-ACK codebooks with different priorities. The UE may also be configured to process first and second physical uplink channels while prioritizing the use of the single HARQ-ACK codebook in conjunction with the use of priority-based HARQ-ACK codebooks with different priorities. Illustrative examples are described herein, where these processes are performed by a UE (or other scheduled entity) communicating with a base station (such as a gNB or other scheduling entity). The operation of the base station is also discussed and described, and a block diagram illustration of an exemplary base station (or other scheduling entity) is provided.
[0035] Before discussing these and other techniques in detail, an overview of wireless communication systems that employ HARQ-ACK feedback is provided.It should be noted, however, that the various concepts throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards.
[0036] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100, by way of example and not limitation. 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 means of the wireless communication system 100, the UE 106 is able to perform data communications with an external data network 110, such as (but not limited to) the Internet.
[0037] The RAN 104 may implement any one or more suitable wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, often referred to as 5G. As another example, the RAN 104 may operate in accordance with a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. 3GPP refers to this hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.
[0038] As shown, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, those skilled in the art may refer to the base station as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an evolved node B (eNB), a gNodeB (gNB), a transmission reception point (TRP) or some other appropriate term. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one of the base stations may be an LTE base station, and the other base station may be a 5G NR base station.
[0039] The radio access network 104 is also shown to support wireless communications for multiple mobile devices. In the 3GPP standard, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other appropriate term. A UE may be a device that provides a user with access to network services.
[0040] In this document, a "mobile" device does not necessarily need to have the ability to move, but can be stationary. The term mobile device or mobile device broadly refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement are changed to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the "Internet of Things" (IoT). In addition, a mobile device may be a car or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio unit, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor helicopter, a quadcopter, a remote control device, a consumer device such as glasses, 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, and / or a wearable device. In addition, the mobile device may be a digital home or smart home device, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. In addition, the mobile device may be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure equipment that controls power (e.g., smart grid), lighting, water use, industrial automation and enterprise equipment, logistics controllers, agricultural equipment, etc. In addition, the mobile device may provide connected medicine or telemedicine support (i.e., remote health care). Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or priority access relative to other types of information, for example, in terms of priority access for the transmission of critical service data, and / or in terms of the associated QoS for the transmission of critical service data.
[0041] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe the scheme can 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) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink can refer to point-to-point transmissions originating from a UE (e.g., UE 106).
[0042] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and apparatuses within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UE 106). That is, for scheduled communications, UE 106 (which may be a scheduled entity) may use resources allocated by scheduling entity 108.
[0043] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity that schedules resources for one or more scheduled entities (e.g., one or more other UEs). As discussed in more detail below, a UE can communicate directly with other UEs in a peer-to-peer manner and / or in a relay configuration.
[0044] like Figure 1 As shown, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106 (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including 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. On the other hand, 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., grant), synchronization or timing information, or other control information) from another entity in the wireless communication network (e.g., the scheduling entity 108).
[0045] In addition, uplink and / or downlink control information and / or traffic information can be sent on a waveform that is divided into frames, subframes, time slots and / or symbols by time. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Within the present disclosure, a frame may refer to a predetermined duration (e.g., 10ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes (each subframe is 1ms). Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.
[0046] Typically, base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of a wireless communication system. Backhaul 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or a backhaul interface using any suitable transport network.
[0047] 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 according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.
[0048] Reference now Figure 2 , by way of example and not limitation, a schematic diagram of a RAN 200 is provided. In some examples, the RAN 200 may be similar to the one described above and in Figure 1 The same as the RAN 104 shown in FIG.
[0049] The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2Cells 202, 204, 206, and 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors in a cell are served by the same base station. A wireless link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.
[0050] Various base station arrangements can be used. Figure 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 for controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna or may be connected to an antenna or RRH 216 via a feeder cable. In the example shown, cells 202, 204, and 206 may be referred to as macro cells, since base stations 210, 212, and 214 support cells having large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNodeB, etc.), since base station 218 supports cells having relatively small sizes. Cell size settings may be performed based on system design and component constraints.
[0051] It will be appreciated that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The base station / scheduling entity 108 shown in FIG.
[0052] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, as a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move depending on the location of the mobile base station (such as UAV 220).
[0053] In the RAN 200, a cell may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, and 218 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 by way of RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 200. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate in cell 202 by communicating with base station 210.
[0054] In other aspects of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communications can be utilized, for example, in device-to-device (D2D), peer-to-peer (P2P), vehicle-to-vehicle (V2V) networks, and / or vehicle-to-everything (V2X). For example, two or more UEs (e.g., UE 238, 240, and 242) can communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UE 238, 240, and 242 can each act as a scheduling entity or a sending sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and transmit sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UE 226 and 228) within the coverage area of a base station (e.g., base station 212) can also transmit sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communications.
[0055] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. This is usually accomplished in an access and mobility management function (AMF, not shown, Figure 1The AMF is a part of the core network 102 in the UE to establish, maintain and release various physical channels between the UE and the RAN. In some scenarios, the AMF may include a security context management function (SCMF) and a security anchor function (SEAF) for performing authentication. The SCMF may manage the security context for both the control plane and the user plane functions in whole or in part.
[0056] In some examples, the RAN 200 may implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). For example, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these 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 perform a handoff or handover from the serving cell to the neighboring (target) cell. For example, a UE 224 (shown as a vehicle, but any suitable form of a UE may be used) may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message to its serving base station 210 indicating the condition. In response, UE 224 may receive a handover command, and the UE may perform a handover to cell 206 .
[0057] In order to achieve a low block error rate (BLER) for transmissions over the radio access network 200 while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize appropriate error-correcting block codes. In a typical block code, an information message or sequence is segmented into coded code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device mathematically adds redundancy to the information message. Utilizing this redundancy in the coded information message may improve the reliability of the message, thereby enabling correction of any bit errors that may occur due to noise.
[0058] In early 5G NR specifications, quasi-cyclic low-density parity check (LDPC) with two different basemaps is used to encode user data traffic: one basemap is used for large code blocks and / or high code rates, and the other basemap is used otherwise. Polar coding is used to encode control information and the physical broadcast channel (PBCH) based on nested sequences. For at least some of these channels, puncturing, shortening, and repetition are used for rate matching.
[0059] However, it will be appreciated by those skilled in the art that aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of the scheduling entity and the scheduled entity may include appropriate hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.
[0060] However, even with the best error correction code, if the communication channel experiences a very large amount of noise, or experiences deep fading or other problems, the bit error rate may exceed the bit error rate that can be compensated. Therefore, many wireless communication networks use hybrid automatic repeat request (HARQ) schemes to further improve data reliability. In the HARQ algorithm, if the first transmission is not correctly decoded at the receiving device, the sending device (e.g., a base station or UE) can retransmit the code block (e.g., encoded using a convolutional code or a block code). In order to facilitate this process, the transmitted encoded code block may include a cyclic redundancy check (CRC) portion, a checksum, or any other appropriate mechanism known to those of ordinary skill in the art to determine whether the encoded code block is correctly decoded at the receiving device. If the received encoded code block is correctly decoded, the receiving device can send an acknowledgment (ACK) that notifies the sending device that retransmission is not required. However, if the received encoded code block is not correctly decoded, the receiving device can send a negative acknowledgment (NACK) requesting retransmission. Typically, a limited number of retransmissions will be performed before the transmission attempt is terminated. Many existing networks limit their HARQ algorithms to four retransmissions. However, within the scope of the present disclosure, any suitable retransmission limit may be utilized in a network.
[0061] The air interface in the radio access network 200 can utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other appropriate multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided 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.
[0062] The air interface in the radio access network 200 can also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link, in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that at a certain time, only one endpoint can send information to the other endpoint. Half-duplex simulation is frequently implemented for wireless links using time division duplex (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, and at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly (e.g., several times per time slot). In wireless links, full-duplex channels usually rely on physical isolation of transmitters and receivers and suitable interference elimination techniques. Full-duplex simulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., in 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 can be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within 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.
[0063] The reference OFDM waveform (which is Figure 3 Various aspects of the present disclosure are described in detail with reference to Figure 1 (schematically shown in Figure 2). It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described below herein. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.
[0064] Reference now Figure 3 , shows an expanded view of an exemplary subframe 302 showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein, depending on any number of factors. Here, time is in the horizontal direction, in units of OFDM symbols; and frequency is in the vertical direction, in units of subcarriers.
[0065] Resource grid 304 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, corresponding multiple resource grids 304 can be available for communication. Resource grid 304 is divided into multiple resource elements (RE) 306. RE (which is 1 carrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RF can represent one or more bits of information. In some examples, a block of REs can be referred to as a physical resource block (PRB) or resource block (RB) 308, which contains any appropriate number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, regardless of the number of digital schemes used. In some examples, depending on the digital scheme, an RB can include any appropriate number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to a single direction of communication (for a given device, a sending or receiving direction).
[0066] A set of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A subband or BWP set may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Therefore, a UE typically utilizes only a subset of a resource grid 304. In some examples, an RB may be the smallest unit of resources that may be allocated to a UE. Therefore, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a base station (e.g., a gNB, an eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.
[0067] In this diagram, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this diagram, while RB 308 is shown as occupying less than the entire duration of subframe 302, this is merely one possible example.
[0068] Each 1 ms subframe 302 may consist of one or more adjacent time slots. Figure 3 In the example shown in , a subframe 302 includes four time slots 310 as an illustrative example. In some examples, the time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Another example may include a micro-time slot (sometimes referred to as a shortened transmission time interval (TTI)) with a shorter duration (e.g., one to three OFDM symbols). In some cases, a micro-time slot or a shortened transmission time interval (TTI) may be sent by occupying resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.
[0069] An expanded view of one of the time slots 310 shows that the time slot 310 includes a control region 312 and a data region 314. In general, the control region 312 may carry control channels, and the data region 314 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown in is merely exemplary in nature, and different slot structures may be utilized, and may include one or more regions in each of the control region and the data region.
[0070] Despite Figure 3 Although not shown in the figure, each RE 306 within the RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide a receiving device to perform channel estimation of the corresponding channel, which can achieve coherent demodulation / detection of the control and / or data channels within the RB 308.
[0071] In some examples, time slot 310 may be used for broadcast or unicast communication. For example, broadcast, multicast or groupcast communication may refer to point-to-multipoint transmission from one device (e.g., a base station, UE or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast communication is delivered to multiple intended recipient devices. Unicast communication may refer to point-to-point transmission from one device to a single other device.
[0072] In an example of cellular communication over a cellular carrier via a Uu interface, for DL transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312) to one or more scheduled entities (e.g., UEs) to carry 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 assignments of REs for DL and UL transmissions. The PDCCH may also carry HARQ feedback transmissions, such as an acknowledgment (ACK) or a negative acknowledgment (NACK). HARQ is a technique well known to those skilled in the art, in which the integrity of a packet transmission may be checked for accuracy at the receiving side, for example, using any appropriate integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if the integrity of the transmission is not confirmed, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may implement append combining, incremental redundancy, and the like.
[0073] The base station may also 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 period (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, time 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 identity (PCI) of the cell.
[0074] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). For example, the SIB may be, for example, a system information type (SystemInformationType) 1 (SIB1) that may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink digital scheme), system frame number, configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration data. The base station may also send other system information (OSI).
[0075] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to carry UL control information (UCI) to a scheduling entity, including one or more UL control channels, such as a physical uplink control channel (PUCCH). UCI may include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, UCI may include a scheduling request (SR), i.e., a request for a scheduling entity to schedule an uplink transmission. Here, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.
[0076] In addition to control information, one or more REs 306 (e.g., within the data region 314) may also be allocated for user data traffic. Such data traffic may be carried on one or more traffic channels (e.g., for DL transmission, a physical downlink shared channel (PDSCH); or for UL transmission, a physical uplink shared channel (PUSCH)). In some examples, one or more REs 306 within the data region 314 may be configured to carry other signals (such as one or more SIBs and DMRS).
[0077] In an example of sidelink communication on a sidelink carrier via a PC5 interface, the control region 312 of the time slot 310 may include a physical sidelink control channel (PSCCH), which includes sidelink control information (SCI) sent 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 region 314 of the time slot 310 may include a physical sidelink shared channel (PSSCH), which includes sidelink data traffic sent by an initiating (transmitting) sidelink device within resources reserved by the transmitting sidelink device via the SCI on the sidelink carrier. Other information may also be sent on various REs 306 within the time slot 310. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 310. In addition, 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 sent within time slot 310 .
[0078] The physical channels described above are typically multiplexed and mapped to transport channels for processing 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.
[0079] Combination of the above Figure 1-3 The channels or carriers described in are not necessarily all of the channels or carriers that may be utilized between the scheduling entity and the scheduled entity, and those skilled in the art will recognize that other channels or carriers, such as other services, control, and feedback channels, may be utilized in addition to the channels or carriers shown.
[0080] 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 the single codebook discussed in detail below, which contains HARQ-ACK feedback for all HARQ processes regardless of priority and may therefore not be directly priority-based. Each codebook includes information bits for encoding or representing a specific HARQ acknowledgment, e.g., a codebook is a specific sequence of bits. A UE may be configured with up to two HARQ-ACK codebooks via the following 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. For the configured HARQ-ACK codebooks, the codebook types may be the same or different, for example, one may be type 1 (semi-static) and the other may be type 2 (dynamic), or both may be type 2, and so on.
[0081] 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 (for example, the priority field is not configured for the DCI or DCI format 1_0 is used), the system assumes a priority of 0 (lower priority). For HARQ-ACK corresponding to semi-persistent scheduling (SPS), the priority is configured via RRC as part of the SPS configuration. The PUCCH resources for the HARQ-ACK codebook are configured separately, where the PUCCH resource indicator (PRI) field in the DCI with a given priority indicates the PUCCH channel resources among the corresponding PUCCH channel resources. Further information on the physical layer procedures for control can be found in the following documents: 3GPP TS 38.213, Release 16, Physical Layer Procedures for Control.
[0082] Figure 4 At a high level, separate processing of low priority and high priority codebooks according to some aspects is shown. Briefly, for the 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 for a 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 the 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 for a PUCCH.
[0083] As far as the cancellation of overlapping physical channels is concerned, in Release 16, if two different UL channels with different priorities overlap in time, the low priority channel is canceled and the high priority channel is sent. If the channels have the same priority, the UE multiplexes the PUCCH with another PUCCH or multiplexes the PUCCH with the PUSCH. If the channels have different priorities, the low priority channel is canceled. It should be noted that the high priority UL channel can be a PUCCH with HARQ-ACK or a PUCCH with SR or PUSCH (dynamic or configured authorization). The low priority channel can be a PUCCH with HARQ-ACK, a PUCCH with SR, a PUCCH with CSI, or a PUSCH (with dynamic or configured authorization). As far as priority indication is concerned, for PUCCH with HARQ-ACK, the priority can be specified via DCI as described above. For PUCCH with SR, the priority is specified in the RRC configuration. For PUCCH with CSI, a low priority is specified (e.g., there is no high priority in this particular case). For dynamic PUSCH, the priority is given in the DCI (DCI format 0_1, 0_2) that schedules PUSCH. For configured granted PUSCH, the priority is given in RRC as part of the CG configuration.
[0084] Figure 5 An example of canceling 500 or multiplexing 502 overlapping channels according to some aspects is shown. In the canceling case 500, if a low priority PUCCH / PUSCH 504 overlaps in time with a high priority PUCCH / PUSCH 506, the low priority PUCCH / PUSCH 504 is canceled. In the multiplexing case 502, if a PUCCH 508 and a PUCCH / PUSCH 510 overlap in time and have the same priority, the PUCCH 508 is time multiplexed with the PUCCH / PUSCH 510.
[0085] Turning now to the "single" (or type 3) codebook of Release 16, the one-shot HARQ-ACK feedback allows the gNB to request feedback for the HARQ-ACK codebook for all configured DL HARQ processes for all configured component carriers (CCs) configured for the UE. One-shot feedback can be configurable with a semi-static codebook, a non-enhanced dynamic HARQ codebook, and an enhanced dynamic codebook. In this document, both non-enhanced dynamic codebooks and enhanced dynamic codebooks are generally referred to as dynamic codebooks. If pdsch-HARQ-ACK-OneShotFeedback is provided to the UE, the codebook is configured in the RRC. If the UE is triggered to report both one-shot and other semi-static or dynamic HARQ-ACK feedback in the same timeslot, the UE only reports the one-shot feedback under Release 16. Essentially, the one-shot feedback "replaces" what was originally requested to be reported. The request is carried in DCI 1_1. That is, when pdsch-HARQ-ACK-OneShotFeedback is provided to the UE, one bit in DCI 1_1 (the "One-shotHARQ-ACK request" field) is set. The UE determines the PUCCH for single HARQ-ACK feedback based on K1, PUCCH resource indicator (PRI), and transmit power control (TPC), where K1 is the offset between the DL time slot where data is scheduled on the PDSCH and the UL time slot where ACK / NACK feedback for the scheduled PDSCH data needs to be sent. According to the process of the Release 15 3GPP NR specification, feedback can be carried on the PUSCH. It should be noted that the DL DCI may or may not schedule the PDSCH. For example, a value of the frequency domain resource assignment field indicates that the DCI does not schedule the PDSCH. Otherwise, the DCI schedules the PDSCH and simultaneously requests single feedback for all HARQ processes.
[0086] Under Release 16, a new data indicator (NDI) can be configured as part of a single HARQ feedback. NDI is sent within the DCI and is used to indicate the first transmission of a transport block. When NDI is configured, the latest NDI value detected by the UE is reported together 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, the NDI value is not reported together with the HARQ-ACK for the corresponding PDSCH. Once feedback for the HARQ process ID is reported in the previous feedback, the UE is expected to reset the HARQ-ACK state for the same HARQ process ID (as discontinuous transmission (DTX) or NACK). For higher HARQ efficiency, when a transport block (TB) contains multiple code blocks, the code blocks can be grouped into code block groups (CBGs). CBG-based HARQ-ACK or TB-based HARQ-ACK can be configured as part of a single HARQ feedback for a CC configured with CBG.
[0087] Below, various techniques are described that allow for combining: (a) a priority-based HARQ-ACK codebook corresponding to two different priorities (e.g., a UL channel with a lower priority can be canceled in the event of a conflict, or the UL channels can be multiplexed if they have equal priority); and (b) a single (type 3) HARQ-ACK codebook. As described above, the single codebook contains HARQ-ACK for all HARQ processes and is generally not prioritized. The following techniques also provide for setting priorities for physical UL channels (such as PUCCH) and selectively canceling overlapping channels (e.g., when one channel has a higher priority) or selectively multiplexing overlapping channels (e.g., when the channels have equal priority).
[0088] Figure 6600 is a flowchart illustrating an exemplary process 600 that can 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 a single HARQ-ACK feedback is fixed to a high priority, regardless of the DCI / priority indicator field in the DCI that triggers the physical UL channel with a single feedback. The high priority is used, at least in part, because the single feedback is a fallback mechanism. Therefore, when a single feedback is requested, the single feedback should be reported. At box 602, the UE determines a priority for a first physical UL channel (such as PUCCH). At box 604, the UE receives a DCI that triggers a second physical UL channel requesting the use of a single HARQ-ACK codebook. At box 606, the UE assigns a high priority to the second physical UL channel requesting the use of a single HARQ-ACK codebook, regardless of the priority indicator field of the DCI that triggers the second physical UL channel. At block 608, the UE cancels the first physical UL channel if it has a low priority (because the second physical UL channel has a high priority), or multiplexes the first and second UL channels if both have a high priority.
[0089] Figure 7 7 is a flow chart 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 requesting single feedback includes a priority indicator field, the priority is set by that field. Otherwise, the priority is assumed to be high (or in other examples, the priority is assumed to be low depending on the configuration of the entire system). Figure 6, the UE determines a priority for a first physical UL channel (box 702). The UE then receives a DCI that triggers a second physical UL channel requesting the use of a single HARQ-ACK feedback codebook (box 704). At box 706, the UE determines whether the DCI includes an indication of priority. If a priority is indicated in the DCI, then after decision box 708, the UE assigns a priority to the second physical UL channel based on the indicated priority at box 710. 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 triggers the second physical UL channel, processing proceeds instead to box 712, in which the UE assigns a priority to the second physical UL channel by assuming a high or low priority (e.g., based on a predetermined system configuration). For example, if the overall standard (which specifies the operation of the UE and other components in the wireless communication system) indicates that a high priority should be assumed in this case, the second physical UL channel is assigned a high priority. Conversely, if the overall standard (e.g., 3GPP new radio standard or specification) indicates that a low priority should be assumed in this scenario, the second physical UL channel is assigned a low priority.
[0090] Thereafter, at box 714, if the first UL channel has a lower priority compared to the second UL channel, the UE cancels the first UL channel; or if the second UL channel has a lower priority compared to the first UL channel, the UE cancels the second UL channel; or if the first and second UL channels have equal priority (for example, both are high or both are low), the UE multiplexes the first and second UL channels.
[0091] Figure 8 8 is a flow chart illustrating an exemplary process 800 that may be performed by a UE or other scheduled entity to assign priorities to physical UL channels in accordance with some aspects. In this example, two or more (multiple) DCIs indicate the same physical UL channel and request a single 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 the earlier DCI indicates the same priority or a different priority. In another example, if the multiple DCIs indicate different priorities (e.g., at least one indicates a low priority and at least one indicates a high priority), the high priority is assumed. Figure 6 and 7 Similar to the process of FIG. 8 , 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 requesting the use of a single HARQ-ACK feedback codebook (block 804).
[0092] At block 806, the UE receives at least one additional DCI (e.g., a second DCI), the at least one additional DCI requesting the use of a single HARQ-ACK codebook for a second physical UL channel. At block 808, the UE assigns priority to the second UL channel in the following manner: (a) based on the priority indicated in the most recent DCI, or (b) assigned as a high priority if the DCI has a different priority. As an example of (a), if the most recent DCI requesting a single 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 at block 804. Conversely, if the most recent DCI indicates a high priority, a high priority is assigned, also regardless of the priority of the DCI received at block 804. As an example of (b), if the most recent DCI requesting a single HARQ-ACK feedback for the second physical UL channel indicates a low priority, but the DCI received at block 804 indicates a high priority, a high priority is assigned. According to the example of (b), as long as at least one DCI has a high priority, a high priority is assigned. In this example, low priority is assigned only when all DCIs requesting single HARQ-ACK feedback for the second physical UL channel indicate low priority.
[0093] Thereafter, at block 810, if the first UL channel has a lower priority than the second UL channel, the UE cancels the first UL channel; or if the second UL channel has a lower priority than the first UL channel, the UE cancels the second UL channel; or if the first and second UL channels both have equal priority (e.g., both are high or both are low), the UE reuses the first and second UL channels. Whether option (a) or option (b) is used depends, for example, on the applicable wireless communication standard that specifies the operation of the UE and other components in the wireless communication system.
[0094] Fig. 9 900 is a flow chart illustrating an exemplary process 900 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 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 a second physical UL channel (e.g., a PUCCH triggered by a DCI requesting the use of a single HARQ-ACK feedback codebook) is assigned a high priority. Otherwise, if all PDSCHs for which HARQ-ACK is reported in the PUCCH are scheduled by a DCI with a priority indicator field set to 0, then the PUCCH is assigned a low priority.
[0095] As in the above process, the UE determines a priority for a first physical UL channel (block 902). The UE then receives a DCI that triggers a second physical UL channel requesting the use of a single HARQ-ACK feedback codebook (block 904). At block 906, the UE determines whether the HARQ-ACK bits reported for at least one given HARQ process corresponding to the PDSCH scheduled by the DCI in the single HARQ-ACK codebook have a priority indicator set to high priority. If so, a high priority is assigned to the second physical UL channel, and if not, a low priority is assigned to the second physical UL channel. Thereafter, at block 908, as already discussed, if the first UL channel has a lower priority than the second UL channel, the UE cancels the first UL channel; if the second UL channel has a lower priority than the first UL channel, the UE cancels the second UL channel; or if both the first and second UL channels have equal priority (e.g., both are high or both are low), the UE multiplexes the first and second UL channels.
[0096] Fig.10 1 is a flowchart illustrating an exemplary process 1000 that can be performed by a UE or other scheduled entity to multiplex physical UL channels according to some aspects. In this example, if the PUCCH with a single feedback has a high priority, the PUCCH is multiplexed with a low priority PUSCH (assuming time overlap). That is, instead of canceling the low priority PUSCH, the low priority PUSCH is multiplexed with a higher priority PUCCH. This can be particularly useful because the payload of a single HARQ-ACK may be large and the PUSCH may have more available resources. If the PUCCH with a single feedback has a low priority, the PUCCH can be multiplexed with a high priority PUSCH (assuming time overlap). That is, instead of canceling the low priority PUCCH, the low priority PUCCH is multiplexed with a high priority PUSCH. This can be useful because a single feedback includes HARQ-ACK for all HARQ processes, some of which may be associated with high priority ultra-reliable low latency communication (URLLC).
[0097] from Fig.10Beginning at block 1002 of , the UE determines a priority for a PUCCH with a single HARQ-ACK feedback. At block 1004, the UE determines a priority for a PUSCH that overlaps in time with the PUCCH. At block 1006, if the PUCCH has a high priority and the PUSCH has a low priority, the UE multiplexes the PUCCH with the overlapping PUSCH. At block 1008, if the PUCCH has a low priority and the PUSCH has a high priority, the UE multiplexes the PUCCH with the overlapping PUSCH. In addition, although in Fig.10 Not shown, but if PUCCH and PUSCH have equal priority, PUCCH and PUSCH can also be multiplexed. Fig.10 Focuses on the scenario where UL channels with unequal priorities are multiplexed. )
[0098] Fig.11 1 is a flowchart illustrating an exemplary process 1100 that can be performed by a UE or other scheduled entity to apply a single HARQ-ACK feedback configuration to two HARQ-ACK codebooks according to some aspects. In this example, two HARQ-ACK codebooks are provided to the UE via RRC using pdsch-HARQ-ACK-CodebookList. Specifically, in this example, if pdsch-HARQ-ACK-OneShotFeedback is configured, it is applied to two HARQ-ACK codebooks of two priorities. That is, a single feedback may be configured for both, or a single feedback may not be configured for all. For example, semi-static + single feedback is configured for the first priority, and dynamic + single feedback is configured for the second priority.
[0099] from Fig.11 Beginning at block 1102 of , the UE configures, receives, or obtains the first and second HARQ-ACK codebooks via RRC (e.g., via pdsch-HARQ-ACK-CodebookList). At block 1104, the UE applies a single-shot HARQ-ACK feedback configuration (e.g., via pdsch-HARQ-ACK-OneShotFeedback) to both the first and second HARQ-ACK codebooks. Thereafter, although Fig.11 Not shown in , but processing may continue to prioritize overlapping physical UL channels and then cancel or multiplex overlapping channels as already discussed.
[0100] Fig.121 is a flowchart illustrating an exemplary process 1200 that may be performed by a UE or other scheduled entity to apply a single HARQ-ACK feedback configuration to a HARQ-ACK codebook according to some aspects. The exemplary process 1200 may be employed when two HARQ-ACK codebooks are provided to the UE via RRC using pdsch-HARQ-ACK-CodebookList. However, in this example, single feedback is configured for two different priorities, respectively. Specifically, in this example, pdsch-HARQ-ACK-OneShotFeedback is configured separately. For example, only dynamic (no single feedback) is configured for the first priority, while dynamic + single is configured for the second priority. It should be noted that if single feedback is configured for only one of these priorities, then if the priority indicator field in the DCI indicates another priority, the DCI field "One-shotHARQ-ACK request" is set to 0.
[0101] from Fig.12 Starting at block 1202 of , the UE configures, receives, or obtains a first and a second HARQ-ACK codebook via RRC (e.g., via pdsch-HARQ-ACK-CodebookList). At block 1204, the UE applies a first HARQ-ACK feedback configuration to the first HARQ-ACK codebook, wherein, in some examples, the first HARQ-ACK is configured for single HARQ-ACK feedback (e.g., via pdsch-HARQ-ACK-OneShotFeedback), while in other examples, it is not configured for single HARQ-ACK feedback. At block 1206, the UE applies a second HARQ-ACK feedback configuration to the second HARQ-ACK codebook, wherein, in some examples, the second HARQ-ACK is configured for single HARQ-ACK feedback, while in other examples, it is not configured for single HARQ-ACK feedback. At block 1208, if single-shot feedback is configured for only one of the priorities, then if the priority indicator field in the DCI indicates another priority, the DCI field "One-shot HARQ-ACK request" is set to 0. In other words, if single-shot HARQ-ACK feedback is configured for the first priority but not the second priority, the DCI with the priority indicator field set to the second priority value will include a single-shot HARQ-ACK request field set to zero.
[0102] Turning now to CBGs, a UE may be configured with a maximum number of CBGs in a component carrier (CC) / serving cell (e.g., via parameter codeBlockGroupTransmission, including maxCodeBlockGroupsPerTransportBlock, which may be set to 2, 4, 6, or 8 as the maximum number of CBGs per TB, which is determined by denoted by ). If so, the UE reports CBG-based HARQ-ACK (with one-bit A / N for each CBG for a given TB). A single (type 3) codebook may be configured to report 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 corresponding to two priorities are configured (e.g., via the RRC parameter pdsch-CodeBlockGroupTransmissionList-r16): and However, for single (type 3), as described above, feedback for all HARQ-IDs is reported regardless of priority in Release 16. Therefore, issues may arise regarding the maximum number of CBGs per TB to be used.
[0103] In the first CBG-based single HARQ-ACK example, the maximum number of CBGs per TB to be used is determined as follows. When the maximum number of CBGs per TB corresponding to two different priorities is provided to the UE in a given CC ( and ), and the UE is configured to report CBG-based HARQ-ACK in a single feedback report, and when the UE is requested to report a single feedback via DCI, the maximum of the two numbers is selected. That is, the number of HARQ-ACK bits for each TB of the HARQ process number for the CC in a single feedback is determined by In this case, if the actual number of CBGs for a given TB for a 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.
[0104] Fig.131 is a flow chart illustrating an exemplary process 1300 that may be performed by a UE or other scheduled entity to insert a NACK value into a vacant bit position in a codebook according to some aspects. Beginning at block 1302 of process 1300, the UE configures, receives, or obtains first and second maximum CBG numbers per TB for first and second priorities for a particular CC, e.g., ( and ). At block 1304, the UE determines whether the UE is requested to report using single HARQ-ACK feedback. If so, the UE sets the number of HARQ-ACK bits for each TB of the HARQ process for the specific CC based on a maximum value, which is 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, for example: bits.
[0105] In the second CBG-based single HARQ-ACK example, the maximum number of CBGs per TB to be used is determined as follows. The priority indicator field of the DCI requesting a single feedback determines the maximum number of CBGs and the number of HARQ-ACK bits for each TB for the HARQ process number for the CC in a single feedback. This option also applies when two maximum numbers of CBGs per TB in a given CC corresponding to two different priorities are provided to the UE, the UE is configured to report CBG-based HARQ-ACK in a single feedback report, and the UE is requested to report a single feedback via DCI. For example, if the priority indicator field is 0, the first maximum number of CBGs is used; if the priority indicator field is 1, the second maximum number of CBGs is used. If the TB is initially scheduled to have a larger number of CBGs than the maximum number of CBGs determined for a single (type 3) HARQ-ACK purpose, the UE generates HARQ-ACK bits for a new CBG including two or more original CBGs by applying a binary AND operation to the HARQ-ACK information bits corresponding to the original CBGs. (By binary AND, this means: 0 AND 0 → 0; 0 AND 1 → 0; 1 AND 0 → 0; and 1 AND 1 → 1.)
[0106] Fig.1414 is a flowchart illustrating an exemplary process 1400 that may be performed by a UE or other scheduled entity to insert a NACK value into a vacant bit position in a codebook according to some aspects. Starting from box 1402 of process 1400, the UE configures, receives, or obtains a first and a second maximum number of CBGs per TB for a first and a second priority for a particular component carrier CC. Here, the priority indicator field of the DCI requesting a single HARQ-ACK feedback determines the maximum number of CBGs and the number of HARQ-ACK bits per TB for the HARQ process number for the particular CC in a single feedback. At box 1404, if the priority indicator field of the DCI is set to indicate a first priority, the UE uses or selects the first maximum number of CBGs, and if the priority indicator field in the DCI is set to indicate a second priority, the UE uses or otherwise selects the second maximum number of CBGs. At box 1406, if the TB was initially scheduled to have a greater number of CBGs than the first or second maximum number of CBGs, the UE generates HARQ-ACK bits for new CBGs including two or more original CBGs, wherein the HARQ-ACK bits are generated by applying a binary AND operation to the HARQ-ACK bits corresponding to the original CBGs.
[0107] In the third CBG-based single HARQ-ACK example, if the maximum number of CBGs for the two priorities is different, or only one of the priorities is CBG-based, the UE will only be expected to be configured with TB-level A / N reporting for a single (e.g., the UE is not expected to be configured with CBG-based feedback for a single feedback). In this example, the UE is configured with TB-level ACK / NACK reporting for a single feedback without using CBG-based feedback for a single feedback.
[0108] Fig.15 15 is a flow chart illustrating an exemplary 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 process 1500, the UE obtains first and second maximum numbers of CBGs per TB for first and second priorities for a particular CC, or 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 only one is CBG-based), the UE configures TB-level ACK / NACK reporting for single feedback, rather than using CBG-based feedback for single feedback.
[0109] Fig.16is a block diagram illustrating an example of a hardware implementation for a scheduling entity 1600 employing a processing system 1614 capable of processing HARQ-ACK, including both priority-based HARQ-ACK and single-shot HARQ-ACK, in accordance with some aspects.
[0110] In one example, Fig.16 The scheduling entity 1600 in may be a base station or gNB as shown in any one or more of the other figures (but it may also be a UE).
[0111] The scheduling entity 1600 can be implemented using a processing system 1614 including one or more processors 1604. Examples of processors 1604 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, the scheduling entity 1600 can be configured to perform any one or more of the functions described herein. That is, the processor 1604 as utilized in the scheduling entity 1600 can be used to implement any one or more of the processes and procedures described elsewhere herein.
[0112] In some cases, the processor 1604 may be implemented via a baseband or modem chip, while in other implementations, the processor 1604 may include multiple devices that are distinct and different from the baseband or modem chip (e.g., in such scenarios that can work together to implement the examples discussed herein). And as described above, various hardware arrangements and components outside of the baseband modem processor may be used in various implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.
[0113] exist Fig.16In the example of , the processing system 1614 can be implemented using a bus architecture, which is generally represented by bus 1602. Depending on the specific application and overall design constraints of the processing system 1614, the bus 1602 may include any number of interconnecting buses and bridges. The bus 1602 communicatively couples various circuits including one or more processors (which are generally represented by processor 1604), memory 1605, and computer-readable media (which are generally represented by computer-readable media 1606). The 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 are therefore not further described. The bus interface 1608 provides an interface between the bus 1602 and the transceiver 1610. The transceiver 1610 provides a communication interface or unit for communicating with various other devices on a transmission medium. Depending on the nature of the device, a user interface 1612 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be provided.
[0114] In some aspects of the present disclosure, the processor 1604 may include circuits 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 single HARQ-ACK processing circuit 1642, and a UL / DL processing circuit 1644.
[0115] The processor 1604 is responsible for managing the bus 1602 and 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 the various functions described below for any particular device. The computer-readable medium 1606 and the memory 1605 may also be used to store data that the processor 1604 manipulates when executing the software.
[0116] One or more processors 1604 in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc. The software can be located on a computer-readable medium 1606. The computer-readable medium 1606 can be a non-transitory computer-readable medium. For example, a non-transitory computer-readable medium includes a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic tape), an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a smart card, a flash memory device (e.g., a card, a stick or a key drive), a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. For example, computer readable media may also include carrier waves, transmission lines, and any other suitable media for sending software and / or instructions that can be accessed and read by a computer. Computer readable media 1606 may be located in processing system 1614, outside processing system 1614, or distributed among multiple entities including processing system 1614. Computer readable media 1606 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium with packaging materials. Those skilled in the art will recognize how to best implement the functions provided throughout this disclosure according to specific applications and the overall design constraints imposed on the entire system.
[0117] 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 single HARQ-ACK processing executable by the single HARQ-ACK processing circuit 1642, and code 1656 for UL / DL processing executable by the UL / DL processing circuit 1644.
[0118] Fig.171 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 present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1714 including 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.
[0119] Processing system 1714 may be substantially similar to that described in Fig.16 The processing system 1614 shown in , includes a bus interface 1708, a bus 1702, a memory 1705, a processor 1704, a computer-readable medium 1706, a user interface 1712 and a transceiver 1710 (communication interface), which is similar to those described above and therefore many details of the system architecture will not be described again. In some cases, the processor 1704 can be implemented via a baseband or modem chip, while in other implementations, the processor 1702 can include multiple devices that are distinct and different from the baseband or modem chip (for example, in such a scenario that can work together to implement the examples discussed herein). And as described above, various hardware arrangements and components outside the baseband modem processor can be used in various implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.
[0120] The processor 1704 as utilized in the scheduled entity 1700 may be used to implement one or more of the various processes described herein for use by the 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 indicated priorities; a single HARQ-ACK processing circuit 1742 configured for single HARQ-ACK processing, including processing a single codebook; and a UL channel priority determination circuit 1744 configured for using Figure 4-16 The various processes of determining UL channel priority and canceling or multiplexing overlapping channels. Figure 4-16 According to the various processes shown in , the processing circuits 1740 and 1742 may include a processing circuit configured to obtain and / or configure multiple HARQ-ACK codebooks, wherein the multiple HARQ-ACK codebooks include priority-based HARQ-ACK codebooks with different priorities and separate single HARQ-ACK codebooks. Figure 4-16In the various processes shown in , circuit 1744 may include a processing circuit configured to process a first physical uplink channel and a second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes a single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of a priority-based HARQ-ACK codebook.
[0121] Computer readable storage medium 1706 may include software executable by processor 1704, which is configured to implement one or more of the functions described elsewhere herein. Figure 4-16 In the various processes shown in the computer-readable storage medium 1706, the computer-readable storage medium 1706 may include: a code 1752 for priority-based HARQ-ACK processing that can be executed by a priority-based HARQ-ACK processing circuit 1740; a code 1754 for single HARQ-ACK processing that can be executed by a single-based HARQ-ACK processing circuit 1742; and a code 1756 for determining UL channel priority and canceling or multiplexing overlapping channels that can be executed by a UL channel priority determination circuit 1744.
[0122] Fig.18 1 is a flow chart 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 of the illustrated features may not be required for all example implementations. The communication method 1800 may be performed, for example, by any of the scheduled entities (such as UEs) shown in these figures, or by other appropriately equipped systems, devices, or apparatuses including wireless communication devices.
[0123] At block 1802, the wireless communication device obtains a plurality of HARQ-ACK codebooks, wherein the plurality of HARQ-ACK codebooks include priority-based HARQ-ACK codebooks with different priorities and separate single HARQ-ACK codebooks. For example, the priority-based HARQ-ACK processing circuit 1640 in conjunction with the above Fig.16 The single HARQ-ACK processing circuit 1642 shown and described together may provide means for obtaining multiple HARQ-ACK codebooks.
[0124] At block 1804, the wireless communication device processes a first physical uplink channel and a second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes a single HARQ-ACK codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook. For example, the above in conjunction with Fig.16 The UL / DL processing circuit 1644 shown and described, along with the priority-based HARQ-ACK processing circuit 1640 and the single HARQ-ACK processing circuit 1642, may provide means for processing a first physical uplink channel and a second physical uplink channel.
[0125] In one configuration, an apparatus for wireless communication includes means for performing the methods and processes described above, including means for communicating as described above. In one aspect, the means may be Fig.16 and Fig.17 A processor configured to perform the functions recorded by the above-mentioned units. In another aspect, the above-mentioned units may be circuits or any devices configured to perform the functions recorded by the above-mentioned units.
[0126] Fig.19 1 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, a processing system 1914 including one or more processors 1904 may be utilized to implement an element or any portion of an element or any combination of elements. The processing system 1914 may be substantially similar to the one described in Fig.16 and 17 The processing system 1614 shown in the figure 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 unit for communicating with various other devices on a transmission medium. The transceiver 1910 includes one or more receivers 1911 and one or more transmitters 1913. The receiver 1911 is coupled to an antenna set 1915. The transmitter 1913 is coupled to the same or different antenna set 1917. The antenna set can be used for beamforming. Depending on the nature of the device, a user interface 1912 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be provided.
[0127] In some cases, the processor 1904 may be implemented via a baseband or modem chip, while in other implementations, the processor 1904 may include multiple devices that are distinct and different from the baseband or modem chip (e.g., in such scenarios that can work together to implement the examples discussed herein). And as described above, various hardware arrangements and components outside of the baseband modem processor may be used in various implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.
[0128] The processor 1904 as used in 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 single / type 3); a physical channel processing circuit 1944; and a DCI processing circuit 1946, wherein these circuits are configured to perform functions corresponding to or complementary to the various UE-side functions or operations described herein. In this regard, the base station may generate and send a signal for configuring the UE to provide HARQ feedback for different CORESET groups. In addition, the base station may configure the UE to have one or more codebooks to be used 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 semi-static type 1 HARQ-ACK codebook) and / or a single type 3 HARQ-ACK codebook. The codebook may be stored in the memory 1905.
[0129] The computer-readable storage medium 1906 may include software executable by the processor 1904, which is 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 HARQ-ACK codebooks (e.g., type 1, type 2, and single / type 3) that can be executed by the HARQ-ACK codebook management circuit 1940; code 1956 for physical channel processing that can be executed by the physical channel processing circuit 1944; and code 1958 for DCI processing that can be executed by the DCI processing circuit 1946.
[0130] Fig. 20 2004 (e.g., UE or scheduled entity) using a processing system 2014. According to various aspects of the present disclosure, an element or any portion of an element 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 substantially similar to the one described in Figure 16-1719, 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 unit for communicating with various other devices on a transmission medium. The transceiver 2010 includes one or more receivers 2011 and one or more transmitters 2013. The receiver 2011 is coupled to an antenna set 2015. The transmitter 2013 is coupled to the same or different antenna set 2017. The antenna set can be used for beamforming. Depending on the nature of the device, a user interface 2012 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be provided.
[0131] In some cases, the processor 2004 may be implemented via a baseband or modem chip, while in other implementations, the processor 2004 may include multiple devices that are distinct and different from the baseband or modem chip (e.g., in such scenarios that can work together to implement the examples discussed herein). And as described above, various hardware arrangements and components outside of the baseband modem processor may be used in various implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.
[0132] The processor 2004 as used in the wireless communication device 2000 can be used to implement one or more of the various processes described herein for use by the UE. In some aspects of the present disclosure, the processor 2004 includes: a HARQ-ACK codebook receiving / management circuit 2040, which is configured to receive / manage codebooks (e.g., type 1, type 2, and single / type 3); a priority-based physical channel processing circuit 2044; and a DCI processing circuit 2046, wherein these circuits are configured to perform functions corresponding to or complementary to the various base station side functions or operations described herein. For example, the HARQ-ACK codebook receiving / management circuit 2040 provides a circuit configured to perform the following operations: obtain multiple HARQ-ACK codebooks, wherein the multiple HARQ-ACK codebooks include priority-based HARQ-ACK codebooks with different priorities and separate single HARQ-ACK codebooks.
[0133] The computer-readable storage medium 2006 may include software executable by the processor 2014, which is 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 HARQ-ACK codebooks (e.g., type 1, type 2, and single-shot / type 3) executable by the HARQ-ACK codebook receiving / management 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 codebook may be stored in the memory 2005.
[0134] The HARQ-ACK codebook receiving / management circuit 2040 may be configured to obtain one or more HARQ-ACK codebooks, including priority-based HARQ-ACK codebooks and separate single codebooks with different priorities. The HARQ-ACK codebook receiving / management 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 according to information stored in the UE. The HARQ-ACK codebook receiving / management circuit 2040 may be additionally or alternatively 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 otherwise obtain or determine DCI. 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.
[0135] The priority-based physical channel processing circuit 2044 can be configured to process the first physical uplink channel and the second physical uplink channel based at least in part on the priority of the first physical uplink channel and the priority of the second physical uplink channel, wherein one of the first physical uplink channel and the second physical uplink channel includes a single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of the priority-based HARQ-ACK codebook. In some examples, the priority-based HARQ-ACK codebook includes one or more of a type 1 semi-static codebook (having a first and a second priority, such as high and low) and a type 2 dynamic codebook (having a first and a second priority, such as high and low), and the single HARQ-ACK codebook includes a type 3 codebook.
[0136] In some aspects, the HARQ-ACK codebook receiving / managing circuit 2040 provides a unit for obtaining multiple HARQ-ACK codebooks, wherein the multiple HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks with different priorities. The priority-based physical channel processing circuit 2044 provides a unit for processing a first physical uplink channel and a second physical uplink channel based at least in part on the priority of the first physical uplink channel and the priority of the second physical uplink channel, wherein one of the first physical uplink channel and the second physical uplink channel includes a single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of the priority-based HARQ-ACK codebook.
[0137] In some aspects, code 2052 for receiving / managing HARQ-ACK codebooks provides instructions that can be executed by one or more processors of a wireless communication device to perform the following operations: obtain multiple HARQ-ACK codebooks, wherein the multiple HARQ-ACK codebooks include priority-based HARQ-ACK codebooks with different priorities and separate single HARQ-ACK codebooks. Priority-based physical channel processing code 2056 provides instructions that can be executed by one or more processors of a wireless communication device to perform the following operations: process a first physical uplink channel and a second physical uplink channel based at least in part on the priority of the first physical uplink channel and the priority of the second physical uplink channel, wherein one of the first physical uplink channel and the second physical uplink channel includes a single HARQ-ACK codebook, and wherein the processing is performed in conjunction with the use of the priority-based HARQ-ACK codebook.
[0138] exist Fig.21 Additional features of the priority-based physical channel processing circuit 2044 for use with single HARQ-ACK feedback are shown in FIG.
[0139] In some aspects, such as in Fig.21As shown in box 2102 of , the priority-based physical channel processing circuit 2044 is configured to process a first physical uplink channel and a second physical uplink channel (wherein one of these channels uses single HARQ-ACK feedback) by the following operations: when the first physical uplink channel and the second physical uplink channel overlap in time, cancel one of the first physical uplink channel and the second physical uplink channel based on the corresponding priority of each of the first physical uplink channel and the second physical uplink channel. That is, a circuit is provided for canceling one of the two physical UL channels based on the corresponding priority of the two physical UL channels (when one of these channels uses single HARQ-ACK feedback) when the two UL channels overlap in time. For example, see Figure 5-10 .
[0140] In some aspects, such as in Fig.21 As shown in block 2104 of , the priority-based physical channel processing circuit 2044 is configured to process the first physical uplink channel and the second physical uplink channel by: when the first physical uplink channel and the second physical uplink channel overlap in time and have equal priority, multiplexing the first physical uplink channel and the second physical uplink channel. For example, see Figure 7-8 That is, circuitry is provided for multiplexing two physical UL channels when the two UL channels overlap in time and have equal priority (when one of the channels uses single feedback).
[0141] In some aspects, at least one of the first physical uplink channel and the second physical uplink channel comprises a PUCCH or a PUSCH. Figure 4 .
[0142] In some aspects, the priority-based physical channel processing circuit 2044 is configured to process a first physical uplink channel and a second physical uplink channel by: determining a priority for the first physical uplink channel; receiving (via the DCI processing circuit 2046) a DCI triggering a second physical uplink channel requesting use of a single HARQ-ACK codebook; assigning a priority to the second physical uplink channel; and canceling the first physical uplink channel when the first physical uplink channel has a lower priority than the second physical uplink channel, canceling the second physical uplink channel when the second physical uplink channel has a lower priority than the first physical uplink channel, and multiplexing the first physical uplink channel and the second physical uplink channel when both the first physical uplink channel and the second physical uplink channel have equal priority. For example, see Figure 6 .
[0143] In some aspects, such as in Fig.21 As shown in block 2106 of , 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 without considering the priority indicator field of the DCI. That is, a circuit is provided for assigning a priority to the physical UL channel without considering the DCI. For example, see Figure 6 In other aspects, such as in Fig.21 As shown in block 2108 of , the priority-based physical channel processing circuit 2044 is configured to assign priority to the second physical uplink channel by: determining whether the DCI includes an indication of priority; and, in response to the DCI including an indication of priority, selecting a priority for the second physical uplink channel based on the DCI; or, in response to the DCI not including an indication of priority, selecting a priority for the second physical uplink channel based on a predetermined priority set to low or high. That is, a circuit is provided for assigning priority to a physical UL channel based on a DCI having a priority indicator. For example, see Figure 7 .
[0144] In some aspects, such as in Fig.21 As shown in block 2110 of , the priority-based physical channel processing circuit 2044 is further configured to: receive (via DCI processing circuit 2046) an additional DCI requesting a single HARQ-ACK codebook and including a priority indicator for a second physical uplink channel; and select a priority for the second physical uplink channel based on the priority indicator of the additional DCI. That is, circuitry is provided for assigning priorities to physical UL channels based on a second or additional DCI having a priority indicator. For example, see Figure 8 .
[0145] In other aspects, the priority-based physical channel processing circuit 2044 is further configured to: receive an additional DCI requesting a single HARQ-ACK codebook and including a priority indicator different 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. For example, see Figure 8 .
[0146] 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 a high priority when at least one reported HARQ-ACK bit for a given HARQ process corresponding to a PDSCH scheduled by a DCI in a single HARQ-ACK codebook has a priority indicator 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. For example, see Fig. 9 .
[0147] In some aspects, at least one of the first physical uplink channel and the second physical uplink channel is a PUCCH with a single HARQ-ACK codebook, and the other of the first physical uplink channel and the second physical uplink channel is a PUSCH that overlaps with the PUCCH in time. In this case, the priority-based physical channel processing circuit 2044 can be configured to process the first physical uplink channel and the second physical uplink channel by: when the PUCCH with a single HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority, multiplexing the PUCCH with the PUSCH; and when the PUCCH with a single HARQ-ACK feedback codebook has a low priority and the PUSCH has a high priority, multiplexing the PUCCH with the PUSCH. For example, see Fig.10 .
[0148] In some aspects, the HARQ-ACK codebook receiving / managing circuit 2040 is further configured to: obtain the first HARQ-ACK codebook and the second HARQ-ACK codebook via RRC configuration; and provide single HARQ-ACK feedback via RRC configuration. In this case, as in Fig.21 As shown in block 2112 of , the priority-based physical channel processing circuit 2044 may be configured to apply a single HARQ-ACK feedback configuration to both the first HARQ-ACK codebook and the second HARQ-ACK codebook. Fig.11 and 12 .
[0149] In some aspects, the priority-based physical channel processing circuit 2044 can be configured to work with a first maximum number of CBGs per TB and a second maximum number of CBGs per TB for a CC for a first priority and a second priority, respectively, and if so, Fig.21As represented by the block 2114 of , the priority-based physical channel processing circuit 2044 is further configured to: set the number of HARQ-ACK bits for each TB of a single HARQ feedback process for a specific CC based on a maximum value, which is the larger of the number of HARQ-ACK bits configured for the first priority and the number of HARQ-AK bits configured for the second priority. For example, see Figure 13-15 .
[0150] Of course, in the above example, Figure 16-17 and 18-21 are provided only as examples, and other units for performing the described functions may be included in various aspects of the present disclosure, including but not limited to Figure 16-17 and instructions stored in a computer-readable storage medium of 18-21, or any other suitable device or unit described in any of these figures and utilizing, for example, the processes and / or algorithms described herein with respect to these figures.
[0151] The following provides an overview of examples of the present disclosure.
[0152] Example 1: A wireless communication device, comprising: a transceiver; a memory; and a processor, which is communicatively coupled to the transceiver and the memory, wherein the processor is configured to: obtain a plurality of HARQ-ACK codebooks, wherein the plurality of HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks having different priorities; and process the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with use of the priority-based HARQ-ACK codebook.
[0153] Example 2: A wireless communication device according to Example 1, wherein the priority-based HARQ-ACK codebook is configured as one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and wherein the single HARQ-ACK codebook is configured as a type 3 codebook.
[0154] Example 3: A wireless communication device according to Example 1 or 2, wherein the processor is further configured to process the first physical uplink channel and the second physical uplink channel by: when the first physical uplink channel and the second physical uplink channel overlap in time, canceling one of the first physical uplink channel and the second physical uplink channel based on the corresponding priority of each of the first physical uplink channel and the second physical uplink channel.
[0155] Example 4: A wireless communication device according to Example 1 or 2, wherein the processor is further configured to process the first physical uplink channel and the second physical uplink channel by: multiplexing the first physical uplink channel and the second physical uplink channel when the first physical uplink channel and the second physical uplink channel overlap in time and have equal priority.
[0156] Example 5: A wireless communication device according to Example 1, 2, 3 or 4, wherein the first physical uplink channel and the second physical uplink channel include one or more of PUCCH and PUSCH.
[0157] Example 6: A wireless communication device according to Example 1, 2, 3, 4 or 5, wherein the processor is further configured to process the first physical uplink channel and the second physical uplink channel by: determining a priority for the first physical uplink channel; receiving a DCI triggering the second physical uplink channel requesting use of the single HARQ-ACK codebook; assigning a priority to the second physical uplink channel; and when the first physical uplink channel has a lower priority than the second physical uplink channel, canceling the first physical uplink channel; when the second physical uplink channel has a lower priority than the first physical uplink channel, canceling the second physical uplink channel; and when the first physical uplink channel and the second physical uplink channel have equal priority, multiplexing the first physical uplink channel and the second physical uplink channel.
[0158] Example 7: A wireless communication device according to Example 1, 2, 3, 4, 5 or 6, wherein the processor is further configured to assign the priority to the second physical uplink channel by performing the following operations: assigning a high priority to the second physical uplink channel without considering the priority indicator field of the DCI.
[0159] Example 8: A wireless communication device according to Example 1, 2, 3, 4, 5 or 6, wherein the processor is further configured to assign the priority to the second physical uplink channel by: determining whether the DCI includes an indication of the priority; in response to the DCI including the 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 the indication of the priority, selecting the priority for the second physical uplink channel based on a predetermined priority set to low or high.
[0160] Example 9: A wireless communication device according to Example 1, 2, 3, 4, 5, 6 or 8, wherein the processor is further configured to: receive an additional DCI for the second physical uplink channel, the additional DCI requesting the single HARQ-ACK codebook and including a priority indicator; and select the priority for the second physical uplink channel based on the priority indicator of the additional DCI.
[0161] Example 10: A wireless communication device according to Example 1, 2, 3, 4, 5, 6 or 8, wherein the processor is further configured to: receive an additional DCI, the additional DCI requesting the single HARQ-ACK codebook and including a priority indicator different from the indication of the priority in the DCI; and select the priority for the second physical uplink channel by assigning a high priority to the second physical uplink channel.
[0162] Example 11: A wireless communication device according to Example 1, 2, 3, 4, 5 or 6, wherein the processor is further configured to assign the priority to the second physical uplink channel by: when at least one reported HARQ-ACK bit for a given HARQ process corresponding to the PDSCH scheduled by the DCI in the single HARQ-ACK codebook has a priority indicator field set to high priority, setting the priority of the second physical uplink channel to high priority; and when the priority indicator field is set to low priority, setting the priority of the second physical uplink channel to low priority.
[0163] Example 12: A wireless communication device according to Example 1, 2, 3, 4 or 5, wherein at least one of the first physical uplink channel and the second physical uplink channel is a PUCCH with the single HARQ-ACK codebook, and the other of the first physical uplink channel and the second physical uplink channel is a PUSCH that overlaps with the PUCCH time, and wherein the processor is further configured to process the first physical uplink channel and the second physical uplink channel by: when the PUCCH with the single HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority, multiplexing the PUCCH with the PUSCH; and when the PUCCH with the single HARQ-ACK feedback codebook has the low priority and the PUSCH has the high priority, multiplexing the PUCCH with the PUSCH.
[0164] Example 13: A wireless communication device according to Example 1, 2, 3, 4 or 5, wherein the processor is further configured to: obtain a first HARQ-ACK codebook and a second HARQ-ACK codebook via a radio resource control (RRC) configuration, and provide a single HARQ-ACK feedback via the RRC configuration, and wherein the processor is further configured to: apply the single HARQ-ACK feedback configuration to both the first HARQ-ACK codebook and the second HARQ-ACK codebook.
[0165] Example 14: A wireless communication device according to Example 1, 2, 3, 4 or 5, wherein the processor is also configured for use with a second maximum number of CBGs per TB for a first TB for a first priority and a second priority, respectively, for a CC, and wherein the processor is further configured to: set the number of HARQ-ACK bits for each TB for a single HARQ feedback process for a specific CC based on a maximum value, the maximum value being 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.
[0166] Example 15: A method for wireless communication by a wireless device in a communication network, the method comprising: obtaining a plurality of HARQ-ACK codebooks, wherein the plurality of HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks having different priorities; and processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with use of the priority-based HARQ-ACK codebook.
[0167] Example 16: The method of Example 15, wherein the priority-based HARQ-ACK codebook comprises one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and wherein the single HARQ-ACK codebook comprises a type 3 codebook.
[0168] Example 17: A method according to Example 15 or 16, wherein the processing of the first physical uplink channel and the second physical uplink channel also includes: when the first physical uplink channel and the second physical uplink channel overlap in time, canceling one of the first physical uplink channel and the second physical uplink channel based on the corresponding priority of each of the first physical uplink channel and the second physical uplink channel.
[0169] Example 18: A method according to Example 15 or 16, wherein the processing of the first physical uplink channel and the second physical uplink channel further includes: when the first physical uplink channel and the second physical uplink channel overlap in time and have equal priority, multiplexing the first physical uplink channel and the second physical uplink channel.
[0170] Example 19: A method according to Example 15, 16, 17 or 18, wherein the first physical uplink channel and the second physical uplink channel include one or more of PUCCH and PUSCH.
[0171] Example 20: A method according to Example 15, 16, 17, 18 or 19, wherein the processing of the first physical uplink channel and the second physical uplink channel includes: determining a priority for the first physical uplink channel; receiving a DCI triggering the second physical uplink channel requesting use of the single HARQ-ACK codebook; assigning a priority to the second physical uplink channel; and when the first physical uplink channel has a lower priority than the second physical uplink channel, canceling the first physical uplink channel; when the second physical uplink channel has a lower priority than the first physical uplink channel, canceling the second physical uplink channel; and when the first physical uplink channel and the second physical uplink channel have equal priority, multiplexing the first physical uplink channel and the second physical uplink channel.
[0172] Example 21: A method according to Example 15, 16, 17, 18, 19 or 20, wherein the assigning the priority to the second physical uplink channel includes: assigning a high priority to the second physical uplink channel regardless of the priority indicator field of the DCI.
[0173] Example 22: A method according to Examples 15, 16, 17, 18, 19 or 20, wherein the assigning of the priority to the second physical uplink channel includes: determining whether the DCI includes an indication of the priority; in response to the DCI including the 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 the indication of the priority, selecting the priority for the second physical uplink channel based on a predetermined priority set to low or high.
[0174] Example 23: The method according to Example 15, 16, 17, 18, 19, 20 or 22 also includes: receiving an additional DCI for the second physical uplink channel, the additional DCI requesting the single 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.
[0175] Example 24: The method according to Example 15, 16, 17, 18, 19, 20 or 22 also includes: receiving an additional DCI, the additional DCI requesting the single HARQ-ACK codebook and including a priority indicator different from the indication of the 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.
[0176] Example 25: A method according to Examples 15, 16, 17, 18, 19 or 20, wherein the assigning of the 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 for a given HARQ process corresponding to the PDSCH scheduled by the DCI in the single HARQ-ACK codebook 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.
[0177] Example 26: A method according to Example 15, 16, 17, 18 or 19, wherein at least one of the first physical uplink channel or the second physical uplink channel is a PUCCH with a single HARQ-ACK codebook, and the other of the first physical uplink channel and the second physical uplink channel is a PUSCH that overlaps with the PUCCH in time, and wherein the processing of the first physical uplink channel and the second physical uplink channel includes: when the PUCCH with the single HARQ-ACK feedback codebook has a high priority and the PUSCH has a low priority, multiplexing the PUCCH with the PUSCH; and when the PUCCH with the single HARQ-ACK feedback codebook has the low priority and the PUSCH has the high priority, multiplexing the PUCCH with the PUSCH.
[0178] Example 27: The method of Example 15, 16, 17, 18 or 19 further includes: obtaining a first HARQ-ACK codebook and a second HARQ-ACK codebook via an RRC configuration; and applying the single HARQ-ACK feedback configuration to both the first HARQ-ACK codebook and the second HARQ-ACK codebook using the RRC configuration.
[0179] Example 28: A method according to Example 15, 16, 17, 18 or 19, wherein the wireless device is configured to have a second maximum number of CBGs per TB having a first maximum number of CBGs per TB for a CC for a first priority and a second priority, respectively, and wherein the method further includes: setting the number of HARQ-ACK bits for each TB for a single HARQ feedback process for a specific CC based on a maximum value, the maximum value being 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.
[0180] Example 29: An apparatus for use in a wireless communication device of a wireless communication network, comprising: a unit for obtaining a plurality of HARQ-ACK codebooks, wherein the plurality of HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks having different priorities; and a unit for processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with use of the priority-based HARQ-ACK codebook.
[0181] Example 30: An article for use with a wireless communication device of a wireless communication network, the article comprising: a computer-readable medium having instructions stored therein executable by one or more processors of the wireless communication device to perform the following operations: obtain multiple HARQ-ACK codebooks, wherein the multiple HARQ-ACK codebooks include priority-based HARQ-ACK codebooks and separate single HARQ-ACK codebooks having different priorities; and process the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes the single HARQ-ACK codebook, and wherein the processing is performed in conjunction with use of the priority-based HARQ-ACK codebook.
[0182] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.
[0183] For example, various aspects may be implemented in 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 the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented in 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 telecommunication standard, network architecture, and / or communication standard used will depend on the specific application and the overall design constraints imposed on the system.
[0184] Although various aspects and embodiments are described in this application by the description of some examples, it will be understood by those skilled in the art that additional implementations and use cases may be generated in many different arrangements and scenarios. The features described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses can be generated via integrated chip embodiments and other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicable scopes for the described innovations. Implementations may have a range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some actual settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., having different sizes, shapes, and configurations.
[0185] In this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to 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, objects A and C can still be considered to be coupled to each other—even if they are not directly physically in contact with each other. For example, a first object can be coupled to a second object even if the first object has never been directly physically in contact with the second object. The terms "circuit" and "circuitry" may be used broadly and are intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the functions described in the present disclosure to be performed (without limitation as to the type of electronic circuitry) and software implementations of information and instructions that, when executed by a processor, enable the functions described in the present disclosure to be performed.
[0186] exist Figure 1-21 One or more of the components, steps, features, and / or functions shown in the present disclosure may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , 2 , 16, 18 and 19-21 can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware. In general, in Figure 1-21 The various components, steps, features and / or functions shown in the description are not mutually exclusive.
[0187] It will be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. It will be understood that the specific order or hierarchy of steps in these methods may be rearranged based on design preferences. The accompanying method claims present elements of the various steps in an example order and are not intended to be limited to the specific order or hierarchy presented unless specifically recited therein.
[0188] To enable any person skilled in the art to implement the various aspects described herein, a previous description is provided. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but are given a full range consistent with the language of the claims, wherein, unless otherwise specifically stated, reference to an element in the singular form is not intended to mean "one and only one", but to mean "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. A phrase referring to "at least one" in a list of items refers to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure are expressly incorporated herein by reference, and are intended to be included in the claims, wherein these structural and functional equivalents are known or will be known to those skilled in the art. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in a claim. No claim element is to be construed under 35 U.S.C. §112(f) unless the element is explicitly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.”
Claims
1. A wireless communication device, comprising: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook; wherein at least one of the first physical uplink channel or the second physical uplink channel is a physical uplink control channel (PUCCH), and the other of the first physical uplink channel or the second physical uplink channel is a physical uplink shared channel (PUSCH) that overlaps with the PUCCH in time; and Wherein, the processor is further configured to: When the PUCCH having the single HARQ-ACK codebook has a high priority and the PUSCH has a low priority, multiplexing the PUCCH with the PUSCH; and When the PUCCH having the single HARQ-ACK codebook has the low priority and the PUSCH has the high priority, the PUCCH is multiplexed with the PUSCH.
2. The wireless communication device according to claim 1, in, The priority-based HARQ-ACK codebook is configured as one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and The single HARQ-ACK codebook is configured as a type 3 codebook.
3. The wireless communication device according to claim 1, in, The processor is further configured to obtain a first HARQ-ACK codebook and a second HARQ-ACK codebook via a radio resource control (RRC) configuration, and provide a single HARQ-ACK feedback via the RRC configuration, and The processor is further configured to: apply a single HARQ-ACK feedback configuration to both the first HARQ-ACK codebook and the second HARQ-ACK codebook.
4. The wireless communication device according to claim 1, in, The processor is further configured to use with a first maximum number of code block groups (CBGs) per transport block (TB) and a second maximum number of CBGs per TB for a component carrier (CC) for a first priority and a second priority, respectively, and The processor is also configured to set the number of HARQ-ACK bits for each TB of a single HARQ feedback process for a specific CC based on the maximum value of 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.
5. A method for wireless communication by a wireless device in a communication network, the method comprising: processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook; wherein at least one of the first physical uplink channel or the second physical uplink channel is a physical uplink control channel (PUCCH), and the other of the first physical uplink channel or the second physical uplink channel is a physical uplink shared channel (PUSCH) that overlaps with the PUCCH in time; and The processing of the first physical uplink channel and the second physical uplink channel further includes: When the PUCCH having the single HARQ-ACK codebook has a high priority and the PUSCH has a low priority, multiplexing the PUCCH with the PUSCH; and When the PUCCH having the single HARQ-ACK codebook has the low priority and the PUSCH has the high priority, the PUCCH is multiplexed with the PUSCH.
6. The method according to claim 5, in, The priority-based HARQ-ACK codebook includes one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and The single HARQ-ACK codebook includes a type 3 codebook.
7. The method according to claim 5, further comprising: obtaining a first HARQ-ACK codebook and a second HARQ-ACK codebook via a radio resource control (RRC) configuration; as well as The single HARQ-ACK feedback configuration is applied to both the first HARQ-ACK codebook and the second HARQ-ACK codebook using the RRC configuration.
8. The method according to claim 5, in, The wireless device is configured with a first maximum number of code block groups (CBGs) per transport block (TB) and a second maximum number of CBGs per TB for a first priority and a second priority, respectively, for a component carrier (CC), and The method also includes: setting the number of HARQ-ACK bits for each TB of a single HARQ feedback process for a specific CC based on the maximum value of 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.
9. An apparatus for use in a wireless communication device of a wireless communication network, comprising: means for processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel comprises a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook; wherein at least one of the first physical uplink channel or the second physical uplink channel is a physical uplink control channel (PUCCH), and the other of the first physical uplink channel or the second physical uplink channel is a physical uplink shared channel (PUSCH) that overlaps with the PUCCH in time; and Wherein, the unit for processing further includes: When the PUCCH having the single HARQ-ACK codebook has a high priority and the PUSCH has a low priority, multiplexing the PUCCH with the PUSCH; and When the PUCCH having the single HARQ-ACK codebook has the low priority and the PUSCH has the high priority, the PUCCH is multiplexed with the PUSCH.
10. An article of manufacture for use with a wireless communication device of a wireless communication network, the article of manufacture comprising: A computer readable medium having instructions stored therein executable by one or more processors of the wireless communication device to: processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook; wherein at least one of the first physical uplink channel or the second physical uplink channel is a physical uplink control channel (PUCCH), and the other of the first physical uplink channel or the second physical uplink channel is a physical uplink shared channel (PUSCH) that overlaps with the PUCCH in time; and The processing of the first physical uplink channel and the second physical uplink channel further includes: When the PUCCH having the single HARQ-ACK codebook has a high priority and the PUSCH has a low priority, multiplexing the PUCCH with the PUSCH; and When the PUCCH having the single HARQ-ACK codebook has the low priority and the PUSCH has the high priority, the PUCCH is multiplexed with the PUSCH.
11. A wireless communication device, comprising: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel or the second physical uplink channel includes a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook, Wherein, the processor is further configured to: determining a priority for the first physical uplink channel; receiving downlink control information (DCI) triggering the second physical uplink channel and requesting use of the single HARQ-ACK codebook; assigning a priority to the second physical uplink channel by assigning a high priority to the second physical uplink channel based on a priority indicator field of the DCI; and The first physical uplink channel is cancelled when the first physical uplink channel has a lower priority than the second physical uplink channel, and the second physical uplink channel is cancelled when the second physical uplink channel has a lower priority than the first physical uplink channel.
12. The wireless communication device according to claim 11, in, The priority-based HARQ-ACK codebook is configured as one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and The single HARQ-ACK codebook is configured as a type 3 codebook.
13. The wireless communication device according to claim 11, in, The processor is further configured to use with a first maximum number of code block groups (CBGs) per transport block (TB) and a second maximum number of CBGs per TB for a component carrier (CC) for a first priority and a second priority, respectively, and The processor is also configured to set the number of HARQ-ACK bits for each TB of a single HARQ feedback process for a specific CC based on the maximum value of 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.
14. A method for wireless communication by a wireless device in a communication network, the method comprising: processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook, The processing further includes: determining a priority for the first physical uplink channel; receiving downlink control information (DCI) triggering the second physical uplink channel and requesting use of the single HARQ-ACK codebook; assigning a priority to the second physical uplink channel by assigning a high priority to the second physical uplink channel based on a priority indicator field of the DCI; and The first physical uplink channel is cancelled when the first physical uplink channel has a lower priority than the second physical uplink channel, and the second physical uplink channel is cancelled when the second physical uplink channel has a lower priority than the first physical uplink channel.
15. The method according to claim 14, in, The priority-based HARQ-ACK codebook includes one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and The single HARQ-ACK codebook includes a type 3 codebook.
16. The method according to claim 14, in, The wireless device is configured with a first maximum number of code block groups (CBGs) per transport block (TB) and a second maximum number of CBGs per TB for a first priority and a second priority, respectively, for a component carrier (CC), and The method also includes: setting the number of HARQ-ACK bits for each TB of a single HARQ feedback process for a specific CC based on the maximum value of 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.
17. A wireless communication device, comprising: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel or the second physical uplink channel includes a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook, wherein the wireless communication device is configured with (a) first and second maximum numbers of code block groups (CBGs) per transport block (TB) for first and second priorities for a particular component carrier (CC), or (b) only a single CBG, and Wherein, the processor is further configured to: TB-level ACK / NACK reporting is provided for single feedback without using CBG-based feedback for the single feedback.
18. The wireless communication device according to claim 17, in, The priority-based HARQ-ACK codebook is configured as one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and The single HARQ-ACK codebook is configured as a type 3 codebook.
19. The wireless communication device according to claim 17, in, The processor is further configured to use with a first maximum number of code block groups (CBGs) per transport block (TB) and a second maximum number of CBGs per TB for a component carrier (CC) for a first priority and a second priority, respectively, and The processor is also configured to set the number of HARQ-ACK bits for each TB of the single feedback for a specific CC based on the maximum value of 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.
20. A method for wireless communication by a wireless communication device in a communication network, the method comprising: configuring the wireless communication device with (a) first and second maximum numbers of code block groups (CBGs) per transport block (TB) for first and second priorities for a particular component carrier (CC), or (b) only a single CBG; as well as processing the first physical uplink channel and the second physical uplink channel 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 physical uplink channel and the second physical uplink channel includes a single hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook, and wherein the processing is performed in conjunction with use of a priority-based HARQ-ACK codebook, The processing also includes: providing a TB-level ACK / NACK report for a single feedback without using CBG-based feedback for the single feedback.
21. The method according to claim 20, in, The priority-based HARQ-ACK codebook includes one or more of a type 1 semi-static codebook and a type 2 dynamic codebook; and The single HARQ-ACK codebook includes a type 3 codebook.
22. The method according to claim 20, in, The wireless communication device is configured with a first maximum number of code block groups (CBGs) per transport block (TB) and a second maximum number of CBGs per TB for a first priority and a second priority, respectively, for a component carrier (CC), and The method also includes: setting the number of HARQ-ACK bits for each TB of the single feedback for a specific CC based on the maximum value of 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.
