Patent Description:
Various embodiments generally may relate to the field of wireless communications, and particularly to the field of Hybrid Automatic Repeat Request Acknowledgment scheduling using uplink resources in a cellular network environment.

Current Third Generation Partnership Project (3GPP) New Radio (NR) specifications do not specifically address issues related to the manner of multiplexing uplink resources, such as UCI carrying HARQ-ACK feedback.

The patent document <CIT> discloses methods of "piggybacking" multiple HARQ-ACKs in a PUSCH channel when both are scheduled in a slot, or of transmitting multiple different PUCCHs in a same subframe, said PUCCHs containing individual UCls.

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase "A or B" means (A), (B), or (A and B).

Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platforms. The next generation wireless communication system, <NUM>, or new radio (NR), will provide access to information and sharing of data anywhere, anytime by various users and applications.

As defined in NR, short physical uplink control channel (PUCCH) (PUCCH formats <NUM> and <NUM>) can span <NUM> or <NUM> symbols and long PUCCH (PUCCH formats <NUM>, <NUM> and <NUM>) can span from <NUM> to <NUM> symbols within a slot. Further, long PUCCH may span multiple slots to further enhance coverage. In addition, for a given User Equipment (UE), two short PUCCHs as well as short PUCCH and long PUCCH can be multiplexed in a time division multiplexing (TDM) manner in the same slot.

In NR, uplink control information (UCI) can be carried by PUCCH or PUSCH. In particular, UCI may include scheduling request (SR), hybrid automatic repeat request - acknowledgement (HARQ-ACK) feedback, channel state information (CSI) report, e.g., channel quality indicator (CQI), pre-coding matrix indicator (PMI), CSI resource indicator (CRI) and rank indicator (RI) and/or beam related information (e.g., L1-RSRP (layer <NUM>- reference signal received power)).

In NR Release <NUM> (Rel-<NUM>), it was agreed that for semi-static and dynamic hybrid automatic repeat request - acknowledgement (HARQ-ACK) codebook, only one HARQ-ACK feedback is to be transmitted in one slot. Further, this HARQ-ACK feedback can be carried by either physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). Further, for semi-static and dynamic HARQ-ACK codebook in a single component carrier (CC) scenario, PUCCH resource allocation is determined in accordance with the last downlink control information (DCI) scheduling the physical downlink shared channel (PDSCH). In particular, a PUCCH resource indicator in the last DCI and/or a starting control channel element (CCE) index for the physical downlink control channel (PDCCH) carrying the last DCI are jointly employed to determine the PUCCH resource carrying HARQ-ACK feedback.

As mentioned above, only one HARQ-ACK feedback or PUCCH/PUSCH transmission carrying HARQ-ACK feedback is allowed in a slot in the NR Rel-<NUM> specification. In the event that the PUCCH carrying HARQ-ACK feedback is scheduled in the last part of the slot, a HARQ-ACK feedback delay can be expected, especially when considering the smaller subcarrier spacing, e.g., <NUM> including a <NUM> slot duration. To support Ultra Reliable Low Latency Communication (URLLC) types of applications, it is envisioned according to embodiments that an additional PUCCH resource carrying HARQ-ACK feedback in a slot may be needed. For instance, the additional PUCCH resource carrying HARQ-ACK feedback may be transmitted in the earlier part of the slot so as to reduce latency.

Where plurality of PUCCH resources carrying HARQ-ACK feedback are envisioned to be scheduled in a slot, however, the plurality of PUCCH resources may overlap with another PUCCH resource carrying a same or different UCI types or carrying PUSCH. In such a case, certain mechanisms are needed for UCI multiplexing to ensure alignment between a NR evolved NodeB (gNodeB) and a UE.

Embodiments pertain to devices, methods, systems and products to allow multiplexing of multiple HARQ-ACK feedbacks and other UCI on PUCCH or PUSCH in a same slot. In particular, embodiments envision multiplexing multiple HARQ-ACK feedbacks and other UCI on PUCCH, or other non-limiting examples envision multiplexing multiple HARQ-ACK feedbacks and PUSCH.

