Hybrid automatic repeat request disabling

By disabling the signaling mechanism of HARQ feedback in IoT NTN, the data rate reduction and power consumption problems caused by HARQ stagnation are solved, and more efficient data transmission and connection time optimization are achieved.

CN119096495APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202380036816.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-28
Filing Date
2023-04-21
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the Third Generation Partnership Program (3GPP) Internet of Things (IoT) Non-terrestrial Network (NTN), hybrid automatic retransmission request (HARQ) feedback may stall, resulting in reduced data rates and it is difficult for prior art to effectively disable HARQ feedback To reduce power consumption and connection time.

Method used

Radio Resource Control (RRC) signaling and Dynamic Control Information (DCI) are used to configure and indicate whether the user equipment (UE) disables HARQ feedback by disabling signaling mechanisms in IoT NTN, including in PDSCH or PUSCH configurations Add a Disable field and use a different radio network temporary identifier (RNTI) to mask cyclic redundancy check (CRC) to indicate the enable or disable of the HARQ procedure.

Benefits of technology

Effectively prevent HARQ stagnation, reduce power consumption, improve data rate, optimize connection time, and improve IoT NTN performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096495A_ABST
    Figure CN119096495A_ABST
Patent Text Reader

Abstract

The present application relates to devices and components, including apparatuses, systems, and methods for providing hybrid automatic repeat request disablement in a wireless communication system.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 336,276, filed on April 28, 2022, entitled “Hybrid Automatic Repeat Request Disablement,” the disclosure of which is incorporated herein by reference in its entirety for all purposes. Technical Field

[0003] The present application relates to the field of wireless technology, and in particular to providing hybrid automatic repeat request disabling in a wireless communication system. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) network provides methods for verifying communications and / or operations between a base station and a user equipment (UE). One of these methods is hybrid automatic repeat request (HARQ) feedback. The UE reports HARQ feedback to the base station to indicate that the communication has been correctly received and / or the operation has been correctly performed. The base station monitors the HARQ feedback from the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 A signal diagram illustrating an example of signaling to disable hybrid automatic repeat request (HARQ) feedback according to some embodiments.

[0006] Figure 2 A diagram showing an example of masking a cyclic redundancy check (CRC) to indicate whether HARQ feedback is to be enabled or disabled is illustrated in accordance with some embodiments.

[0007] Figure 3 An example procedure for dynamic disabling per downlink control information (DCI) using a radio network temporary identifier (RNTI) to indicate whether HARQ feedback is to be disabled is illustrated in accordance with some embodiments.

[0008] Figure 4 An example procedure for hybrid signaling operation according to some embodiments is illustrated.

[0009] Figure 5 A signal diagram illustrating HARQ-Acknowledgement (ACK) reporting according to some embodiments.

[0010] Figure 6 Example information elements including codebooksizeDetermination-r13 according to some embodiments are illustrated.

[0011] Figure 7Example information elements including codebooksizeDeterminationSTTI according to some embodiments are illustrated.

[0012] Figure 8 An example diagram illustrating a HARQ-ACK bundling scenario according to some embodiments is illustrated, where a portion of the HARQ process disables HARQ feedback.

[0013] Fig. 9 A Physical Downlink Shared Channel (PDSCH) timing representation is illustrated according to some embodiments.

[0014] Fig.10 Example procedures for operating a base station in an Internet of Things (IoT) non-terrestrial network (NTN) according to some embodiments are illustrated.

[0015] Fig.11 Example procedures for operating a user equipment (UE) in an IoT NTN according to some embodiments are illustrated.

[0016] Fig.12 A network environment according to some embodiments is illustrated.

[0017] Fig.13 An example UE according to some embodiments is illustrated.

[0018] Fig.14 An example next generation Node B (gNB) according to some embodiments is illustrated. DETAILED DESCRIPTION

[0019] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the descriptions of various embodiments are not obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0020] The following is a glossary of terms that may be used in this disclosure.

[0021] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0022] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0023] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0024] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0025] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0026] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0027] As used herein, the term "channel" refers to any tangible or intangible transmission medium for delivering data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is delivered. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.

[0028] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0029] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0030] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0031] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0032] In conventional 3rd Generation Partnership Project (3GPP) Internet of Things (IoT) non-terrestrial networks (NTNs), hybrid automatic repeat request (HARQ) feedback is used to indicate that a signal has been correctly received. However, in some instances, HARQ may stagnate, resulting in reduced data rates and negatively impacting performance. Therefore, in some instances, it may be desirable to disable HARQ feedback to prevent HARQ stagnation. In addition, disabling HARQ feedback can reduce power consumption and connection time. A method for disabling HARQ feedback in an IoT NTN is disclosed herein.

[0033] Information: IoT NTN

[0034] In Release 18, the IoT NTN work item description aims to make IoT-NTN performance enhancements in Release 18 (Rel-18) to address issues left over from Release 17 (Rel-17). This disclosure considers Rel-17 IoT-NTN as a baseline as well as Rel-17 NR-NTN results. Further IoT-NTN performance enhancement goals include: 1) disabling HARQ feedback to mitigate the impact of HARQ stalling on user equipment (UE) data rate [Radio Access Network Working Group 1 (RAN1), Radio Access Network Working Group 2 (RAN2)]; 2) studying and specifying improved Global Navigation Satellite System (GNSS) operation, if necessary, to achieve new position fixes for UE pre-compensation during long connection times and to achieve reduced power consumption. Simultaneous GNSS and NTN narrowband IoT (NB-IoT) / enhanced machine type communication (eMTC) operation is not assumed. [RAN1]. Note: After the improvement requirements are concluded, the core requirements of Radio Access Network Working Group 4 (RAN4) to achieve this goal may be identified.

[0035] Information: Rel-17 New Radio (NR) NTN

[0036] In 3GPP Release 17 NR NTN, the following agreement related to HARQ feedback disabling has been reached. The enabling / disabling of HARQ feedback for downlink transmissions should be configurable per HARQ process at least via UE-specific Radio Resource Control (RRC) signaling. Confirm the previous working assumption of X=T_proc,1, where X is defined as the time from the end of reception of the last Physical Downlink Shared Channel (PDSCH) or slot-aggregated PDSCH for a given HARQ process with disabled feedback to the start of a Physical Downlink Control Channel (PDCCH) carrying Downlink Control Information (DCI) scheduling another PDSCH or another set of slot-aggregated PDSCHs for the given HARQ process, or a PDSCH without a corresponding PDCCH. For DCI of PDSCH with HARQ process with disabled feedback in Rel-17, the bit fields related to hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback (i.e., physical uplink control channel resource index (PRI), physical uplink shared channel (PUSCH) to HARQ_feedback timing, downlink assignment index (DAI)) are unchanged, with the interpretation from the UE being the same as for HARQ process with feedback enabled. For HARQ feedback for each semi-persistent scheduling (SPS) PDSCH, the UE follows the per-process configuration of HARQ feedback enabled / disabled for the associated HARQ process, except for the first SPS PDSCH after activation when HARQ feedback for SPS activation is additionally enabled. For Type 1 HARQ codebook, the UE will consistently report negative acknowledgement (NACK) only for HARQ process with disabled feedback, regardless of the decoding result of the corresponding PDSCH. For Type 2 HARQ codebook in NTN: Reduce the codebook size by using a HARQ-ACK codebook that includes only HARQ-ACK for PDSCH with HARQ process enabled feedback. Details of the counter downlink assignment index (C-DAI) and total downlink assignment index (T-DAI) counts for DCI of PDSCH with HARQ process enabled / disabled feedback are available for further study.

[0037] Release statement

[0038] General question: How to support disabling HARQ feedback in IoT NTN? In some embodiments, signaling to disable HARQ feedback may support disabling of HARQ feedback in IoT NTN. Signaling to disable HARQ feedback may be semi-static or dynamic. For example, a user equipment (UE) (such as UE 1204 ( Fig.12 )、UE 1206( Fig.12 ) and / or UE 1300( Fig.13)) may provide a base station (such as base station 1208 ( Fig.12 )、Base Station 1212( Fig.12 ) and / or gNB 1400( Fig.14 )) provides signaling to disable HARQ feedback.

[0039] In some embodiments, HARQ-ACK reporting with HARQ disabled for feedback may support disabling of HARQ feedback in IoT NTNs. The HARQ-ACK reporting may include HARQ-ACK codebook construction with transmission time interval (TTI) bundling, and / or HARQ-ACK reporting with channel selection.

[0040] In some embodiments, HARQ with disabled feedback in SPS may support disabling of HARQ feedback in IoT NTN. HARQ with disabled feedback in SPS may include SPS activation, SPS release and / or SPS PDSCH. In some embodiments, processing time constraints in the case of HARQ with disabled feedback may support disabling of HARQ feedback in IoT NTN.

[0041] Method 1: Disable HARQ feedback signaling

[0042] Method 1: Signaling to disable HARQ feedback The signaling to disable HARQ feedback may include both a downlink (DL) HARQ process and an uplink (UL) HARQ process. Figure 1 A signal diagram 100 illustrating an example of signaling to disable HARQ feedback according to some embodiments. Specifically, the signal diagram 100 illustrates signaling that may be performed to indicate whether HARQ feedback is to be disabled in an IoT NTN.

[0043] Signal diagram 100 includes base station 102. Base station 102 may include base station 1208 ( Fig.12 )、Base Station 1212( Fig.12 ) and / or gNB 1400( Fig.14 )'s features. The base station 102 may be part of an NTN serving IoT UEs.

[0044] Signal diagram 100 also includes UE 104. UE 104 may include UE 1204 ( Fig.12 )、UE 1206( Fig.12 ) and / or UE1300( Fig.13 ) features. UE 104 can operate as part of an IoT NTN. For example, in the illustrated embodiment, base station 102 can provide services to UE 104 as part of an IoT NTN.

[0045] The base station 102 may transmit a control transmission 106 to the UE 104. The control transmission 106 may indicate whether HARQ feedback is to be disabled for communications between the UE 104 and the base station 102. For example, the control transmission 106 may include one or more of the elements described in Alternative 1, Alternative 2, and / or Alternative 3 below to indicate whether HARQ feedback is to be disabled.

[0046] Alternative Solution 1: Configure feedback disabling according to HARQ process number. In the UE-specific configuration of PDSCH or PUSCH, HARQ feedback is disabled according to the HARQ process. For example, the control transmission 106 transmitted from the base station 102 to the UE 104 may include a process number corresponding to the HARQ process for which HARQ feedback will be disabled. In the information element (IE) of "PDSCH-ConfigDedicated" or "PUSCH-ConfigDedicated", a field indicating the disabling of HARQ feedback is added. For example, the control transmission 106 may include a PDSCH-ConfigDedicated information element or a PUSCH-ConfigDedicated information element. The PDSCH-ConfigDedicated information element or the PUSCH-ConfigDedicated information element in the control transmission 106 may include an indication that the HARQ process will be disabled. In addition, the PDSCH-ConfigDedicated information element or the PUSCH-ConfigDedicated information element may include a HARQ process number corresponding to the HARQ process to be disabled.

