User equipment framework for 32 hybrid automatic repeat / request processes

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may transmit a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, wherein the UE stores feedback process information in accordance with the quantity of feedback processes. The UE may receive a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, wherein the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

Description

USER EQUIPMENT FRAMEWORK FOR 32 HYBRID AUTOMATIC REPEAT / REQUEST PROCESSESCROSS REFERENCE

[0001] The present Application for Patent claims priority to Greece Patent Application No. 20240100380 by MANOLAKOS et al., entitled “USER EQUIPMENT FRAMEWORK FOR 32 HYBRID AUTOMATIC REPEAT / REQUEST PROCESSES,” filed May 21, 2024, assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.TECHNICAL FIELD

[0002] The following relates to wireless communication, including user equipment framework for 32 hybrid automatic repeat / request processes.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE- Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).SUMMARY

[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0005] A method for wireless communications by a user equipment (UE) is described. The method may include transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0006] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to transmit a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and receive a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0007] Another UE for wireless communications is described. The UE may include means for transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and means for receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to transmit a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and receive a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0009] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the bandwidth information includes one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported by the UE across all component carriers (CCs), a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes.

[0010] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the quantity of feedback processes supported by the UE include 32 hybrid automatic repeat / request (HARQ) processes.

[0011] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

[0012] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for maintaining the feedback process information stored by the UE based on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE.

[0013] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the first frequency configuration and thesecond frequency configuration comply with the quantity of feedback processes supported by the UE and may be associated with up to 32 feedback processes.

[0014] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and may be associated with up to 16 feedback processes.

[0015] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE.

[0016] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processes stored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

[0017] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for resetting the feedback process information stored by the UE based on the reconfiguration message.

[0018] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the first frequency configuration fails to comply with the quantity of feedback processes supported by the UE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes.

[0019] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for resetting the feedback process information stored by the UE based on the reconfiguration message.

[0020] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, each of the first frequency configuration and the second frequency configuration includes a first subset of CCs and a second subset of CCs, the first subset of CCs of the first frequency configuration may have a same quantity of feedback processes as the second frequency configuration, and the second subset of CCs of the first frequency configuration may have a different quantity of feedback processes from the second subset of CCs of the second frequency configuration.

[0021] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for maintaining the feedback process information stored by the UE for the first subset of CCs based on the same quantity of feedback processes and resetting the feedback process information stored by the UE for the second subset of CCs based on the different quantity of feedback processes.

[0022] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, based on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all CCs associated with the UE.

[0023] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, based on the UE capability message, a configuration message that identifies a number of feedback processes per CC associated with the UE.

[0024] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, based on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE.

[0025] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the first frequency configuration and thesecond frequency configuration comply with the upper limit of feedback processes and are, based on the compliance, associated with up to 32 feedback processes.

[0026] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

[0027] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a grant for a wireless communication associated with the first frequency configuration and discarding the grant based on a reset to the feedback process information stored by the UE according to the reconfiguration message.

[0028] A method for wireless communications by a network entity is described. The method may include obtaining, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0029] A network entity for wireless communications is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to obtain, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and output, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for theUE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0030] Another network entity for wireless communications is described. The network entity may include means for obtaining, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and means for outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0031] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to obtain, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes and output, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0032] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the bandwidth information includes one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported by the UE across all CCs, a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes.

[0033] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the quantity of feedback processes supported by the UE include 32 HARQ processes.

[0034] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

[0035] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the feedback process information stored by the UE may be maintained based on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE.

[0036] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first frequency configuration and the second frequency configuration comply with the quantity of feedback processes supported by the UE and may be associated with up to 32 feedback processes.

[0037] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and may be associated with up to 16 feedback processes.

[0038] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE.

[0039] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processes stored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

[0040] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the feedback process information stored by the UE may be reset based on the reconfiguration message.

[0041] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first frequency configuration fails to comply with the quantity of feedback processes supported by the UE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes.

[0042] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the feedback process information stored by the UE may be reset based on the reconfiguration message.

[0043] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, each of the first frequency configuration and the second frequency configuration includes a first subset of CCs and a second subset of CCs, the first subset of CCs of the first frequency configuration may have a same quantity of feedback processes as the second frequency configuration, and the second subset of CCs of the first frequency configuration may have a different quantity of feedback processes from the second subset of CCs of the second frequency configuration.

[0044] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the feedback process information stored by the UE may be maintained for the first subset of CCs based on the same quantity of feedback processes, and the feedback process information stored by the UE may be reset for the second subset of CCs based on the different quantity of feedback processes.

[0045] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the UE and based on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all CCs associated with the UE.

[0046] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the UE and based on the UE capabilitymessage, a configuration message that identifies a number of feedback processes per CC associated with the UE.

[0047] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the UE and based on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE.

[0048] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes and are, based on the compliance, associated with up to 32 feedback processes.

[0049] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

[0050] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the UE, a grant for a wireless communication associated with the first frequency configuration, where the UE discards the grant based on a reset to the feedback process information stored by the UE according to the reconfiguration message.

[0051] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS

[0052] FIG. 1 shows an example of a wireless communication system that supports user equipment (UE) framework for 32 hybrid automatic repeat / request (HARQ) processes in accordance with one or more aspects of the present disclosure.

[0053] FIG. 2 shows an example of a wireless communication system that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0054] FIG. 3 shows an example of a method that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0055] FIG. 4 shows an example of a method that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0056] FIGs. 5 and 6 show block diagrams of devices that support UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0057] FIG. 7 shows a block diagram of a communications manager that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0058] FIG. 8 shows a diagram of a system including a device that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0059] FIGs. 9 and 10 show block diagrams of devices that support UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0060] FIG. 11 shows a block diagram of a communications manager that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0061] FIG. 12 shows a diagram of a system including a device that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.

[0062] FIGs. 13 through 17 show flowcharts illustrating methods that support UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0063] Wireless networks may use hybrid automatic repeat / request (HARQ) processes to ensure successful wireless communications. The HARQ process may include a user equipment (UE) storing feedback information for a number of HARQ processes, where each HARQ process is associated with a particular downlink transmission from the network. However, each UE is generally limited by available memory (e.g., HARQ buffers, modem memory, or other storage mechanisms used by the UE to store HARQ-related information) such that only a certain number of feedback information may be stored at any one time. Moreover, some wireless networks may require that the UE maintain the feedback information being stored by the UE even when the network reconfigures the UE (such as when a new secondary cell (SCell) is added, removed, or otherwise reconfigured). This may result in the UE being unable to comply with the network requirements when reconfigured due to the UE limitations. This aspect may be further expanded when the number of HARQ processes for a specific frequency configuration is increased (e.g., such as from 16 to 32 HARQ processes).

[0064] Accordingly, aspects of the techniques described herein provide for UE capability reporting that identifies the support for 32 HARQ processes. For example, the UE may transmit or otherwise output (and the network entity may receive or otherwise obtain) a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE. For example, the bandwidth information may carry or otherwise identify an aggregated bandwidth, a number of component carriers (CCs), or other information for which the UE supports 32 HARQ processes. The UE may store feedback process information (e.g., HARQ process information) in accordance with the quantity of feedback processes supported by the UE. The UE may receive or otherwise obtain (and the network entity may transmit or otherwise output) a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration. For example, the changemay be a radio resource control (RRC) reconfiguration message identifying a SCell addition, release, or modification that leads to a switch to a different carrier aggregation (CA) configuration for the UE. The change may be associated with (e.g., may impact) one or more of the feedback processing information stored by the UE.

[0065] Aspects of the disclosure are initially described in the context of wireless communication systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to UE framework for 32 HARQ processes.

[0066] FIG. 1 shows an example of a wireless communication system 100 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE- A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

[0068] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, or mobile, orboth at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105), as shown in FIG. 1.

[0069] UEs 115 may be dispersed throughout the wireless communication system 100, and each UE 115 may be stationary or mobile. A UE 115 may also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client. A UE 115 may be a device such as a cellular phone, a smart phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, a MP3 player, or a video device), a camera, a gaming device, a navigation / positioning device (e.g., GNSS (global navigation satellite system) devices based on, for example, GPS (global positioning system), Beidou, GLONASS, or Galileo, or a terrestrial-based device), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, a vehicular device, a meter (e.g., parking meter, electric meter, gas meter, water meter), a monitor, a gas pump, an appliance (e.g., kitchen appliance, washing machine, dryer), a location tag, a medical / healthcare device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, a UE 115 may also refer to a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or an MTC device, or the like, which may be implemented in various articles such as appliances, drones, robots, vehicles, meters, or the like.