As mentioned above, in case a plurality of PUCCH resources carrying HARQ-ACK feedback are scheduled in a slot, and the plurality of PUCCH resources overlap with another PUCCH carrying a same or different UCI types or PUSCH, certain mechanisms need to be defined for UCI multiplexing.

In the following description, dynamic HARQ-ACK feedback corresponds to the case where the HARQ-ACK is in response to a physical downlink shared channel (PDSCH) reception scheduled by a corresponding physical downlink control channel (PDCCH). In addition, semi-persistent scheduled (SPS) HARQ-ACK feedback corresponds to the case where the HARQ-ACK is in response to a PDSCH reception without an associated PDCCH.

Embodiments of multiplexing multiple HARQ-ACK feedback and other UCI on PUCCH in a slot are described below.

According to one embodiment, when a plurality of PUCCH resources carrying dynamic HARQ-ACK feedback in a first UCI overlap with another PUCCH resource carrying a second UCI, wherein HARQ-ACK feedback and the second UCI are not distinguished in terms of the corresponding service types or priorities, and if a timeline requirement is satisfied, the UCI multiplexing follows the procedure as defined in Section <NUM>. <NUM> in TS38.

The second UCI may include a periodic and/or semi-persistent scheduled CSI (P/SP-CSI) report and/or SR and/or SPS HARQ-ACK feedback. Further, it is assumed here that the UE is configured to multiplex HARQ-ACK and CSI in a PUCCH resource via higher layers. Otherwise, the UE is expected to transmit the PUCCH transmissions with the HARQ-ACK feedback and to drop the P/SP-CSI reports.

More specifically, according to some embodiments, in a first step, the UE may determine a set of overlapping PUCCH resources for UCI multiplexing. In NR Rel-<NUM>, for PUCCH resource allocation, the resource set is first determined based on the UCI payload size. Within a resource set, one resource from multiple configured resources are indicated to UE, based on the PUCCH resource indicator field in DCI. Each PUCCH resource is identified by PUCCH format, starting symbol, starting RB (frequency-domain allocation), cyclic shifts, and code domain allocation (e.g., if there is an OCC, etc., depending on the particular format). This information can therefore be indicated to the UE.

When the second UCI and the first HARQ-ACK PUCCH resource are considered for UCI multiplexing, if the resulting determined first PUCCH resource carrying the second UCI and the first HARQ-ACK feedback do not overlap with the second HARQ-ACK PUCCH resource, and if one of the PUCCH resources is a short PUCCH, the UE may transmit two PUCCHs in a slot. Alternatively, the second UCI and the second HARQ-ACK payload may be considered for UCI multiplexing, and if the resulting determined second PUCCH resource carrying the second UCI and the second HARQ-ACK feedback payload do not overlap with the first HARQ-ACK PUCCH resource, and if one of the PUCCH resources is a short PUCCH, then the UE may transmit the first HARQ-ACK PUCCH and the determined second PUCCH resource within the slot.

As a generalization of the above, the UE may evaluate either option of multiplexing the second UCI with the first or the second HARQ-ACK PUCCH resource, and may transmit the combination of multiple PUCCH transmissions within the slot depending on the resulting determined first PUCCH resource (to carry the first HARQ-ACK feedback and the second UCI) or the second PUCCH resource (to carry the second HARQ-ACK and the second UCI). In case both options are feasible, the UE may transmit following either the (i) updated/determined first PUCCH resource and second HARQ-ACK PUCCH, or the (ii) updated/determined second PUCCH resource and first HARQ-ACK PUCCH. The first or second PUCCH resources are "updated" as used herein in the sense that they are used to multiplex the first or second HARQ-ACK feedback with the second UCI, respectively.

