HARQ status for RRC configuration for multi-tb

Abstract

The embodiment of the invention relates to a terminal device, a network device, a method, a device and a computer readable storage medium for HARQ state of RRC configuration of multi-TB scheduling. In a solution, a terminal device may receive information that schedules a plurality of TBs and indicates a plurality of HARQ processes, and may also determine the same HARQ state for all of the plurality of HARQ processes based on a configured HARQ state of a particular HARQ process of the plurality of HARQ processes. Therefore, the same HARQ state can be applied to all scheduled TBs. Thus, flexibility with respect to scheduling is provided, and in addition, DRX behavior for multi-TB scheduling is simplified.

Description

Technical Field

[0001] Example embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to devices, methods, apparatuses, and computer-readable storage media for hybrid automatic repeat request (HARQ) states for radio resource control (RRC) configuration for multi-transport block (TB) scheduling. Background Art

[0002] Non-terrestrial communications can be considered as a complementary approach to terrestrial deployments, where satellite connectivity can provide coverage beyond terrestrial deployments. The 3rd Generation Partnership Project (3GPP) has defined work items for Release 17 (R17) for non-terrestrial networks (NTN) and R18 for Internet of Things (IoT)-NTN performance enhancements, where HARQ enable / disable is an important feature in both work items.

[0003] The benefit of disabling HARQ feedback for NTN and IoT over NTN is to enable the gNB to reuse the HARQ process ID before the full HARQ round trip time (RTT) elapses to avoid HARQ stalls and reduce transmission delays, as well as enable peak throughput. However, some details about the HARQ states should be further studied. Summary of the invention

[0004] Generally, example embodiments of the present disclosure provide a solution for HARQ states of RRC configuration for multi-TB scheduling.

[0005] In a first aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the terminal device at least: receives information that schedules multiple TBs and indicates multiple HARQ processes from a network device; determines a configured HARQ state of a specific HARQ process among the multiple HARQ processes; and determines that all HARQ processes among the multiple HARQ processes have the same HARQ state, which is the configured HARQ state of the specific HARQ process.

[0006] In a second aspect, a network device is provided. The network device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, causes the network device to at least: determine a plurality of HARQ processes including a specific HARQ process with a configured HARQ state; and send information scheduling a plurality of TBs and indicating the plurality of HARQ processes to a terminal device.

[0007] In a third aspect, a method performed by a terminal device is provided. The method includes: receiving information scheduling multiple TBs and indicating multiple HARQ processes from a network device; determining a configured HARQ state of a specific HARQ process among the multiple HARQ processes; and determining that all HARQ processes among the multiple HARQ processes have the same HARQ state, which is the configured HARQ state of the specific HARQ process.

[0008] In a fourth aspect, a method performed by a network device is provided, comprising: determining a plurality of HARQ processes including a specific HARQ process having a configured HARQ state; and sending information scheduling a plurality of TBs and indicating the plurality of HARQ processes to a terminal device.

[0009] In a fifth aspect, an apparatus is provided. The apparatus includes: a component for receiving information that schedules multiple TBs and indicates multiple HARQ processes from a network device; a component for determining a configured HARQ state of a specific HARQ process among the multiple HARQ processes; and a component for determining that all HARQ processes among the multiple HARQ processes have the same HARQ state, which is the configured HARQ state of the specific HARQ process.

[0010] In a sixth aspect, an apparatus is provided. The apparatus includes: a component for determining a plurality of HARQ processes including a specific HARQ process having a configured HARQ state; and a component for sending information scheduling a plurality of TBs and indicating the plurality of HARQ processes to a terminal device.

[0011] In a seventh aspect, a terminal device is provided. The terminal device includes: a receiving circuit system configured to receive information that schedules multiple TBs and indicates multiple HARQ processes from a network device; a determining circuit system configured to determine a configured HARQ state of a specific HARQ process among the multiple HARQ processes; and a determining circuit system configured to determine that all HARQ processes among the multiple HARQ processes have the same HARQ state, which is the configured HARQ state of the specific HARQ process.

[0012] In an eighth aspect, a network device is provided, comprising: a determining circuit system configured to determine multiple HARQ processes including a specific HARQ process having a configured HARQ state; and a sending circuit system configured to send information scheduling multiple TBs and indicating multiple HARQ processes to a terminal device.

[0013] In a ninth aspect, a non-transitory computer-readable medium is provided, wherein the non-transitory computer-readable medium includes program instructions for causing an apparatus to at least perform the method in any one of the third to fourth aspects.

[0014] In a tenth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, causes the apparatus to at least perform the method in any one of the third to fourth aspects.

[0015] It should be understood that the summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0017] Figure 1A-1B A schematic diagram illustrating multiple TBs scheduled by downlink control information (DCI) is shown;

[0018] Figure 2 illustrates an example of a network environment in which some example embodiments of the present disclosure may be implemented;

[0019] Figure 3 illustrates an example of a process flow according to some example embodiments of the present disclosure;

[0020] Figure 4 illustrates another example of a process flow for signaling according to some example embodiments of the present disclosure;

[0021] Figure 5 A flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure is illustrated;

[0022] Figure 6 A flowchart of a method implemented at a network device according to some example embodiments of the present disclosure is illustrated;

[0023] Figure 7 illustrates a simplified block diagram of a device suitable for implementing some example embodiments of the present disclosure; and

[0024] Figure 8 A block diagram illustrating an example of a computer readable medium according to some example embodiments of the present disclosure is illustrated.

[0025] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0026] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure without proposing any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the modes described below.

[0027] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0028] References in this disclosure to "one embodiment," "an embodiment," and "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0029] It should be understood that although the terms "first" and "second" etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms only distinguish one element from another. For example, without departing from the scope of the exemplary embodiment, the first element can be referred to as the second element, and similarly, the second element can be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0030] The term used herein is only for the purpose of describing a particular embodiment and is not intended to limit the exemplary embodiment. As used herein, unless the context clearly indicates otherwise, the singular form "one", "an" and "the" are intended to also include plural forms. It will be further understood that the terms "include", "include", "have", "have", "include" and / or "include" are used herein to specify the existence of features, elements, and / or components, but do not exclude the existence or addition of one or more other features, elements, components and / or their combinations. As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar wording, wherein the list of two or more elements is connected by "and" or "or", meaning at least any one of the elements or at least any two or more of the elements, or at least all of the elements.