[0047] In alternative 1, for a DCI with a HARQ process configured with disabled feedback, the "Downlink Assignment Index" (DAI) field is not used by the UE, or is reinterpreted by the UE. For example, when HARQ process feedback has been disabled, the UE may not use the DAI field, or the bits previously used for the DAI field may be used for other information. The "HARQ-ACK Delay" field and the "HARQ-ACK Resource Offset" field are not used by the UE, or are reinterpreted by the UE. For example, in some embodiments, when HARQ feedback has been disabled, the UE may not use the HARQ-ACK Delay field and the HARQ-ACK Resource Offset field. In addition, when HARQ process feedback has been disabled, the UE may use the bits previously used for the HARQ-ACK Delay field and the HARQ-ACK Resource Offset field for other information. The "Transport Block in Combined Packet" field and the "HARQ-ACK Bundling Flag" field are not used by the UE, or are reinterpreted by the UE. For example, in some embodiments, when HARQ feedback has been disabled, the UE may not use the Transport Block in Combined Packet field and the HARQ-ACK Bundling Flag field. Additionally, when HARQ process feedback has been disabled, the UE may use bits previously used for the transport block field and the HARQ-ACK bundling flag field in the combined packet for other information. For disabled UL HARQ processes, the UE ignores the "new data indicator" field in the UL grant and the physical channel hybrid automatic repeat request indicator channel (PHICH). For example, when the UL HARQ process is disabled, the UE may ignore the new data indicator field in the UL grant and PHICH.

[0048] Alternative 2: Dynamic disabling per DCI. For example, a control transmission 106 transmitted from the base station 102 to the UE 104 may include a DCI indicating that HARQ feedback is to be disabled for a HARQ process. Specifically, the DCI may schedule a HARQ process, wherein the DCI may indicate whether the scheduled HARQ process is to disable HARQ feedback for the HARQ process.

[0049] Option 1 of Alternative 2: An explicit 1-bit field to indicate whether feedback will be disabled for a HARQ process scheduled by the DCI. For example, the DCI included in the control transmission 106 may include a field indicating whether a HARQ process scheduled by the DCI will disable HARQ feedback corresponding to the HARQ process. The field in the DCI may be a 1-bit field, where one value of the 1-bit field may indicate that HARQ feedback will be provided, and another value of the 1-bit field may indicate that HARQ feedback will be disabled.

[0050] Option 2 of Alternative 2: Use a different radio network temporary identifier (RNTI) (different from the cell radio network temporary identifier (C-RNTI)) to indicate whether feedback will be disabled for the HARQ process scheduled by the DCI. For example, the control transmission 106 may include a cyclic redundancy check (CRC) corresponding to the DCI. The CRC may be masked by the RNTI. The base station 102 may use different RNTI values ​​in the CRC mask to indicate whether HARQ feedback will be disabled for the HARQ process being scheduled by the DCI. In some embodiments, the base station 102 may use the C-RNTI to mask the DCI CRC of the corresponding cell to indicate that the HARQ process will enable HARQ feedback, and may use a different RNTI from the C-RNTI to mask the DCI CRC to indicate that the HARQ process will disable HARQ feedback.

[0051] Further to Option 2 of Alternative 2: Cyclic Redundancy Check (CRC) masked with RNTI. Option 2: UE procedure to determine whether to enable or disable HARQ feedback for current downlink data transmission. For example, the base station 102 may mask the CRC with the RNTI to indicate whether HARQ feedback will be enabled or disabled for DL ​​data transmission.

[0052] Further to Option 3 of Alternative 2: A code point of an existing field is used to indicate whether feedback is to be disabled for a HARQ process scheduled by the DCI. For example, the field "HARQ-ACK Delay" or the field "HARQ-ACK Resource Offset" may have a code point indicating that HARQ-ACK feedback is disabled. The DCI included in the control transmission 106 may cause the code point of the HARQ-ACK Delay field or the code point of the HARQ-ACK Resource Offset to be set to a specific value to indicate whether HARQ-ACK feedback is disabled.

[0053] Figure 2 A diagram 200 is illustrated showing an example of masking a CRC for indicating whether HARQ feedback is to be enabled or disabled according to some embodiments. For example, diagram 200 illustrates a method that may be performed by a base station, such as base station 102 ( Figure 1 )) to a UE (such as UE104 ( Figure 1 ))A block transmitted to indicate whether HARQ feedback will be enabled or disabled for DL ​​data transmission.

[0054] Diagram 200 includes a first DCI 202. A base station may generate a DCI to be included in a control transmission (such as control transmission 106 ( Figure 1 )) for transmission to the UE. The first DCI 202 may be used to schedule the HARQ process. A DL data transmission related to the HARQ process may be transmitted by the base station to the UE after the HARQ process has been completed.

[0055] Diagram 200 also includes a first CRC 204. The first CRC 204 may correspond to the first DCI 202, wherein the first CRC 204 and the first DCI 202 may be transmitted in the same control transmission. The first CRC 204 may be a CRC for the first DCI 202.

[0056] Diagram 200 also includes RNTI 206. RNTI 206 may include a different RNTI than the C-RNTI corresponding to first DCI 202. The UE may mask first CRC 204 with RNTI 206 to indicate that HARQ feedback corresponding to the HARQ process being scheduled by first DCI 202 is to disable the HARQ feedback.

[0057] Diagram 200 also includes a second DCI 208 and a second CRC 210. The second DCI 208 and the second CRC 210 may be outputs of the base station based on the first DCI 202, the first CRC 204, and / or the RNTI 206. For example, the second DCI 208 and the second CRC 210 may be DCI and CRC, respectively, transmitted by the base station to the UE to indicate whether HARQ feedback will be disabled for the HARQ process. The second DCI 208 may be equivalent to the first DCI 202. The second CRC 210 may be the result of the base station deciding whether to mask the first CRC 204 with the RNTI 206. For example, if the base station is indicating that HARQ feedback will be enabled, the second CRC 210 may be equivalent to the exclusive OR (XOR) of the first CRC 204 and the C-RNTI. However, if the base station is indicating that HARQ feedback is to be disabled, the second CRC 210 may be equivalent to the XOR of the first CRC 204 and the RNTI 206 instead of the C-RNTI to indicate that HARQ feedback is to be disabled. The UE may receive the second DCI 208 and the second CRC 210 and determine whether HARQ feedback is to be enabled or disabled for the current downlink data transmission.

[0058] Figure 3 An example procedure 300 is illustrated for dynamic disabling per DCI using RNTI to indicate whether HARQ feedback is to be disabled according to some embodiments. Specifically, procedure 300 presents a method that can be performed by a UE (such as UE 104 ( Figure 1 )) based on a slave base station (such as base station 102 ( Figure 1 )) received control transmission, wherein RNTI is used to indicate whether HARQ feedback will be disabled according to the dynamic disabling of DCI.

[0059] The process 300 may include receiving a PDCCH at 302. For example, the UE may receive a control transmission from a base station via the PDCCH. The control transmission may include a DCI (such as the second DCI 208 ( Figure 2 )) and a CRC corresponding to the DCI (such as the second CRC 210 ( Figure 2 )).

[0060] Procedure 300 may include checking whether the PDCCH CRC is masked by the C-RNTI or a different RNTI at 304. For example, the CRC received via the PDCCH may include the RNTI. The UE may determine whether the RNTI included in the CRC is the C-RNTI corresponding to the UE or a RNTI different from the C-RNTI.

[0061] Procedure 300 may include applying HARQ-ACK feedback if the CRC is masked with the C-RNTI, or not applying HARQ-ACK feedback if the CRC is masked with an RNTI different from the C-RNTI. For example, the UE may determine whether to enable or disable HARQ feedback (also referred to as HARQ-ACK feedback) based on the RNTI determination of 304. If the UE determines in 304 that the CRC includes the C-RNTI (also referred to as masking with the C-RNTI), the UE may determine that HARQ feedback is to be enabled for the corresponding HARQ process. If the UE determines that the CRC includes an RNTI different from the C-RNTI, the UE may determine that HARQ feedback is to be disabled for the corresponding HARQ process.

[0062] Alternative Solution 3: Hybrid Signaling. Enabled by RRC configuration according to HARQ process number. For HARQ process numbers that enable RRC configuration, dynamic disabling via DCI is supported. For example, the RRC configuration provided by the base station 102 to the UE 104 may indicate which HARQ process will switch between enabling HARQ feedback and disabling HARQ feedback. Subsequently, the base station 102 may transmit a DCI transmission 108 to the UE 104 to switch between enabling HARQ feedback and disabling HARQ feedback. In some embodiments, once disabled, the UE 104 may continue to operate with HARQ feedback disabled until the base station 102 transmits another DCI transmission indicating that HARQ feedback will be enabled. In other embodiments, the UE may operate with HARQ feedback disabled for the HARQ process corresponding to the DCI transmission, and may switch back to enabling HARQ feedback when the HARQ process is completed. Option 3: Determine whether to enable or disable the UE procedure for HARQ feedback for the current downlink data transmission.

[0063] Figure 4An example procedure 400 is illustrated for hybrid signaling operations according to some embodiments. Specifically, the procedure 400 presents a method that can be performed by a UE (such as UE 104 ( Figure 1 ))Operations performed based on hybrid signaling provided by the base station.

[0064] Procedure 400 may include receiving an RRC configuration regarding whether HARQ feedback is enabled or disabled for a HARQ process number at 402. For example, a base station may transmit an RRC configuration to a UE indicating a HARQ process number for a HARQ process for which HARQ feedback is to be enabled or disabled. In some embodiments, the RRC configuration may also indicate whether HARQ feedback is to be enabled or disabled for the HARQ process based on the RRC configuration. For the description of procedure 400, the RRC configuration may have indicated that HARQ feedback is enabled for the HARQ process based on the RRC configuration at 402.

[0065] Procedure 400 may include receiving a DCI that schedules downlink data transmission using a HARQ process number. For example, the UE may receive the DCI from a base station. The DCI may schedule downlink data transmission using a HARQ process number. In some examples, the HARQ process number may be the same HARQ process number as the HARQ process number in the RRC configuration in 402.

[0066] Procedure 400 may include, at 406, if the HARQ process number is configured with enabling HARQ feedback, and if the DCI does not otherwise indicate HARQ feedback disabling, considering enabling HARQ feedback for downlink transmission. Otherwise, procedure 400 may include considering disabling HARQ feedback for downlink transmission at 406. For example, the UE may be scheduled to perform a HARQ process corresponding to a HARQ process number provided in an RRC configuration and / or a DCI. The UE may determine whether to enable or disable HARQ feedback based on the RRC configuration and / or the DCI. For example, the UE may initially determine whether to enable or disable HARQ feedback for a HARQ process based on the RRC configuration. Subsequently, the UE may determine whether a DCI has been received indicating whether HARQ feedback will be enabled or disabled for the HARQ process, or whether the HARQ feedback will change from the HARQ feedback indication provided in the RRC configuration. If the UE determines that the RRC configuration has indicated that HARQ feedback is to be enabled for the HARQ process and has not received a DCI indicating that HARQ feedback is to be disabled for the HARQ process, the UE may determine that HARQ feedback is to be enabled for downlink transmissions. If the UE determines that the RRC configuration has indicated that HARQ feedback is to be disabled for the HARQ process and has not received a DCI indicating that HARQ feedback is to be enabled for the HARQ process, the UE may determine that HARQ feedback is to be disabled for downlink transmissions. If the UE determines that a DCI indicating that HARQ feedback is to be enabled or disabled has been received for the HARQ process, the UE may determine whether HARQ feedback is to be enabled or disabled for downlink transmissions based on the indication from the DCI.