[0070] Some UEs 115, such as MTC or loT devices, may be low cost or low complexity devices, and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station without human intervention. In some examples, M2M communication or MTC may include communications from devices that integratesensors or meters to measure or capture information and relay that information to a central server or application program that can make use of the information or present the information to humans interacting with the program or application. Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging. In an aspect, techniques disclosed herein may be applicable to MTC or loT UEs. MTC or loT UEs may include MTC / enhanced MTC (eMTC, also referred to as CAT-M, Cat Ml) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), and mMTC (massive MTC), and NB-IoT may include eNB- loT (enhanced NB-IoT), and FeNB-IoT (further enhanced NB-IoT).

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

[0072] As described herein, a node of the wireless communication system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0073] In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link(s) 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network entities 105 may communicate with one another via backhaul communication link(s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communicationlink(s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0074] One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a 5GNB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140).

[0075] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165, a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the networkentities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0076] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs), or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170). In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of aprotocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

[0077] In some wireless communication systems (e.g., the wireless communication system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node(s) 104) may be partially controlled by each other. The IAB node(s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station). The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node(s) 104) via supported access and backhaul links (e.g., backhaul communication link(s) 120). IAB node(s) 104 may include an IAB mobile termination (IAB -MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node(s) 104 used for access via the DU 165 of the IAB node(s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB node(s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node(s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node(s) 104 or components of the IAB node(s) 104) may be configured to operate according to the techniques described herein.

[0078] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB node(s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node(s) 104 may communicate via anFl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.

[0079] IAB node(s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node(s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node(s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node(s) 104). Additionally, or alternatively, IAB node(s) 104 may also be referred to as parent nodes or child nodes to other IAB node(s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node(s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node(s) 104) to receive signaling from a parent IAB node (e.g., the IAB node(s) 104), and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

[0080] For example, IAB node(s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link(s) 120) to the core network 130 and may act as a parent node to IAB node(s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node(s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an Fl interface to IAB node(s) 104, and the IAB node(s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165). That is, data may be relayed to and from IAB node(s) 104 via signaling via an NR Uu interface to MT of IAB node(s) 104 (e.g., other IAB node(s)). Communications with IAB node(s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node(s) 104.

[0081] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

[0082] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

[0083] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0084] The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communicationsystem 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105).

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

[0086] In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non- standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT).

[0087] The communication link(s) 125 of the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from a networkentity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0088] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

[0089] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

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

[0091] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / (A / mflx■ Ay) seconds, for which fmaxmay represent a supported subcarrier spacing, and Ay may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0092] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communication systems, such as the wireless communication system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Ay) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0093] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

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

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

[0096] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with servicesubscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.

[0097] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

[0098] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0099] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones ofnetwork entities 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0100] Some UEs 115, such as MTC or loT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0101] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

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

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

[0104] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles may communicate using vehicle-to- everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or morenetwork nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to- network (V2N) communications, or with both.

[0105] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0106] The wireless communication system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0107] The wireless communication system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known asthe centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

[0108] The wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0109] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that thenetwork entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0110] The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas.Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0111] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to theantenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0112] A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.

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

[0114] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115). The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

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

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

[0117] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal -to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0118] A UE 115 may transmit a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE 115, wherein the UE 115 stores feedback process information in accordance with the quantity of feedback processes. The UE 115 may receive a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE 115, wherein the change is associated with one or more of the feedback process information stored by the UE 115 in accordance with the quantity of feedback processes.

[0119] A network entity 105 may obtain, from a UE 115, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE 115, wherein the UE 115 stores feedback process information in accordance with the quantity of feedback processes. The network entity 105 may output, to the UE 115, a reconfiguration message that identifies a change from a first frequencyconfiguration to a second frequency configuration for the UE 115, wherein the change is associated with one or more of the feedback process information stored by the UE 115 in accordance with the quantity of feedback processes.

[0120] FIG. 2 shows an example of a wireless communication system 200 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. Wireless communication system 200 may implement aspects of wireless communication system 100. Wireless communication system 200 may include a UE 205 a network entity 210, a network entity 215, and a network entity 220, which may be examples of the corresponding devices described herein. In some aspects, the network entity 210, the network entity 215, and the network entity 220 may cells within a cell group associated with the UE 205 (such as a CA cell group). For example, the network entity 210 may be a primary cell (PCell) while the network entity 215 and the network entity 220 are secondary cells (SCells) within the cell group.

[0121] Wireless networks may utilize multiple frequency ranges for wireless communications between UE and the network entities. For example, a frequency range one (FR1) and a frequency range two (FR2) may be used in different scenarios, with the FR2 being a higher radio frequency band relative to the FR1. One non-limiting example may include a CA scenario where the UE are configured to communicate in FR1 and FR2 within a cell group and using a single PUCCH group. The single PUCCH group may include the FR1 PUCCH communications from the UE being applied for FR1 and for FR2. For example, PUCCH communications from the UE may include information associated with both FR1 and FR2.

[0122] However, communications in different frequency ranges as well as in different directions (e.g., uplink vs downlink) may be associated with different coverage areas. For example, aspects of FR2 communications may include communications at a higher frequency, thus reducing the range of the communications relative to communications in FR1. Moreover, downlink communications in FR2 from the network entity (which is equipped with a higher transmit power or improved directional capabilities) provides a greater coverage area than uplink communications in FR2 from the UE (which uses a lower transmit power or reduced directional capabilities relative to the network entity). Thus, the downlink coverage area for FR2 communications may be greater that the corresponding uplink coverage area for FR2. For the FR2 downlinkcommunications using the single PUCCH group, the peak FR2 downlink throughput may further need to be reduced in some wireless networks.

[0123] For example, the PDSCH (e.g., downlink communications) cannot be transmitted in every downlink or special slot of FR2 CC(s) due to the HARQ-ACK feedback delay. The mismatch in timing between the SCS of FR1 and the SCS of FR2 may result in the downlink or special slot availability in FR1 (e.g., used for the HARQ- ACK feedback in the single PUCCH group) being such that the downlink communications in FR2 has to be throttled, at least to some degree. For example, the network entity may have to wait for the HARQ-ACK feedback related to FR2 downlink communications to resume PDSCH transmissions for the same HARQ process identifier. The maximum number of PDSCH transmissions without HARQ-ACK feedback may be limited by the number of HARQ processes configured per CC.

[0124] Wireless networks may also include the UE supporting 32 HARQ processes. For example, the UE may be capable of supporting 32 HARQ processes, such as in FR1-FR2 TDD CA where the ACKs from FR2 CCs are sent to the one PUCCH group in FR1. However, this approach may result in accommodating 32 HARQ processes only for a limited number of CCs, which may be less than the peak CA envelope due to the HARQ buffer size limitation or the firmware memory limitation of the UE.

[0125] That is, one limitation of UE regarding support for 32 HARQ processes may include the HARQ buffer budget (e.g., the amount of buffer spaced available for use) to store log likelihood ratios (LLRs) and the modem memory budget to store and maintain HARQ state information per HARQ process identifier. For example, UE are generally equipped with or otherwise support enough memory to store a limited amount of information (e.g., LLRs or HARQ state information) related to each HARQ process of the UE. As one non-limiting example, a UE may have enough memory to support downlink CA across five CCs. This means that the UE has enough memory to support 80 HARQ processes (e.g., five CCs multiplied by 16 HARQ processes per-CC, according to some wireless networks). If the UE were to be configured with 32 HARQ processes per-CC, this may result in the UE supporting 32 HARQ processes for up to 2 CCs (e.g., 80 HARQ processes divided by 32 HARQ process support=2.5, rounding down to 2 CCs that the UE can support 32 HARQ processes in). Downlinkcommunications in FR2 may provide an increased amount of downlink or special slots such that a large number of HARQ processes may be used with the UE.