[0031] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0032] (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuitry), and

[0033] (b) a combination of hardware circuitry and software such as (where applicable):

[0034] (i) a combination of (one or more) analog and / or digital hardware circuits and software / firmware, and

[0035] (ii) any part of a hardware processor(s) (including a digital signal processor(s)) with software, software and memory(s) that work together to enable a device (such as a mobile phone or server)

[0036] Perform various functions, and

[0037] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) for operation, but where the software may not be present, the software may not be required for operation.

[0038] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to a particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing device, or network device.

[0039] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Non-terrestrial Network (NTN), IoT on NTN, etc. In addition, the communication in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), sixth generation (6G) communication protocols, and / or any other currently known or future to be developed protocols. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be communication technologies and systems of future types that can embody the present disclosure. It should not be regarded as limiting the scope of the present disclosure to the aforementioned systems.

[0040] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. A network device may refer to a base station (BS) or an access point (AP), for example, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a new radio (NR) NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), an integrated access and backhaul (IAB) node, a relay, a low power node such as a femto and a pico, etc., depending on the terminology and technology applied.

[0041] The term "terminal device" refers to any terminal device that may be capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image acquisition terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), an Internet of Things (IoT) device, a machine type communication (MTC) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated processing chain), consumer electronic devices, devices operating on a commercial and / or industrial wireless network, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0042] There are specifications for multi-TB scheduling, i.e., multiple TBs (such as 1, 2, 4, 6, 8) are scheduled by one DCI in IoT in a terrestrial network (TN), where each TB is associated with a separate HARQ process, and the HARQ process ID will be indicated in the DCI. For example, multiple TBs scheduled by one DCI can be sent continuously or interleaved.

[0043] Figure 1A A schematic diagram 110 illustrating multiple TBs scheduled by DCI using consecutive transmissions, and Figure 1BA schematic diagram 120 is shown of multiple TBs scheduled by DCI using staggered transmission. Specifically, one DCI is used to schedule multiple downlink (DL) or uplink (UL) TBs, wherein Figure 1A-1B The "AN" in the DCI refers to confirmation or negative confirmation. For example, for unicast, there may be up to 8 TBs for enhanced machine type communication (eMTC), for example, 8 for coverage enhancement (CE) mode A and 4 for CE mode B; and for NB-IoT, there may be up to 2 TBs. For example, for multicast, there may be up to 8 TBs for eMTC and NB-IoT. Specifically, the number of scheduled TBs is indicated by the DCI, and TBs scheduled by one DCI can use the same resource allocation, MCS, and number of repetitions.

[0044] In some examples, a DCI that schedules multiple TBs may be referred to as a DCI for multi-TB scheduling.

[0045] When multiple TBs are scheduled for NB-IoT, the drx-InactivityTimer will be (re)started when all HARQ RTT timers (corresponding to HARQ processes belonging to the same multi-TB scheduling) have expired for both UL and DL. In addition, for NB-IoT and eMTC, the (UL) HARQ RTT timers of all HARQ processes corresponding to the scheduled TBs are started in the subframe containing the last repetition of the (PUSCH transmission) PDSCH reception of the last scheduled TB. The discontinuous reception (DRX) behavior on multi-TB scheduling described in detail with some examples can be found in the content of the following box.

[0046]

[0047]

[0048] As mentioned, HARQ enable / disable is an important feature in NTN communications. In NR NTN, disabling HARQ feedback for downlink transmission is semi-statically configured by RRC signaling. The configuration is indicated by a bitmap according to the HARQ process index. For example, if the number of configured HARQ processes is 32, the bitmap is a 32-bit bitmap. Considering many factors such as reliability, throughput, scheduling efficiency, power consumption, etc., the network can configure the same or different HARQ feedback states (i.e., HARQ feedback disabled or HARQ feedback enabled) for each HARQ process. In addition, for the HARQ feedback disable / enable agreed in NR NTN, there will be different operations on DRX, as shown below:

[0049] For HARQ feedback disable: The DRX HARQ RTT timer will not be started, which means that the network can continue to schedule retransmissions or new transmissions without waiting for the RTT time length to get the decoding result of the transmission.

[0050] For HARQ feedback enabled: drx-HARQ-RTT-TimerDL length increases the UE-gNB RTT. In this case, the network needs to wait for the RTT time length to get the decoding result of the transmission, and therefore schedule a retransmission or a new transmission based on the decoding result.

[0051] In IoT over NTN, HARQ feedback disable / enable discussion is in progress. It is agreed to support HARQ feedback enable and disable to ensure the reliability of some important Medium Access Control (MAC) Control Element (CE) and RRC signaling, as well as to avoid HARQ stalling.

[0052] Since the number of HARQ processes in IoT and eMTC may be smaller than that of NR UE, for example, there are up to 2 HARQ processes for NB-IoT and 4 HARQ processes for eMTC CE Mode B, if the NR NTN solution is reused, a lot of signaling may be required when reconfiguring HARQ feedback enable / disable. Therefore, dynamic HARQ feedback enable / disable for IoT on NTN is discussed. The content in the following box is some relevant protocols in 3GPP Radio Access Network Group 1 (RAN1) on HARQ feedback enable / disable.

[0053]

[0054] The protocol in RAN1 is to support both option 1 (i.e., as per HARQ process via UE-specific RRC signaling in a semi-static manner) and option 3 (i.e., dynamically and explicitly indicated by DCI) to disable / enable HARQ feedback for NB-IoT and eMTC CE mode B. Both option 1 and option 3 can be configured by the NW. In the case where DCI solution enable / disable signaling (option 3) is configured and bitmap signaling as per HARQ process (option 1) is not configured, the DCI signaling directly indicates the HARQ feedback enable / disable for the corresponding transmission. In some cases, it is agreed that for NB-IoT and LTE-MTC in CE mode B, if multiple TBs are configured, for the direct indication of DCI-based HARQ enable / disable in multiple TBs scheduled by a single DCI, the same indication applies to all scheduled TBs, i.e., HARQ is enabled or disabled for all TBs.

