Method and apparatus for hybrid automatic repeat request-acknowledgement reporting in non-terrestrial network communications

Abstract

For a non-terrestrial network (non-terrestrial network; a solution is provided for downlink received enhanced hybrid automatic repeat request acknowledgement (HARQ-ACK) reporting configured in NTN communication. The invention relates to a method and a device for operating a user equipment (user equipment; a device implemented in a network node (e.g., UE) receives at least one offset value configuration from the network node. The apparatus performs downlink reception configured by the network node. The device determines an offset value applicable to a slot overlapping with a last symbol of the downlink reception. The device transmits HARQ information to the network node according to the offset value.

Description

[0001] Cross-referencing

[0002] This disclosure is part of a non-provisional application that claims priority to U.S. Patent Application No. 63 / 494,482, filed April 6, 2023, the contents of which are incorporated herein by reference in their entirety. [Technical Field]

[0003] This disclosure generally relates to mobile communications, and more specifically, to an enhanced hybrid automatic repeat request-acknowledgement (HARQ-ACK) report configured for downlink reception in non-terrestrial network (NTN) communications. [Background Technology]

[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the claims listed below, and are not recognized as prior art by virtue of being included in this section.

[0005] In wireless communication, such as mobile communications under the 3rd Generation Partnership Project (3GPP) standards, which include 5th Generation (5G) New Radio (NR) and 4th Generation (4G) Long-Term Evolution (LTE), Hybrid Automatic Repeat Request (HARQ) is a communication protocol that allows the sender to detect and correct errors in transmitted data. When data is transmitted from the sender to the receiver, the receiver sends an acknowledgement (ACK) message to the sender, indicating that the data has been successfully received. If the sender does not receive an ACK message within a certain period of time, it assumes that the data has not been received correctly and retransmits the data.

[0006] In NR, downlink (DL) configuration triggered by semi-persistent scheduling (SPS) for physical downlink shared channel (PDSCH) reception is triggered via downlink control information (DCI). The HARQ-ACK report indicates this in the DCI that activates SPS PDSCH reception. For example, for DL ​​slot n...D Upon completion of SPS PDSCH reception, the UE transmits the physical uplink control channel (PUCCH) in uplink (UL) time slot n+k, where k is provided by the PDSCH-to-HARQ feedback timing indication field provided in the DCI format for activating SPS PDSCH reception (if present).

[0007] In NR NTN communication, K is introduced offset To address the long propagation delays in satellite systems, each UE requires a large timing advance (TA) value to compensate for the round-trip time (RTT) between the UE and the 5G base station (5G Node B; gNB) / satellite. As TA increases, the cardinality of the set of usable k values ​​decreases significantly. To address this issue, a scheduling offset K is introduced. offset To enhance transmission timing, including the transmission timing of HARQ-ACK on the PUCCH. However, K offset The value can be dynamically changed / updated through control signaling. The UE may receive a new K value when preparing a HARQ-ACK report for planned downlink reception. offset The value is currently unclear. It is still unclear which K should be applied. offset The value is used to transmit the HARQ-ACK report.

[0008] When K offset When the value changes, there is ambiguity in determining the transmission time of the uplink transmission. Therefore, resolving this ambiguity has become an important issue in newly developed wireless communication networks. Consequently, appropriate solutions are needed to enhance HARQ-ACT reporting in NTN communications. [Summary of the Invention]

[0009] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments will be further described in the detailed description. Therefore, the following summary is not intended to identify the essential features of the claims, nor to determine the scope of the claims.

[0010] The objective of this disclosure is to provide solutions or schemes for addressing the aforementioned problems. More specifically, the various schemes proposed in this disclosure relate to enhanced hybrid automatic repeat request-acknowledgement (HARQ-ACK) reporting configured for downlink reception in non-terrestrial network (NTN) communications.

[0011] In one aspect, a method may involve a user equipment (UE) receiving at least one offset value configuration from a network node. The method may also involve the UE performing downlink reception configured by the network node. The method may further involve the UE determining an offset value applicable to a time slot overlapping with the last symbol of the downlink reception. The method may further involve the UE transmitting HARQ information to the network node based on the offset value.

[0012] In another aspect, a device may include a transceiver that wirelessly communicates with at least one network node during operation. The device may also include a processor communicatively coupled to the transceiver. During operation, the processor may perform operations including receiving at least one offset value configuration from the network node via the transceiver. The processor may also perform operations including performing downlink reception configured by the network node. The processor may further perform operations including determining an offset value applicable to a time slot overlapping with the last symbol of the downlink reception. The processor may further perform operations including transmitting HARQ information to the network node via the transceiver based on the offset value.

[0013] It is worth noting that although the descriptions provided herein may be within the context of certain radio access technologies, networks, and network topologies (such as NTN), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in other types of radio access technologies, networks, and network topologies, such as, but not limited to, Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5th Generation (5G), New Radio (NR), Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), and Industrial Internet of Things (IIoT). Therefore, the scope of this disclosure is not limited to the examples described herein. [Attached Image Description]

[0014] The accompanying drawings are included to provide a further understanding of this disclosure and form part of this disclosure. These drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that the drawings are not necessarily to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0015] Figure 1 This is a diagram of an example network environment in which various proposed schemes according to this disclosure can be implemented.

[0016] Figure 2 This is an illustration of an example scenario based on the proposed solution of this disclosure.

[0017] Figure 3 This is a block diagram of an example communication system based on an embodiment of the present disclosure.

[0018] Figure 4 This is a flowchart of an example process based on an embodiment of the present disclosure.

Detailed Implementation Methods

[0019] Detailed embodiments and implementations of the claims of this disclosure are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative examples of the claims of this disclosure and may be embodied in various forms. This disclosure may be embodied in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are intended to make the description of this disclosure comprehensive and complete, and to fully convey the scope of this disclosure to those skilled in the art. Details of well-known features and techniques may be omitted in the following description to avoid unnecessarily obscuring the presented embodiments and implementations.

[0020] Overview

[0021] Implementations of this disclosure relate to various techniques, methods, schemes, and / or solutions related to the hybrid automatic repeat request-acknowledgment (HARQ-ACK) report received in a downlink configuration for communication with a non-terrestrial network (NTN). According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described individually below, two or more of these possible solutions can be implemented in one or another combination.

[0022] Figure 1An example network environment 100 is illustrated, in which various proposed schemes according to this disclosure can be implemented. Network environment 100 may involve a user equipment (UE) 110 and a wireless network 120 (e.g., an LTE network, a 5G / NR network, an IoT / NB-IoT / IIoT network, a 6G network, and / or an NTN network). UE 110 can communicate with wireless network 120 via network node 125. In some cases, network node 125 may be a non-terrestrial network node of the NTN (e.g., a satellite). In some cases, network node 125 may be a terrestrial network node (e.g., a base station such as a gNB, eNB, or a transmission / reception point (TRP)). In some cases, UE 110 may be an IoT device, such as a narrowband (NB)-IoT UE or an enhanced machine-type communication (eMTC) UE (e.g., a bandwidth-reduced low complexity (BL) UE or a coverage enhancement (CE) UE). Each of UE 110 and network node 125 can be configured to perform operations related to downlink received enhanced HARQ-ACK reports configured in NTN communications according to various proposed schemes of this disclosure, as described below.

[0023] In Release-17NR NTN, an agreement has been reached for the semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH), which is applied to UE-specific K-channels valid in the time slots where relevant downlink control information (DCI) is received. offset For the DCI scheduling of the PUSCH containing channel state information (CSI) and aperiodic sounding reference signal (SRS) on the physical uplink shared channel (PUSCH), and for the HARQ-ACK on the PUCCH, the UE-specific K applied at the time slot of the receive-related DCI is valid. offset Release-17NR NTN K offsetThe protocol is typically applicable to DCIs with a Downlink Assignment Index (DAI), used for downlink (DL) PDSCH and HARQ-ACK reporting DL PDSCH on the PUCCH. If parameter K... offset After SPS PDSCH reception is triggered via DCI, the UE-specific K is controlled via the medium access control (MAC) control element (CE). offset Changes could be ambiguous, because there is no subsequent triggering of SPS PDSCH before the triggering of SPS PDSCH release is received via DCI.