<FIG> illustrates one example of multiplexing two HARQ-ACKs and a second UCI (such as one carrying P/SP-CSI reports) on PUCCH in a slot <NUM> with symbols <NUM>. In particular, <FIG> shows respective time frequency resources 100a and 100b, where resource 100a shows determined uplink resources prior to multiplexing of a first or second HARQ-ACK feedback with the second UCI, and resource 100B shows uplink resources updated after multiplexing of the first HARQ-ACK feedback with the second UCI according to one embodiment (updated uplink resources). In particular, in the example, as shown in <FIG> at 100a, two PUCCH resources 106a and 110a to carry separate first and second HARQ-ACK feedbacks, respectively, are determined by the UE to overlap with another PUCCH resource 108a that is to carry P/SP CSI report. According to the UCI multiplexing procedure of one embodiment, uplink resources may be updated by the UE in the form of PUCCH resource 106b to carry the second UCI of PUCCH resource 108a along with the first HARQ-ACK feedback of PUCCH resource 106a. Given that the determined first PUCCH resource 106a does not overlap with the second determined HARQ-ACK PUCCH resource 110a in <FIG>, the UE may therefore, according to this embodiment, transmit both updated PUCCH resources 106b and 108b in a same slot <NUM> as shown in <FIG>.

By allowing multiple HARQ-ACKs to be transmitted within a slot, a PUCCH resource indicator in the DCls scheduling the PDSCHs where the corresponding HARQ-ACK feedbacks are scheduled in the same slot, may, according to an embodiment, point to different starting symbols for PUCCH resources, or to different PUCCH resources with no time domain overlap. The actual PUCCH resources which carry such feedbacks (as well as other potentially multiplexed reports), may then be determined directly based on the corresponding PUCCH resource indicator values. This is applicable both for the case where HARQ-ACK feedbacks do not overlap with each other or any other report/information, as well as when any HARQ-ACK feedback overlaps (and is multiplexed) with any other reports/information, while the resulting determined PUCCH resource does not overlap with other HARQ-ACK feedbacks (or HARQ-ACK feedbacks multiplexed with some other reports/information).

With the PUCCH resource indicator values being read and used from the corresponding DCls, some reference point may be defined to further adjust the PUCCH resource, such as, for example, its starting symbol. In one example, the PUCCH resource indicator may be interpreted relative to the beginning of the slot. In another example, the PUCCH resource indicator may be interpreted relative to the end/start of the last PUCCH resource carrying a HARQ-ACK.

Alternatively, some relative symbol offset may be defined and dynamically or semi-statically indicated by RRC configuration signaling or L1-signaling, such that in case of multiple HARQ-ACK transmissions within a slot, the timing relationship between the corresponding PUCCH resources carrying the HARQ-ACK feedbacks (potentially each multiplexed with any other report/information), are implicitly or explicitly indicated to the UE.

According to one embodiment, the indication of different PUCCH resources for HARQ-ACK feedback within a slot may be achieved via a combination of a K1 offset (as indicated by a PDSCH-to-HARQ-timing-indicator field in the scheduling DCI format, if present, or as provided by higher layer parameter dl-DataToUL-ACK) and the PUCCH resource indicator (PRI) in the scheduling DCI. Specifically, the starting symbol of a PUCCH resource indicated by the PRI may be interpreted jointly with the indicated value of the PDSCH-to-HARQ-timing-indicator field K1 in the DCI (or as provided by the higher layer parameter dl-DataToUL-ACK), wherein the latter indication may be reinterpreted to indicate the PDSCH-end to the HARQ-ACK-start timing offset using a combination of one or more of: slots, half-slots, or a set of one or more symbols (as against the Rel-<NUM> interpretation in terms of number of slots).

According to an embodiment, the UE may be configured by higher layers (such as by UE-specific RRC signaling) with the possibility of multiple PUCCH transmissions with HARQ-ACK feedback in a slot, or alternatively, configured by higher layers to follow a different interpretation of the K1 offset and PUCCH resource starting symbol determination for HARQ-ACK feedback while being capable of transmitting multiple PUCCH transmissions with HARQ-ACK feedback in a slot.

Following the above, the value indicated using PDSCH-to-HARQ-timing-indicator field in the DCI format (and/or the higher layer parameter dl-DataToUL-ACK) may be interpreted in units of half-slots or in units of a specified number of one or more symbols, e.g., <NUM>, <NUM> or <NUM> symbols. Subsequently, the startingSymbollndex parameter is interpreted with respect to the half-slot boundary as against the slot boundary with the value of the starting PUCCH symbol translated as startingSymbollndex' = (startingSymbolIndex - <NUM>) (and as startingSymbollndex' = (startingSymbollndex - <NUM>) for ECP case).

