WO2022035827A1

WO2022035827A1 - Offsetting configured grant timer and configured grant retransmission timer with round-trip delay in ntn communications

Info

Publication number: WO2022035827A1
Application number: PCT/US2021/045348
Authority: WO
Inventors: Mehmet KUNT; Pradeep Jose; Abhishek Roy
Original assignee: MediaTek Singapore Pte Ltd
Current assignee: MediaTek Singapore Pte Ltd
Priority date: 2020-08-11
Filing date: 2021-08-10
Publication date: 2022-02-17
Anticipated expiration: 2023-02-11

Abstract

Various solutions for offsetting a configured grant timer and a configured grant retransmission timer with round-trip delay in non-terrestrial network (NTN) communications are described. An apparatus, implementable in a user equipment (UE), calculates a value of a user equipment (UE)-specific configured grant timer (CGT) based on a round-trip delay (RTD) between a UE and a network. The apparatus then performs a hybrid automatic repeat request (HARQ) procedure with a network using the UE-specific CGT (CGT_UE).

Description

OFFSETTING CONFIGURED GRANT TIMER AND CONFIGURED GRANT RETRANSMISSION TIMER WITH ROUND-TRIP DELAY IN NTN COMMUNICATIONS

CROSS REFERENCE TO RELATED PATENT APPLICATION(S)

[0001] The present disclosure is part of a non-provisional application claiming the priority benefit of U.S. Patent Application No. 63/063,991 , filed on 11 August 2020, the content of which being incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure is generally related to mobile communications and, more particularly, to offsetting a configured grant timer and a configured grant retransmission timer with round-trip delay in non-terrestrial network (NTN) communications.

BACKGROUND

[0003] Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.

[0004] In wireless communications, such as mobile communications under the 3^rd Generation Partnership Project (3GPP) specification(s) for 5^th Generation (5G) New Radio (NR), a configured grant timer (CGT) is used by a user equipment (UE) to wait for potential retransmission grants from a network after a transmission on a hybrid automatic repeat request (HARQ) process. The CGT is started after each transmission or retransmission (except for autonomous retransmission). When CGT expires, the UE assumes an

1

SUBSTITUTE SHEET (RULE 26) acknowledgement (ACK) for the HARQ process and so new data can overwrite a HARQ buffer. CGT is also used to protect the HARQ buffer between reception of an uplink (UL) grant and a transmission. The configured grant retransmission timer (CGRT), introduced in Release 16 (Rel-16) of the 3GPP specification for NR, is used by the UE to trigger autonomous retransmissions on CGs. In that regard, CGT is used to limit the number of autonomous retransmissions. Moreover, downlink feedback information (DFI) can be used to send an ACK from the network to the UE to stop the autonomous retransmissions. The durations of both CGT and CGRT are linked with a roundtrip delay (RTD) between the UE and the network (e.g. satellite or gNB), e.g., how long it takes for the UE to receive an UL grant for retransmission or DFI from the network. Generally, the durations of both CGT and CGRT should be longer than the RTD.

[0005] In NTN, the RTD can be large for low-Earth-orbit (LEO) and geosynchronous equatorial orbit (GEO) configurations. Additionally, different UEs can experience different RTDs (e.g., differential delay can be large). If CGT and CGRT values are common for all UEs, they could be configured to be greater than a maximum value for RTD. However, for some UEs such as those UEs with relatively smaller RTD (e.g., due to being close to the satellite), this situation could cause unnecessary delay in using the HARQ process for new data transmission. Therefore, there is a need for a solution to address this issue.

2

SUBSTITUTE SHEET (RULE 26) SUMMARY

[0006] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

[0007] An objective of the present disclosure is to propose solutions or schemes that address the issue(s) described herein. More specifically, various schemes proposed in the present disclosure are believed to provide solutions for offsetting a configured grant timer and a configured grant retransmission timer with round-trip delay in NTN communications.