[0067] Method 2: HARQ-ACK reporting

[0068] Method 2: HARQ-ACK reporting. Specifically, a UE (such as UE 104 ( Figure 1 )) may provide a base station (such as base station 102 ( Figure 1 ))Report HARQ-ACK. Figure 5 A signal diagram 500 is illustrated for HARQ-ACK reporting according to some embodiments.

[0069] Signal diagram 500 includes base station 502. Base station 502 may include base station 102 ( Figure 1 )'s features. The base station 502 may be part of an NTN serving IoT UEs.

[0070] Signal diagram 500 also includes UE 504. UE 504 may include UE 104 ( Figure 1) features. UE 504 can operate as part of an IoT NTN. For example, in the illustrated embodiment, base station 502 can provide services to UE 504 as part of an IoT NTN.

[0071] Base station 502 may transmit control transmission 506 to UE 504. Control transmission 506 may indicate whether HARQ feedback is to be disabled for communications between UE 504 and base station 502. In an embodiment, control transmission 506 may include any of the features and / or embodiments of method 1 described above.

[0072] UE 504 may receive control transmission 506 and perform a HARQ process related to control transmission 506. UE 504 may generate uplink transmission 508 based on control transmission 506. For example, UE 504 may generate uplink transmission 508 based on whether control transmission 506 indicates whether HARQ feedback will be enabled or disabled. Uplink transmission 508 may include one or more of the features of Method 2 (including Method 2-1 and / or Method 2-2).

[0073] Method 2-1: Dynamic HARQ-ACK codebook construction. For example, the HARQ-ACK codebook construction for feedback from the UE to the base station can be dynamic, depending on whether the HARQ feedback will be enabled or disabled. The dynamic HARQ-ACK codebook construction can be implemented for physical uplink control channel (PUCCH) format 3 or 4 or 5. Configuration of codebooksizeDetermination-r13=dai or codebooksizeDeterminationSTTI=dai. For example, the dynamic HARQ-ACK codebook construction may affect codebooksizeDetermination-r13=dai or codebooksizeDeterminationSTTI=dai.

[0074] Figure 6 An example information element 600 including codebooksizeDetermination-r13 602 according to some embodiments is illustrated. The codebooksizeDetermination-r13 602 may differ based on whether HARQ feedback is enabled or disabled. Figure 7 An example information element 700 including a codebooksizeDeterminationSTTI 702 according to some embodiments is illustrated. The codebooksizeDeterminationSTTI 702 may differ based on whether HARQ feedback is enabled or disabled.

[0075] If the HARQ process is configured with enabled feedback, the HARQ codebook includes corresponding bits. For example, a control transmission (such as control transmission 506) may indicate that HARQ feedback will be enabled for the HARQ process. A UE (such as UE 504) may determine, based on the control transmission, that HARQ feedback will be enabled for the HARQ process. The UE may generate an uplink transmission (such as uplink transmission 508) with a HARQ codebook that includes bits corresponding to the HARQ feedback for the HARQ process. Thus, in such an instance, codebooksizeDetermination-r13 and / or codebooksizeDeterminationSTTI may include bits corresponding to the HARQ feedback for the HARQ process.

[0076] Alternative 1: If the HARQ process is configured with disabled feedback, the HARQ codebook does not include corresponding bits. For example, a control transmission (such as control transmission 506) may indicate that HARQ feedback will be disabled for the HARQ process. A UE (such as UE 504) may determine, based on the control transmission, that HARQ feedback will be disabled for the HARQ process. The UE may generate an uplink transmission (such as uplink transmission 508) with a HARQ codebook that does not include bits corresponding to the HARQ feedback for the HARQ process. Thus, in such an instance, codebooksizeDetermination-r13 and / or codebooksizeDeterminationSTTI may omit bits corresponding to the HARQ feedback for the HARQ process.

[0077] Refer to the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 36.213 of the 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer Procedures (referred to herein as "TS 36.213") which may define the dynamic HARQ-ACK codebook construction of Alternative 1. Section 7.3.1 of TS 36.213:

[0078] When s < S

[0079] When Time

[0080] If there is a PDSCH providing a transport block (TB) with enabled HARQ-ACK information for the HARQ process on serving cell c associated with the PDCCH / enhanced physical downlink control channel (EPDCCH) / short physical downlink control channel (SPDCCH), or there is a PDCCH / EPDCCH / SPDCCH indicating downlink SPS release on serving cell c for which HARQ-ACK is transmitted in subframe / time slot / subslot n, or ...

[0081] Specifically, this section of TS 36.213 may indicate that this section is for a TB of a HARQ process with enabled HARQ-ACK information. In TS 36.213 Section 7.3.1, s is a subslot index, which may be set to 3 for subslot PDSCH operation with higher layer parameters dl-TTI-length = "subslot" and ul-TTI-length = "slot", or may be set to 2 for subframe PDSCH operation with a configured higher layer parameter shortProcessingTime, otherwise set to 1, c is a cell index, and Can be set to the number of cells configured for the UE by higher layers.

[0082] Alternative 2: If the HARQ process is configured with disabled feedback, the corresponding HARQ bit is always NACK. For example, a control transmission (such as control transmission 506) may indicate that HARQ feedback is to be disabled for the HARQ process. A UE (such as UE 504) may determine that HARQ feedback is to be disabled for the HARQ process based on the control transmission. The UE may generate an uplink transmission (such as uplink transmission 508) with a HARQ codebook, wherein the HARQ feedback is set to NACK for the HARQ process. Therefore, in this example, codebooksizeDetermination-r13 and / or codebooksizeDeterminationSTTI may have a NACK value corresponding to the HARQ feedback for the HARQ process.

[0083] For the HARQ-ACK bundling case (HARQ with transmission time interval (TTI) bundling): For half-duplex frequency division duplex (FDD) operation, in the corresponding DCI, "ce-HARQ-AckBundling" is configured and the "HARQ-ACK bundling flag" is set to 1. General principle: If some HARQ processes in "HARQ with TTI bundling" have disabled feedback and some HARQ processes in HARQ with TTI bundling have enabled feedback, the HARQ-ACK bits corresponding to the HARQ processes with disabled feedback are considered ACK, which means that the final logical AND operation is not affected.

[0084] Figure 8 An example diagram 800 illustrating a HARQ-ACK bundling scenario according to some embodiments is illustrated, wherein a portion of the HARQ process disables HARQ feedback. Specifically, diagram 800 illustrates HARQ-ACK bundling for HARQ feedback of multiple HARQ processes, wherein a portion of the HARQ process disables HARQ feedback. HARQ-ACK bundling may be performed by a UE (such as UE 104( Figure 1 ) and / or UE 504( Figure 5 )) is performed, and the UE can send a HARQ-ACK bundling to a base station (such as base station 102 ( Figure 1 ) and / or base station 502 ( Figure 5 ))Provides HARQ-ACK value.

[0085] Diagram 800 illustrates a first HARQ process 802, a second HARQ process 804, and a third HARQ process 806 for HARQ bundling. For example, HARQ-ACK feedback for the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 may be bundled together. The UE may perform a logical AND on the HARQ feedback for the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 to generate HARQ-ACK feedback to be provided to the base station.

[0086] Each of the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 may be configured to generate an ACK or NACK based on the performance of the HARQ process and / or the configuration of HARQ feedback such as enabled or disabled. In addition, a portion of the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 may be configured with HARQ feedback enabled, while another portion of the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 may be configured with HARQ feedback disabled. In some embodiments, the configuration of the HARQ process as enabled or disabled may be performed by any signaling described with respect to disabling HARQ feedback in method 1. In the illustrated embodiment of the diagram, the first HARQ process 802 and the third HARQ process 806 are configured with HARQ feedback enabled, while the second HARQ process 804 is configured with HARQ feedback disabled.

[0087] Each of the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 may generate an ACK / NACK value based on the result of the HARQ process and / or the configuration of HARQ feedback as enabled or disabled. In the illustrated embodiment, a first value 808 corresponding to the first HARQ process 802 may be generated, a second value 810 corresponding to the second HARQ process 804 may be generated, and a third value 812 corresponding to the third HARQ process 806 may be generated. Since the first HARQ process 802 and the third HARQ process 806 are configured with HARQ feedback enabled, the first value 808 corresponding to the first HARQ process 802 may be generated based on the result of the first HARQ process 806, and the third value 812 corresponding to the third HARQ process 806 may be generated based on the result of the third HARQ process 802. In the illustrated embodiment, the first value 808 may be generated as an ACK, and the third value 812 may be generated as an ACK. Since the second HARQ process 804 is configured with HARQ feedback disabled, the second value 810 may be generated based on disabling HARQ feedback for the second HARQ process 804, as indicated by the diagonal fill of the box corresponding to the second value 810. Since HARQ feedback is disabled for the second HARQ process 804, the second value 810 corresponding to the second HARQ process 804 may be automatically set to the ACK value.

[0088] Subsequently, the UE may combine the values ​​corresponding to the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 to produce a value 816 for the HARQ-ACK combined package 814. For example, the HARQ-ACK combined package 814 may include a combined package including the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806. The values ​​corresponding to the HARQ processes may have a logical AND applied to produce the value 816 of the HARQ-ACK combined package 814. In the illustrated example, the logical AND operation may be applied to the first value 808, the second value 810, and the third value 812 to produce the value 816. Thus, the first value 808 of ACK, the second value 810 of ACK, and the third value 812 of ACK may produce the value 816 of the ACK or HARQ-ACK combined package 814. As will be appreciated by one of ordinary skill in the art, the second value 810 that is automatically set to ACK based on disabling HARQ feedback makes the value 816 dependent on the first value 808 and the third value 812. Subsequently, the UE may transmit the value 816 to the base station to indicate the value of the combined packet. For example, in some embodiments, the value 816 may be transmitted in an uplink transmission 508 from the UE 504 to the base station 502.

[0089] Although diagram 800 is shown as bundling three HARQ processes, it should be understood that in other embodiments, more or fewer HARQ processes may be bundled.

[0090] If all HARQ processes in "HARQ with TTI bundling" have disabled feedback, some alternatives may apply. Alternative 1: Omit the HARQ-ACK bit. Alternative 2: The HARQ-ACK bit is ACK. Alternative 3: The HARQ-ACK bit is NACK. For example, if the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 in diagram 800 all disable HARQ feedback, the value 816 may be set or omitted according to these three alternatives. Specifically, in alternative 1 where the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 all disable HARQ feedback, the value 816 of the combined package 814 may be omitted in the transmission from the UE to the base station. In alternative 2, where the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 all disable HARQ feedback, the value 816 of the combined packet 814 may be set to ACK. In alternative 3, where the first HARQ process 802, the second HARQ process 804, and the third HARQ process 806 all disable HARQ feedback, the value 816 of the combined packet 814 may be set to NACK.

[0091] TS 36.213 Section 7.3.1 may reflect the dynamic HARQ-ACK codebook construction of method 2-1. TS 36.213 Section 7.3.1:

[0092] For HARQ-ACK transmission in subframe n, the UE shall generate one HARQ-ACK bit by performing a logical AND operation of HARQ ACK over all 1≤M≤4 bandwidth reduced low complexity (BL) / coverage enhancement (CE) DL subframes, where subframe n is a "HARQ-ACK transmission subframe" where HARQ-ACK bits corresponding to HARQ processes with disabled feedback are not counted (or counted as ACK).

