CN118160254A

CN118160254A - NTN IOT HARQ disablement

Info

Publication number: CN118160254A
Application number: CN202180103679.5A
Authority: CN
Inventors: 颜智; 刘红梅; 张元涛; 李营营; 汪海明
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2021-12-23
Filing date: 2021-12-23
Publication date: 2024-06-07
Also published as: WO2023115447A1

Abstract

Methods and apparatus for NTN IoT HARQ disabling are disclosed. A UE comprising: a processor; and a receiver coupled to the processor, wherein the processor is configured to: receiving, via a receiver, a control signal for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and receiving the scheduled transport block via the receiver based on the control signal.

Description

NTN IOT HARQ disablement

Technical Field

The subject matter disclosed herein relates generally to wireless communications, and more particularly to methods and apparatus for NTN (non-terrestrial network) IoT (internet of things) HARQ (hybrid automatic repeat request) disabling.

Background

The following abbreviations are defined herein, at least some of which are mentioned in the following description: new Radio (NR), long Term Evolution (LTE), very Large Scale Integration (VLSI), random Access Memory (RAM), read Only Memory (ROM), erasable programmable read only memory (EPROM or flash memory), compact disc read only memory (CD-ROM), local Area Network (LAN), wide Area Network (WAN), user Equipment (UE), evolved node B (eNB), next generation node B (gNB), uplink (UL), downlink (DL), central Processing Unit (CPU), graphics Processing Unit (GPU), field Programmable Gate Array (FPGA), orthogonal Frequency Division Multiplexing (OFDM), radio Resource Control (RRC), user entity/device (mobile terminal), transmitter (TX), receiver (RX), non-terrestrial network (NTN), internet of things (IoT), narrowband internet of things (NBIoT or NB-IoT), physical Downlink Shared Channel (PDSCH), NBIoT Physical Downlink Shared Channel (NPDSCH), physical uplink shared channel (NBIoT), physical Downlink Control Channel (PDCCH), NBIoT physical automatic transmission channel (PDCCH), automatic transmission block (NPDCCH), retransmission request (HARQ), retransmission request (mtc), machine type (mtc), automatic transmission request (ARQ) Radio Link Control (RLC), downlink Control Information (DCI), frequency Division Duplex (FDD), acknowledgement (ACK), cyclic Redundancy Check (CRC), radio Network Temporary Identity (RNTI), cell RNTI (C-RNTI), group RNIT (G-RNTI), paging RNIT (P-RNTI).

A brief description of MPDSCH transmissions is described below with reference to fig. 1. The control signal (e.g., DCI) is transmitted in the MPDCCH at, for example, subframe #0, which schedules multiple TBs (e.g., 8 TBs) transmitted in the PDSCH, with each TB (D0 to D7) being transmitted in a separate subframe (i.e., from subframe #2 to subframe #9, assuming a scheduling delay, which means a delay of reception of the first TB (e.g., D0) from the DCI (e.g., M0), which is 2 subframes). Each scheduled TB is associated with a separate HARQ process number (e.g., from HARQ process #0 to HARQ process # 7) in increasing order of the corresponding HARQ process number. That is, D0 is associated with HARQ process # 0; d1 is associated with HARQ process #1, … …. For each TB (each of D0 to D7), HARQ feedback (each of U0 to U7) is transmitted in the PUCCH to indicate whether PDSCH transmissions in that TB were successfully received by the UE. As shown in fig. 1, each of U0 to U7 indicates whether each of D0 to D7 is successfully received by the UE. U0 is associated with D0 because they are associated with the same HARQ process number (e.g., HARQ process # 0).

The subframe at which the HARQ feedback is transmitted is determined as: for PUCCH for corresponding TB _b starting in subframe s _b, s ₀＝n₀+4,s_b＝max{n_b+4,s_b-1+N_b-1},b≠0,n_b is the last subframe in which PDSCH containing TBb is transmitted, N _b denotes the number of consecutive subframes containing non-BL/CE subframes in which PUCCH with HARQ-ACK for TBb is transmitted. As shown in fig. 1, HARQ feedback (U0 to U7) for 8 PDSCH transmissions (D0 to D7) are transmitted in subframes #6 to #13, respectively, where s _b＝n_b +4, b=0 to 7.