[0008] In one aspect, a method may involve calculating a value of a UE- specific CGT based on a RTD between a DE and a network. The method may also involve performing a HARQ procedure with a network using the UE- specific CGT.

[0009] In another aspect, a method may involve calculating a value of a UE- specific CGRT based on a RTD between a UE and a network. The method may also involve performing a HARQ procedure with a network using the UE- specific CGRT.

[0010] In yet another aspect, an apparatus implementable in a UE may include a transceiver and a processor coupled to the transceiver. The transceiver may be configured to wirelessly communicate with a network. The processor may calculate a value of a UE-specific CGT based on a RTD

3

SUBSTITUTE SHEET (RULE 26) between the UE and the network. The processor may perform a HARQ procedure with the network using the UE-specific CGT.

[0011] It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as 5G/NR mobile communications, the proposed concepts, schemes and any variation(s)/derivative(s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (loT), Narrow Band Internet of Things (NB-loT), Industrial Internet of Things (lloT), vehicle- to-everything (V2X), and non-terrestrial network (NTN) communications. Thus, the scope of the present disclosure is not limited to the examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.

4

SUBSTITUTE SHEET (RULE 26) [0013] FIG. 1 is a diagram of an example network environment in which various proposed schemes in accordance with the present disclosure may be implemented.

[0014] FIG. 2 is a block diagram of an example communication apparatus and an example network apparatus in accordance with an implementation of the present disclosure.

[0015] FIG. 3 is a flowchart of an example process in accordance with an implementation of the present disclosure.

[0016] FIG. 4 is a flowchart of an example process in accordance with an implementation of the present disclosure.

DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

[0017] Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

Overview

5

SUBSTITUTE SHEET (RULE 26) [0018] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to offsetting a configured grant timer and a configured grant retransmission timerwith roundtrip delay in NTN communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.

[0019] FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented. Referring to FIG. 1 , network environment 100 may involve a DE 110 in wireless communication with a wireless network 120 (e.g., a 5G NR mobile network or another type of network such as an NTN). UE 110 may be in wireless communication with wireless network 120 via a network node 125 (e.g., an NTN network node such as a satellite). In network environment 100, UE 1 10 and wireless network 120 (via network node 125) may implement various schemes pertaining to offsetting a configured grant timer and a configured grant retransmission timer with round-trip delay in NTN communications, as described below.

[0020] In general, when a CGT is not running for a given HARQ process identifier (PID), the CG occasion may be used for a new data transmission. Moreover, CGT is started or restarted at the new data transmission or a retransmission (except for autonomous retransmission). When a CGRT expires, UE 1 10 may use a next CG occasion for autonomous retransmission,

6

SUBSTITUTE SHEET (RULE 26) indicating HARQ PID in CG uplink control information (CG-UCI). When CGT expires, the HARQ PID may be re-used for new data.

[0021] In terms of usage, CG may be used by data that requires some or all of the following: reliable transmission, as low latency as possible, and occasional and unpredictable UL data arrival. Examples of such data may include signaling radio bearer (SRB) and medium access control (MAC) control elements (CEs). Regarding reliable transmission, this is so that UL retransmission may be enabled and network node 125 may send retransmission grants. Regarding low latency, this is so that the periodicity of the CG is as small as possible. Regarding occasional and unpredictable UL data arrival, this is so that the CG occasions cannot be tied to UL data arrival easily. In such cases, it may be important to make the CG occasions available for new UL data (e.g., by utilizing them as much as possible). Due to large differential delay, it may be beneficial to have different UE behaviors for far and near UEs. Specifically, far UEs may need to wait for a potential UL retransmission grant from network 120 for a longer period of time, with the cost of lesser availability of CG occasions. For instance, a far UE (with larger RTD) may receive a retransmission grant for HARQ PID = 0 and may restart CGT ; as CGT is large, the UE may miss the next CG occasion for PID = 0 for new data (while waiting for a potential retransmission grant). On the other hand, near UEs may wait for a potential UL retransmission grant for a shorter period of time, with the advantage of more availability of CG occasions. For instance, a near UE (with smaller RTD) may receive a retransmission grant for HARQ PID = 0 and may restart a new CGT, or CGT’, which is smaller than a maximum CGT ; as CGT’ expires early, the UE may use the next CG occasion for PID = 0

7

SUBSTITUTE SHEET (RULE 26) for new data and, thus, may perform the new data transmission earlier than for a far UE. It is noteworthy that the distance between a UE (e.g., UE 110) and a network base station (e.g., network node 125) may change over time, as the UE and the satellite may move with respect to each other.

[0022] The above statements with respect to CG use cases may be applicable to CGRT. Specifically, far UEs may wait for a potential UL retransmission grant from network 120 for a longer period of time and, hence, may need to delay the autonomous retransmissions for a longer period of time. For instance, a far UE may miss more CG occasions for retransmission because CGT and CGRT may be running for a longer period of time (so that the UE may wait for a potential retransmission grant longer). On the other hand, near UEs may wait for a potential UL retransmission grant for a shorter period of time, thereby triggering autonomous retransmissions earlier, with potential latency and better CG resource utilization benefits. For instance, a near UE (with smaller RTD) may use a smaller CGRT, or CGRT’, which is smaller than a maximum CGRT and may enable autonomous retransmissions to be performed earlier; as CGRT’ expires earlier than for a far UE, the near UE may potentially perform more autonomous retransmissions.

[0023] Under a proposed scheme in accordance with the present disclosure, when UE 110 starts or restarts CGT (if configured) after a new transmission or retransmission, UE 110 may use a pre-compensation offset for CGT, which may be determined based on a current value of RTD calculated by UE 110. In other words, the value of CGT may be RTD-specific (herein interchangeably referred to as “UE-specific”) and may depend on the distance between UE 110 and network node 125. As an example, a base CGT value (CGT base) may be

8

SUBSTITUTE SHEET (RULE 26) configured by network 120 (e.g., via radio resource control (RRC) signaling). The CGTbase may be determined based on the processing delay of network 120 (e.g., the time it takes for network 120 to transmit an UL retransmission grant to UE 1 10 for a transport block (TB) not received correctly). UE 110 may calculate its pre-compensation offset (CGTuE_offset) for RTD. UE 110 may add the calculated pre-compensation offset to the CGT configured by network 120 to obtain the UE-specific CGT (CGTuE) for UE 110 as follows: CGTUE = CGTbase + CGTuE_offset. UE 110 may start or restart CGTUE when it performs a transmission or a retransmission (except for autonomous retransmission) using a HARQ process that is configured for a CG (and when UL HARQ retransmissions are enabled). Optionally, UE 1 10 may also use the value of CGTUE when UE 110 receives an UL grant for a HARQ process that is configured for a CG and when UE 110 receives an UL grant for its configured scheduling radio network temporary identifier (CS-RNTI) with a new data indicator (NDI) = 1 (retransmission). This is to prevent the HARQ buffer from being overwritten between an UL grant and an UL retransmission.

[0024] Under another proposed scheme in accordance with the present disclosure, when UE 110 starts or restarts CGRT (if configured) after a new transmission or retransmission, UE 1 10 may use a pre-compensation offset for CGRT, which may be determined based on a current value of RTD calculated by UE 110. In other words, the value of CGRT may be UE-specific and may depend on the distance between UE 110 and network node 125. As an example, a base CGRT value (CGRT base) may be configured by network 120 (e.g., via RRC signaling). The CGRTbase may be determined based on the processing delay of network 120 (e.g., the time it takes for network 120 to

9

SUBSTITUTE SHEET (RULE 26) transmit an UL retransmission grant to UE 110 for a transport block (TB) not received correctly). UE 110 may calculate its pre-compensation offset (CGRTuE_offset) for RTD. UE 1 10 may add the calculated pre-compensation offset to the CGRT configured by network 120 to obtain the UE-specific CGRT (CGRTUE) for UE 110 as follows: CGRTUE ⁼ CGRTbase + CGRTuE_offset. UE 110 may start or restart CGRTUE when it performs a transmission or a retransmission using a HARQ process that is configured for a CG (and when UL HARQ retransmissions are enabled).

[0025] Under yet another proposed scheme in accordance with the present disclosure, it may be useful in NTN communications to allow UE 110 to select and indicate a HARQ PID in CG-UCI, even if CGRT is not configured. Advantageously, this proposed scheme may provide more flexibility to UE 110 to use CG resources with dynamic RTD variation. Moreover, this proposed scheme may improve the utilization of CG resources.

Illustrative Implementations

[0026] FIG. 2 illustrates an example communication system 200 having at least an example apparatus 210 and an example apparatus 220 in accordance with an implementation of the present disclosure. Each of apparatus 210 and apparatus 220 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to offsetting a configured grant timer and a configured grant retransmission timer with roundtrip delay in NTN communications, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above, including network environment 100, as well as processes described below.

10

SUBSTITUTE SHEET (RULE 26) [0027] Each of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a network apparatus ora UE (e.g., UE 110), such as a portable or mobile apparatus, a wearable apparatus, a vehicular device or a vehicle, a wireless communication apparatus or a computing apparatus. For instance, each of apparatus 210 and apparatus 220 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Each of apparatus 210 and apparatus 220 may also be a part of a machine type apparatus, which may be an loT apparatus such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU), a wire communication apparatus or a computing apparatus. For instance, each of apparatus 210 and apparatus 220 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. When implemented in or as a network apparatus, apparatus 210 and/or apparatus 220 may be implemented in an eNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB or TRP in a 5G network, an NR network or an loT network.