[0055] In some cases, if only option 1 is configured (i.e., as per HARQ process via UE-specific RRC signaling in a semi-static manner), it is possible that some HARQ processes are configured as HARQ feedback disabled and some HARQ processes are configured as feedback enabled for multi-TB scheduling. For HARQ processes with DL HARQ feedback enabled, the HARQ RTT timer length is increased by an offset equal to the UE-gNB RTT. For HARQ processes with DL HARQ feedback disabled, the UE will not start the corresponding DL HARQ RTT timer. In this case, DRX-related operations on multi-TB scheduling will not be suitable because the current specified condition for NB-IoT to start or restart the drx-InactivityTimer is "when all HARQ RTT timers have expired", and since the DL HARQ RTT timer is not started for the HARQ process with DL HARQ feedback disabled, the drx-InactivityTimer will not be started or restarted. Therefore, at least for DRX-related operations, detailed solutions on how to use option 1 should be further studied.

[0056] An example embodiment of the present disclosure provides a solution for HARQ state determination for multi-TB scheduling. In the solution, a terminal device can receive information that schedules multiple TBs and indicates multiple HARQ processes, and the terminal device can also determine the same HARQ state for all HARQ processes in the multiple HARQ processes based on the configured HARQ state of a specific HARQ process in the multiple HARQ processes. Therefore, the same HARQ state can be applied to all scheduled TBs. Therefore, flexibility in scheduling is provided, and in addition, the DRX behavior for multi-TB scheduling is simplified. The principles and some example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0057] Figure 2 An example of a network environment 200 in which some example embodiments of the present disclosure may be implemented is illustrated. The network environment 200 may also be referred to as a network system, a communication environment, a communication network, a communication system, etc., and the present disclosure is not limited in this respect. In some example embodiments, the network environment 200 may be implemented as an NTN.

[0058] The network environment 200 may include a terminal device 210 and a network device 220 , and the network device 220 may include a network device 220 - 1 on the ground and / or a communication satellite 220 - 2 .

[0059] In some implementations, network device 220 includes communication satellite 220-2, which can operate as a gNB, or in other words, the gNB (onboard) can be located in communication satellite 220-2. In some examples, terminal device 210 can be located within the coverage area of ​​communication satellite 220-2, for example, the coverage area can be referred to as an NTN cell. In some examples, communication satellite 220-2 can be connected to Figure 2 Communicates with a gateway device associated with a 5G core network (CN) not shown.

[0060] In some implementations, network device 220 includes network device 220-1 on the ground and communication satellite 220-2. In some examples, communication satellite 220-2 can operate as a passive or transparent network relay node between network device 220-1 on the ground and terminal device 210. In some embodiments, communication satellite 220-2 can communicate with terminal device 210 via a service link or wireless interface, and communicate with network device 220-1 on the ground via a feeder link or wireless interface.

[0061] In some embodiments, the communication satellite 220-2 may include a geosynchronous orbit (GEO) satellite, a low earth orbit (LEO) satellite, or other types of satellites. In some embodiments, the satellite 220-2 may belong to one or more satellite systems or architectures, such as a global navigation satellite system (GNSS), a global positioning system (GPS), a global navigation satellite system (GLONASS), a BeiDou navigation satellite system (BDS), etc.

[0062] It should be understood that Figure 2 The network environment 200 shown in FIG. 1 is for illustrative purposes only and does not imply any limitation on the scope of the present disclosure. Figure 2 The terminal device 210 is depicted as a mobile phone, but the terminal device 210 may be any type of user equipment.

[0063] It should be understood that Figure 2 The number of devices (ie, terminal device 210, network device 220) and their connection relationships and types shown in the figure are for illustration purposes only and do not imply any limitation. Network environment 200 may include any suitable number of devices suitable for implementing the embodiments of the present disclosure.

[0064] In the present disclosure, the term "HARQ state" may also be referred to as a HARQ state in a downlink or a HARQ state in an uplink. In the present disclosure, a HARQ state in a downlink may be a HARQ feedback state, a state of HARQ feedback, etc., which may be HARQ feedback disabled (disabled), or HARQ feedback enabled (enabled). In the present disclosure, a HARQ state in an uplink may be a HARQ mode state, a state of HARQ mode, etc., which may be HARQ mode A, or HARQ mode B.

[0065] refer to Figure 3 , Figure 3 An example of a process flow 300 according to some example embodiments of the present disclosure is illustrated. For discussion purposes, reference will be made to Figure 2 300. Process flow 300 involves terminal device 210 and network device 220. It should be understood that although Figure 2 The process flow 300 is described in the network environment 200 of FIG. 1 , but the process flow can also be applied to other communication scenarios.

[0066] like Figure 3 As shown, the network device 220 may send 301 an RRC message 302 to the terminal device 210, and thus the terminal device 210 may receive 303 the RRC message 302. In some example embodiments, the RRC message 302 may also be referred to as an RRC configuration, an RRC configuration message, or the like.

[0067] In some example embodiments, RRC message 302 may include a bitmap indicating a set of HARQ states corresponding to a set of HARQ processes. In other words, network device 220 may configure the HARQ states via the bitmap per HARQ process. In some examples, bitmap signaling per HARQ process is configured by network device 220, for example, only the case of option 1 being configured.

[0068] Assume that the HARQ state in the downlink can be configured. As an example, assume that 4 HARQ processes have been configured with different HARQ feedback states for eMTCCE mode B, as shown below:

[0069] HARQ process ID 0: HARQ feedback disabled;

[0070] HARQ process ID 1: HARQ feedback enabled;

[0071] HARQ process ID 2: HARQ feedback disabled; and

[0072] HARQ process ID 3: HARQ feedback enabled.

[0073] It should be understood that this example is for illustration only and is not limiting in any way, and some other examples not listed herein are also suitable.

[0074] In process 300, the network device 220 determines 310 a plurality of HARQ processes, wherein the plurality of HARQ processes includes a particular HARQ process having a configured HARQ state.

