HARQ-ACK codebook design for carrier aggregation

Abstract

Systems, methods, apparatuses, and computer program products for HARQ-ACK CB design for carrier aggregation. One method may include receiving at least one configuration; receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a first cell and a second cell of a network entity; based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and non-acknowledgements (NACKs); receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH); based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback; and transmitting the asynchronous HARQ-ACK feedback to the second cell of the network entity.

Description

HARQ-ACK CODEBOOK DESIGN FOR CARRIER AGGREGATIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority from, and the benefit of, India Patent Application No.202541006662, filed January 27, 2025, the contents of which are hereby incorporated by reference in their entirety.TECHNICAL FIELD

[0002] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as 3rdGeneration Partnership Project (3GPP) Long Term Evolution (LTE), 5thgeneration (5G) radio access technology (RAT), new radio (NR) access technology, 6thgeneration (6G) RAT, and / or other communications systems. For example, certain example embodiments may relate to systems and / or methods for hybrid automatic repeat request (HARQ)-acknowledgment (ACK) codebook (CB) design for carrier aggregation (CA).BACKGROUND

[0003] Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology, and / or MulteFire Alliance. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E-UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency-communication (URLLC), and massive machine-type communication (mMTC). NR is expected to deliver extreme broadband, ultra-robust, low-latency connectivity, and massive networking to support the Internet of Things (loT). The next generation radio access network (NG-RAN) represents the radio access network (RAN) for 5G, which may provide radio access for NR, LTE, and LTE-A. It is noted that the nodes in 5G providing radio access functionality to a user equipment (UE) (e.g., similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE) may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG-eNB) when built on E-UTRA radio.

[0004] 3GPP 6G is intended to build upon the advantages and breakthroughs of previous cellular technologies, with multi-RAT spectrum sharing (MRSS) enabling smooth transitions from 5G to 6G. 6G CA may further improve on network capacity and coverage, while dual-connectivity can provide support for non-collocated 6G areas. Using next generation mobile broadband (NextGenMBB), UE may experience data rates around 500 Mbps. 6G may also incorporate fixedwireless access (FWA) to improve traffic for fixed locations, such as homes, offices, and businesses. FWA can leverage terahertz and millimeter-wave bands to deliver ultra-fast data speeds, potentially up to 100 Gbps, especially with multiple input multiple output (MIMO) antennas.

[0005] Moreover, 3GPP 6G is expected to incorporate artificial intelligence / machine learning (AI / ML) technologies to perform network automation and enable self-optimizing networks (SONs). For example, AI / ML may monitor network usage, conditions, and traffic in real-time, and automatically adjust network parameters such as interference mitigation, spectrum management, and load balancing, thereby providing faster failure recoveries and reducing network congestion.SUMMARY

[0006] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive at least one configuration. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a first cell and a second cell of a network entity. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determine acknowledgments (ACKs) and nonacknowledgments (NACKs). The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to based upon the asynchronous HARQ-trigger, select a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0007] In accordance with some example embodiments, a method may include receiving at least one configuration. The method may further include receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a first cell and a second cell of a network entity. The method may further include based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and non-acknowledgments (NACKs). The method mayfurther include receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback. The method may further include transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0008] In accordance with certain example embodiments, an apparatus may include means for receiving at least one configuration. The apparatus may further include means for receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a first cell and a second cell of a network entity. The apparatus may further include means for based on the received PDSCH scheduling DO and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and nonacknowledgments (NACKs). The apparatus may further include means for receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include means for based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback. The apparatus may further include means for transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0009] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving at least one configuration. The method may further include receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a first cell and a second cell of a network entity. The method may further include based on the received PDSCH scheduling DO and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and non-acknowledgments (NACKs). The method may further include receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback. The method may further include transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0010] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving at least one configuration. The method may furtherinclude receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a first cell and a second cell of a network entity. The method may further include based on the received PDSCH scheduling DO and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and nonacknowledgments (NACKs). The method may further include receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback. The method may further include transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0011] In accordance with various example embodiments, an apparatus may include receiving circuitry configured to perform receiving at least one configuration. The apparatus may further include receiving circuitry configured to perform receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a first cell and a second cell of a network entity. The apparatus may further include determining circuitry configured to perform based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and nonacknowledgments (NACKs). The apparatus may further include receiving circuitry configured to perform receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include selecting circuitry configured to perform based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback. The apparatus may further include transmitting circuitry configured to perform transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0012] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit at least one configuration. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH on a first cell and on a second cell of the apparatus. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink sharedchannel (PUSCH). The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0013] In accordance with some example embodiments, a method may include transmitting at least one configuration. The method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH on a first cell and on a second cell of the apparatus. The method may further include transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include receiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0014] In accordance with certain example embodiments, an apparatus may include means for transmitting at least one configuration. The apparatus may further include means for transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH on a first cell and on a second cell of the apparatus. The apparatus may further include means for transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include means for receiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0015] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include transmitting at least one configuration. The method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH on a first cell and on a second cell of the apparatus. The method may further include transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include receiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0016] In accordance with some example embodiments, a computer program product may perform a method. The method may include transmitting at least one configuration. The method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH on a first cell and on a second cell of the apparatus. The method may further include transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include receiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0017] In accordance with various example embodiments, an apparatus may include transmitting circuitry configured to perform transmitting at least one configuration. The apparatus may further include transmitting circuitry configured to perform transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH on a first cell and on a second cell of the apparatus. The apparatus may further include transmitting circuitry configured to perform transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include receiving circuitry configured to perform receiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0018] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a network entity. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to based on received PDSCH scheduling DO and a decoding outcome of the corresponding at least one PDSCH, determine at least one acknowledgement (ACK) and non-acknowledgement (NACK). The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to based upon the HARQ-trigger, select an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or PUSCH. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit a HARQ-ACK feedback to the network entity.

[0019] In accordance with some example embodiments, a method may include receiving at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The method may further include receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a network entity. The method may further include based on received PDSCH scheduling DO and a decoding outcome of the corresponding at least one PDSCH, determining at least one acknowledgement (ACK)and non-acknowledgement (NACK). The method may further include receiving a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include based upon the HARQ-trigger, selecting an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or PUSCH. The method may further include transmitting a HARQ-ACK feedback to the network entity.

[0020] In accordance with certain example embodiments, an apparatus may include means for receiving at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The apparatus may further include means for receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a network entity. The apparatus may further include means for based on received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining at least one acknowledgement (ACK) and non-acknowledgement (NACK). The apparatus may further include means for receiving a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include means for based upon the HARQ-trigger, selecting an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or PUSCH. The apparatus may further include means for transmitting a HARQ-ACK feedback to the network entity.

[0021] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The method may further include receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a network entity. The method may further include based on received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining at least one acknowledgement (ACK) and non-acknowledgement (NACK). The method may further include receiving a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include based upon the HARQ-trigger, selecting an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or PUSCH. The method may further include transmitting a HARQ-ACK feedback to the network entity.

[0022] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configurationcomprises configuration of an asynchronous HARQ-ACK feedback. The method may further include receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a network entity. The method may further include based on received PDSCH scheduling DO and a decoding outcome of the corresponding at least one PDSCH, determining at least one acknowledgement (ACK) and non-acknowledgement (NACK). The method may further include receiving a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include based upon the HARQ-trigger, selecting an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or PUSCH. The method may further include transmitting a HARQ-ACK feedback to the network entity.

[0023] In accordance with various example embodiments, an apparatus may include receiving circuitry configured to perform receiving at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The apparatus may further include receiving circuitry configured to perform receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a network entity. The apparatus may further include determining circuitry configured to perform based on received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining at least one acknowledgement (ACK) and non-acknowledgement (NACK). The apparatus may further include receiving circuitry configured to perform receiving a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include selecting circuitry configured to perform based upon the HARQ-trigger, selecting an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or PUSCH. The apparatus may further include transmitting circuitry configured to perform transmitting a HARQ-ACK feedback to the network entity.