[0028] In some implementations, each of apparatus 210 and apparatus 220 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex-instruction-set- computing (CISC) processors, or one or more reduced-instruction-set- computing (RISC) processors. In the various schemes described above, each of apparatus 210 and apparatus 220 may be implemented in or as a network

11

SUBSTITUTE SHEET (RULE 26) apparatus or a UE. Each of apparatus 210 and apparatus 220 may include at least some of those components shown in FIG. 2 such as a processor 212 and a processor 222, respectively, for example. Each of apparatus 210 and apparatus 220 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device), and, thus, such component(s) of apparatus 210 and apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.

[0029] In one aspect, each of processor 212 and processor 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 212 and processor 222, each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 212 and processor 222 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, 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 varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In otherwords, in at least some implementations, each of processor 212 and processor 222 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including those pertaining to offsetting a configured grant timer and a configured grant retransmission timer

12

SUBSTITUTE SHEET (RULE 26) with round-trip delay in NTN communications in accordance with various implementations of the present disclosure.

[0030] In some implementations, apparatus 210 may also include a transceiver 216 coupled to processor 212. Transceiver 216 may be capable of wirelessly transmitting and receiving data. In some implementations, transceiver 216 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs). In some implementations, transceiver 216 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications. In some implementations, apparatus 220 may also include a transceiver 226 coupled to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, transceiver 226 may be capable of wirelessly communicating with different types of UEs/wireless networks of different RATs. In some implementations, transceiver 226 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 226 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.