[0075] In some implementations, the network device 220 may determine the number of multiple TBs to be scheduled, for example, the number of TBs may be expressed as N, where N is a positive integer. For example, N may be one of the following: 1, 2, 4, 6, 8, or another integer. In some examples, multiple TBs are scheduled for NB-IoT on NTN, eMTC CE mode A on NTN, eMTC EC mode B on NTN, or NR on NTN, and the present disclosure is not limited in this regard.

[0076] In some implementations, the network device 220 may determine a specific HARQ state for multiple TBs, i.e., multiple TBs will apply the same HARQ state. In some examples, taking the HARQ state in the downlink as an example, the specific HARQ state may be HARQ feedback enabled, or may be HARQ feedback disabled. In some other examples, taking the HARQ state in the uplink as an example, the specific HARQ state may be HARQ mode A, or may be HARQ mode B.

[0077] In some implementations, the network device 220 may determine (or select) a specific HARQ process that has been configured with a specific HARQ state. As an example mentioned above, if the specific HARQ state is determined to be "HARQ feedback disabled", then HARQ process ID 0 or HARQ process ID 2 may be selected as the specific HARQ process. As an example mentioned above, if the specific HARQ state is determined to be "HARQ feedback enabled", then HARQ process ID 1 or HARQ process ID 3 may be selected as the specific HARQ process.

[0078] In some implementations, the network device 220 may determine a plurality of HARQ processes corresponding to a plurality of TBs, wherein the plurality of HARQ processes include a specific HARQ process, and the specific HARQ process is at a specific position in the plurality of HARQ processes. In some examples, the specific HARQ process corresponds to a specific TB in the plurality of TBs, for example, the specific HARQ process corresponds to a first TB, an mth TB, a middle TB, or a last TB in the plurality of TBs.

[0079] In some examples, multiple HARQ processes may be sorted, and a particular HARQ process may be at a particular position in the sorting. In some implementations, the particular position may be the first position in the sorting, the last position in the sorting, the mth position in the sorting, or an intermediate position in the sorting.

[0080] It should be understood that there is a protocol about a specific location between the terminal device 210 and the network device 220, and the specific HARQ process is located at the specific location. In some examples, the specific location can be predefined. In some other examples, the specific location can be configured to the terminal device 210 by the network device 220.