According to some other embodiments, let us assume that the PDSCH-to-HARQ-timing-indicator field in the DCI format is either N = <NUM> or <NUM> bits long. In such a case, the PDSCH-to-HARQ-timing-indicator field in the DCI format may be interpreted such that the last (N-<NUM>) least significant bit(s) (LSBs) of the DCI bit-field indicate one of <NUM> (N-<NUM>) values in units of slots as configured in the first <NUM> (N-<NUM>) values provided by higher layer parameter dl-DataToUL-ACK, and the most significant bit (MSB) (<NUM> bit) of the PDSCH-to-HARQ-timing-indicator field in the DCI format is used to indicate an additional half-slot offset or a symbol group, where the number of symbols within the symbol group can be predefined in the specification or configured by higher layers. Thus, for the half-slot offset indication, a '<NUM>' may indicate that the timing offset is in terms of an integer number of slots from PDSCH-end, while a '<NUM>' indicates that the timing offset is in terms of an integer number of slots from the PDSCH-end plus another half-slot (<NUM> symbols for normal cyclic prefix (NCP) length and <NUM> symbols for extended cyclic prefix (ECP) length where the cyclic prefix (CP) configuration corresponds to that for the PUCCH in the corresponding UL bandwidth part (BWP)). Further, when an additional half-slot offset is indicated, then the UE interprets the starting symbol for the indicated PUCCH resource with respect to symbol index <NUM> (for NCP) or symbol index <NUM> (for ECP) of the corresponding slot. Accordingly, the parameter startingSymbollndex of the PUCCH resource is translated as startingSymbollndex' = (startingSymbollndex - <NUM>) (and as startingSymbollndex' = (startingSymbollndex - <NUM>) for ECP case).

For the case when the PDSCH-to-HARQ-timing-indicator field in the DCI format is N = <NUM> bit-long, the bit-field may only indicate the whether or not to apply a half-slot offset in addition to the timing offset indicated by the first value indicated by the higher layer parameter dl-DataToUL-ACK. This mechanism can be extended to other variants using indication of the PDSCH to HARQ-ACK timing offset in units of 'k' symbols with value of 'k' other than <NUM> (or <NUM> for the ECP case). An advantage of the above mechanism is that the grouping of HARQ-ACK feedback to multiple PUCCH resources within a slot is realized by indicating this information using part of the slot offset indication instead of using additional DCI bits or alternative mechanisms, e.g., partitioning of PUCCH resource sets or partitioning of HARQ processes or based on RNTI.

In another embodiment, the PUCCH resource information corresponding to the PUCCH resources carrying multiple HARQ-ACK feedbacks, e.g., PUCCH formats, starting symbols, starting RBs (frequency-domain allocation), cyclic shifts, and code domain allocations, may be configured by a jointly encoded time domain resource allocation (TD-RA) table and dynamic indication of a combination of such parameters to the UE.

Referring back to the embodiment shown in <FIG>, in case the updated/determined first PUCCH resource carrying the second UCI and the first HARQ-ACK feedback overlaps with the updated/determined second HARQ-ACK PUCCH resource (not shown), or if the second UCI and two non-overlapping HARQ-ACK PUCCH resources (as shown in <FIG>) are considered for UCI multiplexing, and if the DCI format scheduling the second PDSCH is detected at least N<NUM> symbols before the first symbol of the first HARQ-ACK feedback resource (where N<NUM> is, for example, defined as "Capability #<NUM>" or "Capability #<NUM>" in Table <NUM> below), the UE may, according to an embodiment, multiplex all UCI including multiple HARQ-ACK feedbacks and the second UCI into one PUCCH resource, where µ designates the subcarrier spacing SCS by way of the equation: Δ = 2µ x <NUM> where Δ corresponds to the SCS expressed in kHz.

<FIG> illustrates one example of multiplexing two HARQ-ACKs and P/SP-CSI reports on PUCCH.