[0093] If all HARQ-ACKs on all 1≤M≤4 BL / CE DL subframes are associated with a HARQ process with disabled feedback, then the corresponding one HARQ-ACK bit is

[0094] Alternative 1: Omitted (ie, no HARQ feedback)

[0095] Alternative 2: ACK

[0096] Alternative 3: NACK

[0097] For example, Section 7.3.1 of TS 36.213 illustrated above may state that a HARQ-ACK bit corresponding to a HARQ process with feedback disabled is not counted in some embodiments, or is counted as an ACK in some other embodiments. In addition, Section 7.3.1 of TS 36.213 may state that if all HARQ-ACKs associated with a HARQ process have feedback disabled, the corresponding HARQ-ACK bit may be omitted in some embodiments, may be set to ACK in some embodiments, or may be set to NACK in some embodiments.

[0098] Method 2-2: HARQ-ACK reporting with channel selection. HARQ-ACK reporting is applicable to both FDD and time division duplex (TDD). In addition, HARQ-ACK reporting with channel selection is applicable to PUCCH format 1b with more than 1 configured serving cell. In some serving cells, the scheduled HARQ process is configured with disabled HARQ feedback. In some serving cells, the scheduled HARQ process is configured with enabled HARQ feedback.

[0099] HARQ-ACK multiplexing case with channel selection. General principle: If the scheduled HARQ process on the serving cell has disabled HARQ feedback, then Alternative 1: the corresponding HARQ-ACK feedback is always NACK. Alternative 2: the corresponding HARQ-ACK feedback is always ACK. Alternative 1 and Alternative 2 can simplify the reception of PUCCH format 1b by the evolved Node B (eNB) (also referred to as "base station"). Alternative 3: The corresponding HARQ-ACK feedback is ACK or NACK depending on the corresponding PDSCH decoding result. In Alternative 3, it does not matter whether the scheduled HARQ process has disabled HARQ feedback (same behavior).

[0100] For example, in an instance where HARQ-ACK multiplexing with channel selection has been implemented, the UE may return a defined value for a scheduled HARQ process with HARQ feedback disabled. In alternative 1, the UE 504 may transmit an uplink transmission 508 having a NACK value for the corresponding HARQ-ACK feedback for the HARQ process with HARQ feedback disabled. In alternative 2, the UE 504 may transmit an uplink transmission 508 having an ACK value for the corresponding HARQ-ACK feedback for the HARQ process with HARQ feedback disabled. In alternative 3, the UE 504 may determine a corresponding PDSCH decoding result corresponding to the HARQ process. Based on the PDSCH decoding result, the UE 504 may transmit an uplink transmission 508 having an ACK or NACK value according to the PDSCH decoding result.

[0101] In alternatives 1, 2, and 3, the mapping table (eg, Tables 10.1.2.2.1-3, 10.1.2.2.1-4, 10.1.2.2.1-5 of TS 36.213) remains unchanged. For example, the mapping table for HARQ-ACK channel selection of TS 36.213 may remain unchanged from the conventional mapping table.

[0102] Alternative 4: Omitting the corresponding HARQ-ACK feedback for a HARQ process for which feedback is disabled. The number of HARQ-ACK feedback bits is reduced. A mapping table with a reduced number of A's is used. For example, an uplink transmission 508 transmitted by the UE 504 to the base station 502 may omit HARQ-ACK feedback for a HARQ process for which HARQ feedback has been disabled. Therefore, based on omitting HARQ-ACK feedback for a HARQ process, the number of HARQ-ACK feedback bits within the uplink transmission 508 may be reduced.

[0103] Special case: All scheduled HARQ processes on all configured serving cells have disabled HARQ feedback. Alternative 1: The UE does not need to send HARQ feedback at all. Alternative 2: The UE still needs to send HARQ feedback, which has a corresponding value of NACK or discontinuous reception (DTX) according to the DCI decoding result. For example, if all HARQ processes scheduled on the configured serving cells have disabled HARQ feedback, then in Alternative 1, the UE 504 may omit the HARQ feedback from the uplink transmission 508. In Alternative 2, the UE 504 may determine the DCI decoding result. Based on the DCI decoding result, the UE 504 may transmit a message with a corresponding value of NACK or DTX for the HARQ process while disabling HARQ feedback according to the DCI decoding result.

[0104] Method 3: SPS PDSCH

[0105] Method 3: SPS PDSCH

[0106] SPS configuration. Alternative 1: Same as per HARQ process configuration in method 1. Network specific implementation to ensure that all HARQ processes in the SPS configuration have the same feedback settings. For example, the SPS configuration may utilize signal diagram 100 ( Figure 1 ) is an example of signaling. Base station 102 ( Figure 1 ) can be used in configuring UE 104 ( Figure 1 ) when performing SPS configuration. Base station 102 may transmit control transmission 106 ( Figure 1 ) to configure the UE 104. For Alternative 1, the control transmission 106 of the SPS configuration may include one or more of the features of Method 1, including Alternatives 1 to 3 of Method 1. For example, in some embodiments (such as in Alternatives 1 and 3 of Method 1), the control transmission 106 may include a HARQ process number and indicate whether HARQ feedback will be enabled or disabled for the HARQ process corresponding to the HARQ process number, or indicate a HARQ process number corresponding to a HARQ process that may be enabled or disabled by RRC and / or DCI. In some embodiments, the RNTI may be used to perform a CRC corresponding to a DCI that schedules a HARQ process to indicate whether the HARQ process will disable HARQ feedback, such as in Alternative 2 of Method 1.

[0107] Alternative 2: Separate configuration in SPS configuration. For example, SPS-ConfigDL (or SPS-ConfigUL) has a single bit to indicate whether feedback is enabled or disabled for all HARQ processes in the SPS configuration. For example, a control transmission 106 transmitted by the base station 102 to the UE 104 may include an SPS-ConfigDL information element or an SPS-ConfigUL information element. The SPS-ConfigDL or SPS-ConfigUL in the control transmission 106 may include one or more bits to indicate whether HARQ feedback is to be enabled or disabled for all HARQ processes in the SPS configuration.

[0108] SPS release: always has HARQ feedback because it is not associated with a HARQ process number. For example, an SPS release operation may always enable HARQ feedback. Therefore, in some embodiments, base station 102 may not include an indication of whether HARQ feedback is enabled or disabled for an SPS release operation in control transmission 106.

[0109] SPS Activation: Alternative 1: Indicates RRC configuration that enables / disables HARQ feedback for SPS activation. In the enabled case, the UE reports ACK / NACK for the first SPS PDSCH after activation (depending on the first SPS PDSCH decoding result), regardless of whether HARQ feedback is enabled or disabled for the HARQ process associated with the SPS PDSCH. In the disabled case, if the first SPS PDSCH after activation is associated with a HARQ process that enables feedback, the UE reports ACK / NACK (depending on the first SPS PDSCH decoding result). Alternatively, if the first SPS PDSCH after activation is associated with a HARQ process that disables feedback, the UE does not report HARQ.

[0110] For example, the control transmission 106 transmitted by the base station 102 to the UE 104 may be an RRC configuration transmission. The RRC configuration transmission may indicate whether HARQ feedback is enabled or disabled for SPS activation. Subsequently, the UE 104 may transmit the HARQ feedback in an uplink transmission (such as uplink transmission 508 ( Figure 5 )) reports the value ACK or NACK for the SPS PDSCH after SPS activation. The UE 104 can determine whether to enable or disable HARQ feedback for SPS activation based on the RRC configuration transmission received from the base station 102.

[0111] If UE 104 determines that HARQ feedback is enabled for SPS activation, UE 104 may report an ACK or NACK for the first SPS PDSCH after SPS activation, where the ACK or NACK may be determined based on the first SPS PDSCH encoding result. For this instance where HARQ feedback is enabled for SPS activation, UE 104 may provide ACK / NACK regardless of whether HARQ feedback is enabled or disabled for the HARQ process associated with the SPS PDSCH.

[0112] If the UE 104 determines that HARQ feedback is disabled for SPS activation, the UE 104 may determine whether the first SPS PDSCH after SPS activation is associated with a HARQ process that enables or disables HARQ feedback. If the UE 104 determines that the first SPS PDSCH is associated with a HARQ process that enables HARQ feedback, the UE 104 may provide an ACK or NACK for the first SPS PDSCH, where the ACK or NACK may be determined based on the first SPS PDSCH decoding result. If the UE 104 determines that the first SPS PDSCH is associated with a HARQ process that disables HARQ feedback, the UE 104 may omit reporting HARQ feedback.

[0113] Alternative 2: Depends on the per-HARQ process configuration for the HARQ process in the first SPS PDSCH. If the first SPS PDSCH after activation is associated with a HARQ process with feedback enabled, the UE reports ACK / NACK (depending on the first SPS PDSCH decoding result). Alternatively, if the first SPS PDSCH after activation is associated with a HARQ process with feedback disabled, the UE does not report HARQ.

[0114] For example, UE 104 may determine whether HARQ in the first SPS PDSCH after SPS activation is associated with a HARQ process that enables or disables HARQ feedback. If UE 104 determines that the HARQ process enables HARQ feedback, UE 104 may report an ACK or NACK for the first SPS PDSCH to base station 102 (such as in uplink transmission 508), where the ACK or NACK is determined based on the first SPS PDSCH decoding result. If UE 104 determines that the HARQ process disables HARQ feedback, UE 104 may omit the HARQ feedback corresponding to the first SPS PDSCH in the response to base station 102.

[0115] Alternative 3: Depends on SPS configuration. If the SPS is configured with all HARQ processes with HARQ feedback enabled, the UE reports ACK / NACK in a conventional manner. If the SPS is configured with all HARQ processes with HARQ feedback disabled, the UE does not report ACK / NACK.

[0116] For example, UE 104 may determine whether the SPS configuration configures all HARQ processes with HARQ feedback enabled or disabled. If UE 104 determines that all HARQ processes are configured with HARQ feedback enabled, UE 104 may transmit the HARQ feedback to base station 102 (eg, in uplink transmission 508) according to conventional methods. Figure 1 ) reports ACK or NACK, where the ACK or NACK can be determined based on the result of the HARQ process. If the UE 104 determines that all HARQ processes are configured with disabled HARQ feedback, the UE 104 can omit reporting HARQ feedback to the base station 102.

[0117] SPS PDSCH. Alternative 1: If the corresponding HARQ process in the SPS configuration has feedback disabled, always report NACK. Alternative 2: If the corresponding HARQ process in the SPS configuration has feedback disabled, do not report ACK / NACK.

[0118] For example, UE 104 may determine whether a HARQ process corresponding to an SPS PDSCH transmission configured with an SPS configuration has HARQ feedback disabled. In alternative 1, if UE 104 determines that the HARQ process has HARQ feedback disabled, UE 104 may report a NACK for the HARQ process to base station 102 (such as in uplink transmission 508). In alternative 2, if UE 104 determines that the HARQ process has HARQ feedback disabled, UE 104 may omit reporting HARQ feedback to base station 102.

[0119] TS 36.213 Section 7.3.1 :

[0120] If SPS PDSCH transmission is activated for a UE and the UE is configured to transmit in subframe / slot n-4 or in subslot nX p The SPS PDSCH is received in the UE and the SPS PDSCH provides a transport block (TB) for a HARQ process with enabled HARQ-ACK information.

[0121] O ACK =O ACK +1

