Method and User Equipment for HARQ-ACK Codebook

Abstract

A method for a Hybrid Automatic Repeat reQuest - ACKnowledgment (HARQ - ACK) codebook performed by a User Equipment (UE), comprising receiving a Radio Resource Control (RRC) message from a Network (NW), the RRC message including an indication indicating to the UE whether to disable HARQ feedback for a HARQ process; if the indication of the RRC message indicates to the UE to disable HARQ feedback for the HARQ process, not generating HARQ - ACK bits corresponding to a first Transport Block (TB) and generating at least one HARQ - ACK bit corresponding to at least one second TB; and if a Downlink Control Information (DCI) format from the NW indicates to the UE to feedback the reception of the first TB and at least one second TB in the same time slot, multiplexing at least one HARQ - ACK bit to construct a HARQ - ACK codebook for the first TB and at least one second TB.

Description

[0001] Cross - reference to related applications

[0002] This application is the national phase of International Patent Application No. PCT / CN2021 / 091064, filed on April 29, 2021 under 35 U.S.C. § 371, which claims the benefit and priority of the provisional U.S. patent application Ser. No. 63 / 018,469, entitled "TYPE - 2 HARQ - ACK CODEBOOK WITH BWP SWITCH IN NTN", filed on April 30, 2020. For all purposes, the contents of all the above - mentioned applications are hereby incorporated by reference in their entirety into this disclosure. Technical field

[0003] The present disclosure generally relates to wireless communication, and particularly to a method and a user equipment for constructing a Hybrid - Automatic - Repeat - Request Acknowledge (HARQ - ACK) codebook. Background art

[0004] With the huge growth in the number of connected devices and the rapid increase in user / network (NW) traffic, various efforts have been made to improve different aspects of wireless communication in next - generation wireless communication systems (such as the fifth - generation (5G) New Radio (NR) system) by increasing data rate, latency, reliability, and mobility.

[0005] The 5G NR system is designed to provide flexibility and configurability to optimize NW services and types to adapt to different usage scenarios, such as enhanced Mobile Broadband (eMBB), massive Machine - Type Communication (mMTC), and Ultra - Reliable and Low - Latency Communication (URLLC).

[0006] However, as the demand for radio access continues to increase, there is a need in the art to improve the generation / construction of Hybrid - Automatic - Repeat - Request Acknowledge (HARQ - ACK) codebooks. Summary of the invention

[0007] The present disclosure relates to a method and a user equipment (UE) for constructing a Hybrid - Automatic - Repeat - Request Acknowledge (HARQ - ACK) codebook.

[0008] According to one aspect of the present disclosure, there is provided a method for constructing a Hybrid Automatic Repeat reQuest - ACK (HARQ - ACK) codebook performed by a User Equipment (UE). The method includes: receiving a Radio Resource Control (RRC) message from a network (NW), the RRC message including an indication indicating whether to disable HARQ feedback for a HARQ process for the UE; if the indication of the RRC message indicates to the UE to disable the HARQ feedback for the HARQ process, not generating HARQ - ACK bits corresponding to a first Transport Block (TB), but generating at least one HARQ - ACK bit corresponding to at least one second TB; and if a Downlink Control Information (DCI) format from the NW indicates to the UE to feedback the reception of the first TB and the at least one second TB in the same time slot, multiplexing the at least one HARQ - ACK bit to construct the HARQ - ACK codebook for the first TB and the at least one second TB.

[0009] According to another aspect of the present disclosure, there is provided a User Equipment (UE) for a Hybrid Automatic Repeat reQuest - ACK (HARQ - ACK) codebook in a wireless communication system. The UE includes: a processor; and a memory coupled to the processor, wherein the memory stores a computer - executable program, and when the computer - executable program is executed by the processor, causes the processor to: receive a Radio Resource Control (RRC) message from a network (NW), the RRC message including an indication indicating whether to disable HARQ feedback for a HARQ process for the UE; if the indication of the RRC message indicates to the UE to disable the HARQ feedback for the HARQ process, not generating HARQ - ACK bits corresponding to a first Transport Block (TB), but generating at least one HARQ - ACK bit corresponding to at least one second TB; and if a Downlink Control Information (DCI) format from the NW indicates to the UE to feedback the reception of the first TB and the at least one second TB in the same time slot, multiplexing the at least one HARQ - ACK bit to construct the HARQ - ACK codebook for the first TB and the at least one second TB. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Aspects of the present disclosure are best understood from the following when read in conjunction with the accompanying drawings. The various features are not drawn to scale. For clarity of discussion, the dimensions of the various features may be arbitrarily increased or decreased.

[0011] Figure 1 is a system diagram showing an overview of a Non - Terrestrial Network (NTN) network according to an exemplary embodiment of the present disclosure.

[0012] Figure 2is a time / frequency diagram showing a scenario of configuring three different bandwidth parts (BWPs) according to an exemplary embodiment of the present disclosure.

[0013] Figure 3 is a timing diagram showing the reception of a physical downlink shared channel (PDSCH) with an active downlink (DL) BWP change via DCI format according to an exemplary embodiment of the present disclosure.

[0014] Figure 4 is a timing diagram showing the reception of a semi-persistent scheduling (SPS) PDSCH with an active DL BWP change via DCI format according to an embodiment of the present disclosure.

[0015] Figure 5 is a diagram showing a type 2 HARQ-ACK codebook with more than T D = 4 lost DCI formats according to an embodiment of the present disclosure.

[0016] Figure 6 is a flowchart showing a process for HARQ-ACK codebook construction performed by a UE according to an embodiment of the present disclosure.

[0017] Figure 7 is a block diagram showing a node for wireless communication according to an embodiment of the present disclosure. Detailed Description

[0018] At least a part of the acronyms in the present disclosure are defined as follows. Unless otherwise specified, the acronyms in the present disclosure have the following meanings.

[0019] Acronym Full Name

[0020] 3GPP Third Generation Partnership Project

[0021] BS Base Station

[0022] BWP Bandwidth Part

[0023] CBG Code Block Group

[0024] C-RNTI Cell Radio Network Temporary Identifier

[0025] CSI Channel State Information

[0026] DAI Downlink Allocation Indicator

[0027] DCI Downlink Control Information

[0028] DL Downlink

[0029] DL-SCH Downlink Shared Channel

[0030] EFB Earth Fixed Beam

[0031] EMB Earth Mobile Beam

[0032] FDD Frequency Division Duplexing

[0033] gNB gNodeB

[0034] GNSS Global Navigation Satellite System

[0035] HO Handover

[0036] HARQ Hybrid Automatic Repeat reQuest

[0037] ID Identification

[0038] LEO Low Earth Orbit

[0039] LTE Long Term Evolution

[0040] MAC Media Access Control

[0041] MSGB-RNTI Message B Radio Network Temporary Identifier

[0042] MCG Master Cell Group

[0043] NACK / ACK Negative Acknowledgment / Acknowledgment

[0044] NR New Radio

[0045] NTN Non-Terrestrial Network

[0046] NW Network

[0047] OFDM Orthogonal Frequency Division Multiplexing

[0048] PCell Primary Cell

[0049] PDCCH Physical Downlink Control Channel

[0050] PDSCH Physical Downlink Shared Channel

[0051] PRB Physical Resource Block

[0052] PUCCH Physical Uplink Control Channel

[0053] PUSCH Physical Uplink Shared Channel

[0054] RA Random Access

[0055] RACH Random Access Channel

[0056] RAN Radio Access Network Rel Release

[0057] RNTI Radio Network Temporary Identifier

[0058] RRC Radio Resource Control

[0059] SCell Secondary Cell

[0060] SCG Secondary Cell Group

[0061] SpCell Specific Cell