[0126] Additionally, in some wireless networks the UE is required to maintain the HARQ state or buffer information being stored across SCell addition, release, or reconfiguration. For example, when a new SCell is added, the UE is required to maintain the HARQ state or buffer information for the already configured PCell and SCell(s). When the HARQ related parameters (such as the number of HARQ processes) of the existing SCell(s) are reconfigured, the UE should maintain the HARQ state or buffer information for the already configured PCell and SCell(s).

[0127] However, this approach may be difficult (or not possible) for a UE with a limited HARQ capability. For example, when the UE is configured with M CCs with 32 HARQ processes per CC and a new SCell is added, the UE may not be able to maintain 32 HARQ processes for the existing SCell(s). When the UE is configured with N>M CCs with 16 HARQ processes per CC and some SCell(s) are released with a number of associated HARQ processes being reconfigured to 32 HARQ processes for the remaining K<N CCs, the UE may have to reset the HARQ state or buffer information due to the need for memory map reconfiguration.

[0128] Accordingly, the techniques described herein provide for UE capability reporting regarding the maximum number of HARQ processes supported by the UE. For example, the UE 205 may transmit or otherwise output (and the network entity 210 may receive or otherwise obtain, which is the PCell in this example) a UE capability message that identifies bandwidth information associated with a quantity of feedback processes (e.g., HARQ processes) supported by the UE 205. The UE 205 may generally store feedback process information (e.g., HARQ state or buffer information) in accordance with the quantity of feedback processes supported by the UE 205. For example, the UE 205 may receive or otherwise obtain downlink transmissions from the cells within the cell group and store HARQ information (e.g., feedback process information) associated with the downlink transmissions. In some examples, the downlink transmissions may be provided via FR2 as part of a CA configuration associated with the UE 205.

[0129] In some aspects, the bandwidth information may include information used by the network entity 210 to identify or otherwise determine an amount of HARQ processes that can be configured for the UE 205. In some cases, this information may be used when configuring the UE 205 for CA operations within a cell group. That is, the cell(s) within the cell group may use the bandwidth information to identify or otherwise determine how to configure the UE 205 for CA operations within the cell group (e.g., for addition, release, or reconfiguration of one or more SCells within the cell group).

[0130] Examples of the bandwidth information may include, but are not limited to, a limit of the feedback processes supported by the UE 205 per frequency band, a limit on the total number of feedback processes support by the UE 205 across all CCs, a limit on a subband size supported by the UE 205 per CC, an aggregated bandwidth supported by the UE 205 across all CCs with 32 HARQ processes, or a quantity of CCs supported by the UE 205 with 32 feedback processes. The UE 205 may configure the UE capability message to carry or otherwise convey information identifying one or more of the abovenoted information for the network entity 210 (e.g., the PCell, in this example). This may include the UE capability message indicating the maximum aggregated channel bandwidth across CCs supporting 32 HARQ processes in the band. This may include the UE capability message indicating the maximum number of CCs supporting 32 HARQ processes in the band.

[0131] As one non-limiting example, for a downlink CA configuration (e.g., a frequency configuration) in FR1 and FR2 -based CA, the UE 205 may indicate 32 HARQ process support for {up to 800 MHz aggregated bandwidth, up to five CCs} for the FR2 band. For example, the UE 205 may report support for a maximum number of CCs based on a common pool of 192 HARQ processes across or per-CC. This may support the UE 205 being configured with a frequency configuration (e.g., configuration A) having six CCs (or aggregated bandwidth) with HARQ processes according to: 32, 32, 32, 32, 16, and 16 (e.g., four CCs with 32 HARQ processes and two CCs with 16 HARQ processes). This may support the UE 205 being configured with a frequency configuration (e.g., configuration B) having ten CCs (or aggregated bandwidth) with HARQ processes according to: 16, 16, 16, 16, 16, 16, 16, 16, 16, and 16 (e.g., ten CCs each with 16 HARQ processes).

[0132] Accordingly, aspects of the bandwidth information reported by the UE 205 in the UE capability message may be based on various factors. One aspect may include the bandwidth information relating to the limit on the number of HARQ processes supported by the UE 205 (e.g., 190 HARQ processes, continuing with the example above). Another aspect may include the bandwidth information relating to the limit on the total number of HARQ processes across all CCs (e.g., per UE or per band combination). Another aspect may include the bandwidth information relating to the limit on the subband size, which may be provided according to: subband size = number of HARQ processes x number of layers x maximum modulation order x maximum PRBs per CC (per UE or per band combination). Another aspect may include the bandwidth information related to the aggregated bandwidth across all CCs with 32 HARQ processes. Another aspect may include the bandwidth information relating to the number of CCs with 32 HARQ processes.

[0133] In some examples, separate bandwidth information may be reported for downlink communications and uplink communications. That is, the UE capability reporting for 32 HARQ process support may be separately indicated for downlink and uplink HARQ operations. For example, first bandwidth information for downlink communications and second bandwidth information for uplink communications may be reported in the UE capability message provided by the UE 205.

[0134] Accordingly, the gNB (e.g., the network entity 210, in this example) may configure the UE 205 with 32 HARQ processes for any of the CCs when the {aggregated bandwidth, number of CCs} of the CA configuration is within the UE capability (e.g., based on the bandwidth information reported in the UE capability message). When the SCell(s) configuration results in a CA configuration with the {aggregated bandwidth, number of CCs} exceeds the UE capability, the gNB cannot configure 32 HARQ processes for any CCs (e.g., all CCs would need to have 16 HARQ processes configured).

[0135] The UE 205 may receive or otherwise obtain (and the network entity 210 may transmit or otherwise output) a reconfiguration message that identifies a change from a first frequency configuration (e.g., a first CA configuration) to a second frequency configuration (e.g., a second CA configuration) for the UE 205. The change may be associated with one or more of the feedback process information stored by theUE 205 in accordance with the quantity of feedback processes being stored by the UE 205. In some aspects, the reconfiguration message may include an RRC (re)configuration message that adds, releases, or reconfigures one or more SCells in the cell group associated with the UE 205.

[0136] In some examples, this may provide for CA reconfiguration without the UE 205 resetting the HARQ state (e.g., the feedback process information stored by the UE 205). That is, the UE 205 may maintain the feedback process information stored by the UE 205 based on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE 205. For example, the UE 205 may receive a RRC (re)configuration with SCell addition, release, or modification that leads to a switch from CA configuration A to CA configuration B. If the {aggregated bandwidth, number of CCs} of both configuration A and configuration B are within the UE’s capability for 32 HARQ processes, the CCs in configuration A and in configuration B may be configured with either 32 HARQ processes or M<16 HARQ processes. The UE 205, in this example, may maintain the HARQ buffer or state information being stored during the RRC (re)configuration. That is, in this example both the first frequency configuration and the second frequency configuration comply with the quantity of feedback processes supported by the UE 205 and are associate with up to 32 feedback processes. Thus, in this example where configuration A includes four CCs and configuration B includes five CCs, if the UE 205 supports up to five CCS with 32 HARQ processes, then the transition from configuration A (e.g., the first frequency configuration) to configuration B (e.g., the second frequency configuration) does not require a HARQ reset at the UE 205 or at the network.

[0137] However, in another example the first frequency configuration and the second frequency configuration may both fail to comply with the quantity of feedback processes supported by the UE 205. In this example, both configurations may be associated with up to 16 feedback processes. That is, if the {aggregated bandwidth, number of CCs} of both configuration A and configuration B exceed the UE’s capability for 32 HARQ processes, the CCs in configuration A and in configuration B may be configured with M<16 HARQ processes. The UE 205, in this example, maymaintain the feedback process information (e.g., the HARQ buffer or state information) being stored during the RRC (re)configuration.

[0138] However, in other examples the configuration B may have more than five CCs (e.g., may exceed the UE’s capability as reported in the UE capability message). For example, the configuration B may have six CCs. In this example, aspects of the techniques described herein may provide for at least some degree of HARQ reset.