[0122] HARQ-ACK bits associated with SPS PDSCH transmission

[0123] End if:

[0124] TS 36.213 Section 7.3.1 may reflect the HARQ disabling method for the SPS PDSCH of Alternative 2. For example, TS 36.213 may state that the SPS PDSCH providing TBs for HARQ processes with enabled HARQ-ACK information is defined for HARQ feedback to be provided.

[0125] Method 4: PDSCH processing timeline. The PDSCH processing timeline method may relate to the time at which the UE may expect to receive a PDCCH transmission or receive a PDSCH transmission after receiving a PDSCH transmission. For example, in some embodiments, the UE may not monitor, may ignore, or may indicate an error in a PDCCH transmission received within a time period of a PDSCH transmission or a PDSCH transmission received within a time period of a PDSCH transmission. In some embodiments, the base station may be restricted to scheduling PDCCH transmissions to the UE to at least a specific time period after the base station has transmitted a PDSCH transmission to the UE, or may be restricted to scheduling PDSCH transmissions to the UE to at least a specific time period after the base station has transmitted a PDSCH transmission to the UE.

[0126] Alternative 1: After T from the end of receiving the last PDSCH for the same HARQ process number proc,1 Within , the UE is not expected to receive another PDCCH carrying DCI scheduling another PDSCH for a given HARQ process number with disabled HARQ feedback.

[0127] Alternative 2: After T from the end of receiving the last PDSCH for the same HARQ process number proc,2 Within , the UE is not expected to receive another PDSCH for the given HARQ process number with disabled HARQ feedback.

[0128] Fig. 9 A PDSCH timing representation 900 according to some embodiments is illustrated. Specifically, the timing representation 900 may represent a PDSCH processing timeline for Method 4 (including Alternative 1 and Alternative 2).

[0129] Timing representation 900 may include a first PDCCH transmission 902 and a first PDSCH transmission 904. The first PDCCH transmission 902 and the first PDSCH transmission 904 may be transmitted by a base station, such as base station 102 ( Figure 1 ) and / or base station 502 ( Figure 5 )) to a UE (such as UE 104 ( Figure 1 ) and / or UE504( Figure 5)) transmission. The first PDSCH transmission 904 may correspond to the first PDCCH transmission 902, such as the first PDCCH transmission 902 scheduling the first PDSCH transmission 904. The UE may detect reception of the first PDCCH transmission 902 and the first PDSCH transmission 904.

[0130] The timing representation 900 may include a first timing program period 910. The first timing program period 910 may be related to alternative scheme 1 of method 4. Specifically, the first timing program period 910 may indicate the amount of time after the first PDSCH transmission 904 that the UE is not expected to receive another PDCCH transmission. In the illustrated embodiment, the first timing program period 910 is shown as measured from the end of the first PDSCH transmission 904, but it should be understood that the first timing program period 910 may be measured from different events of the first PDSCH transmission 904, such as the start of the first PDSCH transmission 904. In some embodiments, the UE may not monitor, may ignore, or may indicate an error in the PDCCH transmission received during the first timing program period 910. Once the first timing program period 910 has expired, the UE may begin to monitor for further PDCCH transmissions. In some embodiments, the base station may be prevented from transmitting further PDCCH transmissions until the first timing program period 910 expires. The timing representation 900 may also include a second PDCCH transmission 906 illustrated when the first timing program period 910 expires. The UE may detect a second PDCCH transmission 906 (or other PDCCH transmissions scheduled after the time of the second PDCCH transmission 906) based on the second PDCCH transmission 906 arriving at the UE after expiration of a timing program period from a previous PDSCH transmission, where, in the illustrated embodiment, the previous PDSCH transmission is the first PDSCH transmission 904.

[0131] The timing representation 900 may include a second timing program period 912. The second timing program period 912 may be related to alternative 2 of method 4. Specifically, the second timing program period 912 may indicate the amount of time after the first PDSCH transmission 904 that the UE is not expected to receive another PDSCH transmission. In the illustrated embodiment, the second timing program period 912 is shown as measured from the end of the first PDSCH transmission 904, but it should be understood that the second timing program period 912 may be measured from different events of the first PDSCH transmission 904, such as the start of the first PDSCH transmission 904. In some embodiments, the UE may not monitor, may ignore, or may indicate an error in the PDSCH transmission received during the second timing program period 912. Once the second timing program period 912 has expired, the UE may begin to monitor for further PDSCH transmissions. In some embodiments, the base station may be prevented from transmitting further PDSCH transmissions until the second timing program period 912 expires. The timing representation 900 may also include a second PDSCH transmission 908 illustrated when the second timing program period 912 expires. The UE may detect the second PDSCH transmission 908 (or other PDCCH transmissions scheduled after the time of the second PDSCH transmission 908) based on the second PDSCH transmission 908 arriving at the UE after expiration of a timing program period from a previous PDSCH transmission, where, in the illustrated embodiment, the previous PDSCH transmission is the first PDSCH transmission 904.

[0132] Both alternative 1 and alternative 2 can be applied simultaneously. The first timer program period (T proc,1 ) and the second timing program period (T proc,2 ) may depend on UE capabilities. PDSCH may be a repetition of PDSCH: "last PDSCH" becomes "last PDSCH repetition". PDSCH may be SPS PDSCH. Alternative 2: Applicable to SPS PDSCH without scheduling DCI.

[0133] For example, alternative 1 with a first timing program period 910 between the first PDSCH transmission 904 and the second PDCCH transmission 908 and alternative 2 with a second timing program period 912 between the first PDSCH transmission 904 and the second PDSCH transmission 906 may be implemented in the same embodiment. For example, in some embodiments, the UE may expect any PDCCH transmission to occur at least at the first timing program period 910 after the last PDSCH transmission, and the UE may expect any PDSCH transmission to occur at least at the second timing program period 912 after the last PDSCH transmission. In other embodiments, one of alternative 1 or alternative 2 may be implemented. In addition, the first timing program period 910 and / or the second timing program period 912 may depend on the UE capabilities of the UE implementing these alternatives. For example, the duration of the first timing program period 910 and / or the duration of the second timing program period 912 may depend on the UE capabilities of the UE.

[0134] In some embodiments, PDSCH transmissions may be repeated. Thus, the same PDSCH transmission may be transmitted multiple times in a row. In these examples, the first timing procedure period 910 and / or the second timing procedure period 912 may be measured from the last PDSCH transmission in the repetition of the PDSCH transmission.

[0135] In some embodiments, the PDSCH transmission may be an SPS PDSCH transmission. In these embodiments, Alternative 2 may be applied to an SPS PDSCH transmission, where the SPS PDSCH transmission does not have a scheduling DCI. For example, the first PDSCH transmission 904 may be an SPS PDSCH transmission, and the UE may expect a second time program period 912 before the second PDSCH transmission 908, which in some embodiments may also be an SPS PDSCH.

[0136] Fig.10 An example process 1000 for operating a base station in an IoT NTN according to some embodiments is illustrated. For example, the process 1000 may be performed by a base station such as the base station 102 ( Figure 1 )、Base Station 502( Figure 5 )、Base Station 1208( Fig.12 )、Base Station 1212( Fig.12 ) and / or base station 1400( Fig.14 ) or other base stations to execute.

[0137] Procedure 1000 may include generating a control transmission at 1002. For example, the base station may generate a control transmission indicating whether HARQ feedback is to be disabled for a HARQ process within the IoT NTN. In some embodiments, the control transmission may be an RRC transmission. In some embodiments, the control transmission may be a DCI transmission for scheduling the HARQ process. In some of these embodiments where the control transmission is an RRC transmission, the control transmission may be a first control transmission.

[0138] The control transmission may include a field indicating whether HARQ feedback will be enabled or disabled. For example, in some embodiments, the control transmission may be an RRC transmission. The PDSCH-ConfigDedicated information element or the PUSCH-ConfigDedicated information element of the RRC transmission includes a field indicating whether HARQ feedback will be disabled for the HARQ process associated with the RRC transmission. The field may include a HARQ process number corresponding to the HARQ process. In some embodiments, the control transmission may be a DCI transmission for scheduling HARQ, and in some embodiments, the DCI transmission may include a field indicating whether HARQ feedback will be disabled for the HARQ process. In some of these embodiments, the field may be a one-bit field indicating whether HARQ feedback will be disabled for the HARQ process.

[0139] In some embodiments, the control transmission may include a mask indicating whether HARQ feedback will be enabled or disabled. For example, in some embodiments, the control transmission may be a DCI transmission for scheduling a HARQ process. The CRC of the DCI transmission may be masked with an RNTI different from the C-RNTI of the cell corresponding to the UE to indicate that HARQ feedback will be disabled. The CRC may be de-masked and / or have a C-RNTI for the CRC to indicate that HARQ feedback will be enabled.

[0140] In some embodiments, a control transmission may be used in an SPS instance. For example, the control transmission may be an RRC transmission. The RRC transmission may include a configuration in the SPS-Config information element indicating whether HARQ feedback is to be disabled for a HARQ process associated with the RRC transmission. In some embodiments, the SPS-Config information element may include a single bit indicating whether HARQ feedback is to be disabled for a HARQ process.

[0141] Procedure 1000 may include transmitting a control transmission to the UE at 1004. Specifically, the base station may transmit the control transmission generated at 1002 to the UE. The UE may be configured to perform a HARQ process based on the control transmission. In addition, the UE may determine whether to provide HARQ feedback for the HARQ process to the base station based on the control transmission.

[0142] Procedure 1000 may include generating a DCI transmission at 1006. For example, in some embodiments, the control transmission generated at 1002 may be a first control transmission, wherein the first control transmission is an RRC transmission. In these embodiments, the base station may generate a DCI transmission, wherein the DCI transmission may be a second control transmission. The DCI transmission may also indicate whether HARQ feedback will be disabled for the HARQ process. The RRC transmission may include an RRC field indicating whether HARQ feedback will be disabled for the HARQ process. The RRC field may include a HARQ process number corresponding to the HARQ process. The DCI transmission may include a DCI field further indicating whether HARQ feedback will be disabled for the HARQ process. The DCI field may include a HARQ process number. In some embodiments, 1006 may be omitted.

[0143] Procedure 1000 may include transmitting the DCI transmission to the UE at 1008. Specifically, the base station may transmit to the UE the DCI transmission generated at 1006. In some implementations, 1008 may be omitted.

[0144] The process 1000 may include identifying an uplink transmission received from a UE at 1010. In particular, the base station may identify an uplink transmission received from the UE that corresponds to a control transmission.

[0145] Although the process 1000 is illustrated and described in a particular order, it should be understood that one or more of the operations of the process 1000 may be omitted in an embodiment. It should be understood that one or more of the operations of the process 1000 may be performed simultaneously and / or may be performed in a different order than illustrated and described.

[0146] Fig.11 An example procedure 1100 for operating a UE in an IoT NTN according to some embodiments is illustrated. For example, the procedure 1100 may be performed by a UE such as UE 104 ( Figure 1 )、UE 504( Figure 5 )、UE 1204( Fig.12 )、UE 1206( Fig.12 ) and / or UE 1300( Fig.13 ) or other UE to execute.