In particular, <FIG> shows respective time frequency resources 200a and 200b in symbols <NUM> of a slot <NUM>, where resource 200a shows determined uplink resources prior to multiplexing of a first and second HARQ-ACK feedback with the second UCI, and resource 200b shows uplink resources updated after multiplexing of the first and second HARQ-ACK feedbacks with the second UCI according to one embodiment (updated uplink resources). In particular, in the example, as shown in <FIG>, two PUCCH resources 206a and 210a to carry separate first and second HARQ-ACK feedbacks, respectively, are determined by the UE to overlap with another PUCCH 208a that is to carry P/SP CSI report. According to the UCI multiplexing procedure of one embodiment, uplink resources may be updated by the UE in the form of PUCCH 206b to carry the second UCI of PUCCH resource 208a along with the first and second HARQ-ACK feedbacks of PUCCH resource 206a. Given that the determined first PUCCH resource 206a does not overlap with the second determined HARQ-ACK PUCCH resource 210a in <FIG>, the UE may therefore, according to this embodiment, transmit updated PUCCHs 206b carrying all UCls in a same slot <NUM> as shown in <FIG>. The PUCCH resource 206b may be determined based on the PRI field which is used to indicate the PUCCH carrying the first HARQ-ACK feedback.

According to one embodiment, when multiple HARQ-ACKs are multiplexed in one PUCCH resource (potentially multiplexed with any other UL report/information), the PUCCH resource carrying combined UCI may be determined in accordance with PUCCH resource indicator (PRI) which is used to indicate the PUCCH carrying the first or the last dynamic HARQ-ACK feedback among multiple HARQ-ACK feedbacks. More specifically, one PUCCH resource set may be determined based on the total payload size of the combined UCI. Further, the aforementioned PRI may be used to allow selection of one PUCCH resource from the determined PUCCH resource set.

Alternatively, the PUCCH resource carrying combined UCI may be determined in accordance with PUCCH resource indicator (PRI) which is included in the first or last DCI scheduling the PDSCHs where the corresponding HARQ-ACK feedbacks are scheduled in the same slot. In the case of carrier aggregation, the PRI may be included in the DCI which is transmitted with the lowest component carrier (CC) index.

According to one embodiment, the bit order of HARQ-ACK feedbacks within the combined UCI may follow the timing of one or more of: first symbol of each HARQ-ACK feedback in the same slot, the relative timing between the PDCCH monitoring occasions in which the corresponding scheduling DCls are detected, and the relative timing between the first or last symbol of the scheduled PDSCHs. For instance, assuming N HARQ-ACK feedbacks are scheduled in the same slot, the bit order of HARQ-ACK feedbacks within the combined UCI can be <NUM>st HARQ-ACK, <NUM>nd HARQ-ACK,. , Nth HARQ-ACK. Alternatively, the ordering of the HARQ-ACK feedback information may be determined according to the order of the HARQ process ID (PID) used to schedule the corresponding PDSCHs.

<FIG> illustrates a PUCCH resource <NUM> showing one example of two HARQ-ACK codebooks for multiple HARQ-ACK feedbacks multiplexed therein. When both transport block (TB) based HARQ-ACK feedback codebook <NUM> and code block group (CBG) based HARQ-ACK feedback codebook <NUM> are configured, two separate HARQ-ACK codebooks may be carried by one PUCCH, such as PUCCH <NUM>, according to some embodiments, wherein each HARQ-ACK codebook <NUM> and <NUM> includes multiple TB based HARQ-ACK feedbacks or CBG based HARQ-ACK feedbacks. In the example, TB based HARQ-ACK feedback and CBG based HARQ-ACK feedback are shown as being concatenated and carried by a PUCCH.

Note that the embodiment an example of which is shown in <FIG> may also be applied for the case where SPS HARQ-ACK feedbacks are concatenated with TB/CBG based HARQ-ACK feedback. If the payload size of the combined UCI exceeds the capacity of the determined PUCCH resource, certain portion of the CSI report including CSI part <NUM> and/or CSI part <NUM> may be dropped in accordance with the priority rule as defined in Section <NUM>. <NUM> of TS38.