[0139] As one non-limiting example, this may include the first frequency configuration (e.g., configuration A) complying with the quantity of feedback processes supported by the UE 205. Based on this compliance, the first frequency configuration may be configured with or otherwise associated with up to 32 HARQ processes. However, in this example the second frequency configuration may fail to comply with the quantity of feedback processes stored by the UE 205. Based on this failure to comply, the second frequency configuration may be configured with or otherwise associated with up to 16 feedback processes. In this example, the UE 205 and the network may reset the feedback process information based on the reconfiguration message. That is, if the {aggregated bandwidth, number of CCs} of configuration A is within the UE’s capability for 32 HARQ processes and the {aggregated bandwidth, number of CCs} of configuration B exceed the UE’s capability for 32 HARQ processes, the CCs in configuration A may be configured with either 32 HARQ processes or M<16 HARQ processes. However, the CCs in configuration B may be configured with M<16 HARQ processes. In this scenario, the UE 205 is allowed to reset the HARQ state for all CCs in the band during RRC (re)configuration when the number of HARQ processes are changed from 32 to M<16 for any CC in configuration B after RRC (re)configurati on .

[0140] As another non-limiting example, this may include the first frequency configuration failing to comply with the quantity of feedback processes supported by the UE 205. Based on this failure to comply, the first frequency configuration may be configured with or otherwise support up to 16 feedback processes. In this example, the second frequency configuration may comply with the quantity of feedback processes supported by the UE 205. Based on this compliance, the second frequency configuration may be configured with or otherwise associated with up to 32 feedback processes. Accordingly, the UE 205 may reset the feedback process information stored by the 250based on the reconfiguration message (e.g., in response to). That is, if the {aggregated bandwidth, number of CCs} of configuration A exceed the UE’s capability for 32 HARQ processes and the {aggregated bandwidth, number of CCs} of configuration B are within the UE’s capabilities for 32 HARQ processes, the CCs in configuration A may be configured with M<16 HARQ processes. However, the CCs in configuration B may be configured with either 32 HARQ processes or M<16 HARQ processes. The UE 205 is allowed to reset the HARQ state for all CCs in the band during RRC (re)configuration when the number of HARQ processes are changed from M<16 to 32 for any CCs in configuration B after RRC (re)configuration.

[0141] In some aspects, the UE 205 may advertise its capability for maintaining or resetting the feedback information stored by the UE 205 (such as in the UE capability message or using different signaling). For example, the UE 205 may indicate that the UE 205 can maintain the HARQ state information for certain scenarios. If the UE 205 has advertised such capability, the UE 205 may be expected to maintain the HARQ buffer or state information during RRC (re)configuration.

[0142] In some examples, this may include a partial HARQ reset (e.g., as compared to a full HARQ reset), such as for only the CC(s) that have a different number of HARQ processes being reset). For example, each of the first frequency configuration and the second frequency configuration may include a first subset of CC(s) and a second subset of CC(s). The first subset of CC(s) of the first frequency configuration may have the same quantity of feedback processes as the second frequency configuration. However, the second subset of CC(s) of the first frequency configuration may have a different quantity of feedback processes from the second subset of CC(s) in the second frequency configuration. Accordingly, the UE 205 may maintain the feedback process information stored by the UE 205 for the first subset of CC(s) based on the same quantity of feedback processes and reset the feedback process information stored by the UE 205 for the second subset of CC(s) based on the different quantity of feedback processes. As one non-limiting example, the UE 205 may go from configuration A that includes two CCs each with 32 HARQ processes (32, 32) to configuration B with three CCs that includes three CCs, two with 16 HARQ processes and one with 32 HARQ processes (16, 32, 16). In this situation, any CC that result in a change to the maximum number ofHARQ processes may be reset, but if the maximum number of HARQ processes do not change then the HARQ buffer will not be reset.

[0143] Accordingly, in some aspects the gNB (e.g., the network entity 210, in this example) may need to configure the UE 205 with 32 HARQ processes. For example, the network entity 210 may configure the number of HARQ processes via RRC (re)configuration signaling. Different approaches may be applied for such signaling. One approach may include the UE 205 receiving or otherwise obtaining (and the network entity 210 transmitting or otherwise outputting) a configuration message that identifies a same number of feedback processes applicable to all CCs associated with the UE 205. For example, the gNB may explicitly configure the same number of HARQ processes applicable to all CCs in the RRC (re)configuration message for SCell addition, release, or modification. In some aspects, the RRC (re)configuration message may be based on the UE capability message provided by the UE 205.

[0144] Another approach may include the UE 205 receiving or otherwise obtaining (and the network entity 210, in this example, transmitting or otherwise outputting) a configuration message that identifies a number of feedback processes per CC associated with the UE 205. For example, the gNB may explicitly configure the number of HARQ processes for each CC in the RRC (re)configuration message for SCell addition, release, or modification. In some aspects, the RRC (re)configuration message may be based on the UE capability message provided by the UE 205.

[0145] Yet another approach may include the UE 205 receiving or otherwise obtaining (and the network entity 210, in this example, transmitting or otherwise outputting) a configuration message that identifies an upper limit of feedback processes associated with the UE 205. For example, the gNB may indicate an upper bound for the {aggregated bandwidth, number of CCs} per feedback process (e.g., band or band combination) to enable 32 HARQ processes. In an example where both the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes, both configurations may be configured with or otherwise associated with 32 feedback processes. That is, if the {aggregated bandwidth, number of CCs} of CA configuration is within the gNB -configured upper bound, then 32 HARQ processes may be implicitly configured for all the CCs in the band.

[0146] In an example whether either or both of the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes, each or both configurations may be configured with or otherwise associated with up to 16 feedback processes. That is, if the {aggregated bandwidth, number of CCs} of the CA configuration exceeds the gNB-configured upper bound, then M<16 HARQ processes may be implicitly configured for all CCs in the band (M is the number of HARQ processes during the SCell addition).

[0147] As discussed above, in some examples the UE 205 may reset some or all of the HARQ buffer or state information being stored. In this scenario, the network entity 210 (in this example) may also need to restart HARQ scheduling when the UE 205 is supposed to reset the HARQ state or buffer information during SCell addition, release, or modification. For example, the UE 205 may receive or otherwise obtain (and the network entity 210, in this example, may transmit or otherwise output) a grant for wireless communications associated with the first frequency configuration. In this example, the UE 205 may discard the grant based on a reset to the feedback process information being stored by the UE 205 according to the reconfiguration message. If the gNB schedules PDSCH with HARQ retransmission for CC(s) with discarded HARQ state or buffer information, the UE 205 may be allowed to drop the PDSCH scheduling. If the gNB schedules PUSCH with HARQ retransmission for CC(s) with discarded HARQ state or buffer information, the UE 205 may be allowed to ignore the PUSCH scheduling.

[0148] FIG. 3 shows an example of a method 300 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. Method 300 may implement aspects of wireless communication system 100 or wireless communication system 200. Aspects of method 300 may be implemented at or implemented by a UE or a network entity, which may be examples of the corresponding devices described herein.

[0149] At 305, the UE may transmit or otherwise output a UE capability message. The UE capability message may carry or otherwise convey information that identifies bandwidth information associated with a quantity of feedback processes supported by the UE. For example, the bandwidth information may provide an indication of the number of 32 HARQ processes supported by the UE. For example, the bandwidthinformation may include one or both of the {aggregated bandwidth, number of CCs} information that identifies how may HARQ processes the UE can support storing feedback process information (e.g., HARQ state or buffer information) for. The UE may, therefore, store feedback process information in accordance with the quantity of feedback processes. For example, the UE may perform uplink or downlink communications with a network entity and store the HARQ information associated with such communications until that information can be reported to the network entity via HARQ-ACK signaling. In some examples, the uplink or downlink communications may be associated with FR2 communications while the corresponding HARQ-ACK signaling is provided in FR1 (along with HARQ-ACK information associated with FR1- based communications).

[0150] At 310, the UE may receive or otherwise obtain a (re)configuration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE. In some example, the (re)configuration message may include an RRC (re)configuration message associated with SCell addition, release, or modification, such as for a CA group associated with the UE.

[0151] In some aspects, the change to the second frequency configuration may be associated with one or more of the feedback process information stored by the UE according to the quantity of feedback processes (e.g., the quantity of feedback processes supported by the UE in the UE capability message). For example, at 315 the UE may identify or otherwise determine whether or not the first frequency configuration, the second frequency configuration, or both configurations are with the UE’s capability for 32 HARQ processes.

[0152] If so, at 320 the updated frequency configuration (e.g., the second frequency configuration) may be configured with 32 HARQ processes. That is, the network entity may (re)configure the UE with the first frequency configuration, with the second frequency configuration, or both configuration, with 32 HARQ processes based on the UE capability message. Accordingly, the gNB may configure 32 HARQ processes for any of the CCs when the {aggregated bandwidth, number of CCs} of the CA configuration are within the UE capability.