[0147] Procedure 1100 may include identifying, at 1102, a control transmission received from a base station. For example, the UE may identify a control transmission received from a base station of an IoT NTN indicating that HARQ feedback is to be disabled for a HARQ process. In some instances, the control transmission may indicate that all HARQ processes within a HARQ with TTI bundling are to have HARQ feedback disabled. In some other instances, the control transmission may indicate that all scheduled HARQ processes on all multiple configured serving cells are to have HARQ feedback disabled. Furthermore, in some instances, the control transmission may include a DCI transmission transmitted via a PDCCH, the DCI being used to schedule a PDSCH transmission.

[0148] In some embodiments, the HARQ process may be implemented as part of bundling or performed on a serving cell in a plurality of configured serving cells. For example, in some instances, the HARQ process may be part of HARQ with TTI bundling. In other instances, the HARQ process may be performed on a serving cell in a plurality of configured serving cells.

[0149] Procedure 1100 may include determining that HARQ feedback is to be disabled at 1104. For example, the UE may determine based on a control transmission that HARQ feedback is to be disabled for a HARQ process.

[0150] Procedure 1100 may include determining a corresponding PDSCH decoding result at 1106. For example, the UE may determine the corresponding PDSCH decoding result. In some implementations, 1106 may be omitted.

[0151] Procedure 1100 may include determining a DCI decoding result at 1108. For example, the UE may determine a downlink decoding result. In some implementations, 1108 may be omitted.

[0152] Procedure 1100 may include generating an uplink transmission at 1110. For example, the UE may include generating an uplink transmission with a HARQ codebook based on determining that HARQ feedback is to be disabled for the HARQ process.

[0153] In some embodiments, based on determining that HARQ feedback is to be disabled for the HARQ process, the HARQ codebook may omit or include a specific value for the HARQ process. For example, in some embodiments, based on determining that HARQ feedback is to be disabled for the HARQ process, the HARQ codebook may omit the corresponding bit for the HARQ process. In addition, in some embodiments, based on determining that HARQ feedback is to be disabled for the HARQ process, the HARQ codebook may include a NACK for the HARQ process.

[0154] In some embodiments, a HARQ codebook may be used for a HARQ process that is part of HARQ TTI bundling. For example, in some embodiments where the HARQ process is part of HARQ with TTI bundling, the HARQ information for the HARQ process may be considered as an ACK for determining the HARQ codebook. In some embodiments, based on disabling HARQ feedback for all HARQ processes within the HARQ with TTI bundling, the HARQ codebook may omit the HARQ-ACK bit. In addition, in some embodiments, based on disabling HARQ feedback for all HARQ processes within the HARQ with TTI bundling, the HARQ codebook may have a HARQ-ACK bit value corresponding to ACK. In some embodiments, based on disabling HARQ feedback for all HARQ processes within the HARQ with TTI bundling, the HARQ codebook may have a HARQ-ACK bit value corresponding to NACK.

[0155] In some embodiments, the HARQ process may be performed on a serving cell in a plurality of configured serving cells. In some embodiments, based on determining that HARQ feedback will be disabled for the HARQ process, the HARQ codebook may have a NACK value corresponding to the HARQ process. In addition, in some embodiments, based on determining that HARQ feedback will be disabled for the HARQ process, the HARQ codebook may have an ACK value corresponding to the HARQ process. In some embodiments in which the PDSCH decoding result is determined in 1106, the HARQ codebook may have an ACK value or a NACK value based on the PDSCH decoding result. In addition, in some embodiments, HARQ feedback for the HARQ process may be omitted from the HARQ codebook.

[0156] There may be instances where a control transmission indicates that all scheduled HARQ processes on all multiple configured serving cells are to disable HARQ feedback. In some of these embodiments, HARQ feedback may be omitted from the HARQ codebook. In some of these embodiments where a DCI decoding result is determined in 1108, the HARQ codebook may include a NACK value or a DTX value for the HARQ process.

[0157] Procedure 1100 may include transmitting an uplink transmission at 1112. For example, the UE may transmit the uplink transmission generated at 1110 to a base station.

[0158] Procedure 1100 may include avoiding monitoring subsequent PDCCH transmissions at 1114. For example, in some embodiments, the UE may avoid monitoring subsequent PDCCH transmissions at a defined processing time after a PDSCH transmission. This may occur if the control transmission is a DCI transmission transmitted via a PDCCH and the DCI will schedule a PDSCH transmission. In some embodiments, 1114 may be omitted.

[0159] Procedure 1100 may include avoiding monitoring subsequent PDSCH transmissions at 1116. For example, in some embodiments, the UE may avoid monitoring subsequent PDSCH transmissions within a defined processing time after the PDSCH transmission. This may occur if the control transmission is a DCI transmission transmitted via the PDCCH and the DCI will schedule the PDSCH transmission. In some embodiments, 1116 may be omitted.

[0160] Although the process 1100 is illustrated and described in a particular order, it should be understood that one or more of the operations of the process 1100 may be omitted in an embodiment. It should be understood that one or more of the operations of the process 1100 may be performed simultaneously and / or may be performed in a different order than illustrated and described.

[0161] Although the above description describes methods and alternatives separately for the sake of clarity, it should be understood that two or more methods and / or two or more alternatives may be implemented in the same embodiment. For example, method 1 defining the operation of a base station and method 2 defining the operation of a UE may be implemented in the same embodiment. In addition, alternative 1 of method 2-1 related to dynamic HARQ-ACK codebook construction and alternative 1 of method 2-1 related to HARQ-ACK bundling conditions may be implemented in the same embodiment. Therefore, it should be understood that each embodiment may implement one or more methods and / or one or more alternatives, wherein each embodiment may include different methods and / or alternatives.

[0162] Fig.12 Illustrated is a network environment 1200 according to some embodiments. The network environment 1200 may include a UE 1204, a UE 1206, a mobile base station (BS) 1208, and a mobile BS 1212.

[0163] Mobile BS 1208 / 1212 may be a base station configured to provide a radio access cell (or "service cell") to a geographic location near the mobile BS. Mobile BS 1208 / 1212 may be a terrestrial or non-terrestrial base station that is capable of moving relative to a geographic location (typically on a fixed or predetermined route). For example, mobile BS 1208 / 1212 may be provided by a vehicle, a train, an unmanned aerial vehicle, an airplane, a satellite of various altitude classifications (e.g., low earth orbit, medium earth orbit, geosynchronous orbit, or high earth orbit), etc.

[0164] UE 1204 / 1206 is depicted as a mobile phone. However, UE 1204 / 1206 may be any type of user equipment, such as a computer, a tablet computer, an industrial wireless sensor, a video surveillance / monitoring device, a wearable device, a vehicle, a vehicle equipped with wireless connectivity, an Internet of Things (IoT) device, etc.

[0165] Mobile BS 1208 / 1212 may be configured to provide a fixed service cell at a set geographic location. For example, mobile BS 1208 may initially provide a service cell 1210 for a geographic location 1222 covering both UE 1204 / 1206. When mobile BS 1208 moves away from geographic location 1222, mobile BS 1212 moves toward geographic location 1222, and mobile BS 1212 may take over the provisioning of the same service cell 1210. In order to provide the same service cell 1210, mobile BS 1212 may transmit appropriate system information (SI) and broadcast information of the cell, and may take over the communication to / from UE 1204 / 1206. SI / broadcast information may include, for example: synchronization signals and physical broadcast channel (PBCH) blocks (SSBs), which are transmitted to provide, for example, physical cell identities and master information blocks (MIBs); and other system information blocks (SIBs), which are transmitted in physical downlink shared channels (PDSCHs). In this way, the arriving base station may seamlessly take over the identity and responsibilities of the departing base station. In some embodiments, the transfer of the provisioning of the serving cell 1210 from the mobile BS 1208 to the mobile BS 1212 may be transparent to the UE 1204 / 1206. The UE 1204 / 1206 may view the cell coverage as fixed and may not be aware that it is now being provided by a different mobile BS. Since this transfer is transparent to the UE 1204 / 1206, they may not incur any signaling delays in a traditional handover due to the required UE communication with the source / target base station.

[0166] The serving cell 1210 may provide an air interface compatible with a 3GPP New Radio (NR) access technology or a 3GPP Long Term Evolution (LTE) access technology to the UE 1204 / 1206. The mobile BS 1208 / 1212 may then communicate with a core network 1214, which may be, for example, a 3GPP fifth generation (5G) core network (5GC). The mobile BS 1208 / 1212 may be referred to as a radio access node, an ng-eNB (which provides an LTE access network and is connected to a 5GC), a gNB (which provides an NR access network and is connected to a 5GC), or an access node utilizing a sixth generation (6G) and higher technology.

[0167] The mobile BS 1208 / 1212 may communicate with the UE 1204 / 1206 via a Uu interface, communicate with each other via an Xn interface, and communicate with the core network 1214 via a next generation (NG) interface. In some embodiments, the mobile BS 1208 / 1212 may be coupled to an access and mobility management function (AMF) 1216 of the core network 1214 using an NG control (NG-C) interface, and coupled to a user plane function (UPF) 1218 of the core network 1214 using an NG user (NG-U) interface.

[0168] The NG-C interface may use the Next Generation Application Protocol (NGAP) to transfer signaling messages between the mobile BS 1208 / 1212 and the AMF 1216, which may be a control plane function that provides registration management services, connection management services, reachability management services, and mobility management services. Registration management may allow the UE to register and deregister with the 5G system. Upon registration, a UE context may be created within the core network 1214. The UE context may be a set of parameters that identify and characterize the UE. The UE context may include UE identity information, UE capability information, access and mobility information, or protocol data unit (PDU) session information. Connection management may be used to establish and release a control plane signaling connection between the UE and the AMF 1216. Establishing a control plane signaling connection moves the UE from connection management (CM) idle to CM connection. When a mobile terminated connection is desired, reachability management may allow the UE to be found and paged. Mobility management may be used to maintain the location information of the UE within the network.

[0169] In some embodiments, the AMF 1216 may include a base station tracking function (BSTF) 1220. The BSTF 1220 may be programmed with routing information for each mobile base station including, for example, the mobile BS 1208 / 1212. The routing information may enable the BSTF 1220 to determine the location of the mobile BS 1208 / 1212 at a particular time. This information may be used to provide the mobile BS 1208 / 1212 with relevant information about neighboring base stations, upcoming geographic locations, and relevant cell information, etc. In some embodiments, this may reduce the amount of information required to be exchanged directly between the mobile BS 1208 / 1212 over the Xn interface when the mobile BS 1208 / 1212 is transferring cell deployment responsibilities.

[0170] UPF 1218 may enable routing and forwarding of user plane packets between mobile BS 1208 / 1212 and external networks. Mobile BS 1208 / 1212 may transmit uplink packets to UPF 1218 via a General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U) tunnel. UPF 1218 may remove packet headers and forward packets to an external data network. UPF 1218 may map downlink packets arriving from an external data network to a specific quality of service flow belonging to a specific PDU session before forwarding to mobile BS 1208 / 1212.

[0171] The Xn interface between mobile BS1208 and mobile BS1212 may include a control plane interface (Xn-C) for transferring signaling messages between adjacent base stations and a user plane interface (Xn-U) for transferring data between adjacent base stations. Mobile BS1208 / 1212 may use the Xn interface for basic mobility procedures, dual connection procedures, and global procedures. Basic mobility procedures include, but are not limited to, UE handover preparation and control, radio access network paging, receiving UE context, and sequence number (SN) state transfer. The dual connection procedure involves adding, removing, and managing master nodes and auxiliary nodes for dual connection operations. Global procedures include, but are not limited to, Xn establishment and removal, cell activation, and handover reporting.