[0081] Additionally or alternatively, the network device 220 may send to the terminal device 210 (in Figure 3 In some examples, the configuration indicating the specific location may be the RRC message 302 discussed above. In some other examples, the configuration indication of the specific location may be independent of the RRC message 302 discussed above.

[0082] In some implementations, the specific position may be the first position in the order, the last position in the order, the mth position in the order, or the middle position in the order. Thus, the specific HARQ process may be the first HARQ process in a plurality of HARQ processes, the last HARQ process in a plurality of HARQ processes, the mth HARQ process in a plurality of HARQ processes, or the middle HARQ process in a plurality of HARQ processes. For example, m may be an integer not greater than N.

[0083] In some examples, the middle position may be associated with N / 2. In some examples, the ranking of the middle HARQ process in the plurality of HARQ processes may be equal to a smallest integer greater than N / 2. In some examples, the ranking of the middle HARQ process in the plurality of HARQ processes may be equal to a largest integer no greater than N / 2. In some examples, the middle HARQ process in the plurality of HARQ processes may be an nth HARQ process in the plurality of HARQ processes, where or

[0084] In process 300, network device 220 sends 320 information 322 to terminal device 210, wherein the information schedules a plurality of TBs and indicates a corresponding plurality of HARQ processes. In some examples, the information may include a DCI that schedules the plurality of TBs.

[0085] In some implementations, information (such as a DCI) may include multiple HARQ process IDs in an ordering, where a particular HARQ process ID is located at a particular position in the ordering.

[0086] In some example embodiments, no HARQ state need be included in information 322 (such as DCI), in which case overhead may be reduced. In some examples, information 322 includes a plurality of HARQ processes DI in an order, but does not include any HARQ state.

[0087] On the other side of the communication, the terminal device 210 receives 324 information 322 scheduling multiple TBs and indicating multiple HARQ processes.

[0088] In process 300, the terminal device 210 determines 330 a configured HARQ state of a particular HARQ process of a plurality of HARQ processes.

[0089] In some implementations, the terminal device 210 may determine which is a specific HARQ process at a specific position among multiple HARQ processes. For example, if the specific position is the first, the terminal device 210 may determine that the specific HARQ process is the first of the multiple HARQ processes. As an example, assume that the specific HARQ process is HARQ process ID 0.

[0090] In some implementations, the terminal device 210 may determine the configured HARQ state for a particular HARQ process, for example based on the RRC message 302. For example, the configured HARQ state for HARQ process ID 0 is "HARQ feedback disabled".

[0091] In process 300, the terminal device 210 determines 340 that all HARQ processes in the multiple HARQ processes indicated by the information 322 have the same HARQ state, namely the configured HARQ state of the specific HARQ process. In some examples, the same HARQ state is determined based on the configured HARQ state of the specific HARQ process without considering the other N-1 configured HARQ states of the other N-1 HARQ processes in the multiple HARQ processes.

[0092] In some examples, multiple TBs are scheduled by DCI for downlink transmission, in which aspect, the same HARQ state for all TBs in the multiple TBs may be HARQ feedback disabled in the downlink, or may be HARQ feedback enabled in the downlink.

[0093] In some other examples, multiple TBs are scheduled by DCI for uplink transmission, in which aspect, the same HARQ state for all TBs in the multiple TBs can be a HARQ mode in the uplink, or can be a HARQ mode B in the uplink.

[0094] Additionally or alternatively, the scheduled transmission can be further performed at 350. In some examples, DRX-related operations can be performed based on the same HARQ state for all TBs in the plurality of TBs.

[0095] According to some embodiments described above, a solution for determining the HARQ state of all scheduled TBs in multi-TB scheduling using only RRC configuration (i.e., option 1 only) as HARQ feedback disable / enable is proposed. Specifically, when multiple TBs are scheduled, rules for determining the HARQ state of all HARQ processes associated with multi-TB scheduling can be defined. Using this solution, the network device 220 can flexibly notify the terminal device 210 of the same HARQ state (i.e., HARQ feedback disable / enable) for all scheduled TBs, and use a unified solution for different HARQ state indication solutions to provide flexibility in scheduling and simplify DRX operation.

[0096] Figure 4 An example of a process flow 400 according to some example embodiments of the present disclosure is illustrated. For discussion purposes, reference will be made to Figure 2 400. Process flow 400 involves terminal device 210 and network device 220. It should be understood that although Figure 2 The process flow 400 is described in the network environment 200 of FIG. 1 , but the process flow can also be applied to other communication scenarios.

[0097] For ease of description, the process flow 400 is discussed using the downlink as an example, in which case the HARQ state may be a HARQ feedback state, such as HARQ feedback enabled or HARQ feedback disabled. However, it should be understood that a similar solution may be applied to the uplink, where the HARQ state may be a HARQ mode, such as HARQ mode A or HARQ mode B.

[0098] At 410, the network device 220 may configure the HARQ feedback state (enabled or disabled) via a bitmap per HARQ process, and the network device 220 may also configure a specific position of a specific HARQ process (such as the first one), which may be used to determine the same HARQ feedback state for all scheduled TBs in one DCI. It should be understood that the specific position may also be predefined.

[0099] As an example, assume that 4 HARQ processes have been configured with different HARQ feedback states for eMTC CE mode B as follows: HARQ process ID 0: HARQ feedback disabled; HARQ process ID 1: HARQ feedback enabled; HARQ process ID 2: HARQ feedback disabled; and HARQ process ID 3: HARQ feedback enabled.

[0100] At 420, the network device 220 may determine the number of multiple TBs scheduled by the DCI, for example, the number may be represented as N, and the network device 220 may also determine the HARQ feedback status of all scheduled TBs, for example, the HARQ feedback status of all scheduled TBs is determined to be HARQ feedback disabled.

[0101] At 420, the network device 220 may also determine a HARQ process (e.g., HARQ process ID 0 or HARQ process ID 2) having a configured HARQ feedback state as HARQ feedback disabled, and schedule the HARQ process as the first HARQ process, scheduling the next N-1 HARQ processes regardless of the configured N-1 HARQ feedback states.

[0102] As an example, if the same HARQ feedback state of all scheduled TBs is determined to be HARQ feedback disabled, the multiple HARQ processes may be:

[0103] If N=1, any one of {HARQ process ID 0} or {HARQ process ID 2}; if N=2, any one of {HARQ process ID 0, HARQ process ID 1}, {HARQ process ID 0, HARQ process ID 2}, {HARQ process ID 0, HARQ process ID 3} or {HARQ process ID 2, HARQ process ID 3};

[0104] If N=3, any one of {HARQ process ID 0, HARQ process ID 1, HARQ process ID 2}, {HARQ process ID 0, HARQ process ID 1, HARQ process ID 3}, {HARQ process ID 0, HARQ process ID 2, HARQ process ID 3}; or if N=4, {HARQ process ID 0, HARQ process ID 1, HARQ process ID 2, HARQ process ID 3}.

[0105] Compared to conventional scheduling that may only schedule {HARQ process ID 0}, {HARQ process ID 2}, or {HARQ process ID 0, HARQ process ID 2}, the present disclosure provides flexibility regarding scheduling, where there are more options selected by the network device 220, and scheduling opportunities are expanded.

[0106] At 430 , the network device 220 may send a DCI for multi-TB scheduling, for example, the DCI schedules N TBs for eMTC CE mode B and indicates N HARQ processes, where the first HARQ process is HARQ process ID 0 or HARQ process ID 2.

[0107] At 440, the terminal device 210 may determine that the HARQ feedback state for all scheduled TBs in the DCI should be the same, which is the configured HARQ feedback state of the first HARQ process (HARQ process ID 0 or HARQ process ID 2), i.e., HARQ feedback disabled.

[0108] According to reference Figure 3-Figure 4 In an embodiment, when the HARQ state is configured only via RRC configuration, there is no restriction on the configuration of the HARQ state (i.e., HARQ feedback disable / enable in downlink or HARQ mode A / B in uplink) for each HARQ process. In a multi-TB scheduling DCI, there are fewer restrictions on the scheduling of the HARQ process to be scheduled (i.e., a HARQ process configured with HARQ feedback disable / enable or configured with HARQ mode A / B). In addition, the unified DRX solution can support different HARQ feedback disable / enable (or HARQ mode A / B) signaling solutions, option 1 only, option 3 only, and option 1+option 3, which will reduce the specification complexity in DRX operation for multi-TB.

[0109] Figure 5 FIG. 5 is a flowchart of a method 500 implemented at a terminal device according to some example embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 2 The method 500 is described from the perspective of the terminal device 210 .

[0110] At block 510, the terminal device 210 receives information from a network device that schedules a plurality of TBs and indicates a plurality of HARQ processes. At block 520, the terminal device 210 determines a configured HARQ state of a specific HARQ process in the plurality of HARQ processes. At block 530, the terminal device 210 determines that all HARQ processes in the plurality of HARQ processes have the same HARQ state, which is the configured HARQ state of the specific HARQ process.

[0111] In some example embodiments, the terminal device 210 receives a configuration indicating a specific location of a specific HARQ process from a network device.

[0112] In some example embodiments, the specific location of a specific HARQ process is predefined.

[0113] In some example embodiments, the particular HARQ process is one of: a first HARQ process, a last HARQ process, an mth HARQ process, or a middle HARQ process among the plurality of HARQ processes.

[0114] In some example embodiments, the ranking of the middle HARQ processes in the plurality of HARQ processes is associated with N / 2, where N represents the number of the plurality of HARQ processes. In some example embodiments, the ranking of the middle HARQ processes in the plurality of HARQ processes is equal to one of: a smallest integer greater than N / 2, or a largest integer less than N / 2.

[0115] In some example embodiments, the terminal device 210 receives an RRC message from a network device, the RRC message comprising a bitmap indicating a set of configured HARQ states corresponding to a set of HARQ processes.

[0116] In some example embodiments, the plurality of HARQ processes include another HARQ process different from the specific HARQ process, and wherein the same HARQ state for all HARQ processes of the plurality of HARQ processes is determined regardless of another configured HARQ state of the other HARQ process.

[0117] In some example embodiments, the same HARQ state for all HARQ processes of the plurality of HARQ processes is HARQ feedback disabled in the downlink, or HARQ feedback enabled. In some example embodiments, the same HARQ state for all HARQ processes of the plurality of HARQ processes is HARQ mode A, or HARQ mode B in the uplink.

[0118] In some example embodiments, the information includes scheduling multi-TB DCI for one of: NB-IoT on NTN, eMTC CE mode A on NTN, eMTC CE mode B on NTN, or NR on NTN.

[0119] Figure 6 FIG. 6 is a flowchart of a method 600 implemented at a network device according to some example embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 2 Method 600 is described from the perspective of network device 220 .

[0120] At block 610, the network device 220 determines a plurality of HARQ processes including a specific HARQ process having a configured HARQ state. At block 620, the network device 220 sends information scheduling a plurality of TBs and indicating a plurality of HARQ processes to the terminal device.

[0121] In some example embodiments, network device 220 sends a configuration to the terminal device indicating a specific location of a specific HARQ process.

[0122] In some example embodiments, the specific location of a specific HARQ process is predefined.

[0123] In some example embodiments, the particular HARQ process is one of: a first HARQ process, a last HARQ process, an mth HARQ process, or a middle HARQ process among the plurality of HARQ processes.

[0124] In some example embodiments, the ordering of the middle HARQ process in the plurality of HARQ processes is associated with N / 2, where N represents the number of the plurality of HARQ processes.

[0125] In some example embodiments, the ranking of the middle HARQ process in the plurality of HARQ processes is equal to one of: a smallest integer greater than N / 2, or a largest integer less than N / 2.

[0126] In some example embodiments, the network device 220 sends an RRC message to the terminal device, the RRC message comprising a bitmap indicating a set of configured HARQ states corresponding to a set of HARQ processes.

[0127] In some example embodiments, the same HARQ state for all of the plurality of HARQ processes is determined by the terminal device as the configured HARQ state for the particular HARQ process.

[0128] In some example embodiments, the same HARQ state for all HARQ processes of the plurality of HARQ processes is HARQ feedback disabled in downlink, or HARQ feedback enabled.

[0129] In some example embodiments, the same HARQ state for all HARQ processes of the plurality of HARQ processes is HARQ Mode A, or HARQ Mode B in uplink.

[0130] In some example embodiments, the information includes scheduling multi-TB DCI for one of: NB-IoT on NTN, eMTC CE mode A on NTN, eMTC CE mode B on NTN, or NR on NTN.

[0131] In some example embodiments, an apparatus capable of executing method 500 (e.g., terminal device 210) may include means for executing the corresponding steps of method 500. The apparatus may be implemented in any suitable form. For example, the apparatus may be implemented in a circuit system or a software module.

[0132] In some example embodiments, the apparatus includes: a component for receiving information scheduling multiple TBs and indicating multiple HARQ processes from a network device; a component for determining a configured HARQ state of a specific HARQ process among the multiple HARQ processes; and a component for determining that all HARQ processes among the multiple HARQ processes have the same HARQ state, which is the configured HARQ state of the specific HARQ process.

[0133] In some example embodiments, the apparatus comprises means for receiving, from a network device, a configuration indicating a specific location of a specific HARQ process.

[0134] In some example embodiments, the specific location of a specific HARQ process is predefined.

[0135] In some example embodiments, the particular HARQ process is one of: a first HARQ process, a last HARQ process, an mth HARQ process, or a middle HARQ process among the plurality of HARQ processes.

[0136] In some example embodiments, the ordering of the middle HARQ process in the plurality of HARQ processes is associated with N / 2, where N represents the number of the plurality of HARQ processes.

[0137] In some example embodiments, the ranking of the middle HARQ process in the plurality of HARQ processes is equal to one of: a smallest integer greater than N / 2, or a largest integer less than N / 2.

[0138] In some example embodiments, the apparatus includes means for receiving an RRC message from a network device, the RRC message including a bitmap indicating a set of configured HARQ states corresponding to a set of HARQ processes.

[0139] In some example embodiments, the plurality of HARQ processes include another HARQ process different from the specific HARQ process, and wherein the same HARQ state for all HARQ processes of the plurality of HARQ processes is determined regardless of another configured HARQ state of the other HARQ process.

[0140] In some example embodiments, the configured HARQ state is HARQ feedback disabled, or HARQ feedback enabled in downlink. In some example embodiments, the configured HARQ state is HARQ Mode A, or HARQ Mode B in uplink.

[0141] In some example embodiments, the information includes scheduling multi-TB DCI for one of: NB-IoT on NTN, eMTC CE mode A on NTN, eMTC CE mode B on NTN, or NR on NTN.

[0142] In some example embodiments, an apparatus capable of performing method 600 (e.g., network device 220) may include components for performing the corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0143] In some example embodiments, the apparatus includes: means for determining a plurality of HARQ processes including a specific HARQ process having a configured HARQ state; and means for sending information scheduling a plurality of TBs and indicating the plurality of HARQ processes to a terminal device.