[0024] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel(PUSCH). The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive a HARQ-ACK feedback.

[0025] In accordance with some example embodiments, a method may include transmitting at least one configuration of a hybrid automatic repeat request (HARQ) -acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH. The method may further include transmitting a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include receiving a HARQ-ACK feedback.

[0026] In accordance with certain example embodiments, an apparatus may include means for transmitting at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The apparatus may further include means for transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH. The apparatus may further include means for transmitting a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include means for receiving a HARQ-ACK feedback.

[0027] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include transmitting at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH. The method may further include transmitting a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include receiving a HARQ-ACK feedback.

[0028] In accordance with some example embodiments, a computer program product may perform a method. The method may include transmitting at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH. The method may further include transmitting a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The method may further include receiving a HARQ-ACK feedback.

[0029] In accordance with various example embodiments, an apparatus may include transmitting circuitry configured to perform transmitting at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback. The apparatus may further include transmitting circuitry configured to perform transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH. The apparatus may further include transmitting circuitry configured to perform transmitting a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH). The apparatus may further include receiving circuitry configured to perform receiving a HARQ-ACK feedback.BRIEF DESCRIPTION OF THE DRAWINGS

[0030] For a proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0031] FIG. 1 illustrates an example of HARQ-ACK feedback in a CA case;

[0032] FIG. 2 illustrates an example of an asynchronous (Type 2) CB;

[0033] FIG. 3 illustrates another example of an asynchronous (Type 2) CB operation;

[0034] FIG. 4 illustrates another example of the DAI operation;

[0035] FIG. 5 illustrates an example of a signaling diagram according to certain example embodiments;

[0036] FIG. 6 illustrates an example of another signaling diagram according to certain example embodiments;

[0037] FIG. 7 illustrates an example of a flow diagram of another method according to various example embodiments;

[0038] FIG. 8 illustrates an example of a flow diagram of another method according to various example embodiments;

[0039] FIG. 9 illustrates an example of a flow diagram of another method according to various example embodiments;

[0040] FIG. 10 illustrates an example of a flow diagram of another method according to various example embodiments;

[0041] FIG. 11 illustrates an example of various network devices according to some example embodiments;

[0042] FIG. 12 illustrates an example of a 5G / 6G network and system architecture according to certain example embodiments;

[0043] FIG. 13 illustrates another example of a 6G system architecture according to some example embodiments; and

[0044] FIG. 14 illustrates an example of a 6G RAN user-plane protocol stack.DETAILED DESCRIPTION

[0045] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for HARQ-ACK CB design for CA is not intended to limit the scope of certain example embodiments, but is instead representative of selected example embodiments.

[0046] In 3GPP, physical uplink control channel (PUCCH) in NR may be used to carry uplink control information (UCI), such as scheduling requests (SRs), which may also be used for beam failure recovery requests, HARQ-ACK feedback, and channel state information (CSI) feedback. In general, individual HARQ-ACKs, as well as HARQ-non-acknowledgements (NACKs, also known as negative acknowledgement or no acknowledgement), may refer to one or more bits of acknowledgement information.

[0047] In general, type 1 (z.e., semi-static) HARQ-ACK CBs do not require a downlink (DL) assignment index (DAI), but may result in unnecessarily large CB sizes. Additionally, DL scheduling in any DL cell may reserve PUCCH resources on the PUCCH cell. Moreover, type 3 HARQ-ACK CBs may be constructed based on the DL HARQ processes, and may retrieve the latest HARQ-ACKs for all or a portion of DL HARQ processes. Type 3 HARQ-ACK CBs may be defined as a baseline CB for DL cells requiring loose coordination with the PUCCH cell. However, type 3 HARQ-ACK CBs may have unnecessarily large overhead. To mitigate that, type 3 HARQ-ACK CBs may only be used for a portion of DL HARQ processes; however, consecutive physical downlink shared channels (PDSCHs) may not need to contain consecutive DL HARQ processes. Furthermore, although HARQ-ACK feedback may be completely disabled, this may result in blindly decided on PDSCH HARQ retransmissions, radio link control (RLC) layer retransmissions, and / or conservative PDSCH link adaptations, all reducing achievable throughput and spectral efficiency. In addition, it may be possible to indicate that the HARQ-ACK feedback timing for a PDSCH is provided in a next DCI scheduling PDSCH that indicates a valid HARQ-ACK feedback timing.

[0048] In 3GPP NR, the timing of HARQ-ACK feedback may be signaled to the UE in a DL assignment; thus, HARQ-ACK feedback timing may be fixed before the DL assignment is transmitted. PUCCH resources for HARQ-ACK feedback may also be reserved for the UE at the time of DL scheduling. As a result, the uplink (UL) scheduler of the PUCCH cell may coordinate with the DL schedulers for all the DL serving cells, and potentially before the PUSCH scheduling is complete.

[0049] Furthermore, the DAI (z.e., needed in Type 2 HARQ-ACK CB construction) and PUCCH resource indicator (PRI) values in the DL assignments may need to be aligned across the DL serving cells. For self-scheduling of a serving cell, a field value on a DCI scheduling DL on a cell may depend on the simultaneous scheduling decisions on other DL serving cells. Low latency coordination between separate DL and UL schedulers (e.g., on different frequency ranges or even locations) may present a significant implementation challenge. Therefore, it should be possible to support CA across cells capable to support only loose coordination with increased signaling latency. Some cells may be capable of fast coordination e.g., when scheduling is done within the same unit). To achieve loose coordination, the HARQ-ACK CB construction should not require DCI field coordination across cells, and DL scheduling on a cell should not require simultaneous UL scheduling decision for PUCCH cells (in terms of PUCCH resources).

[0050] Certain example embodiments described herein may have various benefits and / or advantages to overcome the disadvantages described above. For example, certain example embodiments may relax the latency requirements for the coordination between DL and / or UL schedulers either for different cells and / or for DL and UL schedulers within the same cell, allowing for more independent operation of UL and / or DL schedulers. Some example embodiments may also remove the need for coordination in terms of DCI content (as DAI counting) for PDSCHs scheduled in different e.g., non-collocated and / or simultaneously) cells. Various example embodiments may also remove the need for exact knowledge of HARQ-ACK feedback size at the time of HARQ-ACK feedback reception. Thus, certain example embodiments discussed below are directed to improvements in computer-related technology.

[0051] Certain example embodiments may relate to CA, wherein the UE may be configured with more DL serving cells than UL serving cells; thus, HARQ-ACK feedback for multiple DL serving cells may be multiplexed into a transmission on a PUCCH cell. The UL CA capabilities of the UE may have more restrictions than the DL CA capabilities of the UE. For LTE and NR, the HARQ-ACK of DL serving cells of a cell group (e.g., master cell group (MCG) / secondary cell group (SCG) for dual-connectivity, or a PUCCH cell group for dual PUCCH operation) may be reported in a HARQ-ACK CB (containing the HARQ-ACK of the DL serving cells of a cell group), and transmitted on the PUCCH cell of the cell group. Some example embodiments may relate todetermining HARQ-ACK CBs when there is minimal layer 1 (LI) coordination between PUCCH cells and all DL CA serving cells.