[0172] In typical operation, the Xn interface may be established through an automatic neighbor relation procedure (ANR), in which the UE discovers the identity of the neighboring cells of the serving cell. The serving cell may then send a query to the AMF for the appropriate IP address of the neighboring base station. The AMF will then query the neighboring node to obtain the IP address, which will then be transmitted back to the source base station. However, in some embodiments described herein, the UE may not be aware of two different base stations, and UE procedures that rely on ANR may not be possible. Therefore, the Xn interface may be established in other ways. For example, in some embodiments, the BSTF 1220 may provide information (such as IP addresses) to the mobile BS 1208 and the mobile BS 1212 to facilitate the establishment of the Xn interface.

[0173] In order to take over the allocation of cell 1210, mobile BS 1212 may need various state information relative to the state of cell 1210 and the UE currently being served by cell 1210. In some embodiments, the operating state or mode of UE 1204 / 1206 may affect the type of information that needs to be acquired by mobile BS 1212. For example, consider that UE 1204 is in RRC connected mode at the time of transfer, while UE 1206 is in RRC idle mode. The connected UE 1204 may be involved in active communication with mobile BS 1208 when the cell allocation responsibility is transferred to mobile BS 1212. Therefore, mobile BS 1208 may provide UE-level information to mobile BS 1212 to allow mobile BS 1212 to take over the communication. UE-level information may include state information such as, but not limited to, the allocated uplink and downlink resources, the state of ongoing communications (e.g., hybrid automatic repeat request (HARQ) process, transmission / reception buffer, the state of paging / random access / mobility procedures, etc.), etc.

[0174] In some embodiments, concepts related to fixed deployment of serving cells may be abstracted to other levels. For example, in some embodiments, mobile BS 1208 / 1210 may provide fixed deployment configuration of registration / tracking / location areas to facilitate reachability / mobility management procedures of AMF 1216.

[0175] Fig.13An example of an exemplary UE 1300 according to some embodiments is shown. UE 1300 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter, actuator, etc.), video monitoring / surveillance equipment (e.g., camera, camcorder, etc.), a wearable device (e.g., smart watch), a loose IoT device. In some embodiments, UE 1300 can be a RedCap UE or an NR-Light UE.

[0176] UE 1300 may include a processor 1304, RF interface circuitry 1308, memory / storage 1312, a user interface 1316, a sensor 1320, a driver circuit 1322, a power management integrated circuit (PMIC) 1324, antenna structures 1326, and a battery 1328. The components of UE 1300 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.13 The block diagram of UE 1300 is intended to show a high-level view of certain of the components of UE 1300. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0177] Components of UE 1300 may be coupled to various other components via one or more interconnects 1332, which may represent any type of interface, input / output, bus (local, system, or extended), transmission line, trace, optical connection, etc. that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0178] The processor 1304 may include processor circuits such as a baseband processor circuit (BB) 1304A, a central processor unit circuit (CPU) 1304B, and a graphics processor unit circuit (GPU) 1304C. The processor 1304 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1312) to cause the UE 1300 to perform operations as described herein.

[0179] In some embodiments, the baseband processor circuit 1304A can access the communication protocol stack 1136 in the memory / storage device 1312 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1304A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1308.

[0180] The baseband processor circuit 1304A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0181] The memory / storage 1312 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1136) that may be executed by one or more processors in the processor 1304 to cause the UE 1300 to perform various operations described herein. The memory / storage 1312 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1300. In some embodiments, some of the memory / storage 1312 may be located on the processor 1304 itself (e.g., L1 cache and L2 cache), while other memory / storage 1312 is located external to the processor 1304 but accessible via a memory interface. The memory / storage 1312 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0182] The RF interface circuit 1308 may include a transceiver circuit and a radio frequency front end module (RFEM) that allows the UE 1300 to communicate with other devices through a radio access network. The RF interface circuit 1308 may include various elements arranged in a transmission path or a reception path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0183] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1326 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which converts the RF signal down to a baseband signal that is provided to the baseband processor of the processor 1304.

[0184] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1326.

[0185] In various embodiments, the RF interface circuit 1308 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0186] Antenna 1326 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1326 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multiple input / multiple output communications. Antenna 1326 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 1326 may have one or more panels that are designed for a specific frequency band including a band in FR1 or FR2.

[0187] The user interface circuit 1316 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1300. The user interface circuit 1316 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, including in particular one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touchpad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1300.

[0188] Sensors 1320 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0189] The driver circuit 1322 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1300. The driver circuit 1322 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1300. For example, the driver circuit 1322 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1320 and controlling and allowing access to the sensor circuit 1320, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0190] The PMIC 1324 may manage power provided to various components of the UE 1300. Specifically, with respect to the processor 1304, the PMIC 1324 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0191] In some embodiments, the PMIC 1324 may control or otherwise be part of various power saving mechanisms of the UE 1300. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1300 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1300 may transition to the RRC_Idle state, in which the UE is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The UE 1300 enters a very low power state and performs paging, in which the platform again periodically wakes up to listen to the network and then powers off again. The UE 1300 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for a time exceeding the paging interval (from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data transmitted during this time will incur significant latency, and it is assumed that latency is acceptable.

[0192] The battery 1328 can power the UE 1300, but in some examples, the UE 1300 can be installed to be deployed in a fixed location and can have a power source coupled to the power grid. The battery 1328 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1328 can be a typical lead-acid car battery.

[0193] Fig.14 An exemplary gNB 1400 is shown according to some embodiments. The gNB 1400 may include a processor 1404, RF interface circuitry 1408, core network (CN) interface circuitry 1412, memory / storage circuitry 1416, and antenna structures 1426.

[0194] Components of gNB 1400 may be coupled to various other components via one or more interconnects 1428.

[0195] The processor 1404, RF interface circuit 1408, memory / storage circuit 1416 (including communication protocol stack 1410), antenna structure 1426 and interconnect 1428 may be similar to those described with reference to Fig.13 Like named elements are shown and described.

[0196] The CN interface circuitry 1412 may provide connectivity to a core network (e.g., a 5th Generation Core Network (5GC) using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the gNB 1400 via optical fiber or wireless backhaul. The CN interface circuitry 1412 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1412 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0197] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0198] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0199] Example

[0200] In the following sections, additional exemplary embodiments are provided.

[0201] Embodiment 1 may include a method of operating a base station in an Internet of Things (IoT) non-terrestrial network (NTN), the method comprising: generating a control transmission indicating whether a hybrid automatic repeat request (HARQ) feedback is to be disabled for a HARQ process within the IoT NTN; transmitting the control transmission to a user equipment (UE); and identifying an uplink transmission received from the UE corresponding to the control transmission.

[0202] Embodiment 2 may include a method according to embodiment 1 or some other embodiment herein, wherein the control transmission is a radio resource control (RRC) transmission, and wherein a physical downlink shared channel (PDSCH)-ConfigDedicated information element or a physical uplink shared channel (PUSCH)-ConfigDedicated information element of the RRC transmission includes a field indicating whether the HARQ feedback is to be disabled for the HARQ process.

[0203] Embodiment 3 may include a method according to embodiment 2 or some other embodiment herein, wherein the field includes a HARQ process number corresponding to the HARQ process.

[0204] Embodiment 4 may include a method according to embodiment 1 or some other embodiment herein, wherein the control transmission is a downlink control information (DCI) transmission for scheduling the HARQ process, and wherein the DCI transmission includes a field indicating whether the HARQ feedback is to be disabled for the HARQ process.

[0205] Embodiment 5 may include a method according to embodiment 4 or some other embodiment herein, wherein the field is a one-bit field indicating whether the HARQ feedback is to be disabled for the HARQ process.

[0206] Embodiment 6 may include a method according to embodiment 1 or some other embodiment herein, wherein the control transmission is a downlink control information (DCI) transmission for scheduling the HARQ process, and wherein a cyclic redundancy check (CRC) of the DCI transmission is masked with a radio network temporary identifier (RNTI) different from a cell radio network temporary identifier (C-RNTI) of the cell corresponding to the UE to indicate that the HARQ feedback is to be disabled.

[0207] Embodiment 7 may include a method according to embodiment 1, wherein the control transmission is a downlink control information (DCI) transmission for scheduling the HARQ process, and wherein the DCI transmission includes a HARQ-ACK delay field or a HARQ-ACK resource offset field having a code point indicating that the HARQ feedback will be disabled.

[0208] Embodiment 8 may include a method according to embodiment 1 or some other embodiment herein, wherein the control transmission is a radio resource control (RRC) transmission, wherein the method further includes: generating a downlink control information (DCI) transmission further indicating whether the HARQ feedback is to be disabled for the HARQ process; and transmitting the DCI transmission to the UE.

[0209] Embodiment 9 may include a method according to embodiment 8 or some other embodiment herein, wherein the RRC transmission includes an RRC field indicating whether the HARQ feedback will be disabled for the HARQ process, and wherein the DCI transmission includes a DCI field further indicating whether the HARQ feedback will be disabled for the HARQ process.

[0210] Embodiment 10 may include a method according to embodiment 9 or some other embodiment herein, wherein the RRC field includes a HARQ process number corresponding to the HARQ process, and wherein the DCI field includes the HARQ process number.

[0211] Embodiment 11 may include a method according to embodiment 1 or some other embodiment herein, wherein the control transmission is a radio resource control (RRC) transmission, and wherein the RRC transmission includes a configuration in a semi-persistent scheduling (SPS)-Config information element indicating whether the HARQ feedback is to be disabled for the HARQ process.

[0212] Embodiment 12 may include a method according to embodiment 11 or some other embodiment herein, wherein the SPS-Config information element includes a single bit indicating whether the HARQ feedback is to be disabled for the HARQ process.

[0213] Embodiment 13 may include a method of operating a user equipment (UE) in an Internet of Things (IoT) non-terrestrial network (NTN), the method comprising: identifying a control transmission received from a base station of the IoT NTN indicating that HARQ feedback will be disabled for a hybrid automatic repeat request (HARQ) process; determining based on the control transmission that HARQ feedback will be disabled for the HARQ process; generating an uplink transmission with a HARQ codebook based on determining that the HARQ feedback will be disabled for the HARQ process; and transmitting the uplink transmission to the base station.

[0214] Embodiment 14 may include a method according to embodiment 13 or some other embodiment herein, wherein based on determining that the HARQ feedback is to be disabled for the HARQ process, the HARQ codebook omits a corresponding bit for the HARQ process.

[0215] Embodiment 15 may include a method according to embodiment 13 or some other embodiment herein, wherein based on determining that the HARQ feedback is to be disabled for the HARQ process, the HARQ codebook includes a negative acknowledgement (NACK) for the HARQ process.

[0216] Embodiment 16 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is part of a HARQ with transmission time interval (TTI) bundling, and wherein the HARQ information for the HARQ process is considered to be an acknowledgment (ACK) for determining the HARQ codebook.

[0217] Embodiment 17 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is part of a HARQ with transmission time interval (TTI) bundling, wherein the control transmission indicates that all HARQ processes within the HARQ with TTI bundling will disable HARQ feedback, and wherein based on disabling HARQ feedback for all HARQ processes within the HARQ with TTI bundling, the HARQ codebook omits a HARQ-acknowledgement (ACK) bit.