[0024] Figure 2 An example scenario 200 is illustrated under an implementation of this disclosure. Scenario 200 involves at least one UE and one network node / satellite, which may be part of a wireless communication network (e.g., LTE network, 5G / NR network, IoT / NB-IoT / IIoT network, 6G network, and / or NTN network). Scenario 100 illustrates the timeline of HARQ-ACK reporting. The UE can receive downlink received DCI according to the scheduling configuration at T1. The UE can, according to the pre-scheduled old UE-specific K... offset The value determines the time (e.g., T4) for downlink reception of the transmission configuration HARQ-ACK report. The UE can receive a new UE-specific KARQ-ACK report via a MAC CE message at T2. offset Value. New UE-specific K offset The value at T3 specifies an application time that precedes the transmission time of the HARQ-ACK report (e.g., T4). In this case, there is ambiguity regarding which K should be applied. offset The value determines the transmission time of the HARQ-ACK report. It is unclear whether the UE should refer to the older UE-specific K value. offset The value should still refer to the new UE-specific K. offset The value determines the transmission time of the HARQ-ACK report.

[0025] In view of the above, this disclosure proposes several schemes involving determining the transmission time of HARQ-ACK reports for downlink reception regarding the configuration of the UE and network equipment in mobile / NTN communications. According to the schemes of this disclosure, the UE can receive at least one offset value configuration from a network node (e.g., a satellite / base station). The UE can perform downlink reception configured by the network node. The UE can determine an offset value applicable to the time slot overlapping with the last symbol of the downlink reception. The UE can then transmit HARQ information to the network node based on the offset value.