[0052] In various example embodiments, HARQ-ACK CB structure and reporting supporting asynchronous HARQ-ACK feedback may be applied in various scenarios / cases. For example, for a case of CA, a HARQ-ACK CB structure and HARQ-ACK reporting that facilitate loose LI coordination across the schedulers for different cells may be used. HARQ-ACK feedback timing (and the PUCCH resource) may be indicated to a UE within a HARQ-ACK CB cell group containing a PUCCH cell. HARQ-ACK feedback for other, loosely coordinated HARQ-ACK CB cell group(s) may be asynchronous and appended to the HARQ-ACK feedback of the HARQ-ACK CB cell group containing PUCCH cell. Asynchronous HARQ-ACK CB transmissions may also be triggered by a UL grant, wherein the asynchronous HARQ-ACK CB may be multiplexed on PUSCH, and may be transmitted with or without any HARQ-ACK feedback for the HARQ-ACK CB cell group containing PUCCH cell.

[0053] In a case of a single cell, a HARQ-ACK CB structure and reporting that reduces the coordination between the DL and UL schedulers may be used. A UL scheduler may determine when the UE should report PDSCH HARQ-ACK feedback, and PDSCH HARQ-ACK feedback timing and resource may not be indicated to the UE when PDSCH is scheduled.

[0054] In certain example embodiments with CA, when the UE is configured with DL CA (z.e., multiple DL serving cells), each DL serving cell may be associated with a HARQ-ACK CB cell group. A MCG / SCG / PUCCH cell group may include at least one HARQ-ACK CB cell group. Each HARQ-ACK CB cell group may be associated with an identifier and a HARQ-ACK CB type. A single HARQ-ACK CB may be reported per HARQ-ACK CB cell group (for the same PDSCH priority and coordinated set of transmission reception points (TRPs)). Multiple CBs may be generated for a single HARQ-ACK CB cell group for different PDSCH priorities and / or TRPs that are not coordinated. These CBs may have their own separate DAI processes, but may be concatenated for transmissions.

[0055] For dynamic CBs (e.g. , NR Type 2 HARQ-ACK CB), the DAI values may be incremented over the DL serving cells (or over only the activated DL serving cells) within the same HARQ-ACK CB cell group. One HARQ-ACK CB cell group may be associated with a different HARQ-ACK CB type than the other HARQ-ACK CB cell groups. Thus, one or more DL serving cells which operate with same HARQ-ACK CB type may be grouped together in one HARQ-ACK CB cell group. Therefore, a PUCCH cell group may contain more than one HARQ-ACK CB cell group (associated with one or more DL serving cells) of the same or different HARQ-ACK CB type. Individual HARQ-ACK CBs of the HARQ-ACK CB cell groups may be concatenated to createthe HARQ-ACK information to be reported to the base station (BS). The HARQ-ACK information may be reported (e.g., on the PUCCH cell).

[0056] Some example embodiments may include an asynchronous HARQ-ACK CB type (e.g., based on Type 2 HARQ-ACK CB) for HARQ-ACK feedback for HARQ-ACK CB cell groups with loose LI coordination with the PUCCH cell (or UL serving cell on which the HARQ-ACK is transmitted). In the asynchronous HARQ-ACK CB or asynchronous HARQ-ACK feedback, a HARQ-ACK feedback reporting time (z.e., PUCCH slot in case of NR) may not be indicated in PDSCH scheduling DCIs for which HARQ-ACKs are reported. The asynchronous (Type 2) HARQ-ACK CB may include a HARQ-ACK CB indicating a predetermined size. For example, the HARQ-ACK CB size may be proportional to the number of DL HARQ processes available in the HARQ-ACK CB cell group. As another example, the HARQ-ACK CB size may be equal to half of the number of DL HARQ processes available in the HARQ-ACK CB cell group multiplied with the number of ACKs / NACKs reported per HARQ process.

[0057] In various example embodiments, the HARQ-ACK bits may be ordered based on DL DAI indicated on the DL assignments of DL serving cells of the HARQ-ACK CB cell group. DL DAI may allow the UE to recognize when it has failed to detect DL assignment and insert NACK. In HARQ-ACK CB cell groups with asynchronous (Type 2) HARQ-ACK CB, the DL DAI may be incremented continuously and not to reset to 0 when new HARQ-ACK CB is started (as with regular / synchronous Type 2 HARQ-ACK CB).

[0058] In certain example embodiments, the UE may insert into the asynchronous HARQ-ACK CB the HARQ-ACK information that the UE has not previously reported until the most recent available HARQ-ACK or to the end of CB (in case more HARQ-ACK information would need to be reported than the determined HARQ-ACK CB size can contain), whichever is reached first. For example, if the UE has missed the DL assignment associated with the first HARQ-ACK, the UE may skip that and start with the HARQ-ACKs from the first unreported HARQ-ACK for which an associated DL assignment is detected. As another example, if the asynchronous HARQ-ACK CB size is larger than the number of HARQ-ACK bits to be reported, excess HARQ-ACK CB bits may be set to NACKs. Inserting NACKs may prevent an error if the UE has missed the last DL assignment for which the BS expects associated ACK / NACK. The UE and BS may determine the last HARQ-ACK to be reported based on the HARQ-ACK CB transmission time minus a predefined minimum time offset for HARQ-ACK CB and UL transmission (Tx) preparation. Alternatively, the UE may insert the HARQ process number and a cell identifier (from the cells of the HARQ-ACK CB cell groups) associated with the last reported HARQ-ACK, the number of reported HARQ-ACKs or PDSCHs / DCIs for which HARQ-ACKs are reported, and / or number ofexcess NACKs inserted. This may prevent the BS from assuming NACKs to be associated with the PDSCHs for which UE actually did not transmit HARQ-ACK feedback.

[0059] In various example embodiments, if there are more HARQ-ACK bits to be reported than can be included to the asynchronous HARQ-ACK CB, the UE may keep the excess HARQ-ACKs in the buffer and may report them in a later HARQ-ACK feedback instance. In one aspect, the UE may keep / buffer HARQ-ACK bits for a maximum time period, after which the UE may drop those bits. This behavior may be defined or configured per cell, HARQ-ACK CB group or cell group. Alternatively, HARQ-ACK dropping rules may be defined, such as by first dropping HARQ-ACK bits corresponding to serving cell(s) with lower / higher index within the HARQ-ACK cell group. If a HARQ-ACK CB corresponding to a cell group would need to be dropped, the UE may be specified or configured (e.g., via radio resource control (RRC)) for the CB to drop, such as the CB corresponding to the cell group with a lower / higher index.

[0060] In certain example embodiments, the most recent HARQ-ACK may be defined by any PDSCH not scheduled later than the PDCCH triggering the new HARQ-ACK CB transmission. For semi-persistent scheduling (SPS) PDSCH, the supported minimum processing time may be used to define the earliest time for the HARQ-ACK to be multiplex or the PDSCH-to-HARQ in the SPS activation DO could be used to define the earliest time the SPS HARQ-ACK to be mapped to the new HARQ-ACK CB or a PDSCH transmitted before the DCI triggering the HARQ-ACK transmission.

[0061] In some example embodiments, the UE may insert into the CB a time stamp for the first reported HARQ-ACK. The time stamp can be HARQ process number, a cell identifier from the cells of the HARQ-ACK CB cell groups, and / or a DAI value.

[0062] In some example embodiments, the UE may be explicitly triggered to report an asynchronous (Type 2) HARQ-ACK CB. Alternatively, the HARQ-ACK CB may be transmitted for each HARQ-ACK CB cell group whenever HARQ-ACK is transmitted for PDSCHs scheduled on the HARQ-ACK CB cell group containing PUCCH cell (e.g., “regular” HARQ-ACK). The trigger may be included on DL assignments and / or on UL grants. For example, the trigger may be only on a DL assignment and / or on UL grant for a serving cell included in the HARQ-ACK CB cell group containing a PUCCH cell. In another example, the trigger may be on a DL assignment and / or on UL grant scheduling any of the cells of the cell group.