[0062] SPS Semi-Persistent Scheduling

[0063] SRS Sounding Reference Signal

[0064] SUL Supplementary Uplink

[0065] TA Timing Advance

[0066] TB Transport Block

[0067] T-CRNTI Temporary Cell Radio Network Temporary Identifier

[0068] TDD Time Division Duplex

[0069] TRP Transmission / Reception Point

[0070] TR Technical Report

[0071] TS Technical Specification

[0072] UE User Equipment

[0073] UL Uplink

[0074] UL-SCH Uplink Shared Channel

[0075] WI Work Item

[0076] The following contains specific information related to the embodiments in the present disclosure. The accompanying drawings and the detailed disclosure thereof in the present disclosure are only for exemplary embodiments. However, the present disclosure is not limited to these exemplary embodiments. Other variations and embodiments of the present disclosure will occur to those skilled in the art. Unless otherwise specified, the same or corresponding elements in the drawings may be represented by the same or corresponding reference numerals. Moreover, the drawings and diagrams in the present disclosure are generally not drawn to scale and are not intended to correspond to actual relative sizes.

[0077] For the purposes of consistency and ease of understanding, similar features are identified by reference numerals in the exemplary drawings (but not shown in some examples). However, the features in different embodiments may differ in other respects and should not be narrowly limited to what is shown in the drawings.

[0078] References to "one embodiment", "an embodiment", "exemplary embodiments", "various embodiments", "some embodiments", "embodiments of the present disclosure", etc. may indicate that the embodiments of the present disclosure so described may include a particular feature, structure, or characteristic, but not every possible embodiment of the present disclosure necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase "in one embodiment", "in an exemplary embodiment", or "an embodiment" does not necessarily refer to the same embodiment, although they may. Additionally, any phrase used in conjunction with "the present disclosure" like "an embodiment" is not intended to represent that all embodiments of the present disclosure must include a particular feature, structure, or characteristic, but rather should be understood to mean that "at least some embodiments of the present disclosure" include the stated particular feature, structure, or characteristic.

[0079] The term "coupled" is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term "comprising", when utilized, means "comprising but not necessarily limited to"; it specifically denotes an open inclusion or membership in the combinations, groups, series, and equivalents so described.

[0080] The term "and / or" is only for describing the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, or B exists alone. "A and / or B and / or C" may represent the existence of at least one of A, B, and C. Additionally, the character " / " generally indicates that the previous associated object and the subsequent associated object are in an "or" relationship.

[0081] In addition, for the purpose of non-limiting interpretation, specific details such as functional entities, technologies, protocols, standards, etc. are elaborated to provide an understanding of the described technology. In other examples, detailed descriptions of well-known methods, technologies, systems, architectures, etc. are omitted to avoid obscuring the present disclosure with unnecessary details.

[0082] Those skilled in the art will immediately recognize that any NW function or algorithm of the present disclosure can be implemented by hardware, software, or a combination of software and hardware. The described functions may correspond to modules, which can be software, hardware, firmware, or any combination thereof. Software embodiments may include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device.

[0083] For example, one or more microprocessors or general-purpose computers with communication processing capabilities can be programmed with corresponding executable instructions and execute the described NW functions or algorithms. These microprocessors or general-purpose computers can be formed by application specific integrated circuitry (ASIC), programmable logic arrays, and / or using one or more digital signal processors (DSP). Although several exemplary embodiments described in this disclosure are directed to software installed and executed on computer hardware, alternative exemplary embodiments implemented as firmware, hardware, or a combination of hardware and software are also within the scope of this disclosure.

[0084] Computer-readable media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), cassette tapes, magnetic tapes, disk memories, or any other equivalent medium capable of storing computer-readable instructions.

[0085] A radio communication NW architecture (e.g., an LTE system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system) generally includes at least one BS, at least one UE, and one or more optional NW elements providing a connection to the NW. The UE communicates with the NW (e.g., a core network (CN), an evolved packet core (EPC) NW, an evolved universal terrestrial radio access NW (E-UTRAN), a next-generation core (NGC), a 5G core network (5GC), or the Internet) through a RAN established by the BS.

[0086] It should be noted that in the present disclosure, the UE may include, but is not limited to, a mobile station, a mobile terminal or device, a user communication radio terminal. For example, the UE may be a portable radio device, which includes, but is not limited to, a mobile phone with wireless communication capabilities, a tablet computer, a wearable device, a sensor, or a personal digital assistant (PDA). The UE is configured to receive signals via an air interface and transmit signals to one or more cells in the RAN.

[0087] The BS may include, but is not limited to, a Node B (NB) in a Universal Mobile Telecommunication System (UMTS), an evolved Node B (eNB) in LTE-A, a Radio Network Controller (RNC) in UMTS, a Base Station Controller (BSC) in a Global System for Mobile communication (GSM) / GSM EDGE Radio Access Network (GERAN), a next-generation eNB (ng-eNB) in an E-UTRA BS connected to 5GC, a gNB in a 5G Access Network (5G-AN), and any other device capable of controlling radio communication and managing radio resources within a cell. The BS may be connected to the NW via a radio interface to serve one or more UEs.

[0088] The BS may be configured to provide communication services according to at least one of the following Radio Access Technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (commonly known as 2G), GERAN, General Packet Radio Service (GPRS), UMTS based on Wideband-Code Division Multiple Access (W-CDMA) (commonly known as 3G), High-Speed Packet Access (HSPA), LTE, LTE-A, evolved LTE (eLTE), New Radio (NR, commonly known as 5G), and / or LTE-A Pro. However, the scope of the present disclosure should not be limited to the previously disclosed protocols.

[0089] The BS is operable to provide radio coverage to a specific geographical area using multiple cells included in the RAN. The BS can support the operation of the cells. Each cell is operable to provide service to at least one UE within its radio coverage. More specifically, each cell (commonly referred to as a serving cell) can provide service to serve one or more UEs within its radio coverage (e.g., each cell schedules DL and optional UL resources to at least one UE within its radio coverage for downlink and optional uplink packet transmissions). The BS can communicate with one or more UEs in the radio communication system via multiple cells. The cells can allocate sidelink (SL) resources to support ProSe (Proximity service). Each cell can have a coverage area that overlaps with other cells.

[0090] In the case of multi-RAT dual connectivity (MR-DC), the primary cell of the MCG or SCG can be referred to as a special cell (SpCell). The PCell can refer to the SpCell of the MCG. The PSCell can refer to the SpCell of the SCG. The MCG refers to a serving cell group associated with a master node (MN: Master Node), including the SpCell and optionally one or more Scells. The SCG refers to a serving cell group associated with a secondary node (SN: Secondary Node), including the SpCell and optionally one or more Scells.

[0091] In some embodiments, the UE may not have an (LTE / NR) RRC connection to the serving cell of interest for the associated service. In other words, the UE may not have UE-specific RRC signaling exchanged with the serving cell. Instead, the UE may only listen for DL synchronization signals (e.g., DL synchronization burst sets) and / or broadcast system information (SI: SystemInformation) related to the service of interest from such a serving cell. Additionally, the UE may have at least one serving cell on one or more target SL frequency carriers for the associated service. In some other embodiments, the UE may consider the RAN that configures one or more serving cells as the serving RAN.

[0092] As previously disclosed, the frame structure for NR supports flexible configuration to accommodate various next-generation (e.g., 5G) communication requirements, such as eMBB, mMTC, and URLLC, while meeting high-reliability, high-data-rate, and low-latency requirements. The OFDM technology disclosed in 3GPP can be used as the baseline for the NR waveform. Scalable OFDM parameter sets can also be used, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP). In addition, two coding schemes are considered for NR: (1) low-density parity-check (LDPC) codes and (2) polar codes. The coding scheme adaptation can be configured based on the channel condition and / or service application.