[0218] Embodiment 18 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is part of a HARQ with transmission time interval (TTI) bundling, wherein the control transmission indicates that all HARQ processes within the HARQ with TTI bundling will disable HARQ feedback, and wherein based on all the HARQ processes within the HARQ with TTI bundling disabling HARQ feedback, the HARQ codebook has a HARQ-ACK bit value corresponding to an acknowledgment (ACK).

[0219] Embodiment 19 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is part of a HARQ with transmission time interval (TTI) bundling, wherein the control transmission indicates that all HARQ processes within the HARQ with TTI bundling will disable HARQ feedback, and wherein based on all the HARQ processes within the HARQ with TTI bundling disabling HARQ feedback, the HARQ codebook has a HARQ-acknowledgement (ACK) bit value corresponding to a negative acknowledgment (NACK).

[0220] Embodiment 20 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is to be performed on a serving cell among a plurality of configured serving cells, and wherein based on determining that the HARQ feedback is to be disabled for the HARQ process, the HARQ codebook has a negative acknowledgement (NACK) value corresponding to the HARQ process.

[0221] Embodiment 21 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is to be performed on a serving cell among a plurality of configured serving cells, and wherein the determination is based on disabling the HARQ feedback for the HARQ process, and the HARQ codebook has an acknowledgment (ACK) value corresponding to the HARQ process.

[0222] Embodiment 22 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is to be performed on a service cell among multiple configured service cells, wherein the method further includes determining a corresponding physical downlink shared channel (PDSCH) decoding result, wherein the HARQ codebook has an acknowledgment (ACK) value or a negative acknowledgment (NACK) value based on the PDSCH decoding result.

[0223] Embodiment 23 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is to be performed on a serving cell among a plurality of configured serving cells, and wherein the HARQ feedback for the HARQ process is omitted from the HARQ codebook.

[0224] Embodiment 24 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is to be performed on a serving cell among a plurality of configured serving cells, wherein the control transmission indicates that all scheduled HARQ processes on all of the plurality of configured serving cells are to disable HARQ feedback, and wherein the HARQ feedback is omitted from the HARQ codebook.

[0225] Embodiment 25 may include a method according to embodiment 13 or some other embodiment herein, wherein the HARQ process is to be performed on a serving cell among a plurality of configured serving cells, wherein the control transmission indicates that all scheduled HARQ processes on all of the plurality of configured serving cells are to disable HARQ feedback, wherein the method further includes determining a downlink control information (DCI) decoding result, wherein the HARQ codebook includes a negative acknowledgement (NACK) value or a discontinuous transmission (DTX) value for the HARQ process.

[0226] Embodiment 26 may include a method according to embodiment 13 or some other embodiment herein, wherein the control transmission is a downlink control information (DCI) transmission transmitted via a physical downlink control channel (PDCCH), the DCI being used to schedule a physical downlink shared channel (PDSCH) transmission, and wherein the method further includes: avoiding monitoring subsequent PDCCH transmissions within a defined processing time after the PDSCH transmission.

[0227] Embodiment 27 may include a method according to embodiment 13 or some other embodiment herein, wherein the control transmission is a downlink control information (DCI) transmission transmitted via a physical downlink control channel (PDCCH), the DCI being used to schedule a physical downlink shared channel (PDSCH) transmission, and wherein the method further includes: avoiding monitoring subsequent PDSCH transmissions within a defined processing time after the PDSCH transmission.

[0228] Embodiment 28 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1 to 27, or any other method or process described herein.

[0229] Embodiment 29 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 27 or any other method or process described herein.

[0230] Embodiment 30 may include an apparatus including logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 27, or any other method or process described herein.

[0231] Embodiment 31 may include methods, techniques or processes described or related to any one of Embodiments 1 to 27, or parts or components thereof.

[0232] Embodiment 32 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one of Embodiments 1 to 27, or a portion thereof.

[0233] Embodiment 33 may include a signal as described or related to any one of Embodiments 1 to 27, or a portion or component thereof.

[0234] Embodiment 34 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any one of Embodiments 1 to 27, or otherwise described in the present disclosure.

[0235] Embodiment 35 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 27, or a portion or component thereof, or otherwise described in this disclosure.

[0236] Embodiment 36 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any one of Embodiments 1 to 27, or a portion or component thereof, or otherwise described in the present disclosure.

[0237] Embodiment 37 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or portion thereof, as described or related to any one of Embodiments 1 to 27.

[0238] Embodiment 38 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, as described or related to any one of Embodiments 1 to 27.

[0239] Embodiment 39 may include signals in a wireless network as shown and described herein.

[0240] Embodiment 40 may include a method of communicating in a wireless network as shown and described herein.

[0241] Embodiment 41 may include a system for providing wireless communications as shown and described herein.

[0242] Embodiment 42 may include an apparatus for providing wireless communications as shown and described herein.

[0243] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0244] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method of operating a base station in an Internet of Things (IoT) non-terrestrial network (NTN), the method comprising: generating a control transmission indicating whether a hybrid automatic repeat request (HARQ) feedback is to be disabled for a HARQ process within the IoT NTN; transmitting the control transmission to a user equipment (UE); and An uplink transmission received from the UE that corresponds to the control transmission is identified.

2. The method of claim 1 , wherein the control transmission is a radio resource control (RRC) transmission, and wherein a physical downlink shared channel (PDSCH)-ConfigDedicated information element or a physical uplink shared channel (PUSCH)-ConfigDedicated information element of the RRC transmission includes a field indicating whether the HARQ feedback is to be disabled for the HARQ process.

3. The method of claim 1 , wherein the control transmission is a downlink control information (DCI) transmission for scheduling the HARQ process, and wherein the DCI transmission includes a field indicating whether the HARQ feedback is to be disabled for the HARQ process.

4. The method of claim 1 , wherein the control transmission is a downlink control information (DCI) transmission for scheduling the HARQ process, and wherein a cyclic redundancy check (CRC) of the DCI transmission is masked with a radio network temporary identifier (RNTI) different from a cell radio network temporary identifier (C-RNTI) of a cell corresponding to the UE to indicate that the HARQ feedback is to be disabled.

5. The method of claim 1 , wherein the control transmission is a downlink control information (DCI) transmission for scheduling the HARQ process, and wherein the DCI transmission includes a HARQ-ACK delay field or a HARQ-ACK resource offset field having a code point indicating that the HARQ feedback is to be disabled.

6. The method of claim 1 , wherein the control transmission is a radio resource control (RRC) transmission, wherein the method further comprises: generating downlink control information (DCI) transmission further indicating whether the HARQ feedback is to be disabled for the HARQ process; as well as The DCI transmission is transmitted to the UE.

7. The method of claim 6, wherein the RRC transmission includes an RRC field indicating whether the HARQ feedback is to be disabled for the HARQ process, and wherein the DCI transmission includes a DCI field further indicating whether the HARQ feedback is to be disabled for the HARQ process.

8. The method of claim 1, wherein the control transmission is a radio resource control (RRC) transmission, and wherein the RRC transmission includes a configuration in a semi-persistent scheduling (SPS)-Config information element indicating whether the HARQ feedback is to be disabled for the HARQ process.

9. One or more computer-readable media having instructions stored thereon, wherein the instructions, when executed by one or more processors, cause a user equipment (UE) in an Internet of Things (IoT) non-terrestrial network (NTN) to: identifying a control transmission received from a base station of the IoT NTN indicating that a hybrid automatic repeat request (HARQ) feedback is to be disabled for a HARQ process; determining, based on the control transmission, that HARQ feedback is to be disabled for the HARQ process; generating an uplink transmission with a HARQ codebook based on determining that the HARQ feedback is to be disabled for the HARQ process; and The uplink transmission is transmitted to the base station.

10. The one or more computer-readable media of claim 9, wherein based on determining that the HARQ feedback is to be disabled for the HARQ process, the HARQ codebook omits a corresponding bit for the HARQ process.

11. The one or more computer-readable media of claim 9, wherein the HARQ codebook includes a negative acknowledgement (NACK) for the HARQ process based on determining that the HARQ feedback is to be disabled for the HARQ process.

12. One or more computer-readable media according to any one of claims 9 to 11, wherein the HARQ process is part of a HARQ with transmission time interval (TTI) bundling, and wherein HARQ information for the HARQ process is regarded as an acknowledgment (ACK) for determining the HARQ codebook.

13. One or more computer-readable media according to any one of claims 9 to 11, wherein the HARQ process is part of a HARQ with transmission time interval (TTI) bundling, wherein the control transmission indicates that all HARQ processes within the HARQ with TTI bundling will disable HARQ feedback, and wherein based on disabling HARQ feedback for all HARQ processes within the HARQ with TTI bundling, the HARQ codebook omits a HARQ-acknowledgement (ACK) bit.

14. One or more computer-readable media according to any one of claims 9 to 11, wherein the HARQ process is part of a HARQ with transmission time interval (TTI) bundling, wherein the control transmission indicates that all HARQ processes within the HARQ with TTI bundling will disable HARQ feedback, and wherein based on all the HARQ processes within the HARQ with TTI bundling disabling HARQ feedback, the HARQ codebook has a HARQ-ACK bit value corresponding to an acknowledgment (ACK).

15. The one or more computer-readable media of claim 9, wherein the HARQ process is to be performed on a serving cell of a plurality of configured serving cells, and wherein the HARQ codebook has a negative acknowledgement (NACK) value corresponding to the HARQ process based on a determination that the HARQ feedback is to be disabled for the HARQ process.

16. The one or more computer-readable media of claim 9, wherein the HARQ process is to be performed on a serving cell of a plurality of configured serving cells, and wherein the HARQ codebook has an acknowledgment (ACK) value corresponding to the HARQ process based on a determination that the HARQ feedback is to be disabled for the HARQ process.

17. One or more computer-readable media according to any one of claims 9 to 12, wherein the HARQ process is to be performed on a serving cell of a plurality of configured serving cells, The instructions, when executed by the one or more processors, further cause the UE to: A corresponding physical downlink shared channel (PDSCH) decoding result is determined, wherein the HARQ codebook has an acknowledgement (ACK) value or a negative acknowledgement (NACK) value based on the PDSCH decoding result.

18. One or more computer-readable media according to any one of claims 9 to 12, wherein the HARQ process is to be performed on a serving cell among a plurality of configured serving cells, wherein the control transmission indicates that all scheduled HARQ processes on all of the plurality of configured serving cells are to disable HARQ feedback, and wherein the HARQ feedback is omitted from the HARQ codebook.

19. The one or more computer-readable media of claim 9, wherein the HARQ process is to be performed on a serving cell of a plurality of configured serving cells, wherein the control transmission indicates that all scheduled HARQ processes on all of the plurality of configured serving cells are to disable HARQ feedback, wherein the instructions, when executed by the one or more processors, further cause the UE to: A downlink control information (DCI) decoding result is determined, wherein the HARQ codebook includes a negative acknowledgement (NACK) value or a discontinuous transmission (DTX) value for the HARQ process.

20. One or more computer-readable media according to any one of claims 9 to 12, wherein the control transmission is a downlink control information (DCI) transmission transmitted via a physical downlink control channel (PDCCH), the DCI being used to schedule a physical downlink shared channel (PDSCH) transmission, and wherein the instructions, when executed by the one or more processors, also cause the UE to avoid monitoring subsequent PDCCH transmissions within a defined processing time after the PDSCH transmission.

Citation Information

Cited By

  • SPS transmission for IoT ntn

    WO2025232267A1