[0031] In some implementations, apparatus 210 may further include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein. In some implementations, apparatus

220 may further include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein. Each of memory

13

SUBSTITUTE SHEET (RULE 26) 214 and memory 224 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and/or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of memory 214 and memory 224 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM) and/or electrically erasable programmable ROM (EEPROM). Alternatively, or additionally, each of memory 214 and memory 224 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM) and/or phase-change memory.

[0032] Each of apparatus 210 and apparatus 220 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of apparatus 210, as a UE (e.g., UE 110), and apparatus 220, as a network node (e.g., network node 125) of a wireless network (e.g., network 120 as a 5G/NR mobile network), is provided below.

[0033] Under various proposed schemes in accordance with the present disclosure pertaining to offsetting a configured grant timer and a configured grant retransmission timer with round-trip delay in NTN communications, processor 212 of apparatus 210, implemented in or as UE 110, may determine or otherwise calculate a value of a UE-specific CGT (CGTUE) based on a RTD between apparatus 210 and a satellite (e.g., apparatus 220) of a network (e.g., network 120). Additionally, processor 212 may perform, via transceiver 216, a

14

SUBSTITUTE SHEET (RULE 26) HARQ procedure with the network (e.g., via apparatus 220) using the UE- specific CGT.

[0034] In some implementations, in calculating the value of the UE-specific CGT, processor 212 may calculate the UE-specific CGT as a sum of a base CGT (CGTbase) and a UE-specific offset (CGTuE_offset), expressed as: CGTUE = CGTb ase + CGTUE. offset-