[0153] If not, at 325 the updated frequency configuration (e.g., the second frequency configuration) may be configured with up to 16 HARQ processes (e.g., M<16 HARQ processes). That is, the network entity may (re)configure the UE with the first frequency configuration, with the second frequency configuration, or both configuration, with M<16 HARQ processes based on the UE capability message. Accordingly, when the SCells configuration leads to a CA configuration with the {aggregated bandwidth, number of CCs} that exceeds the UE capabilities, the gNB cannot configure 32 HARQ processes for any CCs (e.g., all CCs would be configured with 16 HARQ processes).

[0154] FIG. 4 shows an example of a method 400 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. Method 400 may implement aspects of wireless communication system 100 or wireless communication system 200 or aspect of method 300. Aspects of method 400 may be implemented at or implemented by a UE or a network entity, which may be examples of the corresponding devices described herein.

[0155] At 405, the network entity may receive or otherwise obtain a UE capability message from a UE. The UE capability message may carry or otherwise convey information that identifies bandwidth information associated with a quantity of feedback processes supported by the UE. For example, the bandwidth information may provide an indication of the number of 32 HARQ processes supported by the UE. The bandwidth information may include one or both of the {aggregated bandwidth, number of CCs} information that identifies how may HARQ processes the UE can support storing feedback process information (e.g., HARQ state or buffer information) for. The UE may, therefore, store feedback process information in accordance with the quantity of feedback processes. For example, the UE may perform uplink or downlink communications with a network entity and store the HARQ information associated with such communications until that information can be reported to the network entity via HARQ-ACK signaling. In some examples, the uplink or downlink communications may be associated with FR2 communications while the corresponding HARQ-ACK signaling is provided in FR1 (along with HARQ-ACK information associated with FR1- based communications).

[0156] At 410, the network entity may transmit or otherwise output a (re)configuration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE. In some example, the (re)configuration message may include an RRC (re)configuration message associated with SCell addition, release, or modification, such as for a CA group associated with the UE.

[0157] In some aspects, the change to the second frequency configuration may be associated with one or more of the feedback process information stored by the UE according to the quantity of feedback processes (e.g., the quantity of feedback processes supported by the UE in the UE capability message). For example, at 415 the network entity may identify or otherwise determine whether or not the first frequency configuration, the second frequency configuration, or both configurations are with the UE’s capability for 32 HARQ processes. For example, the network entity may identify or otherwise determine whether the (re)configuration from configuration A to configuration B will result in the UE resetting the feedback process information being stored by the UE or maintaining the feedback process information being stored by the UE.

[0158] As one non-limiting example, when the (re)configuration message changes the UE’s frequency configuration from configuration A that is within the UE’s capability for 32 HARQ processes to configuration B that exceeds the UE’s capability for 32 HARQ processes, the UE may be allowed to reset the HARQ state or buffer information for all CCs during RRC (re)configuration when the number of HARQ processes are changed from 32 to M<16 for any CC in configuration B after the RRC (re)configuration. As another non-limiting example, when the (re)configuration message changes the UE’s frequency configuration from configuration A that exceeds the UE’s capability for 32 HARQ processes to configuration B that is within the UE’s capability for 32 HARQ processes, the UE may be allowed to reset the HARQ state for all CCs in the band during RRC (re)configuration. As yet another non-limiting example, when the {aggregated bandwidth, number of CCs} of both configuration A and configuration B are within the UE’s capability for 32 HARQ processes, the UE may maintain the HARQ buffer or state information during the RRC (re)configuration.

[0159] If the network entity determines that the UE will maintain the feedback process information being stored, at 420 the network entity may maintain the HARQscheduling associated with the UE. That is, the network entity may perform one or more retransmissions of downlink communications to the UE based on receiving HARQ- ACK reporting from the UE for the corresponding HARQ process.

[0160] If the network entity determines that the UE will reset the feedback process information being stored, at 425 the network entity may reset the HARQ scheduling associated with the UE. For example, the network entity may reset any HARQ processes for which the HARQ state or buffer information was being stored but has now been reset by the UE in response to the (re)configuration message. Moreover, the network entity may discard any grant(s) for retransmissions that had previously been sent to the UE for the HARQ processes that were reset.

[0161] FIG. 5 shows a block diagram 500 of a device 505 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520), may include at least one processor, which may be coupled with (e.g., operatively, communicatively, functionally, electronically, or electrically) at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0162] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to UE framework for 32 HARQ processes). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

[0163] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to UE framework for 32 HARQ processes). In someexamples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0164] The communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be examples of means for performing various aspects of UE framework for 32 HARQ processes as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

[0166] Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware, code (e.g., as communications management software) executed by at least one processor (e.g., referred to as a processor-executable code), or any combination thereof. If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, a GPU, a NPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0167] In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0168] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The communications manager 520 is capable of, configured to, or operable to support a means for receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0169] By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for UE capability reporting for 32 HARQ processes where bandwidth information (e.g., aggregated bandwidth, number of CCs, or similar information, is used to signal to the network the quantity of feedback processes supported by the UE.

[0170] FIG. 6 shows a block diagram 600 of a device 605 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one of more components of the device 605 (e.g., the receiver 610, the transmitter 615, the communications manager 620), may include at least one processor, which may be coupled with at leastone memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0171] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to UE framework for 32 HARQ processes). Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0172] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to UE framework for 32 HARQ processes). In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0173] The device 605, or various components thereof, may be an example of means for performing various aspects of UE framework for 32 HARQ processes as described herein. For example, the communications manager 620 may include a capability reporting manager 625 a reconfiguration manager 630, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0174] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The capability reporting manager 625 is capable of, configured to, or operable to support a means for transmitting a UEcapability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The reconfiguration manager 630 is capable of, configured to, or operable to support a means for receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0175] FIG. 7 shows a block diagram 700 of a communications manager 720 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of UE framework for 32 HARQ processes as described herein. For example, the communications manager 720 may include a capability reporting manager 725, a reconfiguration manager 730, an HARQ storage manager 735, an HARQ configuration manager 740, a grant manager 745, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0176] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The capability reporting manager 725 is capable of, configured to, or operable to support a means for transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The reconfiguration manager 730 is capable of, configured to, or operable to support a means for receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0177] In some examples, the bandwidth information includes one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported by the UE across all CCs, a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes. In some examples, the quantity of feedback processes supported by the UE include 32 HARQ processes. In some examples, the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

[0178] In some examples, the HARQ storage manager 735 is capable of, configured to, or operable to support a means for maintaining the feedback process information stored by the UE based on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE. In some examples, the first frequency configuration and the second frequency configuration comply with the quantity of feedback processes supported by the UE and are associated with up to 32 feedback processes. In some examples, the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and are associated with up to 16 feedback processes. In some examples, the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE.

[0179] In some examples, the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processes stored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

[0180] In some examples, the HARQ storage manager 735 is capable of, configured to, or operable to support a means for resetting the feedback process information stored by the UE based on the reconfiguration message. In some examples, the first frequency configuration fails to comply with the quantity of feedback processes supported by the UE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedbackprocesses supported by the UE and is, based on the compliance, associated with up to 32 feedback processes.

[0181] In some examples, the HARQ storage manager 735 is capable of, configured to, or operable to support a means for resetting the feedback process information stored by the UE based on the reconfiguration message. In some examples, each of the first frequency configuration and the second frequency configuration includes a first subset of CCs and a second subset of CCs. In some examples, the first subset of CCs of the first frequency configuration has a same quantity of feedback processes as the second frequency configuration. In some examples, the second subset of CCs of the first frequency configuration has a different quantity of feedback processes from the second subset of CCs of the second frequency configuration.

[0182] In some examples, the HARQ storage manager 735 is capable of, configured to, or operable to support a means for maintaining the feedback process information stored by the UE for the first subset of CCs based on the same quantity of feedback processes. In some examples, the HARQ storage manager 735 is capable of, configured to, or operable to support a means for resetting the feedback process information stored by the UE for the second subset of CCs based on the different quantity of feedback processes.