Embodiments of multiplexing multiple HARQ-ACK feedback and PUSCHs are provided as follows below.

According to one embodiment, as shown by way of example in <FIG>, when a plurality of PUCCH resources carrying dynamic or SPS HARQ-ACK feedback overlap with PUSCH, wherein PUCCHs and PUSCH are not distinguished based on service type or priority, and if the timeline requirement as noted above is satisfied, the UE may piggyback multiple HARQ-ACK feedbacks on PUSCH. This embodiment may also apply for the case when two non-overlapping SPS HARQ-ACK PUCCH resources overlap with the second UCI PUCCH. The second UCI may include periodic and/or semi-persistent scheduled CSI (P/SP-CSI) report and/or SR and/or SPS HARQ-ACK feedback.

Further, in one option, multiple HARQ-ACK feedbacks may be mapped onto a PUSCH resource separately. The amount of resources for each HARQ-ACK feedback may be calculated in accordance with the corresponding HARQ-ACK payload size and configured/indicated beta offset. Further, the multiple HARQ-ACK feedbacks may be mapped sequentially on PUSCH based on one or more of: the transmission timing of the first symbol HARQ-ACK feedback, the relative timing between the PDCCH monitoring occasions in which the corresponding scheduling DCls are detected, and the relative timing between the first or last symbol of the scheduled PDSCHs. In one example, the earliest HARQ-ACK feedback in a slot is mapped first and second HARQ-ACK feedback is mapped after the first HARQ-ACK feedback, etc. Alternatively, the ordering of the mapping of the HARQ-ACK feedback information may be determined according to the order of the HARQ process ID (PID) used to schedule the corresponding PDSCHs.

In yet another option, the information bits of multiple HARQ-ACK feedbacks may be first concatenated. The bit order of HARQ-ACK feedbacks can be defined similar to the aforementioned embodiments, as shown for example in the context of <FIG>. Subsequently, the concatenated HARQ-ACK feedbacks may be modulated and mapped on PUSCH. The amount of resource allocated for combined HARQ-ACK may calculated in accordance with the concatenated HARQ-ACK payload size and configured/indicated beta offset.

<FIG> illustrates one example of multiplexing two HARQ-ACK feedbacks with PUSCH, including multiplexing two HARQ-ACKs and a PUSCH in a slot <NUM> with symbols <NUM>. In particular, <FIG> shows respective time frequency resources 400a and 400b, where resource 400b shows determined uplink resources prior to multiplexing of a first and second HARQ-ACK feedback with a PUSCH, and resource 100b shows uplink resources updated after multiplexing of the first and second HARQ-ACK feedbacks with the PUSCH according to one embodiment (updated uplink resources). In particular, in the example, as shown in <FIG>, two PUCCH resources 406a and 410a to carry separate first and second HARQ-ACK feedbacks, respectively, are determined by the UE to overlap with a PUSCH 408a. According to the HARQ-ACK and PUSCH multiplexing procedure of one embodiment, uplink resources may be updated by the UE in the form of PUCCH 406b to carry the PUSCH 408a along with the first and second HARQ-ACK feedbacks of PUCCH resources 406a and 410a, respectively. Given that the determined first PUCCH resource 406a does not overlap with the second determined HARQ-ACK PUCCH resource 410a in <FIG>, the UE may therefore, according to this embodiment, transmit updated PUCCHs 406b in a slot <NUM> as shown in <FIG>. This, in this embodiment, two PUCCHs carrying separate HARQ-ACK feedbacks overlap with PUSCH. According to aforementioned examples, two HARQ-ACK feedbacks may be combined together and piggyback combined HARQ-ACK feedbacks on PUSCH.

Referring to <FIG>, a process <NUM> according to one embodiment includes at operation <NUM>, determining that UE is configured with a feature of multiple Physical Uplink Control Channel (PUCCH) resources with HARQ-ACK feedback within a slot; at operation <NUM>, determining a Physical Uplink Control Channel (PUCCH) resource to carry Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback in response to a scheduled Physical Downlink Shared Channel (PDSCH) resource; and at operation <NUM>, encoding for transmission to a NR evolved NodeB (gNodeB) the PUCCH resource, the PUCCH resource to carry the HARQ-ACK feedback and: another PUCCH resource carrying Uplink Control Information (UCI) other than HARQ-ACK feedback, and a scheduled Physical Uplink Shared Channel (PUSCH) resource.