[0093] It is also considered that within the transmission time interval of a single NR frame, it should at least include DL transmission data, a guard period, and UL transmission data. Each part of the DL transmission data, the guard period, and the UL transmission data should also be configurable, for example, based on the NW dynamics of NR. Additionally, SL resources can also be provided in the NR frame to support ProSe services.

[0094] Please refer to Figure 1 , which is a system diagram showing an overview of NTN according to an exemplary embodiment of the present disclosure. As Figure 1 shown, a LEO satellite with a transparent payload in a 600-kilometer (km) orbit is proposed to demonstrate the relationship between the gNB, the satellite, and the UE and the satellite beam providing DL transmission. In some embodiments, NTN can refer to a NW or a segment of a NW that uses a spaceborne vehicle (e.g., using a LEO satellite) for transmission. In the 3GPP Release 17 (Rel-17) NTN WI, a LEO NW based on a transparent payload is preferred, and this NW addresses at least 3GPP Category 3 UEs that have GNSS capabilities and have EFB and EMB coverage. The following are more definitions:

[0095] · LEO NW based on transparent payload: It can refer to a relay-based NTN. In this embodiment, the LEO satellite only performs amplification and forwarding in space, while the gNB is located on the ground connected to the core NW. An orbit of 600 km is considered in the WI.

[0096] · 3GPP Category 3 UE: It can refer to Power Class UE 3. This definition is used to set the UL transmission (TX) power level to 23 decibel-milliwatts (dBm) + / - 2 dB. This setting is mainly to ensure backward compatibility with existing technologies (e.g., Rel-15 NR / GSM / UMTS), so that the NW deployment topology remains similar.

[0097] · GNSS: A standard general term that can refer to satellite navigation systems providing autonomous geospatial positioning with global coverage. This term includes, for example, the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), Galileo, Beidou, and other regional systems.

[0098] · EMB: Can refer to the coverage of a satellite beam on the Earth moving with the satellite. As the satellite rotates, different beams serve cells on the ground.

[0099] · EFB: Can refer to the coverage of a satellite beam on the Earth being fixed for a long time. During satellite movement, the antenna angle of each beam can be adjusted to provide service to a fixed area on the Earth for a long time. The main difference from the EMB case is that the round-trip time (RTT) of the statistical device varies with the elevation angle of the beam, and each cell / area has a maximum RTT with the minimum or maximum elevation angle.

[0100] In addition, the following definitions can be used to further elaborate on the terms, examples, embodiments, implementations, actions, behaviors, alternatives, aspects, or claims in this disclosure.

[0101] Timing Advance (TA)

[0102] In some implementations, TA refers to the timing offset between the UL frame and the DL frame. The UL frame can be transmitted in advance based on the TA value indicated by the NW. This is used to ensure that UL signals from different UEs are received in a timely manner at the NW side without interfering with each other. A typical TA value is set to twice the propagation delay. This value is crucial because the NW needs this information to:

[0103] · Perform UL time scheduling, e.g., UL grant and UL slot offset;

[0104] · Ensure layer 1 (L1) synchronization, e.g., the timing advance group (TAG) specific timer defined in Rel-15 NR; and

[0105] · Enhance mobility, e.g., the SMTC (Synchronization Signal Block (SSB) measurement time configuration) measurement gap and conditional HO.

[0106] In NTN, due to the large propagation delay, the UE may apply a larger TA value. As a result, a larger scheduling offset between its DL frame timing and UL frame timing may be required.

[0107] PUCCH Power Control

[0108] In NR, Type 2 HARQ-ACK codebooks are used for the UE to report HARQ-ACK information bits, which are used for PDSCH reception with DCI format scheduling, SPS PDSCH release / deactivation with DCI format scheduling, SPS PDSCH retransmission with DCI format scheduling, and / or SPS PDSCH reception without DCI format scheduling.

[0109] The UL slot for the UE to transmit the HARQ-ACK codebook is indicated by K0 and K1 in the DCI format, where K0 is the slot offset for PDSCH reception provided by the time domain resource allocation field in the DCI format, and K1 is the slot offset for PUCCH transmission with the HARQ-ACK codebook provided by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format.

[0110] The HARQ-ACK codebook size is determined by the following scenarios / conditions:

[0111] · PDCCH monitoring occasion set: Based on the UL transmission slot indicated by K0 and K1, this set has a total of M PDCCH monitoring occasions in the serving cell. Alternatively, the PDCCH monitoring occasion set spans active serving cells, first indexed by cell index, and then by the start time of the search space set.

[0112] · Value of counter DAI: This value is provided by DCI format 1_0 or 1_1. The counter DAI (cDAI) represents the cumulative number of PDSCH receptions or SPS PDSCH releases / deactivations associated with the DCI format up to the current PDCCH monitoring occasion.

[0113] · Value of total DAI (TDAI): This value is provided by DCI format 1_1. tDAI represents the total number of PDSCH receptions or SPS PDSCH releases / deactivations associated with the DCI format up to the current PDCCH monitoring occasion.

[0114] · Based on SPS PDSCH configuration: If an SPS PDSCH configuration is provided, an additional HARQ-ACK bit is added at the end of the codebook. If a single SPS PDSCH configuration in the cell group is provided to the UE, the UE does not expect to be instructed to transmit HARQ-ACK information for more than one SPS PDSCH reception in the same PUCCH.

[0115] The HARQ-ACK information bits in the codebook are determined as follows:

[0116] · Whether the UE receives the TB or CBG scheduled by the corresponding DCI. Further, if the PDCCH monitoring occasion is before the DL or UL BWP change, the UE generates a NACK value corresponding to the received TB or CBG; otherwise, the UE generates HARQ-ACK information bits corresponding to the received TB or the decoding result of the received CBG.

[0117] · Whether the UE does not receive the TB or CBG because the UE does not detect the corresponding DCI. Therefore, the UE does not generate HARQ-ACK information bits.

[0118] BWP operation

[0119] With BWP operation, the receive and transmit bandwidths of the UE can be smaller than the bandwidth of the cell and can be adjusted. The bandwidth can be commanded to change (e.g., shrink during low activity to save power), the position can be moved in the frequency domain (e.g., to increase scheduling flexibility), and the subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the cell's system bandwidth is called a BWP, and bandwidth adaptation (BA) is achieved by configuring the UE with BWPs and notifying the UE which of the configured BWPs is currently active. Please refer to Figure 2 , which is a time / frequency diagram showing a scenario of configuring three different BWPs according to an exemplary embodiment of the present disclosure. As Figure 2 shown, the three BWPs are BWP1, BWP2, and BWP3, where BWP1 is 40 MHz of continuous PRBs with a subcarrier spacing of 15 kHz; BWP2 is 10 MHz of continuous PRBs with a subcarrier spacing of 15 kHz; and BWP3 is 20 MHz of continuous PRBs with a subcarrier spacing of 60 kHz.

[0120] In paired spectra, the DL and UL independently switch BWPs. In unpaired spectra (commonly used for TDD), the DL and UL switch BWPs simultaneously. Paired spectra separate the NW-to-UE and UE-to-NW links in the spectrum and are commonly used for lower-band FDD. Unpaired spectra use the same spectrum for the NW-to-UE and UE-to-NW links, which is a common use for higher-band TDD.