[0183] In some examples, the HARQ configuration manager 740 is capable of, configured to, or operable to support a means for receiving, based on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all CCs associated with the UE. In some examples, the HARQ configuration manager 740 is capable of, configured to, or operable to support a means for receiving, based on the UE capability message, a configuration message that identifies a number of feedback processes per CC associated with the UE. In some examples, the HARQ configuration manager 740 is capable of, configured to, or operable to support a means for receiving, based on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE.

[0184] In some examples, the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes and are,based on the compliance, associated with up to 32 feedback processes. In some examples, the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

[0185] In some examples, the grant manager 745 is capable of, configured to, or operable to support a means for receiving a grant for a wireless communication associated with the first frequency configuration. In some examples, the grant manager 745 is capable of, configured to, or operable to support a means for discarding the grant based on a reset to the feedback process information stored by the UE according to the reconfiguration message.

[0186] FIG. 8 shows a diagram of a system 800 including a device 805 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof). The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input / output (UO) controller, such as an I / O controller 810, a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0187] The I / O controller 810 may manage input and output signals for the device 805. The I / O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the EO controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the EO controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the EO controller 810 may be implemented as part of one or more processors, such as the at least one processor 840.In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0188] In some cases, the device 805 may include a single antenna. However, in some other cases, the device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally via the one or more antennas 825 using wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.

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

[0190] The at least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more GPUs, one or more NPUs (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combinationthereof). In some cases, the at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 840. The at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting UE framework for 32 HARQ processes). For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and the at least one memory 830 configured to perform various functions described herein.

[0191] In some examples, the at least one processor 840 may include multiple processors and the at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory circuitry (which may include the at least one memory 830)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 835 (e.g., processor-executable code) stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.

[0192] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for transmitting a UE capability message that identifies bandwidth information associatedwith a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The communications manager 820 is capable of, configured to, or operable to support a means for receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0193] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for UE capability reporting for 32 HARQ processes where bandwidth information (e.g., aggregated bandwidth, number of CCs, or similar information, is used to signal to the network the quantity of feedback processes supported by the UE.

[0194] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of UE framework for 32 HARQ processes as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

[0195] FIG. 9 shows a block diagram 900 of a device 905 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques.Each of these components may be in communication with one another (e.g., via one or more buses).

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

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

[0198] The communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performing various aspects of UE framework for 32 HARQ processes as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

[0200] Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware, code (e.g., as communications management software) executed by at least one processor (e.g., referred to as a processor-executable code), or any combination thereof. If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, a GPU, a NPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0201] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0202] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for obtaining,from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The communications manager 920 is capable of, configured to, or operable to support a means for outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0203] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for UE capability reporting for 32 HARQ processes where bandwidth information (e.g., aggregated bandwidth, number of CCs, or similar information, is used to signal to the network the quantity of feedback processes supported by the UE.

[0204] FIG. 10 shows a block diagram 1000 of a device 1005 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one of more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

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

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

[0207] The device 1005, or various components thereof, may be an example of means for performing various aspects of UE framework for 32 HARQ processes as described herein. For example, the communications manager 1020 may include a capability reporting manager 1025 a reconfiguration manager 1030, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0208] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The capability reporting manager 1025 is capable of, configured to, or operable to support a means for obtaining, from aUE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The reconfiguration manager 1030 is capable of, configured to, or operable to support a means for outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0209] FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of UE framework for 32 HARQ processes as described herein. For example, the communications manager 1120 may include a capability reporting manager 1125, a reconfiguration manager 1130, an HARQ configuration manager 1135, a grant manager 1140, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0210] The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. The capability reporting manager 1125 is capable of, configured to, or operable to support a means for obtaining, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. Thereconfiguration manager 1130 is capable of, configured to, or operable to support a means for outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0211] In some examples, the bandwidth information includes one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported by the UE across all CCs, a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes. In some examples, the quantity of feedback processes supported by the UE include 32 HARQ processes. In some examples, the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

[0212] In some examples, the feedback process information stored by the UE is maintained based on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE. In some examples, the first frequency configuration and the second frequency configuration comply with the quantity of feedback processes supported by the UE and are associated with up to 32 feedback processes. In some examples, the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and are associated with up to 16 feedback processes. In some examples, the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE. In some examples, the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processes stored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

[0213] In some examples, the feedback process information stored by the UE is reset based on the reconfiguration message. In some examples, the first frequency configuration fails to comply with the quantity of feedback processes supported by theUE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes. In some examples, the feedback process information stored by the UE is reset based on the reconfiguration message.

[0214] In some examples, each of the first frequency configuration and the second frequency configuration includes a first subset of CCs and a second subset of CCs. In some examples, the first subset of CCs of the first frequency configuration has a same quantity of feedback processes as the second frequency configuration. In some examples, the second subset of CCs of the first frequency configuration has a different quantity of feedback processes from the second subset of CCs of the second frequency configuration. In some examples, the feedback process information stored by the UE is maintained for the first subset of CCs based on the same quantity of feedback processes, and the feedback process information stored by the UE is reset for the second subset of CCs based on the different quantity of feedback processes.

[0215] In some examples, the HARQ configuration manager 1135 is capable of, configured to, or operable to support a means for outputting, to the UE and based on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all CCs associated with the UE. In some examples, the HARQ configuration manager 1135 is capable of, configured to, or operable to support a means for outputting, to the UE and based on the UE capability message, a configuration message that identifies a number of feedback processes per CC associated with the UE. In some examples, the HARQ configuration manager 1135 is capable of, configured to, or operable to support a means for outputting, to the UE and based on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE. In some examples, the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes and are, based on the compliance, associated with up to 32 feedback processes. In some examples, the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

[0216] In some examples, the grant manager 1140 is capable of, configured to, or operable to support a means for outputting, to the UE, a grant for a wireless communication associated with the first frequency configuration, where the UE discards the grant based on a reset to the feedback process information stored by the UE according to the reconfiguration message.

[0217] FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include components of a device 905, a device 1005, or a network entity 105 as described herein. The device 1205 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, one or more antennas 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1240).

[0218] The transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configuredto support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or one or more memory components (e.g., the at least one processor 1235, the at least one memory 1225, or both), may be included in a chip or chip assembly that is installed in the device 1205. In some examples, the transceiver 1210 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0219] The at least one memory 1225 may include RAM, ROM, or any combination thereof. The at least one memory 1225 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1230. The code 1230 may include instructions that, when executed by one or more of the at least one processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non -transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by a processor of the at least one processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1225 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0220] The at least one processor 1235 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1235. The at least one processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting UE framework for 32 HARQ processes). For example, the device 1205 or a component of the device 1205 may include at least one processor 1235 and at least one memory 1225 coupled with one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 configured to perform various functions described herein. The at least one processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205. The at least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within one or more of the at least one memory 1225).

[0221] In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1235 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1235) and memory circuitry (which may includethe at least one memory 1225)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1235 or a processing system including the at least one processor 1235 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1225 or otherwise, to perform one or more of the functions described herein.

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

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

[0224] The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communicationsmanager 1220 is capable of, configured to, or operable to support a means for obtaining, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The communications manager 1220 is capable of, configured to, or operable to support a means for outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0225] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for UE capability reporting for 32 HARQ processes where bandwidth information (e.g., aggregated bandwidth, number of CCs, or similar information, is used to signal to the network the quantity of feedback processes supported by the UE.

[0226] In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, one or more of the at least one processor 1235, one or more of the at least one memory 1225, the code 1230, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1235, the at least one memory 1225, the code 1230, or any combination thereof). For example, the code 1230 may include instructions executable by one or more of the at least one processor 1235 to cause the device 1205 to perform various aspects of UE framework for 32 HARQ processes as described herein, or the at least one processor 1235 and the at least one memory 1225 may be otherwise configured to, individually or collectively, perform or support such operations.

[0227] FIG. 13 shows a flowchart illustrating a method 1300 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of thepresent disclosure. The operations of the method 1300 may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0228] At 1305, the method may include transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a capability reporting manager 725 as described with reference to FIG. 7.

[0229] At 1310, the method may include receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a reconfiguration manager 730 as described with reference to FIG. 7.

[0230] FIG. 14 shows a flowchart illustrating a method 1400 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0231] At 1405, the method may include transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordancewith the quantity of feedback processes. The operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a capability reporting manager 725 as described with reference to FIG. 7.