[0026] Specifically, the UE can receive the first configuration of the first offset value (e.g., the old K) before downlink reception. offset (Value). After downlink reception and before HARQ information transmission, the UE can further receive a second configuration of the second offset value (e.g., a new K). offset The UE can determine the first offset value (i.e., the old K). offset The value is an offset value applicable to the time slot overlapping with the last symbol received in the downlink. The UE can then base its decisions on the first offset value (i.e., the old K). offset The value determines the transmission time of the HARQ information.

[0027] In some embodiments, the second offset value (e.g., the new K) offset The value can be provided / received via MAC CE messages. Configured downlink reception can be scheduled by DCI. Configured downlink reception may include SPSPDSCH reception.

[0028] In some embodiments, the application / activation of the second offset value begins before the transmission of HARQ information.

[0029] In some embodiments, the offset value includes a cell-specific K-offset value or a UE-specific K-offset value. The offset value is a scheduling offset used for HARQ-ACK reports received in downlink SPS PDSCH reception.

[0030] In some embodiments, HARQ information can be transmitted on PUCCH or PUSCH. HARQ information may include HARQ-ACK or HARQ-negative ACK (HARQ-NACK).

[0031] In some embodiments, the UE can determine the time slot used for transmitting HARQ information based on the offset value.

[0032] In some embodiments, the offset value can be provided in the DCI format that activates downlink reception.

[0033] In some embodiments, the offset value can be configured for NTN communication.

[0034] According to the implementation scheme of this disclosure, the process of UE reporting control information can be specifically as follows. If the UE provides K through a cell-specific K offset value... cell,offset Or provide K via MAC CE command UE,offset Then, the time slot n+k of PUCCH transmission or PUSCH transmission corresponds to the time slot of PUSCH or PUCCH transmission. And time slot n U -K1,k Corresponding to time slot Where μ is the sub-carrier spacing (SCS) configuration for PUCCH or PUSCH transmission, and K offset Defined (e.g., K) offset =K cell,offset -K UE,offset K cell,offset Provided by a cell-specific K offset value, K UE,offset From difference K offset The MAC CE command is provided; otherwise, if not provided separately, K cell,offset =0 or K UE,offset =0), and in FR1 If no cell-specific K offset value or MAC CE command is provided, then K is respectively. cell,offset =0 or K UE,offset =0. If PUCCH or PUSCH transmissions are scheduled using DCI format, then K UE,offset The value is applicable to the time slot overlapping with the last symbol of the PDCCH reception providing DCI format. For a PUCCH with HARQ-ACK information for SPS PDSCH reception, K... UE,offset The value is applicable to the time slot overlapping with the last symbol of the SPS PDSCH reception. If the PUCCH or PUSCH transmission is scheduled by cyclic redundancy check (CRC) with DCI format scrambling TC-RNTI, then K... UE,offset =0. If the UE provides K via MAC CE command UE,offset If the value is [value], then the UE is in the time slot. The first time slot thereafter applies the MAC CE command, where k is the time slot in which the UE will transmit the PUCCH with HARQ-ACK information provided by the MAC CE command from the PDSCH, and μ is the SCS configuration for PUCCH transmission determined when the MAC CE command is applied.

[0035] Therefore, the offset value used to determine the HARQ information transmission time can be explicitly specified. Even if the offset value is updated / changed, the UE can still determine the correct offset value for transmitting HARQ information. This avoids ambiguity for the UE and improves the performance of HARQ report transmission.

[0036] Example implementation

