Patent Publication Number: US-2023163889-A1

Title: Hybrid automatic repeat request (harq) codebook configurations indicating harq process identifiers

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This Patent Application claims priority to U.S. Provisional Pat. Application No. 63/264,528, filed on Nov. 24, 2021, entitled “HYBRID AUTOMATIC REPEAT REQUEST (HARQ) CODEBOOK CONFIGURATIONS INDICATING HARQ PROCESS IDENTIFIERS,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application. 
    
    
     FIELD OF THE DISCLOSURE 
     Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for hybrid automatic repeat request (HARQ) codebook configurations indicating HARQ process identifiers. 
     BACKGROUND 
     Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP). 
     A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the base station to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the base station. 
     The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, and/or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. 
     SUMMARY 
     In some implementations, an apparatus of a user equipment (UE) for wireless communication includes a memory and one or more processors coupled to the memory, wherein the memory includes instructions executable by the one or more processors to cause the UE to: receive, from a base station, a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) that indicates HARQ process identifiers (IDs) associated with the HARQ CB; and transmit, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     In some implementations, an apparatus of a base station for wireless communication includes a memory and one or more processors coupled to the memory, wherein the memory includes instructions executable by the one or more processors to cause the base station to: transmit, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and receive, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     In some implementations, a method of wireless communication performed by a UE includes receiving, from a base station, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and transmitting, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     In some implementations, a method of wireless communication performed by a base station includes transmitting, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and receiving, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive, from a base station, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and transmit, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: transmit, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and receive, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     In some implementations, an apparatus for wireless communication includes means for receiving, from a base station, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and means for transmitting, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     In some implementations, an apparatus for wireless communication includes means for transmitting, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and means for receiving, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, network node, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification. 
     The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims. 
     While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements. 
         FIG.  1    is a diagram illustrating an example of a wireless network, in accordance with the present disclosure. 
         FIG.  2    is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure. 
         FIG.  3    is a diagram illustrating an example of a Type 3 hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook (CB) configuration, in accordance with the present disclosure. 
         FIGS.  4 - 5    are diagrams illustrating examples associated with HARQ CB configurations indicating HARQ process identifiers (IDs), in accordance with the present disclosure. 
         FIGS.  6 - 7    are diagrams illustrating example processes associated with HARQ CB configurations indicating HARQ process IDs, in accordance with the present disclosure. 
         FIGS.  8 - 9    are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure. 
         FIG.  10    is a diagram illustrating an example of a disaggregated base station architecture, in accordance with the present disclosure. 
     
    
    
     DETAILED DESCRIPTION 
     Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. 
     Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. 
     While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G). 
       FIG.  1    is a diagram illustrating an example of a wireless network  100 , in accordance with the present disclosure. The wireless network  100  may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network  100  may include one or more base stations  110  (shown as a BS  110   a , a BS  110   b , a BS  110   c , and a BS  110   d ), a user equipment (UE)  120  or multiple UEs  120  (shown as a UE  120   a , a UE  120   b , a UE  120   c , a UE  120   d , and a UE  120   e ), and/or other network entities. A base station  110  is an entity that communicates with UEs  120 . A base station  110  (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP). Each base station  110  may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a base station  110  and/or a base station subsystem serving this coverage area, depending on the context in which the term is used. 
     A base station  110  may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs  120  with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs  120  with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs  120  having association with the femto cell (e.g., UEs  120  in a closed subscriber group (CSG)). A base station  110  for a macro cell may be referred to as a macro base station. A base station  110  for a pico cell may be referred to as a pico base station. A base station  110  for a femto cell may be referred to as a femto base station or an in-home base station. In the example shown in  FIG.  1   , the BS  110   a  may be a macro base station for a macro cell  102   a , the BS  110   b  may be a pico base station for a pico cell  102   b , and the BS  110   c  may be a femto base station for a femto cell  102   c . A base station may support one or multiple (e.g., three) cells. 
     In some aspects, the terms “base station” (e.g., the base station  110 ) or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, and/or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the base station  110 . In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “base station” or “network node” may refer to one or more virtual base stations and/or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station. 
     In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station  110  that is mobile (e.g., a mobile base station). In some examples, the base stations  110  may be interconnected to one another and/or to one or more other base stations  110  or network nodes (not shown) in the wireless network  100  through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network. 
     The wireless network  100  may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station  110  or a UE  120 ) and send a transmission of the data to a downstream station (e.g., a UE  120  or a base station  110 ). A relay station may be a UE  120  that can relay transmissions for other UEs  120 . In the example shown in  FIG.  1   , the BS  110   d  (e.g., a relay base station) may communicate with the BS  110   a  (e.g., a macro base station) and the UE  120   d  in order to facilitate communication between the BS  110   a  and the UE  120   d . A base station  110  that relays communications may be referred to as a relay station, a relay base station, a relay, or the like. 
     The wireless network  100  may be a heterogeneous network that includes base stations  110  of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations  110  may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network  100 . For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts). 
     A network controller  130  may couple to or communicate with a set of base stations  110  and may provide coordination and control for these base stations  110 . The network controller  130  may communicate with the base stations  110  via a backhaul communication link. The base stations  110  may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. 
     The UEs  120  may be dispersed throughout the wireless network  100 , and each UE  120  may be stationary or mobile. A UE  120  may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE  120  may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, and/or any other suitable device that is configured to communicate via a wireless medium. 
     Some UEs  120  may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs  120  may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs  120  may be considered a Customer Premises Equipment. A UE  120  may be included inside a housing that houses components of the UE  120 , such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled. 
     In general, any number of wireless networks  100  may be deployed in a given geographic area. Each wireless network  100  may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed. 
     In some examples, two or more UEs  120  (e.g., shown as UE  120   a  and UE  120   e ) may communicate directly using one or more sidelink channels (e.g., without using a base station  110  as an intermediary to communicate with one another). For example, the UEs  120  may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, a UE  120  may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station  110 . 
     Devices of the wireless network  100  may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network  100  may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR 1  (410 MHz – 7.125 GHz) and FR 2  (24.25 GHz – 52.6 GHz). It should be understood that although a portion of FR 1  is greater than 6 GHz, FR 1  is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR 2 , which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. 
     The frequencies between FR 1  and FR 2  are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR 3  (7.125 GHz – 24.25 GHz). Frequency bands falling within FR 3  may inherit FR 1  characteristics and/or FR 2  characteristics, and thus may effectively extend features of FR 1  and/or FR 2  into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR 4   a  or FR 4 - 1  (52.6 GHz – 71 GHz), FR 4  (52.6 GHz – 114.25 GHz), and FR 5  (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band. 
     With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR 1 , or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR 2 , FR 4 , FR 4 - a  or FR 4 - 1 , and/or FR 5 , or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR 1 , FR 2 , FR 3 , FR 4 , FR 4 - a , FR 4 - 1 , and/or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges. 
     In some aspects, a UE (e.g., UE  120 ) may include a communication manager  140 . As described in more detail elsewhere herein, the communication manager  140  may receive, from a base station, a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) that indicates HARQ process identifiers (IDs) associated with the HARQ CB; and transmit, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. Additionally, or alternatively, the communication manager  140  may perform one or more other operations described herein. 
     In some aspects, a base station (e.g., base station  110 ) may include a communication manager  150 . As described in more detail elsewhere herein, the communication manager  150  may transmit, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and receive, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. Additionally, or alternatively, the communication manager  150  may perform one or more other operations described herein. 
     As indicated above,  FIG.  1    is provided as an example. Other examples may differ from what is described with regard to  FIG.  1   . 
       FIG.  2    is a diagram illustrating an example  200  of a base station  110  in communication with a UE  120  in a wireless network  100 , in accordance with the present disclosure. The base station  110  may be equipped with a set of antennas  234   a  through  234   t , such as T antennas (T ≥ 1). The UE  120  may be equipped with a set of antennas  252   a  through  252   r , such as R antennas (R ≥ 1). 
     At the base station  110 , a transmit processor  220  may receive data, from a data source  212 , intended for the UE  120  (or a set of UEs  120 ). The transmit processor  220  may select one or more modulation and coding schemes (MCSs) for the UE  120  based at least in part on one or more channel quality indicators (CQIs) received from that UE  120 . The base station  110  may process (e.g., encode and modulate) the data for the UE  120  based at least in part on the MCS(s) selected for the UE  120  and may provide data symbols for the UE  120 . The transmit processor  220  may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor  220  may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor  230  may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems  232  (e.g., T modems), shown as modems  232   a  through  232   t . For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem  232 . Each modem  232  may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem  232  may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems  232   a  through  232   t  may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas  234  (e.g., T antennas), shown as antennas  234   a  through  234   t . 
     At the UE  120 , a set of antennas  252  (shown as antennas  252   a  through  252   r ) may receive the downlink signals from the base station  110  and/or other base stations  110  and may provide a set of received signals (e.g., R received signals) to a set of modems  254  (e.g., R modems), shown as modems  254   a  through  254   r . For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem  254 . Each modem  254  may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem  254  may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector  256  may obtain received symbols from the modems  254 , may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor  258  may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE  120  to a data sink  260 , and may provide decoded control information and system information to a controller/processor  280 . The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE  120  may be included in a housing  284 . 
     The network controller  130  may include a communication unit  294 , a controller/processor  290 , and a memory  292 . The network controller  130  may include, for example, one or more devices in a core network. The network controller  130  may communicate with the base station  110  via the communication unit  294 . 
     One or more antennas (e.g., antennas  234   a  through  234   t  and/or antennas  252   a  through  252   r ) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of  FIG.  2   . 
     On the uplink, at the UE  120 , a transmit processor  264  may receive and process data from a data source  262  and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor  280 . The transmit processor  264  may generate reference symbols for one or more reference signals. The symbols from the transmit processor  264  may be precoded by a TX MIMO processor  266  if applicable, further processed by the modems  254  (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station  110 . In some examples, the modem  254  of the UE  120  may include a modulator and a demodulator. In some examples, the UE  120  includes a transceiver. The transceiver may include any combination of the antenna(s)  252 , the modem(s)  254 , the MIMO detector  256 , the receive processor  258 , the transmit processor  264 , and/or the TX MIMO processor  266 . The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory  282  to perform aspects of any of the methods described herein (e.g., with reference to  FIGS.  4 - 9   ). 
     At the base station  110 , the uplink signals from UE  120  and/or other UEs may be received by the antennas  234 , processed by the modem  232  (e.g., a demodulator component, shown as DEMOD, of the modem  232 ), detected by a MIMO detector  236  if applicable, and further processed by a receive processor  238  to obtain decoded data and control information sent by the UE  120 . The receive processor  238  may provide the decoded data to a data sink  239  and provide the decoded control information to the controller/processor  240 . The base station  110  may include a communication unit  244  and may communicate with the network controller  130  via the communication unit  244 . The base station  110  may include a scheduler  246  to schedule one or more UEs  120  for downlink and/or uplink communications. In some examples, the modem  232  of the base station  110  may include a modulator and a demodulator. In some examples, the base station  110  includes a transceiver. The transceiver may include any combination of the antenna(s)  234 , the modem(s)  232 , the MIMO detector  236 , the receive processor  238 , the transmit processor  220 , and/or the TX MIMO processor  230 . The transceiver may be used by a processor (e.g., the controller/processor  240 ) and the memory  242  to perform aspects of any of the methods described herein (e.g., with reference to  FIGS.  4 - 9   ). 
     The controller/processor  240  of the base station  110 , the controller/processor  280  of the UE  120 , and/or any other component(s) of  FIG.  2    may perform one or more techniques associated with HARQ CB configurations indicating HARQ process IDs, as described in more detail elsewhere herein. For example, the controller/processor  240  of the base station  110 , the controller/processor  280  of the UE  120 , and/or any other component(s) of  FIG.  2    may perform or direct operations of, for example, process  600  of  FIG.  6   , process  700  of  FIG.  7   , and/or other processes as described herein. The memory  242  and the memory  282  may store data and program codes for the base station  110  and the UE  120 , respectively. In some examples, the memory  242  and/or the memory  282  may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station  110  and/or the UE  120 , may cause the one or more processors, the UE  120 , and/or the base station  110  to perform or direct operations of, for example, process  600  of  FIG.  6   , process  700  of  FIG.  7   , and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples. 
     In some aspects, a UE (e.g., UE  120 ) includes means for receiving, from a base station, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and/or means for transmitting, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. The means for the UE to perform operations described herein may include, for example, one or more of communication manager  140 , antenna  252 , modem  254 , MIMO detector  256 , receive processor  258 , transmit processor  264 , TX MIMO processor  266 , controller/processor  280 , or memory  282 . 
     In some aspects, a base station (e.g., base station  110 ) includes means for transmitting, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB; and/or means for receiving, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. The means for the base station to perform operations described herein may include, for example, one or more of communication manager  150 , transmit processor  220 , TX MIMO processor  230 , modem  232 , antenna  234 , MIMO detector  236 , receive processor  238 , controller/processor  240 , memory  242 , or scheduler  246 . 
     While blocks in  FIG.  2    are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor  264 , the receive processor  258 , and/or the TX MIMO processor  266  may be performed by or under the control of the controller/processor  280 . 
     As indicated above,  FIG.  2    is provided as an example. Other examples may differ from what is described with regard to  FIG.  2   . 
     A UE may use a Type 3 HARQ-ACK CB for a HARQ-ACK retransmission. The UE may transmit the HARQ-ACK retransmission to a base station based at least in part on the Type 3 HARQ-ACK CB. The UE may use the HARQ-ACK CB based at least in part on a semi-persistent scheduling (SPS) HARQ collision with a downlink, a low priority (LP) HARQ dropped internally due to an intra-UE multiplexing, a HARQ multiplexing onto a physical uplink shared channel (PUSCH) where the PUSCH is cancelled via a cancellation indication (CI), and/or a HARQ not decoded at the base station (e.g., due to poor channel conditions). The Type 3 HARQ-ACK CB may be associated with a size and content, such as a set of HARQ IDs. A base station may configure, for the UE, the size and content of the Type 3 HARQ-ACK CB via RRC signaling. In some cases, the base station may simultaneously configure up to 8 Type 3 HARQ-ACK CBs via the RRC signaling. The base station may transmit, to the UE, downlink control information (DCI) to indicate a requested Type 3 HARQ-ACK CB. 
     For the HARQ-ACK retransmission, the Type 3 HARQ-ACK CB (or enhanced Type 3 HARQ-ACK CB) may be supported with a smaller size as compared to earlier version Type 3 HARQ-ACK CBs. A codebook size of a single triggered Type 3 HARQ-ACK codebook may be based at least in part on an RRC configuration. A construction of the Type 3 HARQ-ACK codebook may use HARQ processes as a basis (e.g., order according to HARQ process IDs and serving cells). In other words, the Type 3 HARQ-ACK codebook may be based at least in part on HARQ process IDs. Further, one-shot triggering by a downlink assignment of the HARQ-ACK retransmission on a physical uplink control channel (PUCCH) resource may be supported on a PUCCH resource other than a Type 2 or Type 3 HARQ-ACK codebook, but may be subject to separate UE capabilities. 
     For the Type 3 HARQ-ACK CB, a dynamic selection may be supported based at least in part on an indication in a triggering DCI of the Type 3 HARQ-ACK CB. The Type 3 HARQ-ACK CB may be defined by the RRC configuration. In some cases, a plurality of downlink HARQ processes (e.g., all downlink HARQ processes) of a plurality of configured component carriers (e.g., all component carriers) may be configured as one Type 3 HARQ-ACK CB. Further, the UE may transmit, to the base station, capability signaling (e.g., a value ranging from 1 to X, or a value selected from a set of 1, 2, 4, and 8) indicating a maximum quantity of supported simultaneously configured Type 3 HARQ-ACK CBs that are able to be dynamically indicated to the UE. 
       FIG.  3    is a diagram illustrating an example  300  of a Type 3 HARQ-ACK CB configuration, in accordance with the present disclosure. 
     A base station (e.g., base station  110 ) may transmit, to a UE (e.g., UE  120 ), a first SPS via a physical downlink shared channel (PDSCH) in a slot. The slot may be associated with a first type. The base station may transmit, to the UE, a second SPS via a PDSCH in the slot associated with the first type. The UE may transmit, to the base station, a first HARQ-ACK and a second HARQ-ACK based at least in part on the first SPS and the second SPS, respectively. The UE may transmit the first HARQ-ACK and the second HARQ-ACK via uplink channels. The UE may transmit the first HARQ-ACK and the second HARQ-ACK based at least in part on K1 values associated with the first HARQ-ACK and the second HARQ-ACK, where the K1 values may indicate a quantity of symbols (e.g., 20 symbols). Further, the first HARQ-ACK may be associated with a first HARQ process ID (e.g., HARQ process ID #4), and the second HARQ-ACK may be associated with a second HARQ process ID (e.g., HARQ process ID #12). 
     In some cases, a slot format may change from the first type to a second type, and the base station may transmit, to the UE, a first SPS via a PDSCH in a slot associated with the second type. The base station may also transmit, to the UE, a second SPS via a PDSCH in the slot associated with the second type. A first HARQ-ACK and a second HARQ-ACK associated with the first SPS and the second SPS, respectively, may collide with downlink symbols based at least in part on K1 values associated with the first HARQ-ACK and the second HARQ-ACK. The first HARQ-ACK and the second HARQ-ACK may collide with the downlink symbols based at least in part on the change to the slot format, which may cause the first HARQ-ACK and the second HARQ-ACK to not be transmitted to the base station. As a result, the first HARQ process ID and the second HARQ process ID, associated with the first HARQ-ACK and the second HARQ-ACK, may be missing. At a later time, the base station may transmit, to the UE, a request for a Type 3 HARQ CB. However, the Type 3 HARQ CB may not be configured to contain missing HARQ process IDs. In other words, the Type 3 HARQ CB may not be designed to account for missing HARQ process IDs associated with HARQ-ACKs that are dropped due to collisions. 
     As indicated above,  FIG.  3    is provided as an example. Other examples may differ from what is described with regard to  FIG.  3   . 
     A base station, for a Type 3 HARQ-ACK CB configuration, may not be able to configure beforehand (e.g., via RRC signaling) a list of RRC processes without information regarding which HARQ processes may later become missing. For example, the base station, for the Type 3 HARQ-ACK CB configuration, may be unable to determine beforehand that certain HARQ process IDs (e.g., HARQ process ID #4 and HARQ process ID #12) are likely to be lost or canceled or deferred. 
     Further, for SPS, usage of certain HARQ process IDs may not be guaranteed. For a given SPS periodicity and for a given quantity of activated HARQ processes, a HARQ process ID may depend on a current slot number (e.g., SPS with a period equal to 1 ms while operating at a 30 kHz subcarrier spacing (SCS), which may imply that the SPS is transmitted at slot #0, #2, #4, #6, and so on). 
     For configured downlink assignments with or without a HARQ process ID offset (harq-ProcID-Offset) parameter, a HARQ process ID associated with a slot where a downlink transmission starts may be based at least in part on a current slot, a quantity of slots per frame, a periodicity, a quantity of HARQ processes, and/or the HARQ process ID offset parameter. The current slot may be based at least in part on a system frame number, the quantity of slots per frame, and a slot number in the frame. The quantity of slots per frame may correspond to a quantity of consecutive slots per frame. The current slot may correspond to a slot index of a first transmission occasion of a bundle of configured downlink assignments. 
     When detecting HARQ process IDs prone to HARQ-ACK retransmission, determining which HARQ processes may be requested for HARQ-ACK retransmission via the Type 3 HARQ-ACK CB may not be possible, assuming no SPS configuration and a plurality of HARQ processes (e.g., all HARQ processes) are of a same priority. In other words, indicating that a given HARQ process (e.g., HARQ process ID #4) is more likely to be missed, as compared to other HARQ processes, may not be possible. The plurality of HARQ processes may all share a same quality, unless some HARQ processes are mapped to specific PUCCH formats and uplink control information (UCI) formats, so indicating that the given HARQ process is more likely to be missed may not be possible. 
     In various aspects of techniques and apparatuses described herein, a UE may receive, from a base station, an RRC configuration for a HARQ CB (e.g., a Type 3 HARQ CB) that indicates HARQ process IDs associated with the HARQ CB. The UE may receive, from the base station, DCI that indicates a request for the HARQ CB. The UE may transmit, to the base station, the HARQ CB based at least in part on the DCI and the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. In some aspects, the RRC configuration may indicate a list of component carriers having HARQ process IDs included in the HARQ CB, and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB. In some aspects, the RRC configuration may indicate a list of component carriers having HARQ process IDs included in the HARQ CB, a starting HARQ process ID, and a size associated with consecutive HARQ process IDs in the HARQ CB. In some aspects, the RRC configuration may indicate an equal split of a plurality of HARQ processes from a plurality of component carriers into a total quantity of configured HARQ CBs. In some aspects, a plurality of active HARQ process IDs may not all be included in the HARQ CB . 
     In some aspects, an RRC configuration of each Type 3 HARQ CB may be a first type of RRC configuration, a second type of RRC configuration, or a third type of RRC configuration. The first type of RRC configuration may indicate the list of component carriers whose HARQ process IDs are included in the HARQ CB, and the bitmap indicating the list of the HARQ process IDs to be included in the HARQ CB. The second type of RRC configuration may indicate the list of component carriers whose HARQ process IDs are included in the HARQ CB, the starting HARQ process ID, and the size associated with consecutive HARQ process IDs in the HARQ CB. The third type of RRC configuration may indicate the equal split of the plurality of HARQ processes from the plurality of component carriers into the total quantity of configured HARQ CBs. Different types of RRC configurations may have different RRC message sizes and different reliability levels. The RRC configuration may represent a single HARQ CB based at least in part on not all active HARQ process IDs being included in the single HARQ CB. Further, the HARQ CB may be linked to certain events, such as a SPS HARQ deferral or a low priority HARQ being dropped at the UE. 
       FIG.  4    is a diagram illustrating an example  400  associated with HARQ CB configurations indicating HARQ process IDs, in accordance with the present disclosure. As shown in  FIG.  4   , example  400  includes communication between a UE (e.g., UE  120 ) and a base station (e.g., base station  110 ). In some aspects, the UE and the base station may be included in a wireless network, such as wireless network  100 . 
     As shown by reference number  402 , the UE may receive, from the base station, an RRC configuration for a Type 3 HARQ CB that indicates HARQ process IDs associated with the Type 3 HARQ CB. In some aspects, a plurality of active HARQ process IDs may not all be included in the Type 3 HARQ CB. 
     In some aspects, in a first option, the RRC configuration may indicate a list of component carriers having HARQ process IDs included in the Type 3 HARQ CB, and a bitmap indicating a list of the HARQ process IDs to be included in the Type 3 HARQ CB. In some aspects, a single Type 3 HARQ CB may include HARQ process IDs from a single component carrier, or alternatively, the single Type 3 HARQ CB may include HARQ process IDs from more than one component carrier. In some aspects, a same HARQ process ID may be configured in more than one Type 3 HARQ CB (e.g., in different Type 3 HARQ CBs). For example, a HARQ process ID #4 in a first component carrier may be included in both a Type 3 HARQ CB #1 and a Type 3 HARQ CB #8. 
     In some aspects, in a second option, the RRC configuration may indicate the list of component carriers having HARQ process IDs included in the Type 3 HARQ CB, a starting HARQ process ID, and a size associated with consecutive HARQ process IDs in the Type 3 HARQ CB. In some aspects, a starting HARQ process ID may be the same for a plurality of component carriers (e.g., all component carriers) in a single Type 3 HARQ CB . 
     In some aspects, in a third option, the RRC configuration may indicate an equal split of a plurality of HARQ processes from a plurality of component carriers into a total quantity of configured Type 3 HARQ CBs. 
     As an example, two component carriers with 16 HARQ processes per component carrier (e.g., 32 HARQ processes in total) may be equally split to 8 Type 3 HARQ CBs, where each Type 3 HARQ CB may be an equal size of four. In this example, a first Type 3 HARQ CB may be associated with a first component carrier (CC0) and have HARQ process IDs ordered from HARQ process ID #0 to #3, a second Type 3 HARQ CB may be associated with a first component carrier and have HARQ process IDs ordered from HARQ process ID #4 to #7, and so on. 
     In some aspects, in a first sub-option of the third option, a single Type 3 HARQ CB may indicate a plurality of HARQ process IDs (e.g., all HARQ process IDs) for each component carrier. For example, a first HARQ CB may include all HARQ processes from a first component carrier, a second HARQ CB may include all HARQ processes from a second component carrier, and so on. 
     In some aspects, in a second sub-option of the third option, a plurality of HARQ process IDs (e.g., all HARQ process IDs) from a plurality of component carriers (e.g., all component carriers) may be equally split into a total quantity of configured Type 3 HARQ CBs, with each Type 3 HARQ CB including every Nth HARQ process ID. As an example, two component carriers with 16 HARQ processes per component carrier (e.g., 32 HARQ processes in total) may be equally split to 8 Type 3 HARQ CBs, where each Type 3 HARQ CB may be an equal size of four. In this example, a first Type 3 HARQ CB may be associated with a first component carrier and have HARQ process IDs ordered from HARQ process ID #0, #2, #4, #6; a second Type 3 HARQ CB may be associated with a first component carrier and have HARQ process IDs ordered from HARQ process ID #1, #3, #5, #7, and so on. 
     In some aspects, in a third sub-option of the third option, a plurality of HARQ process IDs (e.g., all HARQ process IDs) from a plurality of component carriers (e.g., all component carriers) may be equally split into a total quantity of configured Type 3 HARQ CBs, N, minus 1, and one other Type 3 HARQ CB. In other words, the HARQ process IDs for the component carriers may be equally split into N-1 Type 3 HARQ CBs and the one other Type 3 HARQ CB. 
     In some aspects, in a fourth option, the RRC configuration of the Type 3 HARQ CB (e.g., a first Type 3 HARQ CB) may contain a plurality of SPS candidate HARQ process IDs (e.g., all SPS candidate HARQ process IDs), based at least in part on a slot number associated with the Type 3 HARQ CB. 
     In some aspects, in a fifth option, the RRC configuration may be based at least in part on an event. In some aspects, in a first sub-option associated with the fifth option, the Type 3 HARQ CB may be based at least in part on an SPS HARQ collision with a downlink. In a second sub-option associated with the fifth option, the Type 3 HARQ CB may be based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing. In a third sub-option associated with the fifth option, the Type 3 HARQ CB may be based at least in part on a CI of an uplink channel containing HARQ, such as a PUSCH including HARQ. The SPS HARQ collision with the downlink, the low priority HARQ being dropped due to the intra-UE multiplexing, and the CI of the uplink channel containing HARQ may correspond to different events. 
     In some aspects, in the first sub-option associated with the fifth option (e.g., the SPS HARQ collision with the downlink), the Type 3 HARQ CB (e.g., a first Type 3 HARQ CB) may include N HARQ processes, where N may already be configured. A starting HARQ Process ID #K may be a HARQ process ID of an earliest SPS HARQ colliding with the downlink. In some aspects, the Type 3 HARQ CB may include HARQ process IDs #K up to #K+N-1. In some aspects, the Type 3 HARQ CB may include HARQ process IDs #K that are distant by M, such as #K, #K+M, #K+2M, and so on. 
     In some aspects, in the second sub-option associated with the fifth option (e.g., the low priority HARQ being dropped due to the intra-UE multiplexing), the Type 3 HARQ CB (e.g., a first Type 3 HARQ CB) may include NHARQ Processes, where N may already be configured. A starting HARQ process ID #K may be a HARQ process ID of an earliest low priority HARQ being dropped. In some aspects, the Type 3 HARQ CB may include HARQ process IDs #K up to #K+N-1. In some aspects, the Type 3 HARQ CB may include HARQ process IDs #K that are distant by M, such as #K, #K+M, #K+2M, and so on. 
     In some aspects, in the third sub-option associated with the fifth option (e.g., the CI of the PUSCH including HARQ), the Type 3 HARQ CB (e.g., a first Type 3 HARQ CB) may include N HARQ Processes, where N may already be configured. A starting HARQ process ID #K may be a HARQ process ID of an earliest HARQ multiplexed onto the PUSCH that is cancelled via the CI. In some aspects, the Type 3 HARQ CB may include HARQ process IDs #K up to #K+N-1. In some aspects, the Type 3 HARQ CB may include HARQ process IDs #K that are distant by M, such as #K, #K+M, #K+2M, and so on. 
     In some aspects, different options (and sub-options of options) for the RRC configuration may be associated with different RRC information elements (IEs) and different quantities of bits. For the first option of the RRC configuration, the list of component carriers may be two bits and the bitmap may be 16 bits per component carrier. Thus, for two component carriers, a total of 36 bits (e.g., 2×2 + 2×16) may be needed for a single Type 3 HARQ CB configuration. For the second option of the RRC configuration, the list of component carriers may be two bits, the starting HARQ process ID may be four bits, and the size may be four bits. Thus, for two component carriers, a total of 20 bits (e.g., 2×2 + 2×4 + 2×4) may be needed for a single Type 3 HARQ CB configuration. 
     For the third, fourth, and fifth options of the RRC configuration, which may be associated with predetermined events, 7 different RRC configuration may be identified corresponding to different predetermined events. These RRC preconfigured cases may be coded in three or four bits. For example, an RRC configuration associated with a first sub-option of the third option may be coded as “000”, an RRC configuration associated with a second sub-option of the third option may be coded as “001”, an RRC configuration associated with a third sub-option of the third option may be coded as “010”, an RRC configuration associated with the fourth option may be coded as “011”, an RRC configuration associated with a first sub-option of the fifth option may be coded as “100”, an RRC configuration associated with a second sub-option of the fifth option may be coded as “101”, and an RRC configuration associated with a third sub-option of the fifth option may be coded as “110”. 
     As an example, a UE may be associated with four component carriers and 16 HARQ processes per component carrier, and hence a total of 64 HARQ processes. For the network to provide full flexibility in terms of a Type 3 HARQ CB construction, for each Type 3 HARQ CB, a bitmap may need to be equal to 64 bits. When the UE supports 8 Type 3 HARQ CBs, then the bitmap may need to be equal to 512 bits. 
     For the network to provide some flexibility by allowing different HARQ process IDs within a given component carrier, then the network may need to indicate both a component carrier ID and a bitmap per component carrier. In this case, 18 bits may be needed per Type 3 HARQ CB, and for 8 configured Type 3 HARQ CBs, a total of 144 bits may be needed. 
     As an alternative, HARQ Process IDs within a given Type 3 HARQ CB may be consecutive. In this case, to determine a given Type 3 HARQ CB, RRC fields associated with a component carrier ID, a starting HARQ process number, and a size may be conveyed by the base station to the UE. For example, 10 bits per Type 3 HARQ CB may be needed, and for 8 configured Type 3 HARQ CBs, a total of 80 bits may be needed. 
     As another alternative, a whole space of HARQ processes may be equally divided into the quantity of configured Type 3 HARQ CBs. For 8 configured Type 3 HARQ CBs, each Type 3 HARQ CB may include 8 consecutive HARQ process IDs. In this case, only a single bit entry in RRC per Type 3 HARQ CB may be sufficient. 
     In some aspects, the RRC configuration may be based at least in part on a channel quality. Depending on the channel quality, the RRC configuration of the Type 3 HARQ CBs may be represented in different forms. For example, the RRC configuration may be according to options one, two, three, four, or five, as described herein, which may result in different amounts of RRC bits and different reliability levels. 
     In some aspects, the UE may transmit, to the base station, a request for a type of RRC configuration based at least in part on an RSRP associated with a signal received from the base station. The UE may receive the RRC configuration from the base station based at least in part on the request for the type of RRC configuration. In some aspects, the base station may determine the type of RRC configuration. In other words, the base station may determine a quantity of RRC bits to be used in a physical cell configuration (PhysicalCellConfig) RRC IE. In some aspects, the type of RRC configuration may be UE-based depending on the RSRP from the base station (e.g., a serving gNB). The UE may transmit the request regarding which type of Type 3 HARQ CB configuration is to be transmitted to the UE, where the type of Type 3 HARQ CB configuration may correspond to the different options described herein. When the RSRP satisfies a threshold, the UE may request a certain Type 3 HARQ CB configuration to be transmitted to the UE (e.g., a type of RRC configuration that uses fewer bits as compared to other types of RRC configurations). 
     As shown by reference number  404 , the UE may transmit, to the base station, the Type 3 HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the Type 3 HARQ CB. The UE may receive, from the base station, DCI that indicates a request for the Type 3 HARQ CB. The UE may transmit the Type 3 HARQ CB based at least in part on the DCI. 
     As indicated above,  FIG.  4    is provided as an example. Other examples may differ from what is described with regard to  FIG.  4   . 
       FIG.  5    is a diagram illustrating an example  500  associated with HARQ CB configurations indicating HARQ process IDs, in accordance with the present disclosure. 
     As shown by reference number  502 , an RRC configuration may indicate a bitmap. The bitmap may indicate a list of HARQ process IDs to be included in a HARQ CB. The bitmap may be for a single component carrier (CC0) and 8 activated HARQ process IDs. A first HARQ codebook may be associated with a first set of activated HARQ process IDs (e.g., HARQ process ID #0, HARQ process ID #2, HARQ process ID #4, and HARQ process ID #8). A second HARQ codebook may be associated with a second set of activated HARQ process IDs (e.g., HARQ process ID #1, HARQ process ID #3, HARQ process ID #5, and HARQ process ID #7). 
     In some aspects, for multiple component carriers, a bitmap representation may indicate a list of component carriers per HARQ CB. In some aspects, a single HARQ CB may indicate HARQ process IDs for more than one component carrier. In some aspects, different HARQ CBs may associated with different sizes. 
     As shown by reference number  504 , an RRC configuration may indicate a starting HARQ process ID and a size, where the size may indicate a quantity of consecutive HARQ processes in one HARQ codebook. The RRC configuration may be for a single component carrier and 10 activated HARQ process IDs. As an example, the RRC configuration may indicate, for a first HARQ codebook, a starting HARQ process ID of #0 and a size of 4. The RRC configuration may indicate, for a second HARQ codebook, a starting HARQ process ID of #4 and a size of 6. 
     As shown by reference number  506 , an RRC configuration may indicate an equal split of active HARQ process IDs per component carrier. The RRC configuration may be for two component carriers and 8 activated HARQ process IDs per component carrier. As an example, the RRC configuration may indicate, for a first component carrier (CC0), a set of 4 HARQ process IDs for a first HARQ CB and a set of 4 HARQ process IDs for a second HARQ CB. The RRC configuration may indicate, for a second component carrier (CC1), a set of 4 HARQ process IDs for a third HARQ CB and a set of 4 HARQ process IDs for a fourth HARQ CB. 
     As indicated above,  FIG.  5    is provided as an example. Other examples may differ from what is described with regard to  FIG.  5   . 
       FIG.  6    is a diagram illustrating an example process  600  performed, for example, by a UE, in accordance with the present disclosure. Example process  600  is an example where the UE (e.g., UE  120 ) performs operations associated with HARQ CB configurations indicating HARQ process IDs. 
     As shown in  FIG.  6   , in some aspects, process  600  may include receiving, from a base station, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB (block  610 ). For example, the UE (e.g., using reception component  802 , depicted in  FIG.  8   ) may receive, from a base station, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB, as described above. 
     As further shown in  FIG.  6   , in some aspects, process  600  may include transmitting, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB (block  620 ). For example, the UE (e.g., using transmission component  804 , depicted in  FIG.  8   ) may transmit, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB, as described above. 
     Process  600  may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein. 
     In a first aspect, process  600  includes receiving, from the base station, DCI that indicates a request for the HARQ CB, wherein the HARQ CB is transmitted based at least in part on the DCI. 
     In a second aspect, alone or in combination with the first aspect, the RRC configuration indicates a list of component carriers having HARQ process IDs included in the HARQ CB, and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB. 
     In a third aspect, alone or in combination with one or more of the first and second aspects, the RRC configuration indicates a list of component carriers having HARQ process IDs included in the HARQ CB, a starting HARQ process ID, and a size associated with consecutive HARQ process IDs in the HARQ CB. 
     In a fourth aspect, alone or in combination with one or more of the first through third aspects, the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers into a total quantity of configured HARQ CBs. 
     In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the HARQ CB is based at least in part on an SPS HARQ collision with a downlink, the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing, or the HARQ CB is based at least in part on a CI of an uplink channel containing HARQ. 
     In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the RRC configuration is based at least in part on a channel quality. 
     In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process  600  includes transmitting, to the base station, a request for a type of RRC configuration based at least in part on an RSRP associated with a signal received from the base station, wherein the RRC configuration received from the base station is based at least in part on the request. 
     In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a plurality of active HARQ process IDs are not all included in the HARQ CB . 
     In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the HARQ CB is a Type 3 HARQ CB. 
     Although  FIG.  6    shows example blocks of process  600 , in some aspects, process  600  may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in  FIG.  6   . Additionally, or alternatively, two or more of the blocks of process  600  may be performed in parallel. 
       FIG.  7    is a diagram illustrating an example process  700  performed, for example, by a base station, in accordance with the present disclosure. Example process  700  is an example where the base station (e.g., base station  110 ) performs operations associated with HARQ CB configurations indicating HARQ process IDs. 
     As shown in  FIG.  7   , in some aspects, process  700  may include transmitting, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB (block  710 ). For example, the base station (e.g., using transmission component  904 , depicted in  FIG.  9   ) may transmit, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB, as described above. 
     As further shown in  FIG.  7   , in some aspects, process  700  may include receiving, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB (block  720 ). For example, the base station (e.g., using reception component  902 , depicted in  FIG.  9   ) may receive, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB, as described above. 
     Process  700  may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein. 
     In a first aspect, the RRC configuration indicates a list of component carriers having HARQ process IDs included in the HARQ CB, and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB. 
     In a second aspect, alone or in combination with the first aspect, the RRC configuration indicates a list of component carriers having HARQ process IDs included in the HARQ CB, a starting HARQ process ID, and a size associated with consecutive HARQ process IDs in the HARQ CB. 
     In a third aspect, alone or in combination with one or more of the first and second aspects, the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers into a total quantity of configured HARQ CBs. 
     In a fourth aspect, alone or in combination with one or more of the first through third aspects, the HARQ CB is based at least in part on an SPS HARQ collision with a downlink, the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing, or the HARQ CB is based at least in part on a CI of an uplink channel containing HARQ. 
     Although  FIG.  7    shows example blocks of process  700 , in some aspects, process  700  may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in  FIG.  7   . Additionally, or alternatively, two or more of the blocks of process  700  may be performed in parallel. 
       FIG.  8    is a diagram of an example apparatus  800  for wireless communication. The apparatus  800  may be a UE, or a UE may include the apparatus  800 . In some aspects, the apparatus  800  includes a reception component  802  and a transmission component  804 , which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus  800  may communicate with another apparatus  806  (such as a UE, a base station, or another wireless communication device) using the reception component  802  and the transmission component  804 . 
     In some aspects, the apparatus  800  may be configured to perform one or more operations described herein in connection with  FIGS.  4 - 5   . Additionally, or alternatively, the apparatus  800  may be configured to perform one or more processes described herein, such as process  600  of  FIG.  6   . In some aspects, the apparatus  800  and/or one or more components shown in  FIG.  8    may include one or more components of the UE described in connection with  FIG.  2   . Additionally, or alternatively, one or more components shown in  FIG.  8    may be implemented within one or more components described in connection with  FIG.  2   . Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component. 
     The reception component  802  may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus  806 . The reception component  802  may provide received communications to one or more other components of the apparatus  800 . In some aspects, the reception component  802  may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus  800 . In some aspects, the reception component  802  may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with  FIG.  2   . 
     The transmission component  804  may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus  806 . In some aspects, one or more other components of the apparatus  800  may generate communications and may provide the generated communications to the transmission component  804  for transmission to the apparatus  806 . In some aspects, the transmission component  804  may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus  806 . In some aspects, the transmission component  804  may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with  FIG.  2   . In some aspects, the transmission component  804  may be co-located with the reception component  802  in a transceiver. 
     The reception component  802  may receive, from a base station, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB. The transmission component  804  may transmit, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     The reception component  802  may receive, from the base station, DCI that indicates a request for the HARQ CB, wherein the HARQ CB is transmitted based at least in part on the DCI. The transmission component  804  may transmit, to the base station, a request for a type of RRC configuration based at least in part on an RSRP associated with a signal received from the base station, wherein the RRC configuration received from the base station is based at least in part on the request. 
     The number and arrangement of components shown in  FIG.  8    are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in  FIG.  8   . Furthermore, two or more components shown in  FIG.  8    may be implemented within a single component, or a single component shown in  FIG.  8    may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in  FIG.  8    may perform one or more functions described as being performed by another set of components shown in  FIG.  8   . 
       FIG.  9    is a diagram of an example apparatus  900  for wireless communication. The apparatus  900  may be a base station, or a base station may include the apparatus  900 . In some aspects, the apparatus  900  includes a reception component  902  and a transmission component  904 , which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus  900  may communicate with another apparatus  906  (such as a UE, a base station, or another wireless communication device) using the reception component  902  and the transmission component  904 . 
     In some aspects, the apparatus  900  may be configured to perform one or more operations described herein in connection with  FIGS.  4 - 5   . Additionally, or alternatively, the apparatus  900  may be configured to perform one or more processes described herein, such as process  700  of  FIG.  7   . In some aspects, the apparatus  900  and/or one or more components shown in  FIG.  9    may include one or more components of the base station described in connection with  FIG.  2   . Additionally, or alternatively, one or more components shown in  FIG.  9    may be implemented within one or more components described in connection with  FIG.  2   . Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component. 
     The reception component  902  may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus  906 . The reception component  902  may provide received communications to one or more other components of the apparatus  900 . In some aspects, the reception component  902  may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus  900 . In some aspects, the reception component  902  may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection with  FIG.  2   . 
     The transmission component  904  may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus  906 . In some aspects, one or more other components of the apparatus  900  may generate communications and may provide the generated communications to the transmission component  904  for transmission to the apparatus  906 . In some aspects, the transmission component  904  may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus  906 . In some aspects, the transmission component  904  may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection with  FIG.  2   . In some aspects, the transmission component  904  may be co-located with the reception component  902  in a transceiver. 
     The transmission component  904  may transmit, to a UE, an RRC configuration for a HARQ CB that indicates HARQ process IDs associated with the HARQ CB. The reception component  902  may receive, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     The number and arrangement of components shown in  FIG.  9    are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in  FIG.  9   . Furthermore, two or more components shown in  FIG.  9    may be implemented within a single component, or a single component shown in  FIG.  9    may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in  FIG.  9    may perform one or more functions described as being performed by another set of components shown in  FIG.  9   . 
       FIG.  10    is a diagram illustrating an example  1000  of a disaggregated base station architecture, in accordance with the present disclosure. 
     Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station (BS, e.g., base station  110 ), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), eNB, NR BS, 5G NB, access point (AP), a TRP, a cell, or the like) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station. 
     An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU). 
     Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an O-RAN (such as the network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. 
     The disaggregated base station architecture shown in  FIG.  10    may include one or more CUs  1010  that can communicate directly with a core network  1020  via a backhaul link, or indirectly with the core network  1020  through one or more disaggregated base station units (such as a Near-RT RIC  1025  via an E2 link, or a Non-RT RIC  1015  associated with a Service Management and Orchestration (SMO) Framework  1005 , or both). A CU  1010  may communicate with one or more DUs  1030  via respective midhaul links, such as an F1 interface. The DUs  1030  may communicate with one or more RUs  1040  via respective fronthaul links. The RUs  1040  may communicate with respective UEs  120  via one or more radio frequency (RF) access links. In some implementations, the UE  120  may be simultaneously served by multiple RUs  1040 . 
     Each of the units (e.g., the CUs  1010 , the DUs  1030 , the RUs  1040 ), as well as the Near-RT RICs  1025 , the Non-RT RICs  1015 , and the SMO Framework  1005 , may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units. 
     In some aspects, the CU  1010  may host one or more higher layer control functions. Such control functions can include RRC, packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU  1010 . The CU  1010  may be configured to handle user plane functionality (e.g., Central Unit – User Plane (CU-UP)), control plane functionality (e.g., Central Unit – Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU  1010  can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU  1010  can be implemented to communicate with the DU  1030 , as necessary, for network control and signaling. 
     The DU  1030  may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs  1040 . In some aspects, the DU  1030  may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3GPP. In some aspects, the DU  1030  may further host one or more low-PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU  1030 , or with the control functions hosted by the CU  1010 . 
     Lower-layer functionality can be implemented by one or more RUs  1040 . In some deployments, an RU  1040 , controlled by a DU  1030 , may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s)  1040  can be implemented to handle over the air (OTA) communication with one or more UEs  120 . In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s)  1040  can be controlled by the corresponding DU  1030 . In some scenarios, this configuration can enable the DU(s)  1030  and the CU  1010  to be implemented in a cloud-based RAN architecture, such as a vRAN architecture. 
     The SMO Framework  1005  may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework  1005  may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework  1005  may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 1090) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs  1010 , DUs  1030 , RUs  1040  and Near-RT RICs  1025 . In some implementations, the SMO Framework  1005  can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB)  1011 , via an O1 interface. Additionally, in some implementations, the SMO Framework  1005  can communicate directly with one or more RUs  1040  via an O1 interface. The SMO Framework  1005  also may include a Non-RT RIC  1015  configured to support functionality of the SMO Framework  1005 . 
     The Non-RT RIC  1015  may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC  1025 . The Non-RT RIC  1015  may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC  1025 . The Near-RT RIC  1025  may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs  1010 , one or more DUs  1030 , or both, as well as an O-eNB, with the Near-RT RIC  1025 . 
     In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC  1025 , the Non-RT RIC  1015  may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC  1025  and may be received at the SMO Framework  1005  or the Non-RT RIC  1015  from non-network data sources or from network functions. In some examples, the Non-RT RIC  1015  or the Near-RT RIC  1025  may be configured to tune RAN behavior or performance. For example, the Non-RT RIC  1015  may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework  1005  (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies). 
     As indicated above,  FIG.  10    is provided as an example. Other examples may differ from what is described with regard to  FIG.  10   . 
     The following provides an overview of some Aspects of the present disclosure: 
     Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a base station, a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) that indicates HARQ process identifiers (IDs) associated with the HARQ CB; and transmitting, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     Aspect 2: The method of Aspect 1, further comprising: receiving, from the base station, downlink control information (DCI) that indicates a request for the HARQ CB, wherein the HARQ CB is transmitted based at least in part on the DCI. 
     Aspect 3: The method of any of Aspects 1 through 2, wherein the RRC configuration indicates: a list of component carriers having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB. 
     Aspect 4: The method of any of Aspects 1 through 3, wherein the RRC configuration indicates: a list of component carriers having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB. 
     Aspect 5: The method of any of Aspects 1 through 4, wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers into a total quantity of configured HARQ CBs. 
     Aspect 6: The method of any of Aspects 1 through 5, wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ. 
     Aspect 7: The method of any of Aspects 1 through 6, wherein the RRC configuration is based at least in part on a channel quality. 
     Aspect 8: The method of any of Aspects 1 through 7, further comprising: transmitting, to the base station, a request for a type of RRC configuration based at least in part on a reference signal received power associated with a signal received from the base station, wherein the RRC configuration received from the base station is based at least in part on the request. 
     Aspect 9: The method of any of Aspects 1 through 8, wherein a plurality of active HARQ process IDs are not all included in the HARQ CB. 
     Aspect 10: The method of any of Aspects 1 through 9, wherein the HARQ CB is a Type 3 HARQ CB. 
     Aspect 11: A method of wireless communication performed by a base station, comprising: transmitting, to a user equipment (UE), a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) that indicates HARQ process identifiers (IDs) associated with the HARQ CB; and receiving, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB. 
     Aspect 12: The method of Aspect 11, wherein the RRC configuration indicates: a list of component carriers having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB. 
     Aspect 13: The method of any of Aspects 11 through 12, wherein the RRC configuration indicates: a list of component carriers having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB. 
     Aspect 14: The method of any of Aspects 11 through 13, wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers into a total quantity of configured HARQ CBs. 
     Aspect 15: The method of any of Aspects 11 through 14, wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ. 
     Aspect 16: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-10. 
     Aspect 17: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-10. 
     Aspect 18: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-10. 
     Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-10. 
     Aspect 20: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-10. 
     Aspect 21: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 11-15. 
     Aspect 22: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 11-15. 
     Aspect 23: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 11-15. 
     Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 11-15. 
     Aspect 25: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 11-15. 
     The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. 
     As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein. 
     As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like. 
     Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c). 
     No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).