[0121] BWP switching is performed between configured BWPs via RRC signaling, DCI signaling, the BWP inactivity timer, or when initiating random access. When the BWP inactivity timer is configured for a serving cell, expiration of the BWP inactivity timer triggers the serving cell to switch the active BWP to the default BWP configured by the NW. Each cell has at most one active BWP, unless the serving cell is configured with SUL, in which case there may be at most one BWP on each UL carrier. More specifically, BWP switching for the serving cell is used to activate an inactive BWP and deactivate the active BWP at a time. BWP switching is controlled by the PDCCH indicating DL allocation or UL grant, by the bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself when initiating the RA procedure or when detecting a successful LBT (Listen-Before-Talk) failure on the SPCell. When the RRC (re)configuration of the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id of the SpCell or the activation of an SCell occurs, the DL BWP and / or UL BWP indicated by the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id (as specified in TS 38.331) are active without receiving the PDCCH indicating DL allocation or UL grant. The active BWP of the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both DL and UL.

[0122] If a DCI format indicating a change in the DL or UL BWP of a cell is detected, it is not necessary for the UE to receive or transmit in the cell for a short period. This period is from the end of the third symbol of the slot in which the UE receives the DCI format until the start of the slot indicated by the slot offset value of the time domain resource allocation field in the DCI format.

[0123] Scheduling enhancements in NTN

[0124] When there is a large offset in the DL and UL frame timing at the UE side in NTN, the existing NR timing definitions involving DL-UL timing interaction may not hold, for example, the offset K1 between UL HARQ feedback and DL PDSCH, and the offset K2 between UL PUSCH and DL DCI.

[0125] In TR 38.821, enhancements have introduced a new offset K_offset and applied it to modify the relevant timing relationships. The value of K_offset can be per beam or per cell. Whether this value is derived from broadcast information or signaled specifically by a higher layer remains to be further studied. The possibility of extending the value ranges of K1 and / or K2 beyond their currently specified ranges can be further discussed when formulating the specifications. Note that to avoid scheduling chaos, i.e., the scheduled UL transmission being earlier than its scheduled DCI, when ignoring the impact of K1 or K2, the value of K_offset can be equal to or greater than the current TA value.

[0126] HARQ-ACK Disabling in NTN

[0127] In NTN, depending on the satellite orbit, the propagation delay ranges from a few milliseconds to several hundred milliseconds. To prevent a reduction in peak data rate due to using only a small number of parallel Stop-and-Wait HARQ processes (e.g., 16 SAW (Stop-and-Wait) HARQ processes are used in Rel-15 NR), it has been agreed that the NW can disable UL HARQ feedback for DL transmissions at the UE receiver to support long propagation delays.

[0128] More features are captured in the current TR 38.821 listed below:

[0129] · Even if HARQ feedback is disabled, the HARQ process can still be configured.

[0130] · Enabling or disabling HARQ feedback is a decision of the NW signaled semi-statically to the UE via RRC signaling.

[0131] · Enabling or disabling HARQ feedback for DL transmissions should be configurable on a per-UE and per-HARQ-process basis via RRC signaling.

[0132] If new HARQ enhancements are introduced for NTN, some problems may occur by reusing the Type 2 HARQ-ACK codebook. For example, if HARQ-ACK is disabled for each HARQ process or each UE according to the Rel-16 NR specification, when the PDCCH monitoring occasion is before the active DL or UL BWP change, the UE can be forced to generate a NACK value for that occasion; if a new scheduling offset K_offset is configured according to the Rel-16 NR specification (e.g., TS 38.213 V16.1.0), the UE can be forced to monitor PDSCH reception opportunities that never occur, thus not generating bits in the HARQ-ACK codebook. In addition, more problems are listed below: · A general description of the Type 2 HARQ-ACK codebook may require new offsets.

[0133] · New offsets may be required for SPS PDSCH reception not scheduled by DCI format.

[0134] · Redundant HARQ-ACK bits used to obtain PUCCH transmission power may need to be removed.

[0135] · Interpretation of the DAI field when HARQ-ACK is configured to be disabled.

[0136] HARQ-ACK bits before an active UL or DL BWP change

[0137] In Rel-16 NR, if the PDCCH does not trigger a DL BWP change and before an active DL or UL BWP change on the serving cell, the HARQ-ACK bit for the PDSCH scheduled by the PDCCH on the serving cell is NACK.

[0138] Specifically, the following pseudocode from 3GPP TS 38.213 V16.1.0 (2020-03) is introduced for this scenario:

[0139]

[0140] If the PDCCH monitoring occasion m is before an active DL BWP change on the serving cell c or an active UL BWP change on the PCell, and the DL BWP change is not triggered in the PDCCH monitoring occasion m

[0141] c = c + 1

[0142] Otherwise […]

[0143]

[0144] end while […]

[0145] For any i ∈ {0, 1, …, O ACK -1}\V S , where some notations are presented below:

[0146] · c: Serving cell index

[0147] · Number of serving cells configured for the UE by higher layers

[0148] · Pcell: Primary cell

[0149] · HARQ-ACK information bits determined by the UE

[0150] ·T D : The set of, where is the number of bits of the counter DAI

[0151] ·j: The parameter for converting the value of the counter DAI into a decimal number

[0152] ·V S : The set of decimal numbers of the counter DAI received by the UE

[0153] ·∪: The union of two sets

[0154] ·∈: Belong to the set

[0155] ·O ACK : The total number of HARQ-ACK information bits determined by the UE

[0156] ·\: Set difference

[0157] ·[…] The ellipsis means omitting or eliminating some words or sentences

[0158] · The value of the DAI counter on the serving cell c in the PDCCH monitoring occasion m

[0159] When the first "conditional statement (if statement)" is satisfied, for example, when m is before the active DL BWP change, the pseudocode goes to the next serving cell c+1 without adding any cDAI to the set V on the serving cell c. As a result, after the pseudocode is completed, the NACK value will be filled in the PDCCH monitoring occasion m S The set. As a result, after the pseudocode is completed, the NACK value will be filled in the PDCCH monitoring occasion m

[0160] Please refer to Figure 3 , which is a timing diagram showing PDSCH reception via DCI format with an active DL BWP change according to an embodiment of the present disclosure. As Figure 3 shown, if the type 2 HARQ-ACK codebook is configured and if the HARQ-ACK information bits for PDSCH reception from slot #1 to slot #5 are multiplexed on the same UL PUCCH slot, the UE can send the NACK values for slot #1 and slot #2 and send the HARQ information bits corresponding to the PDSCH reception in slot #4 and slot #5. For slot #3, there is no PDSCH reception, that is, no HARQ-ACK information bits are generated

[0161] Note that if a single SPS PDSCH reception is activated for a UE and the UE is configured to multiplex the corresponding HARQ-ACK information bits into a Type 2 HARQ-Ack codebook, there is no UE behavior for an active DL or UL BWP change. Some relevant pseudocode from the specification (such as 3GPP TS 38.213 V16.1.0 (2002-03)) is provided below:

[0162]

[0163] As described above, for a single SPS PDSCH reception, only one HARQ-ACK information bit is added after the HARQ-ACK information bits generated for PDSCH reception and SPS PDSCH release. However, if the SPS PDSCH reception is before or after an active DL or UL BWP change, there is no difference.

[0164] Please refer to Figure 4 , which is a timing diagram showing SPS PDSCH reception with an active DL BWP change via DCI format according to an embodiment of the present disclosure. As Figure 4 shown, the scheduled Type 2 HARQ-ACK codebook only contains SPS release and SPS PDSCH reception. The SPS release indicated by the DCI format follows the same rule as PDSCH reception, i.e., the NACK value should be generated by the UE. However, for SPS PDSCH reception, whether it appears in slot #2 on the old DL BWP #1 or in slot #4 on the new DL BWP #2, the UE can generate HARQ-ACK information bits based on the decoding result of the SPS PDSCH reception.