10035] In some implementations, the base CGT may be configured by the network via RRC signaling (e.g., via apparatus 220). In some implementations, the base CGT may be configured by the network based on a processing delay of the network.

[0036] In some implementations, in calculating the value of the UE-specific CGT, processor 212 may perform certain operations. For instance, processor 212 may calculate a current value of the RTD. Moreover, processor 212 may determine the UE-specific offset based on the current value of the RTD.

[0037] In some implementations, processor 212 may also determine or otherwise calculate a value of a UE-specific CGRT (CGRTUE) based on a RTD between apparatus 210 and a satellite (e.g., apparatus 220) of a network (e.g., network 120). Furthermore, processor 212 may perform, via transceiver 216, a HARQ procedure with the network (e.g., via apparatus 220) using the UE- specific CGRT.

[0038] In some implementations, in calculating the value of the UE-specific CGRT, processor 212 may calculate the UE-specific CGRT as a sum of a base CGRT (CGRT base) and a UE-specific offset (CGRTuE_offset), expressed as: CGRTUE = CGRT_b ase + CGRTUE. offset-

15

SUBSTITUTE SHEET (RULE 26) [0039] In some implementations, the base CGRT may be configured by the network via RRC signaling (e.g., via apparatus 220). In some implementations, the base CGRT may be configured by the network based on a processing delay of the network.

[0040] In some implementations, in calculating the value of the UE-specific CGRT, processor 212 may perform certain operations. For instance, processor 212 may calculate a current value of the RTD. Moreover, processor 212 may determine the UE-specific offset based on the current value of the RTD.

Illustrative Processes

[0041] FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure. Process 300 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above, whether partially or entirely, including those pertaining to those described above. More specifically, process 300 may represent an aspect of the proposed concepts and schemes pertaining to offsetting a configured grant timer and a configured grant retransmission timer with round-trip delay in NTN communications. Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310 and 320. Although illustrated as discrete blocks, various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 300 may be executed in the order shown in FIG. 3 or, alternatively in a different order. Furthermore, one or more of the blocks/sub-blocks of process 300 may be executed iteratively. Process 300 may be implemented by or in apparatus 210 and apparatus 220 as well as any

16

SUBSTITUTE SHEET (RULE 26) variations thereof. Solely for illustrative purposes and without limiting the scope, process 300 is described below in the context of apparatus 210 as a UE (e.g., UE 110) and apparatus 220 as a communication entity such as a network node or satellite (e.g., network node 125) of a wireless network or NTN (e.g., wireless network 120). Process 300 may begin at block 310.

[0042] At 310, process 300 may involve processor 212 of apparatus 210 calculating a value of a UE-specific CGT (CGTUE) based on a RTD between apparatus 210 and a satellite (e.g., apparatus 220) of a network (e.g., network 120). Process 300 may proceed from 310 to 320.