[0063] In various example embodiments, the triggering may be extended to include an indicator. For example, the indication may be limited only to HARQ-ACK CB cell groups for which the asynchronous (Type 2) HARQ-ACK CB is configured. As another example, the indicator may indicate those HARQ-ACK CB cell groups for which the asynchronous (Type 2) HARQ-ACK CB is reported. Thus, the indicator may indicate that the HARQ-ACK feedback is reported for allHARQ-ACK CB cell groups (with asynchronous (Type 2) HARQ-ACK CB), for a specific cell group, and / or for none. The indicator may not impact the HARQ-ACK feedback for HARQ-ACK cell groups with “regular” HARQ-ACK CBs (z.e., not configured with the new asynchronous HARQ-ACK CB). As another example, the indicator may indicate to the UE one of the preconfigured CB sizes to be used.

[0064] In certain example embodiments, the UE may be triggered to report HARQ-ACK CBs for one or more HARQ-ACK CB cell groups in an aperiodic manner, semi-persistent, or periodic manner. Aperiodic HARQ-ACK triggering may be done via DCI, while semi-persistent HARQ-ACK triggering may be done via DCI or medium access control (MAC) control element (CE).

[0065] In case of aperiodic HARQ-ACK CB reporting triggering for at least one HARQ-ACK CB cell group, a corresponding time period(s) / window(s) may be configured (e.g., via RRC) or indicated e.g., via DCI triggering the reporting), where the UE generates HARQ-ACK CB (per HARQ-ACK CB cell group) which corresponds to (time domain) resources / allocations within this period or no later than this period. As an example, this time period may correspond to all ACK / NACKs buffered after the previous report until this report minus a minimum processing time. The time period may be defined per HARQ-ACK CB cell group. Alternatively, the time period(s) may be per each cell of a HARQ-ACK CB cell group, in which case the UE may consider the various time periods for the cells of a HARQ-ACK CB cell group when generating the HARQ-ACK CB for the HARQ-ACK CB cell group.

[0066] In some example embodiments, in case of semi-persistent (or even periodic) HARQ-ACK CB reporting for at least one HARQ-ACK CB cell group, at least one corresponding time period / window may be specified, configured, and / or indicated, where the UE may generate HARQ-ACK CB (per HARQ-ACK CB cell group) which corresponds to (time domain) resources / allocations within this period or no later than this period. In one example, the time period may be the period between two UCI reporting occasions on PUCCH or PUSCH.

[0067] In various example embodiments, the time period(s) may account for at least the minimum processing / preparation time for UL transmission (including the HARQ-ACK CB construction and multiplexing); thus, the time period(s) may exclude or not consider the time corresponding at least to the minimum processing / preparation time for UL transmissions.

[0068] In certain example embodiments, the assumed fixed asynchronous HARQ-ACK CB size may depend on the indicated or configured time period(s). There may be an implicit or explicit association between a time period(s) and a (respective) CB size. The UE may concatenate the HARQ-ACK CBs to be reported for a transmission of HARQ-ACK feedback.

[0069] FIG. 1 illustrates an example of HARQ-ACK feedback in a CA case. Cell#l may be part of a HARQ-ACK CB cell group with regular (synchronous) Type 2 HARQ-ACK CB, while Cells#2 and #3 may be part of HARQ-ACK CB cell groups with the new asynchronous (Type 2) HARQ-ACK CB. The asynchronous (Type 2) HARQ-ACK CB may be transmitted based on the trigger on Cell#l (e.g. , through DO), part of HARQ-ACK CB cell group containing PUCCH cell. In some example embodiments, the asynchronous Type 2 HARQ-ACK CB may be triggered by DCIs on other cells (such as Cell#2 or Cell#3). Asynchronous and regular (synchronous) Type 2 HARQ-ACK CBs may be concatenated for transmission. When the trigger is contained on UL grant, an asynchronous (Type 2) HARQ-ACK CB may be transmitted without any regular Type 2 HARQ-ACK CB on the scheduled PUSCH.

[0070] FIG. 2 illustrates an example of asynchronous (Type 2) HARQ-ACK CB. The HARQ-ACK CB may include a time stamp (e.g., HARQ process number and cell identifier for the first reported ACK7NACK). The ACKs / NACKs may be ordered based on the DL DAI incremented within the HARQ-ACK CB cell group. As shown in FIG. 2, the indicated or predetermined HARQ-ACK CB size may be larger than the number of reported ACKs / NACKs. The excess CB bits may be filled with NACKs. A separate bit location for SPS PDSCH ACKs / NACKs is shown in FIG. 3.

[0071] FIG. 3 illustrates another example of asynchronous (Type 2) HARQ-ACK CB operation, wherein the UE has buffered more ACKs / NACKs than can be reported in the indicated (or predetermined) asynchronous HARQ-ACK CB size. In this case, the UE reports the number of ACKs / NACKs fitting to the CB, in the order indicated by the DL DAI, and holds the excess ACK / NACK bits in the buffer for later HARQ-ACK feedback transmission.

[0072] FIG. 4 illustrates another example of asynchronous (Type 2) HARQ-ACK CB in terms of the DAI operation. In particular, cells #2 and #3 may be part of HARQ-ACK CB cell groups with the asynchronous (Type 2) HARQ-ACK CB. PDSCH scheduling DCIs are illustrated for the Cells #2 and #3 with the contained DAI values. DAI may occupy 2 bits and obtain 4 values 0, 1, 2, 3. DAI may be incremented first over the cells that are contained within the same HARQ-ACK CB cell group and contain PDSCH scheduling DCI on the same time instance. These cells are the Cells #2 and #3 illustrated in FIG. 4. After incrementing DAI over the cells for a period of time, the incrementing of the DAI may continue in the next time instance. Once the DAI is incremented to its maximum value (e.g., 3 for a DAI size of 2 bits), it may wrap around back to minimum value (e.g., 0 at the next increment).

[0073] As DAI value is related to the cumulative number of PDSCH scheduling DCIs within a HARQ-ACK CB cell group, the UE may determine from discontinuous DAI values in consecutive (in the sense of DAI incrementing order) PDSCH scheduling DCIs that UE has missed or failed to detect PDSCH scheduling DCIs. As shown in FIG. 4, the UE detects PDSCH scheduling DCI with DA 1=3 on Cell #3. The next PDSCH scheduling DCI that UE detects has also DA 1=3 on Cell #3.Based on discontinuity of DAI incrementing, the UE may determine that it has missed 3 PDSCH scheduling DCI and determines corresponding number of NACKs or, alternatively, HARQ-ACK feedback value indicating PDCCH detection failure.

[0074] FIG. 4 illustrates an example where DAI value may not be reset to 0 at the beginning of a new HARQ-ACK CB as the starting point of a HARQ-ACK CB may not be known at the NE at the time when PDSCH scheduling DCIs are transmitted. Instead, the DAI value may be continuously incremented from the DAI value of previous PDSCH scheduling DCI(s).

[0075] FIG. 4 illustrates an example where ACKs / NACKs may be stored to a buffer. Additionally, the ACKs / NACKs may be ordered to the buffer based on the DL DAI incremented within the HARQ-ACK CB cell group. In some embodiments, HARQ process number and cell identifier that is associated with ACK / NACK may additionally be buffered for each ACK / NACK. In case the buffered NACK is associated with a failed PDCCH detection, an invalid value may be buffered for the HARQ process number and the cell identifier.

[0076] FIG. 4 illustrates another example of asynchronous (Type 2) HARQ-ACK CB operation where the HARQ-ACK CB may include the HARQ process number and cell identifier for the first ACK / NACK included to the HARQ-ACK CB. As shown in FIG. 4, the UE reports the number of ACKs / NACKs fitting to the HARQ-ACK CB, in the order indicated by the DE DAI, and holds the excess ACK / NACK bits in the buffer for later HARQ-ACK feedback transmission when the UE has buffered more ACKs / NACKs than can be reported in the indicated (or predetermined) asynchronous HARQ-ACK CB size.