[0165] Note that for SPS PDSCH reception, it is redundant to feedback HARQ information bits on a deactivated DL BWP (e.g., Figure 4 DL BWP #1 in

[0166] ). This is because after the NW clears the DL allocations configured on the deactivated BWP, retransmission for soft combining is not possible, e.g., the mcs-Table in the SPS-Config field used to indicate the MCS table that the UE can use for DL SPS. Some relevant pseudocode from the specification (such as 3GPP TS 38.321 V16.0.0 (2020-03)) is provided below:

[0167] […]

[0168] 1> If the BWP is deactivated:

[0169] 2> UL-SCH transmission not on the BWP

[0170] 2> RACH transmission not on the BWP

[0171] 2> Do not monitor PDCCH on the BWP

[0172] 2> PUCCH transmission not on the BWP

[0173] 2> Do not report CSI for the BWP

[0174] 2> SRS transmission not on the BWP

[0175] 2> DL-SCH reception not on the BWP

[0176] 2> Clear any configured DL allocations and configured UL authorizations of configured grant type 2 on the BWP

[0177] 2> Suspend any configured UL authorizations of configured grant type 1 on the inactive BWP

[0178] […]

[0179] In Rel-17 NTN, when HARQ and DL SPS enhancements are introduced, these redundant bits may need to be revisited. For example, even if HARQ-ACK is disabled by the NW, whether the redundant NACK bits are still generated as the BWP changes, or whether the enhanced DL SPS can have new UE behaviors to avoid redundant feedback of HARQ-ACK information bits.

[0180] In some embodiments, in Rel-16 NR, the general description of the type 2 HARQ-ACK codebook highly involves the scheduling offsets K0 and K1 indicated by the PDSCH-to-HARQ_feedback timing indicator field. As introduced in the specification (e.g., 3GPP TS 38.213 V16.1.0 (2020-03)), the UE determines the PDCCH monitoring occasion using the DCI format for receiving the scheduled PDSCH or releasing the SPS PDSCH on the active DL BWP of the serving cell c, as described in clause 10.1, and for this monitoring occasion, the UE transmits HARQ-ACK information in the same PUCCH in slot n based on the following:

[0181] · Value of the PDSCH-to-HARQ_feedback timing indicator field: This is used for PUCCH transmission using HARQ-ACK information in slot n in response to PDSCH reception or SPS PDSCH release

[0182] · Time slot offset K0: It is provided by the time domain resource allocation field of the DCI format that schedules PDSCH reception or SPS PDSCH release, and pdsch-AggregationFactor (when provided).

[0183] For Rel-17 NTN, if a new scheduling offset K_offset is configured, it is determined that new input parameters may be required to adapt to Rel-16 NR.

[0184] SPS PDSCH reception

[0185] In Rel-16 NR, if DL SPS is configured for the UE in UL time slot n, the UE determines SPS PDSCH reception based on the time slot number for n and offset K1. Some relevant pseudo-code from the specification (such as 3GPP TS 38.213 V16.0.0 (2019-06)) is provided below:

[0186] For NTN, if a scheduling offset K_offset is provided, it is determined that some modifications may be required.

[0187] PUCCH power control for UCI sizes less than 11

[0188] In Rel-16 NR, if the UCI size determined by the UE is less than 11 bits, the UE determines a different number of HARQ-ACK information bits to obtain the transmission power of the PUCCH. Some introductions from the specification (such as 3GPP TS 38.213 V16.0.0 (2020-03)) are provided below:

[0189] · If there is no PDSCH-CodeBlockGroupTransmission provided to the UE for each of the serving cells, or for PDSCH reception scheduled by a DCI format that does not support CBG-based PDSCH reception, or for SPS PDSCH reception, or for SPS PDSCH release, and if O ACK +O SR +O CSI ≤11, the UE determines the number n HARQ-ACK of HARQ-ACK information bits for obtaining the transmission power of the PUCCH, as described in Section 7.2.1, as follows:

[0190]

[0191] where the above symbols are defined as

[0192] · Value of cDAI or tDAI of the previous DCI format

[0193] ·U DAI,c : All DCI formats with PDSCH or SPS PDSCH release detected by the UE

[0194] · Maximum number of codewords scheduled by the DCI format

[0195] ·mod(·): Modulo operation to find the remainder after division

[0196] · Maximum number of TBs or SPS PDSCH releases received by the UE

[0197] ·N SPS,c : Number of SPS PDSCH receptions received by the UE

[0198] Note that in the above equations, the 'A' part is used to calculate the number of missing DCI formats, and the 'B' part is used to calculate the number of received PDSCH and SPS releases. Note that the determined number is always equal to or less than the HARQ-ACK codebook size, i.e., n HARQ-ACK ≤O ACK , and when more than T D DCI formats are missing, the number is always less than the codebook size.

[0199] Please refer to Figure 5 , which is a diagram showing a type 2 HARQ-ACK codebook with more than T D = 4 missing DCI formats according to an embodiment of the present disclosure. Since cDAI does not continuously miss more than 3 times, for example, for consecutive missed detections of cDAI = 1, 2, 3, and 4, the UE can still obtain the correct HARQ-ACK information bits as O ACK = 9 bits. Some notations are introduced below:

[0200] ·n: NACK value

[0201] ·H: HARQ-ACK information value generated by the UE by decoding the received TB· Codebook size of 9 modulo 4 = 1

[0202] ·U DAI,c = 4: The UE detects 4 DCI formats with PDSCH or SPS release

[0203] ·T D = 4: The DCI format contains 2 bits for cDAI or tDAI indication

[0204] · One DCI format generates one HARQ information bit

[0205] ·N SPS,c = 0: There is no DL SPS scheduling in this codebook

[0206] Based on the above parameters, the UE determines n by eliminating 4 bits from the 5 lost DCI formats HARQ-ACK = 5 bits. Those NACK values may not be as important as the HARQ-ACK information bits associated with the detected DCI format used to obtain the PUCCH transmission power

[0207] Note that BWP switching is not considered in the current specification. For example, if all monitoring occasions are before the active DL or UL BWP change, the UE can only feedback NACK bits to the NW without feedback any valuable information. However, when the UCI size is less than 11, the UE does not eliminate any bits to obtain the transmission power of the PUCCH. This violates the design principle of using n HARQ-ACK of the design principle

[0208] For NTN, if HARQ-ACK is disabled and if there is a UL or DL BWP change, the determination of the HARQ-ACK information bits used to obtain the PUCCH transmission power can be modified. Some design principles can be followed to delete redundant bits

[0209] DAI field for HARQ-ACK disabling

[0210] When HARQ-ACK is disabled, the field of DAI is redundant. To delete the field of DAI, DCI format 1_1 can support 0 bits for the DAI field. In addition, since DCI format 1_0 has a fixed bit length of 2, it may be problematic that DCI 1_0 does not provide 0 bits and '00' (i.e., CDAI = 1) in DCI 1_0. Therefore, some alternative solutions are proposed below

[0211] ·For DCI format 1_1: If the HARQ process number field indicates the number associated with HARQ-ACK disabling (or is called disabled HARQ-ACK), the UE can ignore the DAI field. In one example, if a UE indicates HARQ-ACK disabling, for DCI format 1_1, the DAI field can be configured with zero bits

[0212] · For DCI format 1_0: If the HARQ process number field indicates a number associated with HARQ-ACK disabling, the UE may ignore the DAI field. In one example, if a UE that indicates HARQ-ACK disabling is involved, DCI format 1_0 is restricted for DL scheduling.

[0213] · When HARQ-ACK disabling is configured by the NW, a new RNTI may be introduced to redefine the fields of DCI format 1_0 and / or DCI format 1_1.