[0232] At 1410, the method may include receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes. The operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a reconfiguration manager 730 as described with reference to FIG. 7.

[0233] At 1415, the method may include maintaining the feedback process information stored by the UE based on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE. The operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by an HARQ storage manager 735 as described with reference to FIG. 7.

[0234] FIG. 15 shows a flowchart illustrating a method 1500 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or its components as described herein. For example, the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0235] At 1505, the method may include transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of theoperations of 1505 may be performed by a capability reporting manager 725 as described with reference to FIG. 7.

[0236] At 1510, the method may include receiving, based on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all component carriers (CCs) associated with the UE. The operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by an HARQ configuration manager 740 as described with reference to FIG. 7.

[0237] At 1515, the method may include receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes. The operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a reconfiguration manager 730 as described with reference to FIG. 7.

[0238] FIG. 16 shows a flowchart illustrating a method 1600 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1600 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0239] At 1605, the method may include obtaining, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a capability reporting manager 1125 as described with reference to FIG. 11.

[0240] At 1610, the method may include outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes. The operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a reconfiguration manager 1130 as described with reference to FIG. 11.

[0241] FIG. 17 shows a flowchart illustrating a method 1700 that supports UE framework for 32 HARQ processes in accordance with one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1700 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0242] At 1705, the method may include obtaining, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, where the UE stores feedback process information in accordance with the quantity of feedback processes. The operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a capability reporting manager 1125 as described with reference to FIG. 11.

[0243] At 1710, the method may include outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, where the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes. The operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a reconfiguration manager 1130 as described with reference to FIG. 11.

[0244] At 1715, the method may include outputting, to the UE, a grant for a wireless communication associated with the first frequency configuration, where the UE discards the grant based on a reset to the feedback process information stored by the UE according to the reconfiguration message. The operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a grant manager 1140 as described with reference to FIG. 11.

[0245] The following provides an overview of aspects of the present disclosure:

[0246] Aspect 1 : A method for wireless communications at a UE, comprising: transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, wherein the UE stores feedback process information in accordance with the quantity of feedback processes; and receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, wherein the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0247] Aspect 2: The method of aspect 1, wherein the bandwidth information comprises one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported by the UE across all CCs, a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes.

[0248] Aspect 3 : The method of any of aspects 1 through 2, wherein the quantity of feedback processes supported by the UE comprise 32 HARQ processes.

[0249] Aspect 4: The method of any of aspects 1 through 3, wherein the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

[0250] Aspect 5: The method of any of aspects 1 through 4, further comprising: maintaining the feedback process information stored by the UE based at least in part onthe first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE.

[0251] Aspect 6: The method of claim 1, wherein the first frequency configuration and the second frequency configuration comply with the quantity of feedback processes supported by the UE and are associated with up to 32 feedback processes.

[0252] Aspect 7 : The method of any of aspects 1 through 6, wherein the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and are associated with up to 16 feedback processes.

[0253] Aspect 8 : The method of any of aspects 1 through 7, wherein the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE.

[0254] Aspect 9: The method of any of aspects 1 through 8, wherein the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processes stored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

[0255] Aspect 10: The method of aspect 9, further comprising: resetting the feedback process information stored by the UE based at least in part on the reconfiguration message.

[0256] Aspect 11 : The method of any of aspects 1 through 10, wherein the first frequency configuration fails to comply with the quantity of feedback processes supported by the UE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes.

[0257] Aspect 12: The method of aspect 11, further comprising: resetting the feedback process information stored by the UE based at least in part on the reconfiguration message.

[0258] Aspect 13: The method of any of aspects 1 through 12, wherein each of the first frequency configuration and the second frequency configuration comprises a first subset of CCs and a second subset of CCs, and the first subset of CCs of the first frequency configuration has a same quantity of feedback processes as the second frequency configuration , and the second subset of CCs of the first frequency configuration has a different quantity of feedback processes from the second subset of CCs of the second frequency configuration.

[0259] Aspect 14: The method of aspect 13, further comprising: maintaining the feedback process information stored by the UE for the first subset of CCs based on the same quantity of feedback processes; and resetting the feedback process information stored by the UE for the second subset of CCs based on the different quantity of feedback processes.

[0260] Aspect 15: The method of any of aspects 1 through 14, further comprising: receiving, based at least in part on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all CCs associated with the UE.

[0261] Aspect 16: The method of any of aspects 1 through 15, further comprising: receiving, based at least in part on the UE capability message, a configuration message that identifies a number of feedback processes per CC associated with the UE.

[0262] Aspect 17: The method of any of aspects 1 through 16, further comprising: receiving, based at least in part on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE.

[0263] Aspect 18: The method of aspect 17, wherein the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes and are, based on the compliance, associated with up to 32 feedback processes.

[0264] Aspect 19: The method of any of aspects 17 through 18, wherein the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

[0265] Aspect 20: The method of any of aspects 1 through 19, further comprising: receiving a grant for a wireless communication associated with the first frequency configuration; and discarding the grant based at least in part on a reset to the feedback process information stored by the UE according to the reconfiguration message.

[0266] Aspect 21 : A method for wireless communications at a network entity, comprising: obtaining, from a UE, a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, wherein the UE stores feedback process information in accordance with the quantity of feedback processes; and outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, wherein the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

[0267] Aspect 22: The method of aspect 21, wherein the bandwidth information comprises one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported by the UE across all CCs, a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes.

[0268] Aspect 23: The method of any of aspects 21 through 22, wherein the quantity of feedback processes supported by the UE comprise 32 HARQ processes.

[0269] Aspect 24: The method of any of aspects 21 through 23, wherein the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

[0270] Aspect 25: The method of any of aspects 21 through 24, wherein the feedback process information stored by the UE is maintained based at least in part on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE.

[0271] Aspect 26: The method of claim 21, wherein the first frequency configuration and the second frequency configuration comply with the quantity offeedback processes supported by the UE and are associated with up to 32 feedback processes.

[0272] Aspect 27: The method of any of aspects 21 through 26, wherein the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and are associated with up to 16 feedback processes.

[0273] Aspect 28: The method of any of aspects 21 through 27, wherein the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE.

[0274] Aspect 29: The method of any of aspects 21 through 28, wherein the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processes stored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

[0275] Aspect 30: The method of aspect 29, wherein the feedback process information stored by the UE is reset based at least in part on the reconfiguration message.

[0276] Aspect 31 : The method of any of aspects 21 through 30, wherein the first frequency configuration fails to comply with the quantity of feedback processes supported by the UE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes.

[0277] Aspect 32: The method of aspect 31, wherein the feedback process information stored by the UE is reset based at least in part on the reconfiguration message.

[0278] Aspect 33 : The method of any of aspects 21 through 32, wherein each of the first frequency configuration and the second frequency configuration comprises a first subset of CCs and a second subset of CCs, and the first subset of CCs of the firstfrequency configuration has a same quantity of feedback processes as the second frequency configuration , and the second subset of CCs of the first frequency configuration has a different quantity of feedback processes from the second subset of CCs of the second frequency configuration.

[0279] Aspect 34: The method of aspect 33, wherein the feedback process information stored by the UE is maintained for the first subset of CCs based on the same quantity of feedback processes, and the feedback process information stored by the UE is reset for the second subset of CCs based on the different quantity of feedback processes.

[0280] Aspect 35: The method of any of aspects 21 through 34, further comprising: outputting, to the UE and based at least in part on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all CCs associated with the UE.

[0281] Aspect 36: The method of any of aspects 21 through 35, further comprising: outputting, to the UE and based at least in part on the UE capability message, a configuration message that identifies a number of feedback processes per CC associated with the UE.

[0282] Aspect 37: The method of any of aspects 21 through 36, further comprising: outputting, to the UE and based at least in part on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE.

[0283] Aspect 38: The method of aspect 37, wherein the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes and are, based on the compliance, associated with up to 32 feedback processes.

[0284] Aspect 39: The method of any of aspects 37 through 38, wherein the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

[0285] Aspect 40: The method of any of aspects 21 through 39, further comprising: outputting, to the UE, a grant for a wireless communication associated with the first frequency configuration, wherein the UE discards the grant based at least in part on a reset to the feedback process information stored by the UE according to the reconfiguration message.