[0077] In certain example embodiments, when the UE receives the trigger to report asynchronous (Type 2) HARQ-ACK CB in UL grants, minimum processing time for asynchronous (Type 2) HARQ-ACK CB is predetermined / standardized. For example, it may be the minimum processing time for PUSCH preparation procedure. For timing purposes, the slot duration of a configured / predetermined cell (e.g., PUCCH cell) may be used, irrespective of the cell on which PUSCH is scheduled.

[0078] Transmission time for regular Type 2 CB may be normally determined based on an indicated HARQ-ACK feedback timing and PUCCH resource. If the indicated PUCCH resource is overlapping with the PUSCH containing an asynchronous (Type 2) HARQ-ACK CB, the HARQ-ACK CBs may be concatenated. The UE grant may contain UL DAI for the regular (z.e., synchronous) Type 2 HARQ-ACK CB, and may be related to that HARQ CB cell group only. There may be no DAI in the UL grant for the asynchronous (Type 2) HARQ-ACK CB, except for an explicit asynchronous (Type 2) HARQ-ACK CB trigger.

[0079] In certain example embodiments with a single cell, the UE may be configured with an asynchronous (Type 2) HARQ-ACK CB, as discussed above, even when it is configured for asingle cell. In particular, HARQ-ACK feedback reporting time may not be indicated in the DL assignments scheduling PDSCHs for which HARQ-ACKs are to be reported. The asynchronous HARQ-ACK CB may have a predetermined size. The HARQ-ACK CB size may be proportional to the number of HARQ processes available in the cell. HARQ-ACK bits may be ordered based on DAI indicated on the DL assignments. Based on the DAI in the DL assignment, the UE may recognize when it has failed to detect a DL assignment and inserts NACK correspondingly. The DAI in DL assignments may be incremented continuously (and not reset to 0) when the new asynchronous HARQ-ACK CB is started (as with regular Type 2 HARQ-ACK CB).

[0080] The UE may insert HARQ-ACK information to the asynchronous HARQ-ACK CB that the UE has not previously reported until the most recent available HARQ-ACK or to the end of CB (in case more HARQ-ACK information would need to be reported than the determined HARQ-ACK CB size can contain), whichever is reached first. If the UE has missed the DL assignment associated with the first HARQ-ACK, the UE may skip the first HARQ-ACK, and start with the HARQ-ACKs from the first unreported HARQ-ACK for which an associated DL assignment is detected. If the asynchronous HARQ-ACK CB size is larger than the number of HARQ-ACK bits to be reported, excess HARQ-ACK CB bits may be set to NACKs. Inserting NACKs may prevent an error if the UE has missed the last DL assignment for which the BS expects associated ACK / NACK. The UE and BS may determine the last HARQ-ACK to be reported based on the HARQ-ACK CB transmission time minus a predefined minimum time offset for HARQ-ACK CB and UL Tx preparation. Alternatively, the UE may insert the HARQ process number for the last reported HARQ-ACK, or the number of reported HARQ-ACKs or PDSCHs / DCIs for which HARQ-ACKs are reported, or number of excess NACKs inserted. If there are more HARQ-ACK bits to be reported than can be included in the CB, the UE may keep the excess HARQ-ACKs in the buffer, and report them in a later HARQ-ACK feedback instance. As an example, the UE may keep / buffer HARQ-ACK bits for a maximum time period, after which the UE may drop those bits. The most recent HARQ-ACK may be defined by any PDSCH not scheduled later than the PDCCH triggering the HARQ-ACK CB transmission. For SPS PDSCH, the supported minimum processing time may define the earliest time for the HARQ-ACK to be multiplex or the PDSCH-to-HARQ in the SPS activation DCI could be used to define the earliest time the SPS HARQ-ACK to be mapped to the new HARQ-ACK CB or a PDSCH transmitted before the DCI triggering the HARQ-ACK transmission. The UE may also insert the HARQ process number and / or cell ID / identifier for the first reported HARQ-ACK to the asynchronous HARQ-ACK CB.

[0081] In some example embodiments, the UE may be explicitly triggered to report HARQ-ACK feedback. The trigger may be included on a DL assignment and / or on a UL grant. In an alternative, the indicator may indicate to the UE at least one preconfigured HARQ-ACK CB size to be used.

[0082] In various example embodiments, the UE may be triggered to report HARQ-ACK in an aperiodic manner or semi-persistent (or even periodic) manner. For example, with aperiodic HARQ-ACK CB reporting, a corresponding time period / window may be configured or indicated, where the UE generates the asynchronous HARQ-ACK CB corresponding to this period or no later than this period. As another example, with semi-persistent (or even periodic) HARQ-ACK CB reporting, a corresponding time period / window may be specified, configured, or indicated, where the UE generates HARQ-ACK CB corresponding to this period or no later than this period. As an example, the time period may be the period between two (UL) reporting PUCCH / PUSCH occasions.

[0083] In certain example embodiments, the asynchronous HARQ-ACK CB may be transmitted as MAC CE. As an example, the UE may receive a trigger for asynchronous HARQ-ACK reporting, and multiplex HARQ-ACK CB as MAC CE into at least one MAC protocol data unit (MAC PDU). In another example, there is no trigger for HARQ-ACK reporting, but the UE may determine when it multiplexes HARQ-ACK CB as MAC CE into MAC PDU. The determination can be based on prioritization between different data available for multiplexing. Thus, the UE may use an alternative where the UE inserts to the CB the HARQ process number for the last reported HARQ-ACK, or the number of reported HARQ-ACKs or PDSCHs / DCIs for which HARQ-ACKs are reported, or number of excess NACKs inserted.

[0084] FIG. 5 illustrates an example of a signaling diagram 500 depicting techniques for HARQ-ACK CB design for CA. NE 550 (containing Cell#2520 and Cell#l 530) may be similar to NE 1110, and UE 540 may be similar to UE 1120, as illustrated in FIG. 11, according to certain example embodiments.

[0085] At operation 501, UE 540 may receive a configuration for HARQ-ACK CB cell groups. The configuration may contain also other parameters (e.g., the HARQ-ACK CB type for a HARQ-ACK CB cell group, an asynchronous (Type 2) HARQ-ACK CB size or a set of asynchronous (Type 2) HARQ-ACK CB sizes).

[0086] At operation 502, NE 550 may receive an indication e.g., scheduler) operating Cell#l that Cell#2 is activated for UE 540 and is used for data delivery.

[0087] At operation 503, NE 550 may transmit PDSCH scheduling DCIs and PDSCHs from Cell #1 530 and / or Cell #2 520 to UE 540. The DCIs may include DAI, wherein DCI DAIs may be incremented separately for Cell#l 530 and Cell#2520 if Cell#l 530 and Cell#2520 are associated with different HARQ-ACK CB groups. DCIs scheduling PDSCHs in Cell#l may include timing information for the regular Type 2 CB of Cell#l if Cell#l is associated with HARQ-ACK CB group containing the PUCCH cell.

[0088] At operation 504, based on received PDSCH scheduling DCIs (z.e., the received DL assignments) and the decoding outcome of the corresponding PDSCHs, UE 540 may determine and order the ACK / NACKs, which may be done separately for both cells associated with different HARQ-ACK CB groups.

[0089] At operation 505, serving Cell#l 530 may determine HARQ-ACK feedback timing and resource for asynchronous HARQ-ACK feedback. The determination of timing may be based on the past time from the previous asynchronous HARQ-ACK CB feedback and possibly on other issues (e.g., whether PDSCH or PUSCH will be scheduled for UE 540 for data transmission). The determination of resources may be based on the asynchronous (Type 2) HARQ-ACK CB size and whether PDSCH or PUSCH will be scheduled to UE 540. If a PDCCH scheduling PUSCH (z.e., UL grant) is to trigger the asynchronous HARQ-ACK feedback reporting, the asynchronous (Type 2) HARQ-ACK CB may be included on the PUSCH transmission and the PUSCH is selected as the resource. If a DL assignment of Cell#l 530 is to trigger the asynchronous HARQ-ACK feedback, UE 540 may be instructed to report a regular Type 2 HARQ-ACK CB for Cell #1 530 on a PUCCH resource, and the PUCCH resource is selected also for the asynchronous HARQ-ACK CB feedback transmission for Cell#2520.