[0214] Note that if the UE detects consecutive DCI formats indicating the same cDAI value through the associated PDSCH reception, i.e., the conditions in the pseudocode can be met, the UE determines that (T -1) DCI formats are missing and fills NACK in the HARQ-ACK codebook. Any new interpolation for receiving the same cDAI may lose the correction ability. D -1) DCI formats are missing and fills NACK in the HARQ-ACK codebook. Any new interpolation for receiving the same cDAI may lose the correction ability.

[0215] A better way is to keep the DAI unchanged and add a new process for deleting disabled HARQ-ACK bits after determining the HARQ-ACK codebook, which can improve the specification with minimal modifications and / or changes.

[0216] In some embodiments, for HARQ-ACK codebook determination, if a scheduling offset K_offset is configured, new UE behavior may be required for Rel-16 type 2 HARQ-ACK codebooks. Some solutions are proposed below:

[0217] · Add a new definition of the slot offset. In one example, the slot offset value may include at least K_offset and K1.

[0218] · Add K_offset to the slot offset defined in Rel-16 NR. In one example, the new offset K_offset can be directly added to the statement of the slot offset.

[0219] For PDSCH reception or SPS release, if HARQ-ACK disabling is provided, new UE behavior may be required when the listening opportunity is before the active DL or UL BWP change. Some solutions are proposed below:

[0220] · Discard redundant HARQ-ACK bits: If it is for HARQ-ACK bits associated with a HARQ-ACK disabled process ID; alternatively, if an NTN scenario is identified, e.g., k_offset is configured, or HARQ-ACK disable is indicated on a per-UE basis, or a new parameter indicates a dynamic codebook for NTN, e.g., pdsch-HARQ-ACK-Codebook = NTNdynamic. · Retain redundant NACK bits: By ignoring at least one HARQ-ACK bit indicated as HARQ-ACK disabled. For example, if there is no BWP change, no HARQ-ACK bits are generated. If there is a BWP change, the UE may be forced to feedback a NACK for PDSCH reception or SPS release, and feedback HARQ-ACK bits for SPS PDSCH.

[0221] · The MAC entity may not indicate an ACK for SPS deactivation to the physical layer.

[0222] If the UE receives a DCI indicating SPS deactivation, when the UE is configured with HARQ-ACK disable for a HARQ process (e.g., if the HARQ process ID is included in the harq-ACK-Disabled-List or harq-ACK-Disabled-per-UE is set to true / valid), the MAC entity of the UE may not indicate an ACK for SPS deactivation to the physical layer. For PUCCH transmission power determination, if HARQ-ACK disable is provided, new UE behavior may be required. Some solutions are proposed below:

[0223] · If it is determined that the reception or release is associated with a HARQ-ACK disabled process ID, or the reception or release is associated with a monitoring occasion before an active UL or DL BWP change, redundant bits in multiple received PDSCHs and SP releases can be removed.

[0224] · If HARQ-ACK disable is on a per-UE basis, all bits are removed. In one example, a number (e.g., 0) is used for PUCCH transmission power derivation. In another example, a default number (e.g., 1) can be used for PUCCH transmission power derivation.

[0225] · Retain redundant bits by ignoring the indication of HARQ-ACK disable.

[0226] To delete the disabled HARQ-ACK bits, a new procedure can be added at the end of the pseudo-code as proposed in the 3GPP TS specification. For example, the disabled HARQ-ACK bits can be deleted after determining the HARQ-ACK codebook. In one example, when the UE detects the reception of a PDSCH scheduled by a DCI format associated with HARQ-ACK disabling or an SPS release, a flag can be added during the HARQ-ACK codebook determination. In another example, the flag can be used to delete the bits associated with the DCI reception indicating HARQ-ACK disabling at the end of the pseudo-code.

[0227] Receiving from NW to UE

[0228] In some embodiments, the RRC signaling can configure the following parameters from the NW to the UE via an RRC message:

[0229] · pdsch-HARQ-ACK-Codebook: This can be configured as semi-static (Type 1 HARQ-ACK codebook), dynamic (Type 2 HARQ-ACK codebook), enhancedDynamic-r16 (Type 2 HARQ-ACK codebook for Rel-16 NR-U), or NTNdynamic (enhanced Type 2 HARQ-ACK codebook for Rel-17 NTN).

[0230] · pdsch-AggregationFactor: This is the number of repetitions of the data. If not present, the value is 1. · dl-DataToUL-ACK: This is the list of timings from a given PDSCH to a DL ACK in a time slot.

[0231] · bwp-InactivityTimer: This is the duration for which the UE falls back to the default BWP.

[0232] · firstActiveDownlinkBWP-Id: This field contains the DL-BWP ID to be activated when performing an RRC (re)configuration.

[0233] · firstActiveUplinkBWP-Id: This field contains the ID of the UL BWP to be activated when performing an RRC (re)configuration.

[0234] · dl-DataToUL-ACK-NTN: This is the list of timings from a given PDSCH to a DL ACK for NTN.

[0235] · K_offset-NTN: This is the new timing offset value K_offset from a given DL to UL.

[0236] ·harq-ACK-Disabled-List: This is a list of HARQ process IDs for HARQ-ACK disabling.

[0237] ·HARQ-ACK-DISABLED-Per-UE: This is an identifier for disabling HARQ-ACK processes on a per-UE basis.

[0238] In some embodiments, the physical layer may indicate the following information from the NW to the UE via DCI format:

[0239] ·PDSCH-to-HARQ_feedback timing indicator field. It further specifies the slot offset K1 for PUCCH transmission using the HARQ-ACK information in slot n in response to PDSCH reception or SPS PDSCH release. For DCI format 1_0, the field values are mapped to {1, 2, 3, 4, 5, 6, 7, 8}. For DCI format 1_1, the field values are mapped to the values of the set of slot numbers provided by dlDataToUL-ACK or dl-DataToUL-ACK-NTN (if configured). In one example, the set provided by dl-DataToUL-ACK-NTN may contain non-numeric values for HARQ-ACK codebook determination, e.g., values indicating inapplicability. In another example, when a non-numeric value is indicated, the UE ignores the corresponding HARQ feedback.

[0240] ·Time domain resource allocation field. It further specifies the slot offset K0 provided by pdsch-AggregationFactor for the DCI format that schedules PDSCH reception or SPS PDSCH release.

[0241] · DAI field. In one example, it further specifies the value of the counter DAI, e.g., the cumulative number of {serving cell, PDCCH monitoring occasion} pairs where there is a PDSCH reception or SPS PDSCH release associated with a DCI format up to the current serving cell and the current PDCCH monitoring occasion. In another example, it further specifies the total DAI value, e.g., the total number of {serving cell, PDCCH monitoring occasion} pairs where there is a PDSCH reception or SPS PDSCH release associated with a DCI format up to the current PDCCH monitoring occasion m and from the PDCCH monitoring occasion update to the PDCCH monitoring occasion. In another example, for DCI format 1_1, the DAI field can be configured by 0 bits or by a non-numeric value (e.g., not applicable value) for HARQ-ACK codebook determination. When a non-numeric value is indicated, the UE ignores the corresponding HARQ feedback. · BWP indicator field. In one example, this field contains the DL-BWP ID to be activated for DCI format 1_1, or contains the UL-BWP ID to be activated for DCI format 0_1. In another example, if the UE may not support active BWP change via DCI, the UE ignores this bit field.

[0242] Transmission from UE to NW

[0243] The HARQ-ACK information bits associated with PDSCH reception, SPS PDSCH reception, and SPS PDSCH release scheduled by the NW in the active DL BWP of the serving cell can be transmitted from the UE to the NW in the PUCCH transmission of a time slot, or multiplexed in the PUSCH transmission.

[0244] UE Behavior

[0245] In some embodiments, if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic or pdsch-HARQ-ACK Codebook = NTNdynamic, the solutions in this section can be applied.