[0037] Figure 3An example communication system 300 is shown, which has an example communication device 310 and an example network device 320, conforming to one implementation of this disclosure. Each of the communication device 310 and the network device 320 can perform various functions to implement the schemes, techniques, processes, and methods described herein, which relate to enhanced HARQ-ACK reporting of downlink reception configured in NTN communication, including the scenarios / schemes described above and the processes described below.

[0038] Communication device 310 may be part of an electronic device, which may be a UE (User Equipment), such as a portable or mobile device, wearable device, wireless communication device, or computing device. For example, communication device 310 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device (such as a tablet, laptop, or notebook computer). Communication device 310 may also be part of a machine-type device, which may be an IoT, NB-IoT, IIoT, or NTN device, such as a fixed or stationary device, home appliance, wired communication device, or computing device. For example, communication device 310 may be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. Alternatively, communication device 310 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set computing (CISC) processors. Communication device 310 may include... Figure 3 At least some of the components shown, such as processor 312. Communication device 310 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, for simplicity and brevity, these components of communication device 310 are not included in... Figure 3 It is shown in the text and is not described in the following text.

[0039] Network device 320 may be part of an electronic device / site, which may be a network node such as a base station, small cell, router, gateway, or satellite. For example, network device 320 may be implemented in an eNodeB in LTE, a gNB in ​​5G, NR, IoT, NB-IoT, IIoT, or a satellite in an NTN network. Alternatively, network device 320 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 320 may include... Figure 3 At least some of the components shown, such as processor 322. Network device 320 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, for simplicity and brevity, these components of network device 320 are not included in... Figure 3 It is shown in the text and is not described in the following text.

[0040] In one aspect, each of processors 312 and 322 may be implemented as one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 312 and 322, in embodiments consistent with this disclosure, each of processors 312 and 322 may include multiple processors in some embodiments, and a single processor in others. In another aspect, each of processors 312 and 322 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, these components being configured and arranged to achieve a particular purpose of this disclosure. In other words, in at least some embodiments, each of processors 312 and 322 is a dedicated machine specifically designed, arranged, and configured to perform a specific task, including enhanced HARQ-ACK reporting for configuring downlink reception according to various embodiments of this disclosure.

[0041] In some embodiments, the communication device 310 may further include a transceiver 316 coupled to the processor 312, capable of wirelessly transmitting and receiving data. In some embodiments, the communication device 310 may further include a memory 314 coupled to the processor 312, capable of being accessed and storing data by the processor 312. In some embodiments, the network device 320 may further include a transceiver 326 coupled to the processor 322, capable of wirelessly transmitting and receiving data. In some embodiments, the network device 320 may further include a memory 324 coupled to the processor 322, capable of being accessed and storing data by the processor 322. Therefore, the communication device 310 and the network device 320 can communicate wirelessly via transceiver 316 and transceiver 326, respectively.

[0042] Each of the communication device 3410 and the network device 320 can be a communication entity capable of communicating using various proposed schemes of this disclosure. To aid in better understanding, the following description of the operation, functions, and capabilities of the communication device 310 and the network device 320 is provided in the context of a mobile communication environment, wherein the communication device 310 is implemented as a communication device or user equipment (e.g., UE 110), and the network device 320 is implemented as a network node or base station (e.g., network node 125) of a communication network (e.g., network 120). It is also worth noting that although the example embodiments described below are provided in the context of an NTN, the same embodiments can be implemented in other types of networks.

[0043] In some proposed embodiments of the enhanced HARQ-ACK report according to this disclosure, for downlink reception configured in NTN communication, communication device 310 is implemented as or acts as UE 110 in network environment 100, network device 320 is implemented as or acts as network node 125, and processor 312 can receive at least one offset value configuration from network device 320 via transceiver 316. Processor 312 can perform downlink reception configured by network device 320. Processor 312 can also determine an offset value applicable to the time slot overlapping with the last symbol of the downlink reception. Then, processor 312 can transmit HARQ information to network device 320 according to the offset value via transceiver 316.

[0044] In some embodiments, processor 312 may receive a first configuration of a first offset value via transceiver 316 before downlink reception. Processor 312 may also receive a second configuration of a second offset value via transceiver 316 after downlink reception and before transmission of HARQ information. Processor 312 can then determine that the first offset value is an offset value applicable to the time slot overlapping with the last symbol of the downlink reception.

[0045] In some embodiments, the second offset value can be received via MAC CE.

[0046] In some embodiments, the application of the second offset value can begin before the transmission of HARQ information.

