Patent Description:
As demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and NR technologies. These improvements can apply to other multiple access technologies and the telecommunication standards that employ these technologies.

<NPL>) discusses some essential remaining issues on multi-TRP/panel operation, and discloses proposals.

<NPL>) discusses observations and related proposals on the multiple TRP transmission design for NR-PDCCH.

<NPL>) discusses the critical remaining open issues to be addressed in relation to SPS corresponding to Type <NUM> and GF Type <NUM>, and provides proposals to address the issues and a potential TP.

<NPL>) discloses observations and related proposals on the remaining details of DL data channel design.

So that the above-recited features of the present disclosure can be understood in detail, a more particular description is provided herein, with some aspects of the disclosure being illustrated in the appended drawings. However, the appended drawings illustrate only some aspects of this disclosure and are therefore not to be considered limiting of the scope of the disclosure.

These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as "elements" or "features").

While some aspects may be described herein using terminology commonly associated with <NUM> and/or <NUM> wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as <NUM>, including NR technologies.

While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and/or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, and/or the like). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including one or more antennas, RF-chains, power amplifiers, modulators, buffers, processors, interleavers, adders/summers, and/or the like). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.

A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, robotics, drones, implantable devices, augmented reality devices, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

At base station <NUM>, a transmit processor <NUM> can carry out a number of functions associated with communications. For example, transmit processor <NUM> may receive data from a data source <NUM> for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs.

At UE <NUM>, antennas 252a through 252r may receive downlink signals from base station <NUM> and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with HARQ process identifier determination for multiple configured scheduling processes, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG> and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively.

In some aspects, UE <NUM> may include means for determining a first hybrid automatic repeat request (HARQ) process identifier set associated with a first configured scheduling process, means for determining a second HARQ process identifier set associated with a second configured scheduling process, means for assigning an HARQ process identifier, included in the first HARQ process identifier set, to a process instance associated with the first configured scheduling process, means for assigning an HARQ process identifier, included in the second HARQ process identifier set, to a process instance associated with the second configured scheduling process, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as antenna <NUM>, DEMOD <NUM>, MOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, controller/processor <NUM>, and/or the like.

<FIG> shows an example frame structure <NUM> for FDD in a telecommunications system (e.g., NR). In some aspects, a scheduling unit for the FDD may frame-based, subframe-based, slot-based, symbol-based, and/or the like.

An interlace structure may be used for each of the downlink and uplink for FDD in certain telecommunications systems (e.g., NR). For example, Q interlaces with indices of <NUM> through Q - <NUM> may be defined, where Q may be equal to <NUM>, <NUM>, <NUM>, <NUM>, or some other value. Each interlace may include slots that are spaced apart by Q frames. In particular, interlace q may include slots q, q + Q, q + 2Q, etc., where q ∈ {<NUM>,. , Q-<NUM>}.

In a wireless network, various scheduling processes may be configured for downlink communication and/or uplink communication. For example, a semi-persistent scheduling (SPS) process may be configured for downlink communication between a transmit receive point (TRP) and a user equipment (UE). As another example, a grant-free scheduling (GFS) process or uplink configured grant process may be configured for uplink communication between the TRP and the UE.

In some cases, the TRP and UE may implement a plurality of hybrid automatic repeat request (HARQ) processes, associated with a configured scheduling process, for forward error correction for downlink communication and/or uplink communication. An HARQ process may store, in a buffer memory, a received original communication and any received retransmissions of the communication that are associated with a particular process instance (which may include a semi-persistent scheduling transmission in the case of downlink communication or may include a grant-free transmission or an uplink configured grant transmission in the case of uplink communication) of the configured scheduling process. In this way, the original communication and the received retransmission(s) may be combined (which may be referred to as soft combining) to correct any errors that may have occurred in the original communication.