[0043] At 320, process 300 may involve processor 212 performing, via transceiver 216, a HARQ procedure with the network (e.g., via apparatus 220) using the UE-specific CGT.

[0044] In some implementations, in calculating the value of the UE-specific CGT, process 300 may involve processor 212 calculating the UE-specific CGT as a sum of a base CGT (CGTbase) and a UE-specific offset (CGTuE_offset), expressed as: CGTUE ⁼ CGTbase ⁺ CGTUE_ offset-

[0045] In some implementations, the base CGT may be configured by the network via RRC signaling. In some implementations, the base CGT may be configured by the network based on a processing delay of the network.

[0046] In some implementations, in calculating the value of the UE-specific CGT, process 300 may involve processor 212 performing certain operations. For instance, process 300 may involve processor 212 calculating a current value of the RTD. Moreover, process 300 may involve processor 212 determining the UE-specific offset based on the current value of the RTD.

17

SUBSTITUTE SHEET (RULE 26) [0047] FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure. Process 400 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above, whether partially or entirely, including those pertaining to those described above. More specifically, process 400 may represent an aspect of the proposed concepts and schemes pertaining to offsetting a configured grant timer and a configured grant retransmission timer with round-trip delay in NTN communications. Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410 and 420. Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 400 may be executed in the order shown in FIG. 4 or, alternatively in a different order. Furthermore, one or more of the blocks/sub-blocks of process 400 may be executed iteratively. Process 400 may be implemented by or in apparatus 210 and apparatus 220 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 400 is described below in the context of apparatus 210 as a UE (e.g., DE 110) and apparatus 220 as a communication entity such as a network node or satellite (e.g., network node 125) of a wireless network or NTN (e.g., wireless network 120). Process 400 may begin at block 410.

[0048] At 410, process 400 may involve processor 212 of apparatus 210 calculating a value of a UE-specific CGRT (CGRTUE) based on a RTD between apparatus 210 and a satellite (e.g., apparatus 220) of a network (e.g., network 120). Process 400 may proceed from 410 to 420.

18

SUBSTITUTE SHEET (RULE 26) [0049] At 420, process 400 may involve processor 212 performing, via transceiver 216, a HARQ procedure with the network (e.g., via apparatus 220) using the UE-specific CGRT.

[0050] In some implementations, in calculating the value of the UE-specific CGRT, process 400 may involve processor 212 calculating the UE-specific CGRT as a sum of a base CGRT (CGRTbase) and a UE-specific offset (CGRTuE_offset), expressed as: CGRTUE ⁼ CGRTbase + CGRTuE_offset.

[0051] In some implementations, the base CGRT may be configured by the network via RRC signaling. In some implementations, the base CGRT may be configured by the network based on a processing delay of the network.

[0052] In some implementations, in calculating the value of the UE-specific CGRT, process 400 may involve processor 212 performing certain operations. For instance, process 400 may involve processor 212 calculating a current value of the RTD. Moreover, process 400 may involve processor 212 determining the UE-specific offset based on the current value of the RTD.

Additional Notes

[0053] The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or

19

SUBSTITUTE SHEET (RULE 26) intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable", to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0054] Further, with respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0055] Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim

20

SUBSTITUTE SHEET (RULE 26) recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an," e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more;” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms,

21

SUBSTITUTE SHEET (RULE 26) whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”

[0056] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

22

SUBSTITUTE SHEET (RULE 26)

Claims

CLAIMS What is claimed is:

1. A method, comprising: calculating a value of a user equipment (UE)-specific configured grant timer (CGT) based on a round-trip delay (RTD) between a UE and a network; and performing a hybrid automatic repeat request (HARQ) procedure with a network using the UE-specific CGT (CGTUE).

2. The method of Claim 1 , wherein the calculating of the value of the UE-specific CGT comprises calculating the UE-specific CGT as a sum of a base CGT (CGTbase) and a UE-specific offset (CGTuE_offset), expressed as:

CGTUE ⁼ CGTb ase + CGTuE_offset

3. The method of Claim 2, wherein the base CGT is configured by the network via radio resource control (RRC) signaling.

4. The method of Claim 3, wherein the base CGT is configured by the network based on a processing delay of the network.

5. The method of Claim 2, wherein the calculating of the value of the UE-specific CGT further comprises: calculating a current value of the RTD; and determining the UE-specific offset based on the current value of the RTD.

23

SUBSTITUTE SHEET (RULE 26)

6. A method, comprising: calculating a value of a user equipment (UE)-specific configured grant retransmission timer (CGRT) based on a round-trip delay (RTD) between a DE and a network; and performing a hybrid automatic repeat request (HARQ) procedure with a network using the UE-specific CGRT (CGRTUE).

7. The method of Claim 6, wherein the calculating of the value of the UE-specific CGRT comprises calculating the UE-specific CGRT as a sum of a base CGRT (CGRT base) and a UE-specific offset (CGRTuE_offset), expressed as:

CGRTUE = CGRT_b ase + CGRTUE. offset-

8. The method of Claim 7, wherein the base CGRT is configured by the network via radio resource control (RRC) signaling.

9. The method of Claim 8, wherein the base CGRT is configured by the network based on a processing delay of the network.

10. The method of Claim 7, wherein the calculating of the value of the UE-specific CGRT further comprises: calculating a current value of the RTD; and determining the UE-specific offset based on the current value of the RTD.

24

SUBSTITUTE SHEET (RULE 26)

11. An apparatus implementable in a user equipment (UE), comprising: a transceiver configured to wirelessly communicate with a network; and a processor coupled to the transceiver and configured to perform operations comprising: calculating a value of a UE-specific configured grant timer (CGT) based on a round-trip delay (RTD) between the UE and the network; and performing, via the transceiver, a hybrid automatic repeat request

(HARQ) procedure with a network using the UE-specific CGT (CGTUE).

12. The apparatus of Claim 11 , wherein, in calculating the value of the UE-specific CGT, the processor calculated the UE-specific CGT as a sum of a base CGT (CGT base) and a UE-specific offset (CGTuE_offset), expressed as:

CGTUE ⁼ CGTb ase + CGTuE_offset

13. The apparatus of Claim 12, wherein the base CGT is configured by the network via radio resource control (RRC) signaling.

14. The apparatus of Claim 13, wherein the base CGT is configured by the network based on a processing delay of the network.

15. The apparatus of Claim 12, wherein, in calculating the value of the UE-specific CGT, the processor further performs operations comprising: calculating a current value of the RTD; and determining the UE-specific offset based on the current value of the RTD.

25

SUBSTITUTE SHEET (RULE 26)

16. The apparatus of Claim 11 , wherein the processor is further configured to perform operations comprising: calculating a value of a UE-specific configured grant retransmission timer (CGRT) based on a round-trip delay (RTD) between the UE and the network; and performing, via the transceiver, the HARQ procedure with a network using the UE-specific CGRT (CGRTUE).

17. The apparatus of Claim 16, wherein, in calculating the value of the UE-specific CGRT, the processor calculates the UE-specific CGRT as a sum of a base CGRT (CGRTbase) and a UE-specific offset (CGRTuE_offset), expressed as:

CGRTUE = CGRT_b ase + CGRTUE. offset-

18. The apparatus of Claim 17, wherein the base CGRT is configured by the network via radio resource control (RRC) signaling.

19. The apparatus of Claim 18, wherein the base CGRT is configured by the network based on a processing delay of the network.

20. The apparatus of Claim 17, wherein, in calculating the value of the UE-specific CGRT, the processor further performs operations comprising: calculating a current value of the RTD; and determining the UE-specific offset based on the current value of the RTD.

26

SUBSTITUTE SHEET (RULE 26)