[0144] In some example embodiments, the apparatus comprises means for sending a configuration indicating a specific location of a specific HARQ process to a terminal device.

[0145] In some example embodiments, the specific location of a specific HARQ process is predefined.

[0146] In some example embodiments, the particular HARQ process is one of: a first HARQ process, a last HARQ process, an mth HARQ process, or a middle HARQ process among the plurality of HARQ processes.

[0147] In some example embodiments, the ordering of the middle HARQ process in the plurality of HARQ processes is associated with N / 2, where N represents the number of the plurality of HARQ processes.

[0148] In some example embodiments, the ranking of the middle HARQ process in the plurality of HARQ processes is equal to one of: a smallest integer greater than N / 2, or a largest integer less than N / 2.

[0149] In some example embodiments, the apparatus comprises: means for sending an RRC message to a terminal device, the RRC message comprising a bitmap indicating a set of configured HARQ states corresponding to a set of HARQ processes.

[0150] In some example embodiments, the same HARQ state for all of the plurality of HARQ processes is determined by the terminal device as the configured HARQ state for the particular HARQ process.

[0151] In some example embodiments, the configured HARQ state is HARQ feedback disabled, or HARQ feedback enabled in downlink. In some example embodiments, the configured HARQ state is HARQ Mode A, or HARQ Mode B in uplink.