[0090] At operation 506, based on the determination, Cell#l 530 may transmit to UE 540 a HARQ-ACK trigger for asynchronous (Type 2) HARQ-ACK feedback is transmitted on DO scheduling PDSCH or PUSCH. The trigger may also indicate asynchronous (Type 2) HARQ-ACK CB size from the set of configured CB sizes.

[0091] At operation 507, based on the predefined / indicated asynchronous (Type 2) HARQ-ACK CB size, UE 540 may select a corresponding sequence of ACK / NACKs from the ACK / NACKs ordered at operation 504 for the asynchronous HARQ-ACK feedback of Cell#2520, together with necessary HARQ process number(s) and cell identifiers. If there is also HARQ-ACK feedback for Cell#l 530 to be reported for the same HARQ-ACK reporting instance e.g., if the triggering is happening through a PDCCH scheduling PDSCH on Cell#l 530), UE 540 may append the asynchronous (Type 2) HARQ-ACK CB of Cell#2520 to the regular Type 2 HARQ-ACK CB for Cell#l 530 for HARQ-ACK feedback.

[0092] At operation 508, UE 540 may transmit to Cell#l 530 HARQ-ACK feedback on PUCCH or PUSCH.

[0093] At operation 509, Cell#l 530 may receive the HARQ-ACK feedback. The reliability of the decoding outcome of the reception may be determined, such as based on a CRC check.

[0094] At operation 510, Cell#l 530 may forward the asynchronous HARQ-ACK feedback of Cell#2520 to Cell #2520.

[0095] FIG. 6 illustrates an example of a signaling diagram 600 depicting techniques for HARQ-ACK CB design for a single cell case. NE 610 and UE 620 may be similar to NE 1110 and UE 1120, respectively, as illustrated in FIG. 11, according to certain example embodiments.

[0096] At operation 601, UE 620 may receive a configuration for HARQ-ACK CB type(s) (e.g., asynchronous (Type 2) HARQ-ACK CB). The configuration may contain also other parameters e.g., a set of asynchronous (Type 2) HARQ-ACK CB sizes).

[0097] At operation 602, NE 610 may transmit PDSCH scheduling DCIs and PDSCHs to UE 620. The DCIs may include DAI.

[0098] At operation 603, based on received PDSCH scheduling DCIs (z.e., the received DL assignments) and the decoding outcome of the corresponding PDSCHs, UE 620 may determine and order the ACK / NACKs.

[0099] At operation 604, NE 610 may determine HARQ-ACK feedback timing and resources for asynchronous HARQ-ACK feedback. The determination of timing may be based on a past time from the previous asynchronous HARQ-ACK CB feedback, among other factors e.g., whether PDSCH or PUSCH will be scheduled for UE 620 for data transmission). The determination of resources may be based on the asynchronous (Type 2) HARQ-ACK CB size and whether PDSCH or PUSCH will be scheduled to UE 620. If a PDCCH scheduling PUSCH (i.e., UL grant) is to trigger the asynchronous HARQ-ACK feedback reporting, the asynchronous (Type 2) HARQ-ACK CB may be included on the PUSCH transmission and the PUSCH may be selected as the resource. If a DL assignment is to trigger the asynchronous HARQ-ACK feedback, a PUCCH resource may be selected for the asynchronous HARQ-ACK CB feedback transmission.

[0100] At operation 605, based on the determination, NE 610 may transmit to UE 620 a HARQ-ACK trigger for asynchronous (Type 2) HARQ-ACK feedback on DCI scheduling PDSCH or PUSCH. The trigger may also indicate an asynchronous (Type 2) HARQ-ACK CB size from the set of configured asynchronous HARQ-ACK CB sizes.

[0101] At operation 606, based on the predefined / indicated asynchronous (Type 2) HARQ-ACK CB size, UE 620 may select a corresponding sequence of ACK / NACKs from the ACK / NACKs ordered at operation 603 for the asynchronous HARQ-ACK feedback, together with necessary HARQ process number(s) and cell identifiers.

[0102] At operation 607, UE 620 may transmit to NE 610 HARQ-ACK feedback on PUCCH or PUSCH.

[0103] At operation 608, NE 610 may receive the HARQ-ACK feedback transmitted by UE 620 at operation 607. The reliability of the decoding outcome of the reception may be determined, such as based on a CRC check.

[0104] FIG. 7 illustrates an example of a flow diagram of a method 700 that may be performed by a UE, such as UE 1120 illustrated in FIG. 11, according to various example embodiments.

[0105] At step 701, the method may include receiving at least one configuration.

[0106] At step 702, the method may further include receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a first cell and a second cell of a network entity.

[0107] At step 703, the method may further include, based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and non-acknowledgments (NACKs).

[0108] At step 704, the method may further include receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH).

[0109] At step 705, the method may further include based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback.

[0110] At step 706, the method may further include transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0111] In certain example embodiments, the at least one configuration may include a HARQ-ACK codebook (CB) cell group configuration.

[0112] In some example embodiments, the at least one of a HARQ process number and a cell identifier of a first ACK / NACK in the selected sequence of ACKs / NACKs may be transmitted with the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0113] In various example embodiments, the at least one configuration may include a configuration of a first HARQ-ACK CB cell group comprising the first cell with synchronous HARQ-ACK feedback, and a second HARQ-ACK CB cell group comprising the second cell with asynchronous HARQ-ACK feedback.

[0114] In certain example embodiments, the method may further include determining a size of the asynchronous HARQ-ACK feedback based on at least one of the HARQ-trigger and the at least one configuration.

[0115] In some example embodiments, each of the at least one PDSCH scheduling DCI may include a downlink assignment index (DAI) incremented separately for PDSCH from the first cell of the network entity and for PDSCH from the second cell of the network entity.

[0116] In various example embodiments, the sequence of ACKs / NACKs may be ordered based on the DAI.

[0117] In certain example embodiments, the DCI scheduling PDSCH associated with the first cell of the network entity may include timing information for the asynchronous HARQ-ACK feedback and the synchronous HARQ-ACK feedback.

[0118] FIG. 8 illustrates an example of a flow diagram of a method 800 that may be performed by a NE, such as NE 1110 illustrated in FIG. 11, according to various example embodiments.

[0119] At step 801, the method may include transmitting at least one configuration.

[0120] At step 802, the method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH on a first cell and on a second cell of the apparatus.

[0121] At step 803, the method may further include transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH).

[0122] At step 804, the method may further include receiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0123] In certain example embodiments, the at least one configuration may include a HARQ-ACK codebook (CB) cell group configuration.

[0124] In some example embodiments, at least one of a HARQ process number and a cell identifier of a first ACK7NACK in the selected sequence of ACKs / NACKs may be transmitted with the asynchronous HARQ-ACK feedback on the first cell.

[0125] In various example embodiments, the at least one HARQ-ACK CB cell group configuration may indicate a synchronous HARQ-ACK feedback CB size or at least one asynchronous HARQ-ACK feedback CB size.

[0126] In certain example embodiments, the at least one configuration may include a configuration of a first HARQ-ACK CB cell group comprising the first cell with synchronous HARQ-ACK feedback, and a second HARQ-ACK CB cell group comprising the second cell with asynchronous HARQ-ACK feedback.

[0127] In some example embodiments, each of the at least one PDSCH scheduling DCI may include a downlink assignment index (DAI) incremented separately for PDSCH from the first cell of the apparatus and for PDSCH from the second cell.