In some cases, the HARQ process identifiers that are associated with the plurality of HARQ processes may not be transmitted to the UE when the configured scheduling process is initiated. Instead, the UE may determine the HARQ process identifiers based at least in part on an equation. For example, for a semi-persistent scheduling type of configured scheduling process, the UE may determine the HARQ process identifiers based at least in part on Equation <NUM>: <MAT> where nrofHARQ_Processes corresponds to the quantity of HARQ processes associated with the SPS. CURRENT_slot may be determined according to Equation <NUM>: <MAT> where SFN corresponds to the subframe number of CURRENT_slot.

As another example, for a grant-free scheduling (GFS) type or an uplink configured grant type of configured scheduling process, the UE may determine the HARQ process identifiers based at least in part on Equation <NUM>: <MAT> where nrofHARQ_Processes corresponds to the quantity of HARQ processes associated with the GFS. CURRENT_slot may be determined according to Equation <NUM>: <MAT> where SFN corresponds to the subframe number of CURRENT_slot.

While the UE may be capable of determining the HARQ process identifiers in a single-TRP configuration (e.g., where the UE communicates with a single TRP), the UE may be unable to determine respective HARQ process identifier sets for a plurality of TRPs in a multi-TRP configuration or for a plurality of antenna panels in a multi-panel configuration. As a result, the UE may be unable to determine which HARQ processes are assigned to a particular TRP in the multi-TRP configuration or assigned to a particular antenna panel in the multi-panel configuration, which in turn may result in the UE being unable to perform forward error correction for downlink communication and/or uplink communication with the TRP or antenna panel. Even in some single-TRP configurations, such as where the UE is configured with more than one semi-persistent scheduling grant and/or more than one uplink configured grant, the UE may be unable to determine which HARQ process belongs to which grant configuration.

Some aspects, described herein, provide techniques and apparatuses for HARQ process identifier determination for multiple configured scheduling processes. In some aspects, a UE may determine respective HARQ process identifier sets for a plurality of configured scheduling processes. In some aspects, the UE may receive, from a TRP, information associated with a first HARQ process identifier set and information associated with a second HARQ process identifier set. The UE may determine the first HARQ process identifier set based at least in part on the information associated with the first HARQ process identifier set, and may determine the second HARQ process identifier set based at least in part on the information associated with the second HARQ process identifier set. The UE may assign HARQ process identifiers, included in the first HARQ process identifier set, to process instances associated with the first configured scheduling process. Moreover, the UE may assign HARQ process identifiers, included in the second HARQ process identifier set, to process instances associated with the second configured scheduling process.

In this way, the UE and a plurality of TRPs may be permitted to determine respective HARQ process identifier sets for a multi-TRP configuration and/or a multi-panel configuration and/or may be permitted to assign HARQ process identifiers, from the respective HARQ process identifier sets, to process instances associated with respective configured scheduling processes. As a result, the UE may be permitted to determine which HARQ processes are assigned to a particular configured scheduling process in the multi-TRP configuration, which in turn may result in the UE being capable of performing forward error correction for downlink communication and/or uplink communication for the plurality of TRPs in the multi-TRP configuration.

<FIG> are diagrams illustrating an example <NUM> of HARQ process identifier determination for multiple configured scheduling processes, in accordance with various aspects of the present disclosure. As shown in <FIG>, example <NUM> may include a plurality of transmit receive points (TRPs) (e.g., TRP1, TRP2, and/or the like,) and a UE (e.g., UE <NUM>). In some aspects, each TRP, of the plurality of TRPs illustrated in <FIG>, may correspond to a respective BS (e.g., BS 110a, BS 110b, and/or the like). In some aspects, two or more TRPs, of the plurality of TRPs, may be correspond to the same BS. For example, a first TRP may correspond to a first antenna panel or antenna array of a BS and a second TRP may correspond to a second antenna panel or antenna array of the BS.

In some aspects, the plurality of TRPs may configure one or more respective scheduling processes. For example, TRP1 may configure a SPS process for downlink communication between TRP1 and UE <NUM> and a GFS process for uplink communication between TRP1 and UE <NUM>, TRP2 may configure a SPS process for downlink communication between TRP2 and UE <NUM> and a GFS process for uplink communication between TRP2 and UE <NUM>, and so on.