[0152] In some example embodiments, the information includes scheduling multi-TB DCI for one of: NB-IoT on NTN, eMTC CE mode A on NTN, eMTC CE mode B on NTN, or NR on NTN.

[0153] Figure 7 A simplified block diagram of a device 700 suitable for implementing some example embodiments of the present disclosure is shown. The device 700 may be provided to implement a communication device, such as Figure 2 The terminal device 210 and the network device 220 are shown. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processors 710, and one or more communication modules 740 coupled to the processors 710.

[0154] The communication module 740 is used for two-way communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary for communicating with other network elements.

[0155] Processor 710 may be of any type suitable for the local technology network, and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Device 700 may have multiple processors, such as application specific integrated circuit chips that are time-dependent to a clock that synchronizes a main processor.

[0156] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not be retained during the duration of a power outage.

[0157] The computer program 730 includes computer executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 may perform any suitable actions and processes by loading the program 730 into the RAM 722.

[0158] The embodiments of the present disclosure can be implemented by means of program 730, so that the device 700 can execute the following steps: Figures 3 to 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0159] In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (such as in the memory 720) or in other storage devices accessible by the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0160] Figure 8 800 according to some example embodiments of the present disclosure. The computer readable medium 800 has a program 730 stored thereon. It should be noted that although Figure 8 Computer readable medium 800 is depicted in the form of a CD or DVD, but may be in any other form suitable for carrying or retaining program 730.

[0161] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representation, it should be understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0162] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as those included in a program module, executed in a device on a target real or virtual processor to perform the above-referenced Figures 3 to 6In any of the methods described in. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules can be combined or divided between program modules as desired. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0163] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the function / operation specified in the flow chart and / or block diagram to be realized. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0164] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0165] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include electrical connections with one or more lines, portable computer floppy disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. As used herein, the term "non-transient" is a restriction on the medium itself (i.e., tangible, not a signal), in contrast to the restriction on data storage persistence (e.g., RAM vs. ROM).

[0166] Further, although the operation is described in a specific order, this should not be understood as requiring such operation to be performed in the specific order shown or in a sorted order, or to perform all illustrated operations, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but rather descriptions of features that may be specific to a particular embodiment. Some features described in the context of the separated embodiment may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or with any suitable sub-combination.

[0167] Although the disclosure has been described in language specific to structural features and / or methodological acts, it will be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0168] The embodiments of the present disclosure provide the following examples.

[0169] Example 1. A terminal device, comprising:

[0170] at least one processor; and

[0171] At least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least:

[0172] Receiving information from a network device that schedules a plurality of transport blocks TB and indicates a corresponding plurality of hybrid automatic repeat request (HARQ) processes;

[0173] determining a configured HARQ state of a particular HARQ process among the plurality of HARQ processes; and

[0174] It is determined that all of the multiple HARQ processes have a same HARQ state, where the same HARQ state is a configured HARQ state for the particular HARQ process.

[0175] Example 2. The terminal device according to Example 1, wherein the terminal device is further configured to:

[0176] A configuration indicating a specific location of the specific HARQ process is received from the network device.

[0177] Example 3. The terminal device according to Example 1, wherein the specific location of the specific HARQ process is predefined.

[0178] Example 4. A terminal device according to any one of Examples 1 to 3, wherein the specific HARQ process is one of: the first HARQ process, the last HARQ process, the mth HARQ process, or an intermediate HARQ process among the multiple HARQ processes.

[0179] Example 5. A terminal device according to Example 4, wherein the ordering of the middle HARQ process in the multiple HARQ processes is associated with N / 2, where N represents the number of the multiple HARQ processes.

[0180] Example 6. The terminal device of Example 5, wherein the order of the middle HARQ process in the plurality of HARQ processes is equal to one of the following:

[0181] the smallest integer greater than N / 2, or

[0182] The largest integer not exceeding N / 2.

[0183] Example 7. The terminal device according to any one of Examples 1 to 6, wherein the terminal device is further caused to:

[0184] A radio resource control (RRC) message is received from the network device, the RRC message including a bitmap indicating a set of configured HARQ states corresponding to a set of HARQ processes.

[0185] Example 8. A terminal device according to any one of Examples 1 to 7, wherein the multiple HARQ processes include: another HARQ process different from the specific HARQ process, and wherein the same HARQ state for all HARQ processes in the multiple HARQ processes is determined regardless of another configured HARQ state of the other HARQ process.

[0186] Example 9. The terminal device according to any one of Examples 1 to 8, wherein the configured HARQ state is HARQ feedback disablement or HARQ feedback enablement in a downlink.

[0187] Example 10. The terminal device according to any one of Examples 1 to 8, wherein the configured HARQ state is HARQ feedback mode A or HARQ mode B in uplink.

[0188] Example 11. A terminal device according to any one of Examples 1 to 10, wherein the information includes downlink control information (DCI) scheduling multiple TBs for one of the following:

[0189] Narrowband Internet of Things (NB-IoT) over non-terrestrial networks (NTN),

[0190] Enhanced Machine Type Communication eMTC Coverage Enhancement CE Mode A over NTN,

[0191] eMTC CE Mode B on NTN, or

[0192] New Radio NR on NTN.

[0193] Example 12. A network device comprising:

[0194] at least one processor; and

[0195] at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least:

[0196] determining a plurality of hybrid automatic repeat request (HARQ) processes including a particular HARQ process having a configured HARQ state; and

[0197] Information scheduling multiple transport blocks TB and indicating the multiple HARQ processes is sent to the terminal device.

[0198] Example 13. The network device of Example 12, wherein the network device is further configured to:

[0199] A configuration indicating a specific location of the specific HARQ process is sent to the terminal device.

[0200] Example 14. The network device of Example 12, wherein the specific location of the specific HARQ process is predefined.