[0128] In various example embodiments, the sequence of ACKs / NACKs may be ordered based on the DAI.

[0129] In certain example embodiments, the DCI scheduling PDSCH associated with the first cell of the apparatus may include timing information for the asynchronous HARQ-ACK feedback and the synchronous HARQ-ACK feedback.

[0130] In some example embodiments, the method may further include receiving asynchronous HARQ-ACK feedback.

[0131] FIG. 9 illustrates an example of a flow diagram of a method 900 that may be performed by a UE, such as UE 1120 illustrated in FIG. 11, according to various example embodiments.

[0132] At step 901, the method may include receiving at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback.

[0133] At step 902, the method may further include receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a network entity.

[0134] At step 903, the method may further include, based on received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determine at least one acknowledgement (ACK) and non-acknowledgement (NACK).

[0135] At step 904, the method may further include receiving a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH).

[0136] At step 905, the method may further include, based upon the HARQ-trigger, selecting an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or PUSCH.

[0137] At step 906, the method may further include transmitting a HARQ-ACK feedback to the network entity.

[0138] In some example embodiments, the method may further include determining a size of the asynchronous HARQ-ACK feedback based on at least one of the HARQ-trigger and the at least one configuration.

[0139] In various example embodiments, the last ACK7NACK in the selected sequence may be determined based on at least one of the size of asynchronous HARQ-ACK feedback, timing of the HARQ-ACK feedback transmission, and timing of the HARQ-trigger reception.

[0140] In certain example embodiments, a HARQ process number of a first ACK7NACK in the selected sequence of ACKs / NACKs may be transmitted with the HARQ-ACK feedback to the network entity.

[0141] In some example embodiments, the sequence of ACKs / NACKs may be ordered based on the downlink assignment index (DAI).

[0142] FIG. 10 illustrates an example of a flow diagram of a method 1000 that may be performed by a NE, such as NE 1110 illustrated in FIG. 11, according to various example embodiments.

[0143] At step 1001, the method may include transmitting at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback.

[0144] At step 1002, the method may further include transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH.

[0145] At step 1003, the method may further include transmitting a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH)

[0146] At step 1004, the method may further include receiving a HARQ-ACK feedback.

[0147] In certain example embodiments, the method may further include determining a size of the asynchronous HARQ-ACK feedback based on at least one of the HARQ-trigger and the at least one configuration.

[0148] In some example embodiments, the at least one HARQ-ACK feedback configuration indicates at least one asynchronous HARQ-ACK feedback CB size.

[0149] In various example embodiments, the last ACK7NACK in the selected sequence may be determined based on at least one of the size of asynchronous HARQ-ACK feedback, timing of the HARQ-ACK feedback transmission, and timing of the HARQ-trigger reception.

[0150] In certain example embodiments, a HARQ process number of a first ACK7NACK in the selected sequence of ACKs / NACKs may be transmitted with the HARQ-ACK feedback.

[0151] In some example embodiments, the sequence of ACKs / NACKs may be ordered based on the downlink assignment index (DAI).

[0152] FIG. 11 illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE 1110 and / or UE 1120.

[0153] NE 1110 may be one or more of a base station (e.g., 3G UMTS NodeB, 4G LTE Evolved NodeB, 5G NR Next Generation NodeB, 6G gNB, 6G gNE, 5G-6G MRSS), a serving gateway, a server, and / or any other access node or combination thereof.

[0154] NE 1110 may further include at least one gNB -centralized unit (CU), which may be associated with at least one gNB -distributed unit (DU). The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one Fl interface, at least one Xn-C interface, and / or at least one NG interface via a 5thgeneration core (5GC).

[0155] UE 1120 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.Furthermore, NE 1110 and / or UE 1120 may be one or more of a citizens broadband radio service device (CBSD).

[0156] NE 1110 and / or UE 1120 may include at least one processor, respectively indicated as 1111 and 1121. Processors 1111 and 1121 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

[0157] At least one memory may be provided in one or more of the devices, as indicated at 1112 and 1122. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories 1112 and 1122 may independently be any suitable storage device, such as a non-transitory computer-readable medium. The term “non-transitory,” as used herein, may correspond to a limitation of the medium itself (z.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., random access memory (RAM) vs. read-only memory (ROM)). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0158] Processors 1111 and 1121, memories 1112 and 1122, and any subset thereof, may be configured to provide means corresponding to the various blocks of FIGs. 1-14. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.

[0159] As shown in FIG. 11 , transceivers 1113 and 1123 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 1114 and 1124. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers 1113 and 1123 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

[0160] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (z.e., FIGs. 1-14). Therefore, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be performed entirely in hardware.

[0161] In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGs. 1-14. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry), (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0162] FIG. 12 illustrates an example of a 5G / 6G network and system architecture according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE illustrated in FIG. 12 may be similar to NE 1110 and UE 1120, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of DL packets, and / or triggering of DL data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

[0163] FIG. 9 illustrates an example of a proposed 6G architecture, which may support life cycle management (LCM) configured to natively support AI / ML, cloud-native functionalities. 6G gNBs may also be configured to support multi-RAT spectrum sharing (MRSS).

[0164] FIG. 10 illustrates an example of a proposed 6G RAN protocol stack, which may share some similarities with a 5G RAN protocol stack. For example, the depicted 6G RAN protocol stack may incorporate service data application protocol (SDAP), packet data convergence protocol (PDCP), RLC, and medium access control (MAC) functions, which may interface with multiple radio protocol units (RPUs).

[0165] According to certain example embodiments, processors 1111 and 1121, and memories 1112 and 1122, may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 1113 and 1123 may be included in or may form a part of transceiving circuitry.

[0166] In some example embodiments, an apparatus (e.g., NE 1110 and / or UE 1120) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0167] In various example embodiments, apparatus 1110 may be controlled by memory 1112 and processor 1111 to receive at least one configuration; receive at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a first cell and a second cell of a network entity; based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determine acknowledgments (ACKs) and non-acknowledgments (NACKs); receive, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH); based upon the asynchronous HARQ-trigger, select a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback; and transmit the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0168] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving at least one configuration; means for receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a first cell and a second cell of a network entity; means for, based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and non-acknowledgments (NACKs); means for receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH); means for, based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as anasynchronous HARQ-ACK feedback; and means for transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

[0169] In various example embodiments, apparatus 1110 may be controlled by memory 1112 and processor 1111 to transmit at least one configuration; transmit at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH on a first cell and on a second cell of the apparatus; transmit an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH); and receive the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0170] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting at least one configuration; means for transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH on a first cell and on a second cell of the apparatus; means for transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH); and means for receiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

[0171] In various example embodiments, apparatus 1110 may be controlled by memory 1112 and processor 1111 to receive at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback; receive at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a network entity; based on received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determine at least one acknowledgement (ACK) and nonacknowledgement (NACK); receive a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH); based upon the HARQ-trigger, select an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or PUSCH; and transmit a HARQ-ACK feedback to the network entity.

[0172] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback; means for receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH from a network entity; means for, based on received PDSCH scheduling DCI and a decoding outcome of thecorresponding at least one PDSCH, determining at least one acknowledgement (ACK) and nonacknowledgement (NACK); means for receiving a HARQ-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH); means for, based upon the HARQ-trigger, selecting an asynchronous HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or PUSCH; and means for transmitting a HARQ-ACK feedback to the network entity.

[0173] In various example embodiments, apparatus 1110 may be controlled by memory 1112 and processor 1111 to transmit at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback; transmit at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH; transmit a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH); receive a HARQ-ACK feedback.

[0174] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting at least one configuration of a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback, wherein the at least one configuration comprises configuration of an asynchronous HARQ-ACK feedback; means for transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH; means for transmitting a HARQ-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH); means for receiving a HARQ-ACK feedback.