In some aspects, the plurality of TRPs may assign HARQ process identifier sets to the configured scheduling processes. For example, TRP1 may assign an HARQ process identifier set to the SPS process associated with TRP1 and an HARQ process identifier set to the GFS process associated with TRP1. As another example, TRP2 may assign an HARQ process identifier set to the SPS process associated with TRP2 and an HARQ process identifier set to the GFS process associated with TRP2.

In some aspects, TRP1 and TRP2 may coordinate the assignment of respective HARQ process identifier sets. For example, TRP1 and TRP2 may coordinate the assignment of respective HARQ process identifier sets such that the respective HARQ process identifier sets are disjoint HARQ process identifier sets (e.g., such that no HARQ process identifier, included in a first HARQ process identifier set associated with a configured scheduling process of TRP1, is included in a second HARQ process identifier set associated with a configured scheduling process of TRP2, and vice-versa). As another example, TRP1 and TRP2 may coordinate the assignment of respective HARQ process identifier sets such that the respective HARQ process identifier sets are the same HARQ process identifier sets (e.g., such that the HARQ process identifiers, included in a first HARQ process identifier set associated with a configured scheduling process of TRP1, are also included in a second HARQ process identifier set associated with a configured scheduling process of TRP2, and vice-versa). According to the invention, TRP1 and TRP2 coordinate the assignment of respective HARQ process identifier sets such that the respective HARQ process identifier sets at least partially overlap (e.g., such that a subset of HARQ process identifiers, included in a first HARQ process identifier set associated with a configured scheduling process of TRP1, are also included in a second HARQ process identifier set associated with a configured scheduling process of TRP2).

In some aspects, TRP1 may transmit, to TRP2, information identifying a quantity of HARQ process identifiers that are included in an HARQ process identifier set that is assigned to a configured scheduling process of TRP1, may transmit information identifying the HARQ process identifiers that are included in the HARQ process identifier set, and/or the like. In some aspects, TRP2 may transmit similar information to TRP1.

As shown in <FIG>, and by reference number <NUM>, TRP1 and/or TRP2 may transmit, to UE <NUM>, information associated with one or more HARQ process identifier sets that are associated with a configured scheduling process of TRP1, information associated with one or more HARQ process identifier sets that are associated with a configured scheduling process of TRP2, and/or the like. For example, in some aspects, TRP1 may transmit a signaling communication (e.g., a radio resource control (RRC) communication, a downlink control information (DCI) communication, a medium access control control element (MAC-CE) communication, and/or the like) that includes information associated with a first HARQ process identifier set that is associated with a configured scheduling process of TRP1, and information associated with a second HARQ process identifier set that is associated with a configured scheduling process of TRP2. As another example, TRP1 may transmit a signaling communication that includes the information associated with the first HARQ process identifier set, and TRP2 may transmit a signaling communication that includes the information associated with the second HARQ process identifier set.

In some aspects, the information associated with a particular HARQ process identifier set may include information identifying a quantity of HARQ process identifiers included in the HARQ process identifier set, an offset associated with the HARQ process identifier set, and/or the like.

The offset associated with an HARQ process identifier set may be determined based at least in part on a quantity of HARQ process identifiers that is included in another HARQ process identifier set. For example, if an HARQ process identifier set, associated with an SPS process of TRP <NUM>, includes four HARQ process identifiers, the offset associated with an HARQ processor identifier set, that is associated with an SPS process of TRP2, may be determined as four.

As further shown in <FIG>, and by reference number <NUM>, UE <NUM> may determine the first HARQ process identifier set (e.g., may determine the HARQ process identifiers that are included in the first HARQ process identifier set) and the second HARQ process identifier set (e.g., may determine the HARQ process identifiers that are included in the second HARQ process identifier set). For example, UE <NUM> may determine the first HARQ process identifier set based at least in part on the information associated with the first HARQ process identifier set. As another example, UE <NUM> may determine the second HARQ process identifier set based at least in part on the information associated with the second HARQ process identifier set.