[0246] The UE determines the monitoring occasion of the PDCCH using the DCI format that schedules PDSCH reception or SPS PDSCH release on the active DL BWP of serving cell c, and for this monitoring occasion, the UE transmits HARQ-ACK information in the same PUCCH in time slot n based on K0, K1, and based on K_offset (if provided).

[0247] Enhanced Type 2 HARQ-ACK Codebook for NTN

[0248] The UE determines the total number O according to the following pseudocodeACK of the HARQ-ACK information bits

[0249] Initialization

[0250] Let m = 0; Let j = 0; Let V temp = 0; Let Set to the set of redundant bits to be deleted.

[0251] Set to the number of serving cells configured by the higher layer for the UE.

[0252] Set M to the number of PDCCH monitoring occasions.

[0253] PDSCH and SPS Release

[0254]

[0255]

[0256]

[0257] Check the carry of tDAI if V temp2 < V temp

[0258] j = j + 1 end if

[0259] For SPS PDSCH

[0260]

[0261]

[0262] Fill NACK and delete redundant bits

[0263] For any i ∈ {0, 1, …, O ACK - 1}\V S ,

[0264] For any i ∈ V R ,

[0265] exclude the HARQ-ACK bits before multiplexing in the HARQ-ACK codebook

[0266] The UE determines the PDCCH monitoring occasion using the DCI format for receiving the scheduled PDSCH or SPS PDSCH release on the active DL BWP of the serving cell, and for this monitoring occasion, the UE transmits HARQ-ACK information in the same PUCCH in slot n based on K0, K1, and based on K_offset (if provided).

[0267] In one example, if pdsch-HARQ-ACKCodebook = NTNdynamic is provided, and if the HARQ process number field in the DCI format indicates a HARQ process number associated with HARQ-ACK disabling provided by harq-ACK-Disabled-List or by harq-ACK-Disabled-per-UE, the UE may not multiplex the HARQ-ACK information bits for PUCCH transmission in slot n.

[0268] In another example, if the DAI field provided by the DCI format is configured with 0 bits or a non-numeric value, and if the HARQ process number field in DCI format 1_1 indicates a HARQ process number associated with HARQ-ACK disabling provided by harq-ACK-Disable-List or by harq-ACK-Disable-per-UE, the UE may not multiplex the HARQ-ACK information bits for PUCCH transmission in slot n.

[0269] In another example, if there is a PDSCH-to-HARQ_feedback timing indicator field in the DCI format that provides a non-numeric value from dl-DataToUL-ACK-NTN, the UE may not multiplex the HARQ-ACK information bits for PUCCH transmission in slot n.

[0270] In another example, if none of the above scenarios are met, the UE may apply the legacy process.

[0271] In one embodiment, if the corresponding HARQ process is disabled (e.g., the HARQ process ID is included in the harq-ACK-Disabled-List or harq-ACK-Disabled-per-UE is set to true), the MAC entity of the UE does not instruct the physical layer to generate an ACK for the data in the TB. Some related pseudocode is presented below:

[0272] 1> If the HARQ process is associated with a transmission indicated by a temporary C-RNTI and contention resolution has not been successful; or

[0273] 1> If the HARQ process is associated with the transmission indicated by the MSGB-RNTI and the RA

[0274] procedure has not been successfully completed; or

[0275] 1> If the HARQ process is equal to the broadcast process;

[0276] 1> If the RA process is disabled (e.g., the HARQ process ID is included in the harq-ACK-

[0277] Disabled-List or harq-ACK-Disabled-per-UE is set to true); or

[0278] 1> If the timeAlignmentTimer associated with the TAG of the serving cell on which the HARQ feedback is to be transmitted stops or expires;

[0279] 2> Do not indicate to the physical layer to generate an ACK for the data in this TB.

[0280] 1> Otherwise: 2> Indicate to the physical layer to generate an ACK for the data in this TB.

[0281] Determination for PUCCH power control

[0282] · If no PDSCH-CodeBlockGroupTransmission is provided to the UE for each of the serving cells, or for PDSCH reception scheduled by a DCI format that does not support CBG-based PDSCH reception, or for SPS PDSCH reception, or for SPS PDSCH release, and if O ACK +O SR +O CSI ≤11, the UE determines the number n of HARQ-ACK information bits for obtaining the transmission power of the PUCCH HARQ-ACK , as described in Clause 7.2.1, as follows:

[0283]

[0284] where

[0285] · Refers to the number of TBs received in the PDSCH scheduled by the DCI format detected by the UE in the PDCCH monitoring occasion m of serving cell c when no harq-ACK-SpatialBundlingPUCCH is provided, or the number of PDSCHs scheduled by the DCI format detected by the UE in the PDCCH monitoring occasion m of serving cell c when harq-ACK-SpatialBundlingPUCCH is provided, or the number of DCI formats detected by the UE in the PDCCH monitoring occasion m of serving cell c that indicate the release of SPS PDSCH therein.

[0286] ·N SPS,c Is the number of SPS PDSCH receptions performed by the UE on serving cell c. The UE transmits the corresponding HARQ-ACK information for serving cell c in the PUCCH that is the same as the HARQ-ACK information for the PDSCH reception within M PDCCH monitoring occasions.

[0287] · If pdsch-HARQ-ACK-Codebook = NTNdynamic is provided to the UE, then Is the number of HARQ-ACK information bits deleted by the UE due to active DL or UL BWP change or due to HARQ-ACK disabling. For example, V R The cardinality of. Otherwise,

[0288] Please refer to Figure 6 Which is a flowchart showing a process 60 for HARQ-ACK codebook construction performed by the UE according to an embodiment of the present disclosure. As Figure 6 Shown, the process 60 for the UE includes the following actions:

[0289] Action 600: Start.

[0290] Action 602: Receive an RRC message from the NW. The RRC message includes an indication that indicates to the UE whether HARQ feedback for the HARQ process is disabled.

[0291] Action 604: If the indication of the RRC message indicates to the UE that HARQ feedback for the HARQ process is disabled, then do not generate HARQ-ACK bits corresponding to the first TB, but generate at least one HARQ-ACK bit corresponding to at least one second TB.

[0292] Action 606: If the DCI format from the NW indicates to the UE the reception of a first TB and at least one second TB in the same time slot, multiplex at least one HARQ-ACK bit to construct a HARQ-ACK codebook for the first TB and the at least one second TB.

[0293] Action 608: End.

[0294] Preferably, Actions 602 to 606 of Procedure 60 can be performed by the UE. Specifically, the indication of the RRC message configures the harq-ACK-Disabled-List parameter to include a list of HARQ processes for which HARQ feedback is disabled, and the HARQ-ACK codebook is a type 2 HARQ-ACK codebook, and the NW is NTN.

[0295] In some embodiments, the UE can receive an RRC message from the NW, such that the NW can indicate to the UE whether to disable HARQ feedback for a HARQ process in Action 602 through the indication of the RRC message. In Action 604, if the NW indicates to the UE to disable HARQ feedback for a HARQ process, the UE may not generate HARQ-ACK bits corresponding to one TB (e.g., the first TB), but may generate at least one HARQ-ACK bit corresponding to another (some) TB (e.g., at least one second TB). In Action 606, if the DCI format from the NW indicates to the UE the reception of TBs (e.g., including the first TB and at least one second TB) in the same time slot, the UE can multiplex at least one HARQ-ACK bit to construct a HARQ-ACK codebook for the first TB and the at least one second TB.

[0296] Procedure 60 may include further actions / procedures / mechanisms / operations. In some embodiments, if the indication of the RRC message indicates to the UE to disable HARQ feedback for a HARQ process, the UE may discard at least one HARQ-ACK bit associated with the disabled HARQ process (e.g., the HARQ process with disabled feedback).