[0175] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “various embodiments,” “certain embodiments,” “some embodiments,” or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases “in various embodiments,” “in certain embodiments,” “in some embodiments,” or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0176] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0177] Additionally, if desired, the different functions or procedures discussed above may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0178] One having ordinary skill in the art will readily understand that the example embodiments discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the example embodiments.

[0179] Partial Glossary

[0180] 3GPP 3rdGeneration Partnership Project

[0181] 5G 5thGeneration

[0182] 5GC 5thGeneration Core

[0183] 6G 6thGeneration

[0184] ACK Acknowledgement

[0185] AF Application Function

[0186] Al Artificial Intelligence

[0187] ASIC Application Specific Integrated Circuit

[0188] BS Base Station

[0189] CA Carrier Aggregation

[0190] CB Codebook

[0191] CBSD Citizens Broadband Radio Service Device

[0192] CE Control Element

[0193] CPU Central Processing Unit

[0194] CSI Channel State Information

[0195] CU Centralized Unit

[0196] DAI Downlink Assignment Index

[0197] DC Dual Connectivity

[0198] DL Downlink

[0199] DU Distributed Unit

[0200] eMBB Enhanced Mobile Broadband

[0201] eNB Evolved Node B

[0202] FWA Fixed Wireless Access

[0203] gNB Next Generation Node B

[0204] GPS Global Positioning System

[0205] HARQ Hybrid Automatic Repeat Request

[0206] HDD Hard Disk Drive

[0207] loT Internet of Things

[0208] LI Layer 1

[0209] LCM Life Cycle Management

[0210] LTE Long-Term Evolution

[0211] LTE- A Long-Term Evolution Advanced

[0212] MAC Medium Access Control

[0213] MBB Mobile Broadband

[0214] MCG Master Cell Group

[0215] MEMS Micro Electrical Mechanical System

[0216] MIMO Multiple Input Multiple Output

[0217] ML Machine Learning

[0218] mMTC Massive Machine Type Communication

[0219] MRSS Multi-RAT Spectrum Sharing

[0220] MSG Master Cell Group

[0221] NACK Non- Acknowledgement

[0222] NE Network Entity

[0223] NG Next Generation

[0224] NG-eNB Next Generation Evolved Node B

[0225] NG-RAN Next Generation Radio Access Network

[0226] NR New Radio

[0227] PDA Personal Digital Assistance

[0228] PDCCH Physical Downlink Control Channel

[0229] PDCP Packet Data Convergence Protocol

[0230] PDSCH Physical Downlink Shared Channel

[0231] PRI PUCCH Resource Indicator

[0232] PUCCH Physical Uplink Control Channel

[0233] PUSCH Physical Uplink Shared Channel

[0234] QoS Quality of Service

[0235] RAM Random Access Memory

[0236] RAN Radio Access Network

[0237] RAT Radio Access Technology

[0238] RF Radio Frequency

[0239] RLC Radio Link Control

[0240] ROM Read-Only Memory

[0241] RPU Radio Protocol Unit

[0242] RRC Radio Resource Control

[0243] SCG Secondary Cell Group

[0244] SDAP Service Data Application Protocol

[0245] SPS Semi-Persistent Scheduling

[0246] SR Scheduling Report

[0247] TRP Transmission Reception Point

[0248] Tx Transmission

[0249] UCI Uplink Control Information

[0250] UE User Equipment

[0251] UL Uplink

[0252] UPF User Plane Function

Claims

1. WE CLAIM:

1. An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive at least one configuration;receive at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a first cell and a second cell of a network entity;based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determine acknowledgments (ACKs) and non-acknowledgments (NACKs);receive, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH);based upon the asynchronous HARQ-trigger, select a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback; and transmit the asynchronous HARQ-ACK feedback to the first cell of the network entity.

2. The apparatus of claim 1, wherein the at least one configuration comprises a HARQ-ACK codebook (CB) cell group configuration.

3. The apparatus of claim 1, wherein at least one of a HARQ process number and a cell identifier of a first ACK / NACK in the selected sequence of ACKs / NACKs is transmitted with the asynchronous HARQ-ACK feedback to the first cell of the network entity.

4. The apparatus of claim 1, wherein the at least one configuration comprises a configuration of a first HARQ-ACK CB cell group comprising the first cell with synchronous HARQ-ACK feedback, and a second HARQ-ACK CB cell group comprising the second cell with asynchronous HARQ-ACK feedback.

5. The apparatus of claim 4, wherein the at least one memory storing the instructions, when executed by the at least one processor, further cause the apparatus at least to:determine a size of the asynchronous HARQ-ACK feedback based on at least one of the HARQ-trigger and the at least one configuration.

6. The apparatus of claim 1, wherein each of the at least one PDSCH scheduling DO comprises a downlink assignment index (DAI) incremented separately for PDSCH from the first cell of the network entity and for PDSCH from the second cell of the network entity.

7. The apparatus of claim 1, wherein the sequence of ACKs / NACKs is ordered based on the DAI.

8. The apparatus of claim 3, wherein the DO scheduling PDSCH associated with the first cell of the network entity comprise timing information for the asynchronous HARQ-ACK feedback and the synchronous HARQ-ACK feedback.

9. An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:transmit at least one configuration;transmit at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH on a first cell and on a second cell of the apparatus; transmit an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH); and receive the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

10. The apparatus of claim 9, wherein the at least one configuration comprises a HARQ-ACK codebook (CB) cell group configuration.

11. The apparatus of claim 9, wherein at least one of a HARQ process number and a cell identifier of a first ACK7NACK in the selected sequence of ACKs / NACKs is transmitted with the asynchronous HARQ-ACK feedback on the first cell.

12. The apparatus of claim 9, wherein the at least one HARQ-ACK CB cell group configuration indicates a synchronous HARQ-ACK feedback CB size or at least one asynchronous HARQ-ACK feedback CB size.

13. The apparatus of claim 9, wherein the at least one configuration comprises a configuration of a first HARQ-ACK CB cell group comprising the first cell with synchronous HARQ-ACK feedback, and a second HARQ-ACK CB cell group comprising the second cell withasynchronous HARQ-ACK feedback.

14. The apparatus of claim 9, wherein each of the at least one PDSCH scheduling DO comprises a downlink assignment index (DAI) incremented separately for PDSCH from the first cell of the apparatus and for PDSCH from the second cell.

15. The apparatus of claim 9, wherein the sequence of ACKs / NACKs is ordered based on the DAI.

16. The apparatus of claim 9, wherein the DO scheduling PDSCH associated with the first cell of the apparatus comprise timing information for the asynchronous HARQ-ACK feedback and the synchronous HARQ-ACK feedback.

17. The apparatus of claim 9, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to:receive asynchronous HARQ-ACK feedback.

18. A method comprising:receiving at least one configuration;receiving at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DO) and at least one PDSCH from a first cell and a second cell of a network entity;based on the received PDSCH scheduling DCI and a decoding outcome of the corresponding at least one PDSCH, determining acknowledgments (ACKs) and non-acknowledgments (NACKs);receiving, from the first cell of the network entity, an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DCI scheduling PDSCH or physical uplink shared channel (PUSCH);based upon the asynchronous HARQ-trigger, selecting a corresponding sequence of ACKs / NACKs from the determined ACKs / NACKs as an asynchronous HARQ-ACK feedback; and transmitting the asynchronous HARQ-ACK feedback to the first cell of the network entity.

19. A method comprising:transmitting at least one configuration;transmitting at least one physical downlink shared channel (PDSCH) scheduling downlink control information (DCI) and at least one PDSCH on a first cell and on a second cell of the apparatus;transmitting an asynchronous hybrid automatic repeat request (HARQ)-trigger for asynchronous HARQ-ACK feedback on DO scheduling PDSCH or physical uplink shared channel (PUSCH); andreceiving the asynchronous HARQ-ACK feedback on the first cell of the apparatus.

Images