In some aspects, if the information associated with an HARQ process identifier set includes information identifying an offset associated with the HARQ process identifier set and a quantity of HARQ process identifiers included in the HARQ process identifier set, UE <NUM> may determine the HARQ process identifier set based at least in part on the offset associated with the HARQ process identifier set and the quantity of HARQ process identifiers included in the HARQ process identifier set. For example, UE <NUM> may determine the HARQ process identifier set based at least in part on adding the value of the offset associated with the HARQ process identifier set to Equation <NUM> and/or Equation <NUM> above.

As shown in <FIG>, and by reference number <NUM>, TRP1, TRP2, and/or UE <NUM> may assign HARQ process identifiers, included in the first HARQ process identifier set and/or the second HARQ process identifier set. For example, TRP1 and UE <NUM> may assign HARQ process identifiers, included in the first HARQ process identifier set, to process instances (e.g., SPS transmissions, GFS transmission, and/or the like) associated with a configured scheduling process of TRP1 (e.g., a SPS process, a GFS process). As another example, TRP2 and UE <NUM> may assign HARQ process identifiers, included in the second HARQ process identifier set, to process instances (e.g., SPS transmissions, GFS transmission, and/or the like) associated with a configured scheduling process of TRP2 (e.g., a SPS process, a GFS process).

In some aspects, HARQ process identifiers may be assigned to process instances of the configured scheduling process of TRP1 and the configured scheduling process of TRP2 based at least in part on whether the first HARQ process identifier set and the second HARQ process identifier set are disjoint HARQ processing identifier sets, whether the first HARQ process identifier set and the second HARQ process identifier set at least partially overlap, or whether the first HARQ process identifier set and the second HARQ process identifier set fully overlap.

<FIG> illustrates an example of assigning HARQ process identifiers from disjoint HARQ process identifier sets. As shown in <FIG>, the first HARQ process identifier set may include HARQ process identifiers {<NUM>, <NUM>, <NUM>, <NUM>}, and the second HARQ process identifier set may include HARQ process identifiers {<NUM>, <NUM>, <NUM>, <NUM>}. As further shown in <FIG>, HARQ process identifiers, included in the first HARQ process identifier set, may be sequentially assigned (e.g., by UE <NUM> and TRP1) to process identifiers of the configured scheduling process of TRP1. For example, HARQ process identifier <NUM> may be assigned to the first process instance of the configured scheduling process of TRP1, HARQ process identifier <NUM> may be assigned to the second process instance of the configured scheduling process of TRP1 (e.g., the next processing instance in the time domain), and so on.

Similarly, HARQ process identifiers, included in the second HARQ process identifier set, may be sequentially assigned (e.g., by UE <NUM> and TRP2) to process identifiers of a configured scheduling process of TRP2. For example, HARQ process identifier <NUM> may be assigned to the first process instance of the configured scheduling process of TRP2, HARQ process identifier <NUM> may be assigned to the second process instance of the configured scheduling process of TRP2 (e.g., the next processing instance in the time domain), and so on.

In this way, the HARQ process identifiers, included in each HARQ process identifier set, are spaced out as far as possible in the time domain. This ensures adequate spacing between HARQ process identifiers for retransmissions of a particular process instance. Moreover, in this way, if a process instance associated with the configured scheduling process of TRP1, and a process instance associated with the configured scheduling process of TRP2 overlap in the time domain, the HARQ process identifiers are assigned in a manner that does not result in a particular HARQ process identifier being assigned to overlapping process instances. For example, while the second process instance associated with the configured scheduling process of TRP1, and the second process instance associated with the scheduling process of TRP2, overlap in the time domain, the second process instance associated with the configured scheduling process of TRP1 is assigned HARQ process identifier <NUM>, whereas the second process instance associated with the configured scheduling process of TRP2 is assigned HARQ process identifier <NUM>, and thus no conflict of HARQ process identifiers occurs.