[0047] In some embodiments, the offset value may include a cell-specific K-offset value or a UE-specific K-offset value.

[0048] In some embodiments, downlink reception may include SPS PDSCH reception.

[0049] In some embodiments, processor 312 can transmit HARQ information on PUCCHPUSCH via transceiver 316.

[0050] In some embodiments, the processor 312 can determine the time slot for transmitting HARQ information based on the offset value.

[0051] In some embodiments, the offset value can be provided in the DCI format that activates downlink reception.

[0052] In some embodiments, the offset value can be configured for NTN communication.

[0053] Example Process

[0054] Figure 4 An example flow 400 according to an embodiment of the present disclosure is illustrated. Flow 400 may be an example embodiment of some or all of the above-described scheme, relating to enhanced HARQ-ACK reporting received in a downlink configuration in NTN communication according to the present disclosure. Flow 400 may represent an embodiment of a feature implementation of communication device 310 and / or network device 320. Flow 400 may include one or more operations, actions, or functions, as shown in steps 410, 420, 430, and 440. Although shown as discrete steps, the individual steps of flow 400 may be divided into more steps, combined into fewer steps, or eliminated, depending on the desired implementation. Furthermore, the steps of flow 400 may be arranged in... Figure 4 The process can be executed in the order shown, or in a different order. Process 400 can be implemented by communication device 310 or any suitable user equipment or machine type device. For illustrative purposes only and without limitation, process 400 is described below as communication device 310 implemented as or as UE 110, and network device 320 implemented as or as network node 125. Process 400 may begin at step 410.

[0055] In step 410, process 400 may involve the processor 312 of device 310 receiving at least one offset value configuration from the network node. Process 400 may proceed from step 410 to step 420.

[0056] In step 420, process 400 may involve processor 312 performing downlink reception configured by the network node. Process 400 may proceed from step 420 to step 430.

[0057] In step 430, process 400 may involve processor 312 determining an offset value applicable to the time slot overlapping with the last symbol received in the downlink. Process 400 may proceed from step 430 to step 440.

[0058] In step 440, process 400 may involve processor 312 transmitting HARQ information to network nodes based on offset values.

[0059] In some embodiments, process 400 may involve a first configuration where processor 312 receives a first offset value before downlink reception. Process 400 may also involve a second configuration where processor 312 receives a second offset value after downlink reception and before transmitting HARQ information. Process 400 may also involve processor 312 determining that the first offset value is an offset value applicable to a time slot overlapping with the last symbol of downlink reception.

[0060] In some embodiments, process 400 may involve processor 312 receiving a second offset value via MAC CE.

[0061] In some embodiments, the application of the second offset value can begin before the transmission of HARQ information.

[0062] In some embodiments, the offset value may include a cell-specific K-offset value or a UE-specific K-offset value.

[0063] In some embodiments, downlink reception may include SPS PDSCH reception.

[0064] In some embodiments, process 400 may involve processor 312 transmitting HARQ information on PUCCH or PUSCH.

[0065] In some embodiments, process 400 may involve processor 312 determining a time slot for transmitting HARQ information based on an offset value.

[0066] In some embodiments, process 400 may involve processor 312 acquiring an offset value in the DCI format for activating downlink reception.

[0067] In some embodiments, the offset value can be configured for NTN communication.

[0068] Additional notes

[0069] The described objects may sometimes show different components contained within or connected to different other components. It should be understood that these depicted architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same function can be effectively “associated” to achieve the desired functionality. Therefore, any two components combined in this document to achieve a specific function can be considered “associated” to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operationally connected” or “operationally coupled” to achieve the desired functionality, and any two components that can be suchly associated can also be considered “operationally coupled” to achieve the desired functionality. Specific examples of operational coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.

[0070] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed herein.