Different numbers of HARQ processes are supported in eMTC and NBIoT. For eMTC CE mode a, 8 HARQ processes are supported. Thus, there are 8 HARQ process numbers (i.e., HARQ processes #0 to # 7) in eMTC CE mode a. For eMTC CE mode B, 2 HARQ processes are supported; or if multi-TB scheduling is configured, 4 HARQ processes are supported. For NBIoT, 2 HARQ processes (if configured) are supported.

Disabling of HARQ feedback has been supported in NR NTN. In particular, the enabling and disabling of HARQ feedback for downlink transmissions (e.g., PDSCH transmissions) may be configurable for each HARQ process at least via UE-specific RRC signaling. For example, the UE may be configured by RRC parameters to enable or disable HARQ feedback for each HARQ process (i.e., each HARQ process number) via a bitmap manner. As shown in fig. 2, assuming that there are 8 HARQ processes (with HARQ process numbers #0 to # 7), a bitmap with 8 bits may indicate HARQ feedback disabling or enabling for the 8 HARQ processes. For example, 0 indicates HARQ feedback disabled and 1 indicates HARQ feedback enabled.

When HARQ feedback disable is configured for a HARQ process number, no explicit UL feedback for DL transmissions acknowledges successful transmission of the TB associated with the HARQ process with that HARQ process number. This means that the HARQ process number can be reused for a new DL transmission without waiting for HARQ feedback. This may avoid HARQ stall (stabilizing) and thus avoid throughput degradation. Correspondingly, retransmissions at the RLC layer (i.e., RLC ARQ) may be required to meet reliability requirements. In general, ARQ retransmissions in the RLC layer may have high latency, which may be acceptable for IoT services (e.g., eMTC and NBIoT) because IoT services are typically delay tolerant.

If a HARQ feedback disabling mechanism in NR NTN is introduced in IoT NTN (e.g., a UE may be configured to enable or disable HARQ feedback for each HARQ process via a bitmap manner through RRC parameters, and when multiple TBs are scheduled, the scheduled TBs are sent in ascending order of corresponding HARQ process numbers), the TBs associated with HARQ feedback enabled HARQ process numbers and the TBs associated with HARQ process numbers for which HARQ feedback is disabled may be sent in an interleaved manner.

For example, as shown in fig. 3, HARQ processes #1, #3, #5, and #7 are configured for HARQ feedback disabling. Thus, HARQ feedback U1, U3, U5, and U7 associated with HARQ processes #1, #3, #5, and #7 (i.e., HARQ feedback for D1, D3, D5, and D7) is not transmitted. On the other hand, HARQ processes #0, #2, #4, and #6 are configured as HARQ feedback enablement. Thus, HARQ feedback U0, U2, U4, and U6 associated with HARQ processes #0, #2, #4, and #6 (i.e., HARQ feedback for D0, D2, D4, and D6) is transmitted. Although U1, U3, and U5 are not transmitted, the base station tends not to use these UL resources because they are located among other used resources (e.g., U0, U2, U4, and U6). In other words, PUCCH resources in U1, U3, and U5 are likely to be wasted due to PUCCH discontinuous transmission. In addition, the last HARQ feedback is in subframe #12 (for transmission of U6). In comparison to fig. 1, in which no HARQ feedback is configured, although four HARQ processes are configured with HARQ feedback disabled, HARQ ACK feedback delay is improved by only one subframe (from subframe #13 to subframe # 12).

In general, it is not advantageous to simply apply NR NTN HARQ feedback disable mechanisms to IoT NTNs.

HARQ feedback disable also affects NPDCCH search space constraints. For maximum HARQ process number=2, NPDCCH search space constraints are described below with reference to fig. 4. If the NB-IoT UE detects NPDCCH with DCI format N1 or N2 ending in subframe #n and if NPDSCH transmission starts from subframe #n+k, then the UE is not required to listen for NPDCCH candidates in any subframes starting from subframe #n+k-2 to subframe #n+k-1 (UE is required to listen for NPDCCH candidates in subframes from subframe #n+1 to subframe #n+k-3); and if NB-IoT UE detects NPDCCH with DCI format N1 ending in subframe #n and if corresponding NPDSCH transmission starts from subframe #n+k and for FDD, if corresponding NPUSCH format 2 transmission starts from subframe #n+m, then UE is not required to listen NPDCCH in any subframe starting from subframe #n+k to subframe #n+m-1.

As shown in fig. 4, the HARQ delay (from the end of NPDSCH reception to the start of NPUSCH transmission) is greater than 12ms. HARQ delays are used for NPDSCH decoding, protocol procedures, DL/UL switching, UL data preparation, and UL scheduling flexibility.

Fig. 5 illustrates NPDCCH search space constraints where HARQ feedback (e.g., for paging and multicast scenarios) is not present.

If NBIoT UE receives the NPDSCH transmission ending in subframe #n and if the UE is not required to transmit the corresponding NPUSCH format 2, it is not required that the UE listens NPDCCH in any subframes starting from subframe #n+1 to subframe #n+12.

However, is the NPDCCH search space constraint described above for the case where there is no HARQ feedback applicable to the case where HARQ feedback is disabled in unicast transmission?

The present invention relates to enhancing HARQ feedback disabling configurations for NTN IoT.

Disclosure of Invention

Methods and apparatus for NTN IoT HARQ disabling are disclosed.

In one embodiment, a UE includes: a processor; and a receiver coupled to the processor, wherein the processor is configured to receive, via the receiver, control signals for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and receiving the scheduled transport block via the receiver based on the control signal.

In some embodiments, the processor is further configured to determine HARQ feedback for each of the scheduled transport blocks based on the associated HARQ process number and HARQ configuration.

In one embodiment, the HARQ configuration indicates HARQ processes enabled or disabled for HARQ feedback via a bitmap manner.

In another embodiment, the HARQ configuration indicates the number of HARQ processes for which HARQ feedback is enabled or the number of HARQ processes for which HARQ feedback is disabled. Accordingly, the processor is further configured to determine the HARQ feedback enabled HARQ process and the HARQ feedback disabled HARQ process based on the number of HARQ feedback enabled HARQ processes or the number of HARQ feedback disabled HARQ processes.

In yet another embodiment, the processor is configured to receive, via the receiver, the scheduled transport blocks in a transmission order determined by the HARQ process number and corresponding HARQ feedback enablement or disablement.

In another embodiment, the association of the scheduled TB and HARQ process number is determined by the HARQ process number indicated in the control signal and the corresponding HARQ process that is enabled or disabled by HARQ feedback.

In some embodiments, the processor is further configured to terminate listening to the search space for another control signal in a period after receiving the scheduled transport block, the period being determined by at least one of: HARQ processes enabled or disabled for HARQ feedback corresponding to the scheduled transport block, an RNTI type associated with control signal CRC scrambling, and a search space type associated with control signal.

In one embodiment, a method at a UE includes: receiving a control signal for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and receiving the scheduled transport block based on the control signal.

In another embodiment, a base station unit includes: a processor; and a transmitter coupled to the processor, wherein the processor is configured to: transmitting, via the transmitter, control signals for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and transmitting the scheduled transport block via the transmitter based on the control signal.

In yet another embodiment, a method at a base station unit includes: transmitting control signals for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and transmitting the scheduled transport block based on the control signal.

Drawings

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered limiting of scope, embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

Fig. 1 illustrates PDSCH transmissions with scheduled multiple TBs;

FIG. 2 illustrates NR NTN HARQ feedback disable indications;

fig. 3 illustrates a HARQ feedback disabling mechanism introduced into the NR NTN of the IoT NTN;

FIG. 4 illustrates NPDCCH search space constraints;

fig. 5 illustrates NPDCCH search space constraints where HARQ feedback is not present (e.g., for paging and multicast scenarios);

Fig. 6 illustrates an example of configuring all HARQ feedback disabled HARQ processes to the last scheduled TB;

fig. 7 illustrates an example of the first embodiment;

Fig. 8 illustrates an example of a fourth embodiment;

FIG. 9 is a schematic flow chart diagram illustrating one embodiment of a method;

FIG. 10 is a schematic flow chart diagram illustrating another embodiment of a method; and

FIG. 11 is a schematic block diagram illustrating an apparatus according to one embodiment.

Detailed Description

As will be appreciated by one of skill in the art, certain aspects of the embodiments may be embodied as a system, apparatus, method or program product. Thus, an embodiment may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," module "or" system. Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and/or program code, hereinafter referred to as "code. The storage devices may be tangible, non-transitory, and/or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device only employs signals for the access code.

Some of the functional units described in this specification may be labeled as "modules" in order to more particularly emphasize their individual embodiments. For example, a module may be implemented as a hardware circuit comprising custom Very Large Scale Integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, comprise one or more physical or logical blocks of executable code, which may, for instance, be organized as an object, procedure, or function. However, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organization within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer-readable storage devices. Where a module or portion of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores code. The storage device may be, for example, but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

A non-exhaustive list of more specific examples of storage devices would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for performing operations of embodiments may include any number of rows and may be written in any combination including one or more of an object oriented programming language such as Python, ruby, java, smalltalk, C ++ or the like and a conventional procedural programming language such as the "C" programming language and/or machine language such as assembly language. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the final scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases "in one embodiment," in an embodiment, "and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean" one or more but not all embodiments. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a," "an," and "the" also mean "one or more" unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics of the various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid any obscuring aspects of the embodiments.

Aspects of the different embodiments are described below with reference to schematic flow chart diagrams and/or schematic block diagrams of methods, apparatuses, systems and program products according to the embodiments. It will be understood that each block of the schematic flow diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flow diagrams and/or schematic block diagrams, can be implemented by codes. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart and/or schematic block diagram block or blocks.

The code may further be stored in a memory device that is capable of directing a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the memory device produce an article of manufacture including instructions which implement the function specified in the schematic flow chart diagrams and/or schematic block diagram block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.

The schematic flow chart diagrams and/or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).

It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figure.

Although various arrow types and line types may be employed in the flow chart diagrams and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or listening period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements of previous figures. Like numbers refer to like elements throughout, including alternative embodiments of like elements.

In the description of the background section, fig. 3 illustrates that if the HARQ feedback disabling mechanism in the NR NTN is simply introduced in the IoT NTN, the TBs associated with HARQ feedback enabled HARQ process numbers and the TBs associated with HARQ feedback disabled HARQ process numbers may be transmitted in an interleaved manner, which is undesirable.

On the other hand, when a plurality of TBs are scheduled and the scheduled TBs are transmitted in an ascending order of corresponding HARQ process numbers, if all HARQ processes with HARQ feedback disabled are configured to the last scheduled TB, resources wasted due to discontinuous transmission can be saved. In addition, HARQ ACK feedback delay can be minimized.

An example of the corresponding HARQ process number increasing order is described as follows. Assume that a maximum of 8 HARQ processes (e.g., HARQ process numbers 0 through 7) are supported. Four TBs (e.g., TB1, TB2, TB3, and TB 4) are scheduled by DCI. HARQ process numbers 2, 3, 5 and 7 are assigned by the binomial coefficient values indicated in the DCI. Thus, TB1 is associated with HARQ process # 2; TB2 is associated with HARQ process # 3; TB3 is associated with HARQ process # 5; and TB4 is associated with HARQ process # 7. Thus, the four TBs are transmitted in the order of increasing corresponding HARQ process numbers (i.e., the order of 2, 3, 5, 7), i.e., in the order of TB1, TB2, TB3, and TB 4.

Fig. 6 illustrates an example of configuring all HARQ feedback disabled HARQ processes to the last scheduled TB. As shown in fig. 6, a control signal (e.g., DCI) is sent in MPDCCH at subframe #0, which schedules 8 TBs sent in PDSCH, where each scheduled TB is associated with a separate HARQ process number (e.g., from HARQ process #0 to HARQ process # 7) in increasing order of the corresponding HARQ process number. HARQ processes #0, #1, #2, and #3 are configured for HARQ feedback enablement, while HARQ processes #4, #5, #6, and #7 are configured for HARQ feedback disablement (i.e., associated with the last scheduled TBs (D4, D5, D6, and D7)). Thus, U0, U1, U2, and U3 for HARQ processes #0, #1, #2, and #3 (i.e., HARQ feedback for D0, D1, D2, and D3) are transmitted without repetition (e.g., repetition number of 1), while U4, U5, U6, and U7 for HARQ processes #4, #5, #6, and #7 (i.e., HARQ feedback for D4, D5, D6, and D7) are not transmitted. As compared with the example shown in fig. 3, it can be seen that in the example of fig. 6, the unused UL resources U4, U5, U6 and U7 that are not interleaved can be used by the base station without waste. Since all HARQ feedback (e.g., U0, U1, U2, and U3) is transmitted without an interval, so that the last HARQ ACK feedback is in subframe #9 (for transmission of U3), the HARQ ACK feedback delay can be improved to the maximum extent.

In general, it is advantageous to configure HARQ processes with HARQ feedback disabled in the last scheduled TB.

According to a first embodiment, the UE is configured by RRC parameters (e.g., "HARQ-enabling-disabling") to enable or disable HARQ feedback for each HARQ process via a bitmap manner, e.g., in the manner described with reference to fig. 2. Depending on the base station configuring the HARQ process with HARQ feedback disabled in the last scheduled TB (i.e. in the last HARQ process number).

Fig. 7 illustrates an example of the first embodiment. A control signal (e.g., DCI) is sent in MPDCCH at subframe #0, which schedules 8 TBs sent in PDSCH, where each scheduled TB is sequentially associated with a separate HARQ process number (e.g., from HARQ process #0 to HARQ process # 7). According to the first embodiment, the base station can only configure the HARQ process or processes at the end to be HARQ feedback disabled. In the example of fig. 7, only the last three HARQ processes (with HARQ process numbers 5, 6 and 7) are configured for HARQ feedback disabling.

The first embodiment has the disadvantage of limiting the scheduling. That is, the base station cannot arbitrarily configure the HARQ process to disable HARQ feedback. According to the first embodiment, only the last one or more HARQ processes can be configured as HARQ feedback disabled.

According to a second embodiment, the UE is configured to indicate the number of HARQ processes for which HARQ feedback is enabled or the number of HARQ processes for which HARQ feedback is disabled by means of RRC parameters. The HARQ feedback enabled HARQ process and the HARQ feedback disabled HARQ process can be derived from the number of HARQ feedback enabled HARQ processes or the number of HARQ feedback disabled HARQ processes.

If the number of HARQ feedback enabled HARQ processes is configured, the HARQ feedback enabled HARQ process has the number of HARQ feedback enabled HARQ processes and starts with the HARQ process having the lowest number (e.g., HARQ process # 0); and the HARQ feedback disabled HARQ process has the total number of HARQ processes minus the number of HARQ feedback enabled HARQ processes and starts with the next number of HARQ process numbers of the last HARQ process for which HARQ feedback is enabled.

For example, the UE can be configured with the number of HARQ feedback enabled HARQ processes, e.g., N0. Assuming that the total number of HARQ processes is N (e.g., HARQ process numbers may be 0, 1, …, N-1), the HARQ feedback enabled HARQ processes are { HARQ process #0, HARQ process #1, …, HARQ process # n0-1}, and the HARQ feedback disabled HARQ processes are { HARQ process # N0, HARQ process # n0+1, …, HARQ process #n-1}. Specifically, if n=8 and n0=3, the HARQ feedback enabled HARQ process is { HARQ process #0, HARQ process #1, HARQ process #2}, and the HARQ feedback disabled HARQ process is { HARQ process #3, HARQ process #4, HARQ process #5, HARQ process #6, HARQ process #7}.

If the number of HARQ processes for which HARQ feedback is disabled is configured, the HARQ feedback enabled HARQ process has the total number of HARQ processes minus the number of HARQ processes for which HARQ feedback is disabled and starts with the HARQ process having the lowest number (e.g., HARQ process # 0); and the HARQ feedback disabled HARQ process has the number of HARQ feedback disabled HARQ processes and starts with the next number of HARQ process numbers of the last HARQ process for which HARQ feedback is enabled.

For another example, the UE is configured with the number of HARQ processes for which HARQ feedback is disabled, e.g., N1. Assuming that the total number of HARQ processes is N (e.g., HARQ process numbers may be 0, 1, …, N-1), HARQ feedback enabled HARQ processes are { HARQ process #0, HARQ process #1, …, HARQ process #n-N1-1}, and HARQ feedback disabled HARQ processes are { HARQ process #n-N1, HARQ process #n-1+1, …, HARQ process #n-1}. Specifically, if n=8 and n1=3, the HARQ feedback enabled HARQ process is { HARQ process #0, HARQ process #1, HARQ process #2, HARQ process #3, HARQ process #4}, and the HARQ feedback disabled HARQ process is { HARQ process #5, HARQ process #6, HARQ process #7}.

According to a third embodiment, the UE is configured to enable or disable HARQ feedback per HARQ process (i.e. per HARQ process number) via bitmap means by means of RRC parameters. In addition, the scheduled TBs are transmitted in a reordered sequence (i.e., an order different from the conventional order) based on the corresponding HARQ process that the HARQ feedback is enabled or disabled and the HARQ process number, and in particular, based on the corresponding HARQ process before the HARQ feedback is enabled that the HARQ process number is incremented. Note that the corresponding HARQ process means a HARQ process corresponding to a TB.

For example, assume that HARQ processes with HARQ feedback enabled or disabled are configured { disable, enable, disable, enable }, for a total of 4 HARQ process numbers (e.g., 0 to 3). Namely, { HARQ feedback disabled HARQ process #0, HARQ feedback enabled HARQ process #1, HARQ feedback disabled HARQ process #2, HARQ feedback enabled HARQ process #3}. The base station schedules 3 TBs (e.g., TB0, TB1, and TB 3) using HARQ processes #0, #1, and #3 (note that HARQ process #2 is not used). The scheduled TBs are associated with HARQ process numbers in ascending order: TB0, TB1, and TB3 are associated with HARQ process #0, HARQ process #1, and HARQ process #3, respectively.

Traditionally, scheduled TBs are sent sequentially. That is, BL/CE DL subframe N _r·N+l with l=0, 1, kn-1 is associated with TB _r+1, r=0, 1, kn _TB -1, where N is the number of repetitions per TB and N _TB is the number of scheduled TBs. BL/CE DL subframe n _r·N+l is a downlink subframe with subframe index r.N +1 available for eMTC. For example, the 3 TBs scheduled are sequentially transmitted in the ascending order of HARQ process numbers, i.e., { TB0, TB1, and TB3}, which is the ascending order of HARQ process numbers: HARQ process #0, HARQ process #1, and HARQ process #3.

According to a third embodiment, the 3 TBs (TB 0, TB1 and TB 3) scheduled are transmitted in a reordered sequence, wherein the reordered sequence is based on the corresponding HARQ process (e.g., { disabled, enabled, disabled, enabled }) and HARQ process number (e.g., 0,1 and 3) that were enabled or disabled based on the HARQ feedback, e.g., based on the corresponding HARQ process before disabled, i.e., { TB1, TB3, TB0} that was incremented based on the HARQ process number. That is, the corresponding HARQ processes for which HARQ feedback is enabled (in this example: TB1 and TB3 in ascending order of HARQ process number) are transmitted before the corresponding HARQ processes for which HARQ feedback is disabled (in this example, TB0; note that HARQ process #2 is not used in this example).

That is, TBl and TB3 belonging to the HARQ feedback enabled HARQ process are transmitted before TB0 belonging to the HARQ feedback disabled HARQ process; and within TB1 and TB3, TB1 is transmitted before TB3 based on the HARQ process number ascending order.

According to a third embodiment, scheduled TBs are transmitted in a reordered sequence. That is, BL/CE DL subframe N _r·N+l with l=0, 1, kn-1 is associated with TB _f(r)+1, f (r) is a function of the reordering index of sequential TBs _r with HARQ processes corresponding to feedback enabled and disabled TBs sequentially increasing in HARQ process number, where N is the number of repetitions per TB and N _TB is the number of scheduled TBs.

According to a third embodiment, TBs corresponding to HARQ processes for which HARQ feedback is disabled are explicitly sent in the last scheduled TB.

According to a fourth embodiment, the UE is configured to enable or disable HARQ feedback per HARQ process (i.e. per HARQ process number) via bitmap means by means of RRC parameters. In addition, the association of the scheduled TBs with the HARQ process numbers is reordered. The association between TBs and HARQ process numbers can be determined based on the DCI indication and the corresponding HARQ process that HARQ feedback is enabled or disabled, and in particular, the incrementally numbered TBs scheduled in DCI are associated with HARQ process numbers that were incremented by HARQ process numbers before the HARQ feedback is enabled.

For example, assume that HARQ processes with HARQ feedback enabled or disabled are configured { disable, enable, disable, enable }, for a total of 4 HARQ process numbers (e.g., 0 to 3). The base station uses DCI to schedule 3 TBs (e.g., TB0, TB1, and TB 3) with HARQ processes #0, #1, and # 3. The 3 TBs (TB 0, TB1, and TB 3) scheduled are sequentially transmitted in the order { TB0, TB1, and TB3} (which is the same as the prior art).

Conventionally, for BL/CE UEs, if the UE is configured with multiple TB transmissions, the HARQ process ID h _i for each of the scheduled TBTB _i+1 is determined from the combined index (e.g., binomial coefficient value) indicated in the DCI. For example, 3 scheduled TBs are sequentially associated with three HARQ processes (e.g., HARQ processes #0, #1, and #3 determined from the combining index), i.e., { TB0 and HARQ process #0, TB1 and HARQ process #1, and TB3 and HARQ process #3}.

On the other hand, according to the fourth embodiment, the association between the scheduled TBs (TB 0, TB1, and TB 3) and HARQ processes #0, #1, and #3 is determined based on the DCI indication (i.e., TB0, TB1, and TB3 are scheduled) and the corresponding HARQ process (i.e., { disabled, enabled, disabled, enabled }) for which HARQ feedback is enabled or disabled. Specifically, the TBs numbered incrementally in DCI schedule (i.e., TB0, TB1, and TB 3) are associated with HARQ feedback enabled HARQ process numbers (HARQ process #1 and HARQ process #3 in increasing order of HARQ process numbers) before being associated with HARQ feedback enabled HARQ process numbers (HARQ process #0; note that HARQ process #2 is not used in this example). That is, the association between the TB and the HARQ process number according to the second sub-embodiment of the third embodiment is { TB0 and HARQ process #1, TB1 and HARQ process #3, and TB3 and HARQ process #0}.

According to the fourth embodiment, the association of scheduled TBs with HARQ process numbers is reordered. That is, for BL/CE UEs, if the UE is configured with multiple TB transmissions, then for scheduledHARQ process ID/>Is the reordering/>, of HARQ processes with HARQ feedback enabled and disabled and HARQ process numbers incrementedWhere h' _i(i＝0,1,...,N_TB -1) is determined from the combined index (e.g., binomial coefficient value) indicated in the DCI.

According to the fourth embodiment, TBs corresponding to HARQ processes for which HARQ feedback is disabled are also explicitly transmitted in the last scheduled TB.

The fifth embodiment relates to NPDCCH search space constraints in IoT NTN with HARQ feedback disabled.

If legacy NPDCCH search space constraints for paging and multicasting without HARQ feedback therein are used in HARQ feedback disabled IoT NTN (as shown in fig. 5), the HARQ delay (from the end of reception of TB1 to listening of the next DCI 1) is at least 12ms. The HARQ delay is for NPDSCH decoding, protocol procedures, new listening carrier switching, etc. This means that if NBIoT UE receives the NPDSCH transmission ending in subframe #n and if the UE is not required to send the corresponding NPUSCH format 2, it is not required that the UE listens NPDCCH in any subframe starting from subframe #n+1 to subframe #n+12.

However, if the peak data rate is the goal to improve, then the NPDCCH listening termination of 12ms is too long for the unicast case. NPDSCH the decoding time is less than 8ms (e.g., 4 ms). Furthermore, in unicast, the same UE-specific search space is listened to, which saves time. Specifically, in unicast transmission, if a corresponding HARQ process disabled for HARQ feedback detects DCI (e.g., DCI 1) (when the supported HARQ process number is 2), the UE shall continue to listen to the UE-specific search space for another new DCI (e.g., DCI 2). Further, if the HARQ process number is 2, demodulation of NPDCCH and decoding of NPDSCH can be performed simultaneously. In general, when configuring HARQ feedback in unicast, it is not advantageous to follow the legacy NPDCCH search space constraints for paging and multicasting.

According to a fourth embodiment, the UE terminates listening NPDCCH in a period determined by a corresponding NPDSCH HARQ process enabled or disabled by HARQ feedback, or by a search space type (e.g., common search space or UE-specific search space), or by a corresponding DCI with CRC-scrambled RNTI (e.g., by C-RNTI or G-RNTI or P-RNTI).

Fig. 8 illustrates an example of the fourth embodiment.

For example, if NBIoT UE receives a NPDSCH transmission ending in subframe #n (e.g., TB 1) and if the UE is not required to transmit the corresponding NPUSCH format 2, then if the HARQ process corresponding to TB1 is configured by the RRC parameter "HARQ-enabling-disable" as "HARQ feedback disabled", then the UE is not required to listen NPDCCH in any subframes starting from subframe #n+1 to subframe #n+4 or #n+8; otherwise (if it is paging and multicast), the UE is not required to listen NPDCCH in any subframe starting from subframe #n+1 to subframe #n+12.

For another example, if NBIoT UE receives NPDSCH transmission (e.g., TB 1) ending in subframe #n (scheduled by DCI sent in NPDCCH), then the UE is not required to send the corresponding NPUSCH format 2 and NPDCCH is associated with CRC scrambled by C-RNTI or G-RNTI, and is not required to listen NPDCCH in any subframes starting from subframe #n+1 to subframe #n+4 or #n+8; otherwise (if it is paging and multicast (e.g., NPDCCH is associated with CRC scrambled by P-RNTI)), the UE is not required to listen NPDCCH in any subframes starting from subframe #n+1 to subframe #n+12.

For yet another example, if NBIoT UE receives NPDSCH transmission (e.g., TB 1) ending in subframe #n (scheduled by DCI sent in NPDCCH) and if the UE is not required to send the corresponding NPUSCH format 2, then if NPDCCH the associated DCI is in the UE-specific search space, the UE is not required to listen NPDCCH in any subframes starting from subframe #n+1 to subframe #n+4 or #n+8; otherwise (if it is paging and multicast (e.g., NPDCCH associated DCI in common search space)), the UE is not required to listen NPDCCH in any subframes starting from subframe #n+1 to subframe #n+12.

If the UE receives NPDSCH ending in subframe #n for the HARQ process for which HARQ feedback is disabled, it is not expected that the UE receives NPDCCH with DCI format N1 for the same HARQ process ID in any subframe starting from subframe #n+1 to subframe #n+12.

In the example of fig. 8, NBIoT UE receives NPDSCH transmission TB1 (scheduled by DCI 1) associated with the HARQ process number for which HARQ feedback is disabled. The UE will not listen for control signals within 4ms from the end of the TB1 transmission in NPDSCH. That is, the UE (re) starts listening for the control signal 4ms after the end of the TB1 transmission in NPDSCH. In addition, the UE also receives NPDSCH transport TB2 (scheduled by DCI 2) associated with the HARQ feedback enabled HARQ process number. From the end of the TB2 transmission in NPDSCH to the beginning of the NPUSCH format 2 transmission, i.e. at least 12ms, the ue will not listen for control signals.

Fig. 9 is a schematic flow chart diagram illustrating one embodiment of a method 900 in accordance with the present application. In some embodiments, method 900 is performed by an apparatus, such as a remote Unit (UE). In some embodiments, method 900 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

The method 900 may include: 902 receiving a control signal for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and 904 receiving the scheduled transport block based on the control signal.

In some embodiments, the method further comprises determining HARQ feedback for each of the scheduled transport blocks based on the associated HARQ process number and HARQ configuration.

In another embodiment, the HARQ configuration indicates the number of HARQ processes for which HARQ feedback is enabled or the number of HARQ processes for which HARQ feedback is disabled. Accordingly, the method may further include determining a HARQ feedback enabled HARQ process and a HARQ feedback disabled HARQ process according to the number of HARQ feedback enabled HARQ processes or the number of HARQ feedback disabled HARQ processes.

In yet another embodiment, the scheduled transport blocks are received in a transmission order determined by the HARQ process number and corresponding HARQ feedback enablement or disablement.

In some embodiments, the method may further comprise terminating listening to a search space for another control signal in a period after receiving the scheduled transport block, the period being determined by at least one of: HARQ processes enabled or disabled for HARQ feedback corresponding to the scheduled transport block, an RNTI type associated with control signal CRC scrambling, and a search space type associated with control signal.

Fig. 10 is a schematic flow chart diagram illustrating another embodiment of a method 1000 in accordance with the present application. In some embodiments, method 1000 is performed by an apparatus, such as a base station unit. In some embodiments, method 1000 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

The method 1000 may include: 1002 send a control signal for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and 1004 transmitting the scheduled transport block based on the control signal.

In yet another embodiment, the scheduled transport blocks are transmitted in a transmission order determined by the HARQ process number and corresponding HARQ feedback enablement or disablement.

Referring to fig. 11, a ue (i.e., a remote unit) includes a processor, a memory, and a transceiver. The processor implements the functions, processes and/or methods set forth in fig. 9.

The UE comprises: a processor; and a receiver coupled to the processor, wherein the processor is configured to: receiving, via a receiver, a control signal for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and receiving the scheduled transport block via the receiver based on the control signal.

Referring to fig. 11, a gnb (i.e., base station unit) includes a processor, a memory, and a transceiver. The processor implements the functions, processes and/or methods set forth in fig. 10.

The base station unit includes: a processor; and a transmitter coupled to the processor, wherein the processor is configured to: transmitting, via the transmitter, control signals for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and transmitting the scheduled transport block via the transmitter based on the control signal.

In yet another embodiment, the processor is configured to transmit, via the transmitter, the scheduled transport blocks in a transmission order determined by the HARQ process number and corresponding HARQ feedback enablement or disablement.

The layers of the radio interface protocol may be implemented by a processor. The memory is connected to the processor to store various information for driving the processor. The transceiver is coupled to the processor to transmit and/or receive radio signals. It goes without saying that the transceiver may be implemented as a transmitter for transmitting radio signals and as a receiver for receiving radio signals.

The memory may be located inside or outside the processor and connected to the processor by various well-known means.

In the above-described embodiments, the components and features of the embodiments are combined in a predetermined form. Each component or feature should be considered an option unless explicitly stated otherwise. Each component or feature may be implemented without being associated with other components or features. Further, embodiments may be configured by associating some components and/or features. The order of the operations described in the embodiments may be altered. Some components or features of any embodiment may be included in or replaced with components and features corresponding to another embodiment. It is apparent that claims not explicitly cited in the claims are combined to form embodiments or are included in new claims.

Embodiments may be implemented by hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, the example embodiments described herein may be implemented using one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc., according to a hardware implementation.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A UE, comprising:

A processor; and

A receiver coupled to the processor,

Wherein the processor is configured to

Receiving, via the receiver, a control signal for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and

The scheduled transport block is received via the receiver based on the control signal.

2. The UE of claim 1, wherein the processor is further configured to

HARQ feedback for each of the scheduled transport blocks is determined based on the associated HARQ process number and the HARQ configuration.

3. The UE of claim 1, wherein the HARQ configuration indicates HARQ processes enabled or disabled for HARQ feedback via a bitmap manner.

4. The UE of claim 1, wherein the HARQ configuration indicates a number of HARQ processes for which HARQ feedback is enabled or a number of HARQ processes for which HARQ feedback is disabled.

5. The UE of claim 4, wherein the processor is further configured to: determining HARQ processes with HARQ feedback enabled and HARQ processes with HARQ feedback disabled according to the number of HARQ processes with HARQ feedback enabled or the number of HARQ processes with HARQ feedback disabled.

6. The UE of claim 1, wherein the processor is configured to: the scheduled transport blocks are received via the receiver in a transmission order determined by the HARQ process number and corresponding HARQ feedback enablement or disablement.

7. The UE of claim 1, wherein the association of the scheduled TB with the HARQ process number is determined by the indicated HARQ process number in the control signal and a corresponding HARQ process enabled or disabled for HARQ feedback.

8. The UE of claim 1, wherein the processor is further configured to: terminating listening to a search space for another control signal in a period after receiving the scheduled transport block, the period being determined by at least one of:

HARQ feedback for the scheduled transport block enables or disables HARQ processes,

Type of RNTI associated with control signal CRC scrambling, and

A search space type associated with the control signal.

9. A method of a UE, comprising:

Receiving a control signal for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and

And receiving the scheduled transport block based on the control signal.

10. The method of claim 9, further comprising:

11. The method of claim 9, wherein the HARQ configuration indicates a number of HARQ processes for which HARQ feedback is enabled or a number of HARQ processes for which HARQ feedback is disabled.

12. The method of claim 9, wherein the scheduled transport blocks are received in a transmission order determined by the HARQ process number and corresponding HARQ feedback enablement or disablement.

13. The method of claim 9, wherein the association of the scheduled TB with the HARQ process number is determined by the indicated HARQ process number in the control signal and the corresponding HARQ process for HARQ feedback enablement or disablement.

14. The method of claim 9, further comprising:

Terminating listening to a search space for another control signal in a period after receiving the scheduled transport block, the period being determined by at least one of:

Type of RNTI associated with control signal CRC scrambling, and

A search space type associated with the control signal.

15. A base station, comprising:

A processor; and

A transmitter coupled to the processor,

Wherein the processor is configured to

Transmitting, via the transmitter, control signals for HARQ configuration and scheduling transport blocks, wherein each of the scheduled transport blocks is associated with a HARQ process number; and

The scheduled transport block is transmitted via the transmitter based on the control signal.