In some aspects, TRP1, TRP2, and/or UE <NUM> may assign HARQ process identifiers to process instances associated with respective configured scheduling processes based at least in part on calculating an index associated with a particular HARQ process identifier set. For example, TRP1, TRP2, and/or UE <NUM> may use Equation <NUM> (e.g., for an SPS configured scheduling process) or Equation <NUM> (e.g., for a GFS configured scheduling process) to compute an HARQ process identifier index for a particular process instance associated with a configured scheduling process. The HARQ process identifier index may indicate a position, of the HARQ process identifier that is to be assigned to the process instance, in the HARQ process identifier set that is associated with the configured scheduling process.

As an example of the above, TRP2 and/or UE <NUM> may compute an HARQ process identifier index for the third process instance associated with the configured scheduling process of TRP2 (e.g., using Equation <NUM> or Equation <NUM>). The HARQ process identifier index, for the third process instance associated with the configured scheduling process of TRP2, may be computed as <NUM>. TRP2 and/or UE <NUM> may therefore identify the third HARQ process identifier in the second HARQ process identifier set (i.e., HARQ process identifier <NUM>), and may assign the third HARQ process identifier to the third process instance associated with the configured scheduling process of TRP2.

<FIG> illustrates an example of assigning HARQ process identifiers from HARQ process identifier sets that fully overlap. As shown in <FIG>, the first HARQ process identifier set and the second HARQ process identifier set may be assigned a shared HARQ process identifier set of HARQ process identifiers {<NUM>, <NUM>, <NUM>, <NUM>}. In some aspects, UE <NUM>, TRP1, and TRP2 may assign HARQ process identifiers, from the shared process identifier set, to the configured scheduling process of TRP1 and/or to the configured scheduling process of TRP2 based at least in part on various factors. In some aspects, the various factors may include a periodicity of the configured scheduling process of TRP1 (e.g., a frequency at which process instances associated with the configured scheduling process of TRP1 occur in the time domain), a periodicity of the configured scheduling process of TRP2 (e.g., a frequency at which process instances associated with the configured scheduling process of TRP2 occur in the time domain), a priority associated with the configured scheduling process of TRP1, a priority associated with the configured scheduling process of TRP2, and/or the like.

In some aspects, the priority associated with the configured scheduling process of TRP1, and the priority associated with the configured scheduling process of TRP2, may be determined based at least on which TRP is the serving TRP for UE <NUM>. Accordingly, if TRP <NUM> is the serving TRP for UE <NUM>, the configured scheduling process of TRP1 may be assigned a greater priority relative to the configured scheduling process of TRP2.

In some aspects, TRP1, TRP2, and/or UE <NUM> may sequentially assign HARQ process identifiers, from the shared HARQ process identifier set, to process instances associated with the configured scheduling process of TRP1 and/or process instances associated with the configured scheduling process of TRP2 as the process instances occur in the time domain unless respective process instances associated with the configured scheduling process of TRP1 and the configures scheduling process of TRP2 overlap in the time domain. If respective process instances associated with the configured scheduling process of TRP1 and the configured scheduling process of TRP2 overlap in the time domain, TRP1, TRP2, and/or UE <NUM> may assign the next HARQ process identifier, in the sequence of HARQ process identifiers included in the shared HARQ process identifier set, based at least in part on the priority of the configured scheduling process of TRP1 and the priority of the configured scheduling process of TRP2.

As an example of the above, since the first process instance associated with the configured scheduling process of TRP1 occurs first in the time domain, and there is no overlap with another process instance, TRP1, TRP2, and/or UE <NUM> may assign HARQ process identifier <NUM> to the first process instance associated with the configured scheduling process of TRP1. Since the first process instance associated with the configured scheduling process of TRP2 occurs next in the time domain, and there is no overlap with another process instance, TRP1, TRP2, and/or UE <NUM> may assign HARQ process identifier <NUM> to the first process instance associated with the configured scheduling process of TRP2.