<FIG> illustrates an architecture of a system <NUM> of a network according to some embodiments. The system <NUM> is shown to include a user equipment (UE) <NUM> and a UE <NUM>. The UEs <NUM> and <NUM> are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device.

The UEs <NUM> and <NUM> may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) <NUM>. The UEs <NUM> and <NUM> utilize connections <NUM> and <NUM>, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections <NUM> and <NUM> are illustrated as an air interface to enable communicative coupling and may be consistent with cellular communications protocols.

The connection <NUM> may comprise a local wireless connection, such as a connection consistent with any IEEE <NUM> protocol, wherein the AP <NUM> would comprise a wireless fidelity (WiFi®) router.

The RAN <NUM> may include one or more access nodes that enable the connections <NUM> and <NUM>. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation or New Radio evolved NodeBs (gNodeB), RAN nodes, and so forth, and may comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).

According to some embodiments, the UEs <NUM> and <NUM> may be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes <NUM> and <NUM> over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals may comprise a plurality of orthogonal subcarriers.

The RAN <NUM> is shown to be communicatively coupled to a core network (CN) <NUM> -via an S1 interface <NUM>. In embodiments, the CN <NUM> may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface <NUM> is split into two parts: the S1-U interface <NUM>, which carries traffic data between the RAN nodes <NUM> and <NUM> and the serving gateway (S-GW) <NUM>, and the S1-mobility management entity (MME) interface <NUM>, which is a signalling interface between the RAN nodes <NUM> and <NUM> and MMEs <NUM>.

The CN <NUM> includes network elements. The term "network element" may describe a physical or virtualized equipment used to provide wired or wireless communication network services. In this embodiment, the CN <NUM> comprises, as network elements, the MMEs <NUM>, the S-GW <NUM>, the Packet Data Network (PDN) Gateway (P-GW) <NUM>, and a home subscriber server (HSS) <NUM>.

<FIG> illustrates example interfaces of baseband circuitry according to various embodiments. The baseband circuitry <NUM> may be included in a UE or gNodeB, for example, in UE or gNodeB of <FIG>, and may comprise processors <NUM>-<NUM> and a memory <NUM> utilized by said processors. Each of the processors <NUM>-<NUM> may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory <NUM>. Baseband circuitry <NUM> may also include an audio digital signal processor (Audio DSP) <NUM>.

The baseband circuitry <NUM> may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface <NUM> (e.g., an interface to send/receive data to/from memory external to the baseband circuitry <NUM>), an application circuitry interface <NUM> (e.g., an interface to send/receive data to/from an application circuitry), an RF circuitry interface <NUM> (e.g., an interface to send/receive data to/from an RF circuitry), a wireless hardware connectivity interface <NUM> (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface <NUM> (e.g., an interface to send/receive power or control signals to/from a power management integrated circuit (PMIC).

Claim 1:
An apparatus of a user equipment, UE, comprising:
a Radio Frequency, RF, interface, and
processing circuitry coupled to the RF interface, the processing circuitry configured to:
determine an overlap between a plurality of determined Physical Uplink Control Channel, PUCCH, resources to carry a respective plurality of Hybrid Automatic Repeat Request Acknowledgment, HARQ-ACK, feedbacks and another determined PUCCH resource to carry an Uplink Control Information, UCI;
determine an updated PUCCH resource for carrying at least a first HARQ-ACK feedback of the plurality of HARQ-ACK feedbacks and the UCI, wherein the updated PUCCH resource does not overlap with a determined PUCCH resource to carry a second HARQ-ACK feedback of the plurality of HARQ-ACK feedbacks not included in the updated PUCCH resource; and
encode the updated PUCCH resource and the determined PUCCH resource for transmission to a base station within one slot.