[0071] Furthermore, those skilled in the art will understand that, generally, the terms used herein, particularly in appended claims, such as the body portion of appended claims, are typically designed as “open” terms. For example, the word “comprising” should be interpreted as “comprising but not limited to,” the word “having” should be interpreted as “at least having,” and the word “including” should be interpreted as “including but not limited to,” etc. Those skilled in the art will also further understand that if a specific quantity introduced in a claim is explicitly mentioned, such intent will be explicitly stated in the claim, and without such a statement, such intent does not exist. For example, to aid understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce the claim statement. However, the use of these phrases should not be construed as implying that introducing a claim statement with the indefinite article “a” would limit any particular claim containing such an introductory claim statement to containing only one such statement, even if the same claim includes the introductory phrase “one or more” or “at least one” and the indefinite article “a,” for example, “a” should be interpreted as “at least one” or “one or more”; the same applies to definite articles used to introduce claim statements. Furthermore, even when a specific number of claims is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as at least the stated number. For example, stating only "two statements" without any other modifiers means at least two statements, or two or more statements. Additionally, when using conventions such as "at least one A, B, and C," this structure is generally understood by those skilled in the art. For example, "a system having at least one A, B, and C" includes, but is not limited to, a system having only A, a system having only B, a system having only C, a system having both A and B, a system having both A and C, a system having both B and C, and a system having both A, B, and C, etc. Similarly, when using conventions such as "at least one A, B, or C," this structure is generally understood by those skilled in the art. For example, "a system having at least one A, B, or C" includes, but is not limited to, a system having only A, a system having only B, a system having only C, a system having both A and B, a system having both A and C, a system having both B and C, and a system having both A, B, and C, etc. Those skilled in the art will further understand that virtually any extractive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to include the possibility of including one of the terms, including any one of the terms, or including both terms simultaneously. For example, the phrase “A or B” would be understood to include “A” or “B” or to include both “A” and “B”.

[0072] As can be seen from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and their true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: The device's processor receives at least one offset value configuration from the network node; The processor performs the downlink reception configured for this network node; The processor determines the offset value applicable to the time slot that overlaps with the last symbol received in the downlink; as well as The processor transmits the hybrid automatic repeat request information to the network node based on the offset value.

2. The method of claim 1, wherein receiving the at least one offset value configuration includes: The processor receives a first configuration of the first offset value before receiving the downlink; as well as The processor receives the second offset value after receiving the downlink and before transmitting the hybrid automatic repeat request information; and Determining this offset value includes: The processor determines that the first offset value is the offset value applicable to the time slot that overlaps with the last symbol received by the downlink.

3. The method of claim 2, wherein the second offset value is received via a control element of the media access control.

4. The method of claim 2, wherein the application time of the second offset value begins before the transmission of the hybrid automatic repeat request information.

5. The method of claim 1, wherein the offset value includes a cell-specific K-offset value or a user equipment-specific K-offset value.

6. The method of claim 1, wherein the downlink reception includes semi-persistent scheduling of physical downlink shared channel reception.

7. The method of claim 1, wherein the hybrid automatic repeat request information is transmitted on the physical uplink control channel or the physical uplink shared channel.

8. The method of claim 1, further comprising: The processor determines the time slot for transmitting the hybrid automatic repeat request information based on the offset value.

9. The method of claim 1, wherein the offset value is provided in the downlink control information format received when the downlink is activated.

10. The method of claim 1, wherein the offset value is a non-terrestrial network communication configuration.

11. An apparatus comprising: A transceiver that communicates wirelessly with at least one network node during operation; as well as The processor, communicatively coupled to the transceiver, performs the following operations during operation: Receive at least one offset configuration value from the network node through the transceiver; Perform downlink reception configured by the network node; Determine the offset value applicable to the time slot that overlaps with the last symbol received in the downlink; and The transceiver transmits the hybrid automatic repeat request information to the network node based on the offset value.

12. The device of claim 11, wherein during operation, the processor further performs the following operations: The transceiver receives a first configuration of the first offset value before receiving the downlink; as well as The transceiver receives the second offset value after the downlink reception and before the transmission of the hybrid automatic repeat request information; and In determining this offset value, the processor further performs the following operations: The first offset value is determined to be the offset value applicable to the time slot that overlaps with the last symbol received by the downlink.

13. The device of claim 12, wherein the second offset value is received via a control element of media access control.

14. The device of claim 12, wherein the application time of the second offset value begins before the transmission of the hybrid automatic repeat request information.

15. The device of claim 11, wherein the offset value includes a cell-specific K-offset value or a user equipment-specific K-offset value.

16. The apparatus of claim 11, wherein the downlink reception includes semi-persistent scheduling of physical downlink shared channel reception.

17. The device of claim 11, wherein the hybrid automatic repeat request information is transmitted on a physical uplink control channel or a physical uplink shared channel.

18. The device as claimed in claim 11, wherein, During operation, the processor further performs the following operations: The offset value determines the time slot used to transmit the hybrid automatic repeat request information.

19. The device of claim 11, wherein the offset value is provided in the downlink control information format received when activating the downlink.

20. The device of claim 11, wherein the offset value is a non-terrestrial network communication configuration.

Images