Since the second process instance associated the configured scheduling process for TRP1 and the second process instance associated with the configured scheduling process for TRP2 overlap in the time domain, TRP1, TRP2, and/or UE <NUM> may assign HARQ process identifiers to the second process instance associated the configured scheduling process for TRP1 and the second process instance associated with the configured scheduling process for TRP2 based at least in part on the priority associated with the configured scheduling process of TRP <NUM> and the priority associated with the configured scheduling process of TRP2. In this case, if the priority associated with the configured scheduling process of TRP1 is greater relative to the priority associated with the configured scheduling process of TRP2, TRP1, TRP2, and/or UE <NUM> may assign the next sequential HARQ process identifier in the shared HARQ process identifier set (e.g., HARQ process identifier <NUM>) to the second process instance associated with the configured scheduling process of TRP1, and may assign the subsequent HARQ process identifier in the shared HARQ process identifier set (e.g., HARQ process identifier <NUM>) to the second process instance associated with the configured scheduling process of TRP2. TRP1, TRP2, and/or UE <NUM> may proceed to assign HARQ process identifiers from the shared HARQ process identifier set accordingly.

<FIG> illustrates an example of assigning HARQ process identifiers from HARQ process identifier sets that at least partially overlap (e.g., where at least one HARQ process identifier, included in an HARQ process identifier set, is not included in the other HARQ process identifier set, and where at least one HARQ process identifier, included in an HARQ process identifier set, is also included in the other HARQ process identifier set). As shown in <FIG>, the first HARQ process identifier set may include HARQ process identifiers {<NUM>, <NUM>, <NUM>, <NUM>}, and the second HARQ process identifier set may include HARQ process identifiers {<NUM>, <NUM>, <NUM>}. In this case, HARQ process identifiers {<NUM>, <NUM>, <NUM>} are shared HARQ process identifiers and HARQ process identifier <NUM> is a unique HARQ process identifier that is only included in the first HARQ process identifier set.

In some aspects, TRP1, TRP2, and/or UE <NUM> may assign the shared HARQ process identifiers to the process instances included in the configured scheduling process of TRP1, and/or to the process instances included in the configured scheduling process of TRP2, in a manner similar as described above in reference to <FIG>. In addition, TRP <NUM>, TRP2, and/or UE <NUM> may assign the unique HARQ process identifiers in a manner that maximizes the spacing between the same HARQ process identifiers in the time domain. To do so, TRP1, TRP2, and/or UE <NUM> may assign HARQ process identifiers included in the first HARQ process identifier set and/or the second HARQ process identifier set based at least in part on additional factors, such as a quantity of HARQ process identifiers included in the first HARQ process identifier set, a quantity of HARQ process identifiers included in the second HARQ process identifier set, a quantity of shared HARQ process identifiers included in the first HARQ process identifier set and the second HARQ process identifier set, a quantity of unique HARQ process identifiers included in the first HARQ process identifier set, a quantity of unique HARQ process identifiers included in the second HARQ process identifier set, and/or the like.

In this way, UE <NUM>, TRP <NUM>, and TRP2 may be permitted to determine respective HARQ process identifier sets for a multi-TRP configuration and/or a multi-panel configuration and/or may be permitted to assign HARQ process identifiers, from the respective HARQ process identifier sets, to process instances associated with respective configured scheduling processes. As a result, UE <NUM> may be permitted to determine which HARQ processes are assigned to a particular configured scheduling process in the multi-TRP configuration, which in turn may result in UE <NUM> being capable of performing forward error correction for downlink communication and/or uplink communication for TRP1 and TRP2 in the multi-TRP configuration.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a UE (e.g., UE <NUM>) performs HARQ process identifier determination for multiple configured scheduling processes.