[0201] Example 15. A network device according to any one of Examples 12 to 14, wherein the particular HARQ process is one of: a first HARQ process, a last HARQ process, an mth HARQ process, or a middle HARQ process among the multiple HARQ processes.

[0202] Example 16. The network device of Example 15, wherein the ordering of the middle HARQ process in the plurality of HARQ processes is associated with N / 2, where N represents the number of the plurality of HARQ processes.

[0203] Example 17. The network device of Example 16, wherein the ordering of the middle HARQ process in the plurality of HARQ processes is equal to one of:

[0204] the smallest integer greater than N / 2, or

[0205] The largest integer not exceeding N / 2.

[0206] Example 18. The network device of any one of Examples 12 to 17, wherein the network device is further caused to:

[0207] A radio resource control (RRC) message is sent to the terminal device, the RRC message comprising: a bitmap indicating a set of configured HARQ states corresponding to a set of HARQ processes.

[0208] Example 19. A network device according to any one of Examples 12 to 18, wherein the same HARQ state for all HARQ processes in the multiple HARQ processes is determined by the terminal device as the configured HARQ state for the specific HARQ process.

[0209] Example 20. A network device according to any one of Examples 12 to 19, wherein the configured HARQ state is HARQ feedback disablement or HARQ feedback enablement in downlink.

[0210] Example 21. A network device according to any one of Examples 12 to 19, wherein the configured HARQ state is HARQ mode A or HARQ mode B in uplink.

[0211] Example 22. The network device of any one of Examples 12 to 21, wherein the information includes downlink control information (DCI) scheduling multiple TBs for one of:

[0212] Narrowband Internet of Things (NB-IoT) over non-terrestrial networks (NTN),

[0213] Enhanced Machine Type Communication eMTC Coverage Enhancement CE Mode A over NTN,

[0214] eMTC CE Mode B on NTN, or

[0215] New Radio NR on NTN.

[0216] Example 23. A method comprising:

[0217] At the terminal device, receiving information scheduling a plurality of transport blocks TB and indicating a plurality of hybrid automatic repeat request (HARQ) processes from a network device;

[0218] determining a configured HARQ state of a particular HARQ process among the plurality of HARQ processes; and

[0219] It is determined that all HARQ processes of the plurality of HARQ processes have a same HARQ state, where the same HARQ state is the configured HARQ state of the specific HARQ process.

[0220] Example 24. A method comprising:

[0221] At a network device, determining a plurality of Hybrid Automatic Repeat Request (HARQ) processes including a particular HARQ process having a configured HARQ state; and

[0222] Information scheduling multiple transport blocks TB and indicating the multiple HARQ processes is sent to the terminal device.

[0223] Example 25. An apparatus comprising:

[0224] A means for receiving, at a terminal device, information from a network device scheduling a plurality of transport blocks TB and indicating a plurality of hybrid automatic repeat request (HARQ) processes;

[0225] means for determining a configured HARQ state of a particular HARQ process of the plurality of HARQ processes; and

[0226] Means for determining that all of the plurality of HARQ processes have a same HARQ state, the same HARQ state being the configured HARQ state of the particular HARQ process.

[0227] Example 26. An apparatus comprising:

[0228] means for determining, at a network device, a plurality of Hybrid Automatic Repeat Request (HARQ) processes including a particular Hybrid Automatic Repeat Request (HARQ) process having a configured HARQ state; and

[0229] A component used to send information scheduling multiple transport blocks TB and indicating the multiple HARQ processes to a terminal device.

[0230] Example 27. A computer-readable medium comprising program instructions for causing an apparatus to at least perform the method according to any one of Examples 23 to 24.

Claims

1. A terminal device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least: Receiving information for scheduling a plurality of transport blocks TB and indicating a corresponding plurality of hybrid automatic repeat request HARQ processes from a network device; determining a configured HARQ state of a specific HARQ process among the plurality of HARQ processes; as well as It is determined that all of the multiple HARQ processes have a same HARQ state, where the same HARQ state is the configured HARQ state of the specific HARQ process.

2. The terminal device according to claim 1, wherein the terminal device is further configured to: A configuration indicating a specific location of the specific HARQ process is received from the network device.

3. The terminal device according to claim 1 or 2, wherein the specific HARQ process is one of the following: the first HARQ process, the last HARQ process, the mth HARQ process, or the middle HARQ process among the multiple HARQ processes.

4. The terminal device according to claim 3, wherein the ordering of the middle HARQ process in the multiple HARQ processes is associated with N / 2, where N represents the number of the multiple HARQ processes.

5. The terminal device according to claim 4, wherein the order of the middle HARQ process in the plurality of HARQ processes is equal to one of the following: the smallest integer greater than N / 2, or The largest integer not exceeding N / 2.

6. The terminal device according to any one of claims 1 to 5, wherein the terminal device is further configured to: A radio resource control (RRC) message is received from the network device, wherein the RRC message includes: A bitmap indicating a set of configured HARQ states corresponding to a set of HARQ processes.

7. The terminal device according to any one of claims 1 to 6, wherein the plurality of HARQ processes comprises: Another HARQ process different from the specific HARQ process, and wherein the same HARQ state for all HARQ processes of the plurality of HARQ processes is determined regardless of another configured HARQ state of the another HARQ process.

8. A terminal device according to any one of claims 1 to 7, wherein the configured HARQ state is HARQ feedback disable or HARQ feedback enable in the downlink, or the configured HARQ state is HARQ feedback mode A or HARQ mode B in the uplink.

9. The terminal device according to any one of claims 1 to 8, wherein the information comprises downlink control information DCI for scheduling multiple TBs for one of the following: Narrowband Internet of Things (NB-IoT) over non-terrestrial networks (NTN), Enhanced Machine Type Communication eMTC Coverage Enhancement CE Mode A over NTN, eMTC CE Mode B on NTN, or New Radio NR on NTN.

10. A network device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: determining a plurality of HARQ processes including a specific hybrid automatic repeat request HARQ process, the specific HARQ process having a configured HARQ state; as well as Information for scheduling multiple transport blocks TB and indicating the multiple HARQ processes is sent to the terminal device.

Images