[0297] In some embodiments, the UE can receive a DCI message from the NW. Next, if one HARQ-ACK bit associated with the disabled HARQ process ID is discarded, the UE can ignore the DAI field of the DCI message.

[0298] In some embodiments, if the transmission of a TB is indicated by a T-CRNTI and the contention resolution corresponding to the transmission has not been successful, or if the HARQ process associated with the transmission is indicated by an MSGB-RNTI and the RA process has not been successfully completed, or if the HARQ process is equal to a broadcast process, or if the TimeAlignment timer associated with the tag including the serving cell on which the HARQ feedback is to be transmitted expires or stops, the UE may not generate HARQ-ACK bits corresponding to the one TB.

[0299] Of course, the detailed mechanism and / or operation of process 60 is described in the above paragraphs and is omitted hereinafter for the sake of brevity. For example, the detailed mechanism and / or operation of actions 602 to 606 is described in the above paragraphs and is omitted hereinafter for the sake of brevity.

[0300] Please refer to Figure 7 , which is a block diagram showing a node 700 for wireless communication according to an exemplary embodiment of the present disclosure. As Figure 7 shown, the node 700 includes a transceiver 706, a processor 708, a memory 702, one or more presentation components 704, and at least one antenna 710. The node 700 may also include a radio frequency (RF) band module, a base station communication module, an NW communication module, a system communication management module, an input / output (I / O) port, I / O components, and a power supply (not explicitly shown in Figure 7 ). Each of these components may communicate with each other directly or indirectly through one or more buses 724. The node 700 may be a UE or a BS that performs various functions disclosed herein. For example, refer to Figure 6 .

[0301] The transceiver 706, which includes a transmitter 716 (e.g., transmitting / transmission circuitry) and a receiver 718 (e.g., receiving / reception circuitry), may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 706 may be configured to transmit in different types of subframes and time slots, including but not limited to usable, unusable, and flexibly usable subframe and time slot formats. The transceiver 706 may be configured to receive data and control channels.

[0302] Node 700 may include a variety of computer-readable media. Computer-readable media can be any available media accessible by node 700 and includes both volatile (and non-volatile) media, and removable (and non-removable) media. By way of example and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media includes both volatile (and non-volatile), and removable (and non-removable) media, implemented in any method or technology for storing information such as computer-readable.

[0303] Computer storage media includes RAM, ROM, EEPROM, flash memory (or other storage technology), CD-ROM, digital versatile disk (DVD), (or other optical disk storage device), magnetic tape cartridges, magnetic tape, disk storage (or other magnetic storage device), etc. Computer storage media does not include propagated data signals. Communication media may typically include computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transmission mechanism, and includes any information delivery media.

[0304] The term "modulated data signal" may refer to a signal having one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example and not limitation, communication media includes wired media such as a wired NW or direct wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Any prior art combination should also be included within the scope of computer-readable media.

[0305] Memory 702 may include computer storage media in the form of volatile and / or non-volatile memory. Memory 702 may be removable, non-removable, or a combination thereof. For example, memory 702 may include solid state memory, hard disk drives, optical disk drives, etc.

[0306] As Figure 7 shown, memory 702 may store a computer-executable (readable) program 714 (e.g., software code), the computer-executable program 714 being configured to cause processor 708 to perform the various functions disclosed herein when executed, e.g., with reference to Figure 6 . Optionally, the computer-executable program 714 may not be directly executed by processor 708, but is configured to cause node 700 (e.g., when compiled and executed) to perform the various functions disclosed herein.

[0307] The processor 708 (e.g., having processing circuitry) may include intelligent hardware devices such as a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 708 may include a memory. The processor 708 may process data 712 and computer-executable programs 714 received from the memory 702, as well as information received via the transceiver 706, the baseband communication module, and / or the NW communication module. The processor 708 may also process information to be sent to the transceiver 706 for transmission via the antenna 710 to the NW communication module for subsequent transmission to the CN.

[0308] One or more presentation components 704 may present data to a person or other device. Examples of presentation components 704 may include display devices, speakers, printing components, vibrating components, etc.

[0309] In accordance with the present disclosure, it will be apparent that various techniques may be utilized to implement the concepts of the present disclosure without departing from the scope of these concepts. Additionally, although the concepts have been disclosed by specific reference to certain embodiments, those skilled in the art will recognize that changes may be made in form and detail without departing from the scope of these concepts. Accordingly, the disclosed embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that this application is not limited to the particular disclosed embodiments. Many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A method for constructing a Hybrid Automatic Repeat reQuest - ACKnowledgment (HARQ - ACK) codebook performed by a User Equipment (UE), the method comprising: Receiving, from a Network (NW), a Radio Resource Control (RRC) message, the RRC message including an indication for the UE to disable HARQ feedback for a HARQ process; Not generating HARQ - ACK bits corresponding to a first Transport Block (TB) associated with the HARQ process, but generating at least one HARQ - ACK bit corresponding to at least one second TB not associated with the HARQ process; Receiving, from the NW, a first Downlink Control Information (DCI) format, the first DCI format indicating to the UE the reception of the first TB and the at least one second TB to be fed back in the same time slot; Multiplexing the at least one HARQ - ACK bit corresponding to the at least one second TB, while excluding HARQ feedback for the first TB, to construct the HARQ - ACK codebook for the first TB and the at least one second TB; Receiving, from the NW, a second DCI format for scheduling a Physical Downlink Shared Channel (PDSCH), the second DCI format including a HARQ process number and a Downlink Allocation Index (DAI); And If the HARQ process number is associated with the HARQ process, ignoring the DAI of the second DCI format.

2. The method according to claim 1, wherein The indication in the RRC message is to configure a harq - ACK - Disabled - List parameter, and the harq - ACK - Disabled - List parameter indicates a list of HARQ process identifier (ID) for which HARQ feedback is disabled.

3. The method according to claim 1, wherein The HARQ - ACK codebook is a type 2 HARQ - ACK codebook, and the NW is a Non - Terrestrial Network (NTN).

4. A User Equipment (UE) for constructing a Hybrid Automatic Repeat reQuest - ACKnowledgment (HARQ - ACK) codebook in a wireless communication system, the UE comprising: A processor; And A memory coupled to the processor, wherein the memory stores a computer - executable program, and when the computer - executable program is executed by the processor, it causes the processor to: Receive, from a Network (NW), a Radio Resource Control (RRC) message, the RRC message including an indication for the UE to disable HARQ feedback for a HARQ process; Not generate HARQ - ACK bits corresponding to a first Transport Block (TB) associated with the HARQ process, but generate at least one HARQ - ACK bit corresponding to at least one second TB not associated with the HARQ process; Receive, from the NW, a first Downlink Control Information (DCI) format, the first DCI format indicating to the UE the reception of the first TB and the at least one second TB to be fed back in the same time slot; Multiplex the at least one HARQ-ACK bit corresponding to the at least one second TB while excluding the HARQ feedback for the first TB to construct a HARQ-ACK codebook for the first TB and the at least one second TB; Receive a second DCI format for scheduling a physical downlink shared channel PDSCH from the NW, the second DCI format including a HARQ process number and a downlink allocation index DAI; and If the HARQ process number is associated with the HARQ process, ignore the DAI of the second DCI format.

5. The UE according to claim 4, characterized in that, The indication in the RRC message is to configure the harq-ACK-Disabled-List parameter, and the harq-ACK-Disabled-List parameter indicates a list of HARQ process identifier IDs for which HARQ feedback is disabled.

6. The UE according to claim 4, characterized in that, The HARQ-ACK codebook is a type 2 HARQ-ACK codebook, and the NW is a non-terrestrial network NTN.

Images