As shown in <FIG>, in some aspects, process <NUM> may include determining a first HARQ process identifier set associated with a first configured scheduling process (block <NUM>). For example, the UE (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may determine a first HARQ process identifier set associated with a first configured scheduling process, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include determining a second HARQ process identifier set associated with a second configured scheduling process (block <NUM>). For example, the UE (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may determine a second HARQ process identifier set associated with a second configured scheduling process, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include assigning an HARQ process identifier, included in the first HARQ process identifier set, to a process instance associated with the first configured scheduling process (block <NUM>). For example, the UE (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may assign an HARQ process identifier, included in the first HARQ process identifier set, to a process instance associated with the first configured scheduling process, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include assigning an HARQ process identifier, included in the second HARQ process identifier set, to a process instance associated with the second configured scheduling process (block <NUM>). For example, the UE (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may assign an HARQ process identifier, included in the second HARQ process identifier set, to a process instance associated with the second configured scheduling process, as described above.

In a first aspect, the first configured scheduling process is associated with a first TRP included in a multi-TRP configuration and the second configured scheduling process is associated with a second TRP included in the multi-TRP configuration. In a second aspect, alone or in combination with the first aspect, the first configured scheduling process is associated with a first antenna panel included in a multi-panel configuration and the second configured scheduling process is associated with a second antenna panel included in the multi-panel configuration.

According to the invention, alone or in combination with one or more of the first or second aspects, process <NUM> comprises assigning another HARQ process identifier, included in the first HARQ process identifier set, to another process instance associated with the first configured scheduling process, wherein the other HARQ process identifier, included in the first HARQ process identifier set, is sequentially incremented respective to the HARQ process identifier, included in the first HARQ process identifier set, assigned to the process instance associated with the first configured scheduling process, and assigning another HARQ process identifier, included in the second HARQ process identifier set, to another process instance associated with the second configured scheduling process, wherein the other HARQ process identifier, included in the second HARQ process identifier set, is sequentially incrementing respective to the HARQ process identifier, included in the first HARQ process identifier set, assigned to the process instance associated with the first configured scheduling process.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first HARQ process identifier set and the second HARQ process identifier set are disjoint HARQ process identifier sets. In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, assigning the HARQ process identifier, included in the first HARQ process identifier set, to the process instance associated with the first configured scheduling process comprises computing a HARQ process identifier index and assigning, based at least in part on determining that the HARQ process identifier index is associated with the with the HARQ process identifier included in the first HARQ process identifier set, the HARQ process identifier, included in the first HARQ process identifier set, to the process instance associated with the first configured scheduling process. In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, assigning the HARQ process identifier, included in the second HARQ process identifier set, to the process instance associated with the second configured scheduling process comprises computing another HARQ process identifier index and assigning, based at least in part on determining that the other HARQ process identifier index is associated with the with the HARQ process identifier included in the second HARQ process identifier set, the HARQ process identifier, included in the second HARQ process identifier set, to the process instance associated with the second configured scheduling process.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process <NUM> comprises receiving information identifying a first offset associated with the first HARQ process identifier set and a second offset associated with the first HARQ process identifier set. In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, determining the first HARQ process identifier set comprises determining the first HARQ process identifier set based at least in part on the first offset, and determining the second HARQ process identifier set comprises determining the second HARQ process identifier set based at least in part on the second offset. In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the second offset is based at least in part on a quantity of HARQ process identifiers included in the first HARQ process identifier set. In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the first HARQ process identifier set and the second HARQ process identifier set are a shared HARQ process identifier set.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, assigning the HARQ process identifier, included in the first HARQ process identifier set, to the process instance associated with the first configured scheduling process comprises assigning a first shared HARQ process identifier, included in the shared HARQ process identifier set, to the process instance associated with the first configured scheduling process. In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, assigning the HARQ process identifier, included in the second HARQ process identifier set, to the process instance associated with the second configured scheduling process comprises assigning a second shared HARQ process identifier, included in the shared HARQ process identifier set, to the process instance associated with the second configured scheduling process, wherein the second shared HARQ process identifier is sequentially incremented, within the shared HARQ process identifier set, relative to the first shared HARQ process identifier.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the process instance associated with the first configured scheduling process and the process instance associated with the second configured scheduling process at least partially overlap in time. In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, assigning the first shared HARQ process identifier, included in the shared HARQ process identifier set, to the process instance associated with the first configured scheduling process comprises assigning, based at least in part on a priority associated with the first configured scheduling process and a priority associated with a second configured scheduling process, the first shared HARQ process identifier, included in the shared HARQ process identifier set, to the process instance associated with the first configured scheduling process.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the first HARQ process identifier set and the second HARQ process identifier set include one or more shared HARQ process identifiers. In some aspects, assigning the HARQ process identifier, included in the first HARQ process identifier set, to the process instance associated with the first configured scheduling process comprises assigning a first shared HARQ process identifier, of the one or more shared HARQ process identifiers, to the process instance associated with the first configured scheduling process. In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, assigning the HARQ process identifier, included in the second HARQ process identifier set, to the process instance associated with the second configured scheduling process comprises assigning a second shared HARQ process identifier, of the one or more shared HARQ process identifiers, to the process instance associated with the second configured scheduling process, wherein the second shared HARQ process identifier is sequentially incremented, within the shared HARQ process identifier set, relative to the first shared HARQ process identifier.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the process instance associated with the first configured scheduling process and the process instance associated with the second configured scheduling process at least partially overlap in time. In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, assigning the HARQ process identifier, included in the first HARQ process identifier set, to the process instance associated with the first configured scheduling process comprises assigning the HARQ process identifier, included in the first HARQ process identifier set, to the process instance associated with the first configured scheduling process, wherein the HARQ process identifier, included in the first HARQ process identifier set, is not included in the second HARQ process identifier set. In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, assigning the HARQ process identifier, included in the second HARQ process identifier set, to the process instance associated with the second configured scheduling process comprises assigning a shared HARQ process identifier, of the one or more shared HARQ process identifiers, to the process instance associated with the second configured scheduling process.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, process <NUM> comprises periodically assigning, to one or more subsequent process instances associated with the first configured scheduling process, the HARQ process identifier included in the first HARQ process identifier set, wherein the HARQ process identifier included, in the first HARQ process identifier set, is not included in the second HARQ process identifier set.

In a twenty-first aspect, alone or in combination with one or more of the first through nineteenth aspects, periodically assigning, to the one or more subsequent process instances associated with the first configured scheduling process, the HARQ process identifier included in the first HARQ process identifier set comprises periodically assigning the HARQ process identifier, included in the first HARQ process identifier set, based at least in part on at least one of a periodicity of the first configured scheduling process, a periodicity of the second configured scheduling process, a quantity of HARQ process identifiers included in the one or more shared HARQ process identifiers, or a quantity of HARQ process identifiers, included in the first HARQ process identifier set, that is not included in the second HARQ process identifier set.

In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the first configured scheduling process and the second configured scheduling process comprise respective downlink semi-persistent scheduling processes or respective uplink configured grant scheduling processes.

As used herein, satisfying a threshold may, depending on context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like.

Claim 1:
A method (<NUM>) of wireless communication performed by a user equipment, UE, comprising:
receiving information identifying a first offset is associated with a first hybrid automatic repeat request, HARQ, process identifier set and a second offset is associated with a second HARQ process identifier set;
determining (<NUM>), based at least in part on the first offset, the first HARQ process identifier set associated with a first configured scheduling process associated with a first transmit receive point, TRP, included in a multi-TRP configuration for downlink communication and/or uplink communication;
determining (<NUM>), based at least in part on the second offset, the second HARQ process identifier set associated with a second configured scheduling process associated with a second TRP included in the multi-TRP configuration for downlink communication and/or uplink communication,
wherein the second HARQ process identifier set at least partially overlaps with the first HARQ process identifier set;
assigning (<NUM>) an HARQ process identifier, included in the first HARQ process identifier set, to a process instance associated with the first configured scheduling process;
assigning (<NUM>) an HARQ process identifier, included in the second HARQ process identifier set, to a process instance associated with the second configured scheduling process;
assigning another HARQ process identifier, included in the first HARQ process identifier set, to another process instance associated with the first configured scheduling process,
wherein the other HARQ process identifier, included in the first HARQ process identifier set, is sequentially incremented respective to the HARQ process identifier, included in the first HARQ process identifier set, assigned to the process instance associated with the first configured scheduling process; and
assigning another HARQ process identifier, included in the second HARQ process identifier set, to another process instance associated with the second configured scheduling process,
wherein the other HARQ process identifier, included in the second HARQ process identifier set, is sequentially incremented respective to the other HARQ process identifier, included in the first HARQ process identifier set, assigned to the process instance associated with the first configured scheduling process.