[0286] Aspect 41 : A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 20.

[0287] Aspect 42: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 20.

[0288] Aspect 43 : A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 20.

[0289] Aspect 44: A network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 21 through 40.

[0290] Aspect 45: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 21 through 40.

[0291] Aspect 46: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 21 through 40.

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

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

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

[0295] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU), a neural processing unit (NPU), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

[0296] The functions described herein may be implemented using hardware, software executed by a processor, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, hardwiring, or combinations of anyof these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0297] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. 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, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0298] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change memory , compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non- transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wirelesstechnologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0299] As used herein, including in the claims, “or” as used in a list of items (e.g., including a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means, e.g., A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an exemplary step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” As used herein, the term “and / or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, and / or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.

[0300] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computeror a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0301] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0302] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. Forexample, a component introduced with the article “a” may be understood to mean “one or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0303] The term “determine” or “determining” or “identify” or “identifying” encompasses a variety of actions and, therefore, “determining” or “identifying” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” or “identifying” can include receiving (such as receiving information or signaling, e.g., receiving information or signaling for determining, receiving information or signaling for identifying), accessing (such as accessing data in a memory, or accessing information) and the like. Also, “determining” or “identifying” can include resolving, obtaining, selecting, choosing, establishing and other such similar actions.

[0304] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

[0305] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures,known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0306] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to: transmit a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, wherein the UE stores feedback process information in accordance with the quantity of feedback processes; and receive a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, wherein the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

2. The UE of claim 1, wherein the bandwidth information comprises one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported by the UE across all component carriers (CCs), a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes.

3. The UE of claim 1, wherein the quantity of feedback processes supported by the UE comprise 32 hybrid automatic repeat / request (HARQ) processes.

4. The UE of claim 1, wherein the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

5. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:maintain the feedback process information stored by the UE based at least in part on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE.

6. The UE of claim 1, wherein the first frequency configuration and the second frequency configuration comply with the quantity of feedback processes supported by the UE and are associated with up to 32 feedback processes.

7. The UE of claim 1, wherein the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and are associated with up to 16 feedback processes.

8. The UE of claim 1, wherein the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE.

9. The UE of claim 1, wherein the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processes stored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

10. The UE of claim 9, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: reset the feedback process information stored by the UE based at least in part on the reconfiguration message.

11. The UE of claim 1, wherein the first frequency configuration fails to comply with the quantity of feedback processes supported by the UE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes.

12. The UE of claim 11, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: reset the feedback process information stored by the UE based at least in part on the reconfiguration message.

13. The UE of claim 1, wherein: each of the first frequency configuration and the second frequency configuration comprises a first subset of component carriers (CCs) and a second subset of CCs, the first subset of CCs of the first frequency configuration has a same quantity of feedback processes as the second frequency configuration , and the second subset of CCs of the first frequency configuration has a different quantity of feedback processes from the second subset of CCs of the second frequency configuration.

14. The UE of claim 13, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: maintain the feedback process information stored by the UE for the first subset of CCs based on the same quantity of feedback processes; and reset the feedback process information stored by the UE for the second subset of CCs based on the different quantity of feedback processes.

15. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive, based at least in part on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all component carriers (CCs) associated with the UE.

16. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive, based at least in part on the UE capability message, a configuration message that identifies a number of feedback processes per component carrier (CC) associated with the UE.

17. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive, based at least in part on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE.

18. The UE of claim 17, wherein the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes and are, based on the compliance, associated with up to 32 feedback processes.

19. The UE of claim 17, wherein the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

20. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive a grant for a wireless communication associated with the first frequency configuration; and discard the grant based at least in part on a reset to the feedback process information stored by the UE according to the reconfiguration message.

21. A network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to: obtain, from a user equipment (UE), a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, wherein the UE stores feedback process information in accordance with the quantity of feedback processes; and output, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, wherein the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

22. The network entity of claim 21, wherein the bandwidth information comprises one or more of a limit of feedback processes supported by the UE per frequency band, a limit on a total number of feedback processes supported bythe UE across all component carriers (CCs), a limit on a subband size supported by the UE per CC, an aggregated bandwidth supported by the UE across all CCs with 32 feedback processes, or a quantity of CCs supported by the UE with 32 feedback processes.

23. The network entity of claim 21, wherein the quantity of feedback processes supported by the UE comprise 32 hybrid automatic repeat / request (HARQ) processes.

24. The network entity of claim 21, wherein the UE capability message indicates a first bandwidth information for downlink communications and a second bandwidth information for uplink communications.

25. The network entity of claim 21, wherein the feedback process information stored by the UE is maintained based at least in part on the first frequency configuration and the second frequency configuration complying with the quantity of feedback processes supported by the UE.

26. The network entity of claim 21, wherein the first frequency configuration and the second frequency configuration comply with the quantity of feedback processes supported by the UE and are associated with up to 32 feedback processes.

27. The network entity of claim 21, wherein the first frequency configuration and the second frequency configuration fail to comply with the quantity of feedback processes supported by the UE and are associated with up to 16 feedback processes.

28. The network entity of claim 21, wherein the UE capability message identifies support for maintaining or resetting the feedback process information stored by the UE.

29. The network entity of claim 21, wherein the first frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes and the second frequency configuration fails to comply with the quantity of feedback processesstored by the UE and is, based on the failure to comply, associated with up to 16 feedback processes.

30. The network entity of claim 29, wherein the feedback process information stored by the UE is reset based at least in part on the reconfiguration message.

31. The network entity of claim 21, wherein the first frequency configuration fails to comply with the quantity of feedback processes supported by the UE and is, based on the failure to comply, associated with up to 16 feedback processes and the second frequency configuration complies with the quantity of feedback processes supported by the UE and is, based on the compliance, associated with up to 32 feedback processes.

32. The network entity of claim 31, wherein the feedback process information stored by the UE is reset based at least in part on the reconfiguration message.

33. The network entity of claim 21, wherein: each of the first frequency configuration and the second frequency configuration comprises a first subset of component carriers (CCs) and a second subset of CCs, the first subset of CCs of the first frequency configuration has a same quantity of feedback processes as the second frequency configuration , and the second subset of CCs of the first frequency configuration has a different quantity of feedback processes from the second subset of CCs of the second frequency configuration.

34. The network entity of claim 33, wherein the feedback process information stored by the UE is maintained for the first subset of CCs based on the same quantity of feedback processes, and the feedback process information stored by the UE is reset for the second subset of CCs based on the different quantity of feedback processes.

35. The network entity of claim 21, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: output, to the UE and based at least in part on the UE capability message, a configuration message that identifies a same number of feedback processes applicable to all component carriers (CCs) associated with the UE.

36. The network entity of claim 21, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: output, to the UE and based at least in part on the UE capability message, a configuration message that identifies a number of feedback processes per component carrier (CC) associated with the UE.

37. The network entity of claim 21, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to: output, to the UE and based at least in part on the UE capability message, a configuration message that identifies an upper limit of feedback processes associated with the UE.

38. The network entity of claim 37, wherein the first frequency configuration and the second frequency configuration comply with the upper limit of feedback processes and are, based on the compliance, associated with up to 32 feedback processes.

39. The network entity of claim 37, wherein the first frequency configuration and the second frequency configuration fail to comply with the upper limit of feedback processes and are, based on the failure to comply, associated with up to 16 feedback processes.

40. The network entity of claim 21, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:output, to the UE, a grant for a wireless communication associated with the first frequency configuration, wherein the UE discards the grant based at least in part on a reset to the feedback process information stored by the UE according to the reconfiguration message.

41. A method for wireless communications at a user equipment (UE), comprising: transmitting a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, wherein the UE stores feedback process information in accordance with the quantity of feedback processes; and receiving a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, wherein the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

42. A method for wireless communications at a network entity, comprising: obtaining, from a user equipment (UE), a UE capability message that identifies bandwidth information associated with a quantity of feedback processes supported by the UE, wherein the UE stores feedback process information in accordance with the quantity of feedback processes; and outputting, to the UE, a reconfiguration message that identifies a change from a first frequency configuration to a second frequency configuration for the UE, wherein the change is associated with one or more of the feedback process information stored by the UE in accordance with the quantity of feedback processes.

Images