Method and apparatus for physical downlink shared channel scheduling delay count

Abstract

A method implemented by a user equipment (UE) in a communication network is provided. The method includes receiving, from a network node, a delay indicator indicating a scheduling delay of a physical downlink shared channel (PDSCH), and the UE counts the scheduling delay of the PDSCH according to the received indicator.

Description

Technical Field

[0001] This disclosure generally relates to the field of delay processing, and more specifically, to methods and apparatus for scheduling delay counting for Physical Downlink Shared Channel (PDSCH). Background Technology

[0002] A new work item (WI) entitled “Rel-17 enhancements for Narrowband-Internet of Things (NB-IoT) and Long Term Evolution – Machine Type Communication (LTE-MTC)” has recently been agreed upon. In this context, one goal of LTE-MTC is to specify the introduction of 14 Hybrid Automatic Repeat Request (HARQ) procedures in the downlink (DL), as described in the following work item description (WID):

[0003] For half-duplex-frequency division duplex (HD-FDD) Cat M1 user equipment (UE), additional physical downlink shared channel (PDSCH) scheduling delay is supported for introducing the 14-HARQ procedure in the DL.

[0004] For LTE-MTC, the WID target for HD-FDD Cat M1 UEs can achieve its peak data rate for the MTC Physical Downlink Control Channel (MPDCCH), Physical Downlink Shared Channel (PDSCH), and Physical Uplink Control Channel (PUCCH) by combining 10 HARQ procedures and HARQ acknowledgment (HARQ-ACK) bundles for CatM1 HD-FDD UEs, as described in Tables 1A and 1B.

[0005] Table 1A

[0006]

[0007] Table 1B

[0008] Subframe # 17 18 19 20 21 22 23 24 25 26 27 28 MPDCCH 0 1 2 3 4 5 6 7 8 9 PDSCH 0 1 2 3 4 5 6 7 8 9 PUCCH(ACK)

[0009] The solid and dashed arrows in Tables 1A and 1B respectively illustrate examples of "PDSCH scheduling delay" (containing 2 subframes) and "HARQ-ACK delay" (containing 11 subframes).

[0010] The Rel-17 enhancement for LTE-MTC aims to improve peak data rates by “supporting additional PDSCH scheduling delays for the 14-HARQ procedure introduced in the DL for HD-FDD Cat M1 UEs”, as shown in Tables 2A and 2B, and is intended to be achieved using the framework described in Tables 1A and 1B.

[0011] Table 2A

[0012]

[0013] Table 2B

[0014]

[0015] The solid and dashed arrows in Tables 2A and 2B respectively illustrate examples of "PDSCH scheduling delay" (containing 7 subframes) and "HARQ-ACK delay" (containing 13 subframes).

[0016] Regarding the introduction of 14 HARQ procedures in DL, the following is mentioned in 3GPP TS 36.212v.16.1.0:

[0017] Assuming 1000 bits of TBS are transmitted in each PDSCH, the peak data rate achieved by this scheduling is (10×1000) / 17 = 588 kbps. In this contribution, we propose to increase the peak data rate to (12×1000) / 17 = 706 kbps (a 20% increase) by allowing data scheduling in subframes 0 and 1.

[0018] See 3GPP TS 36.212v.16.1.0, “Evolved Universal Terrestrial RadioAccess (E-UTRA); Multiplexing and channel coding”, version 16.1.0. Although a 12-HARQ procedure is used to estimate the increase in peak data rate, there are a total of 14 HARQ procedures. As can be seen in Tables 2A and 2B, the reason for having 14 HARQ procedures (i.e., spanning from #0 to #13) is that HARQ procedures #10 and #11 (bound to MPDCCH 10 and 11) require waiting for an acknowledgment (ACK) bundle, which follows the upcoming set of MPDCCHs ending with HARQ procedures #12 and #13 (bound to MPDCCH 12 and 13).

[0019] As can be seen from Tables 2A and 2B, introducing 14 HARQ procedures into DL will require adding new values ​​to both the PDSCH scheduling delay and the HARQ-ACK delay.

[0020] Based on the aforementioned technique, when there are 10 HARQ procedures, the PDSCH scheduling delay uses a value of 2. That is, the PDSCH begins on the second subframe after the MPDCCH, which is used to schedule the corresponding DL data, ends. On the other hand, when there are 14 HARQ procedures, in addition to the traditional value of 2, the PDSCH scheduling delay is also required to be equal to a value of 7 (see the blue arrow in Table 2A).

[0021] In 3GPP TS 36.212, it has been proposed that, in addition to the traditional value 2, the PDSCH scheduling delay can also support a value of 7, and for HARQ-ACK delay, the following values ​​have been proposed: 4, 5, 6, 7, 9, 11, 13, and 15. See "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding", version 16.1.0.

[0022] However, some issues exist. For example, the proposed technique for supporting the 14-HARQ procedure in the DL for HD-FDD Cat M1 UE does not account for the further latency caused when this feature happens to coexist with other scenarios / features, which will affect PDSCH scheduling latency. As another example, scenarios / features where the 14 HARQ procedure features can coexist require specific handling for evaluating PDSCH scheduling latency. Summary of the Invention

[0023] To address the aforementioned problems with existing solutions, a new system, method, and technique for determining PDSCH scheduling delay are proposed.

[0024] According to some embodiments, a method implemented by a user equipment (UE) in a communication network is provided. The method includes receiving an indicator in downlink control information (DCI) and, in response to the presence of physical uplink control channel (PUCCH) duplication, counting the scheduling delay of the physical downlink shared channel (PDSCH) based on the indicator received in the DCI.

[0025] According to some embodiments, a method implemented by a network node in a communication network is provided. The method includes setting a delay indicator that indicates a scheduling delay of the PDSCH, and sending the delay indicator to notify the UE of the scheduling delay.

[0026] According to some embodiments, a network node in a communication network is provided. The network node includes a processor and a memory communicatively coupled to the processor and adapted to store instructions. When executed by the processor, the instructions cause the network node to perform operations according to some embodiments described herein.

[0027] According to some embodiments, a network node in a communication network is provided. The network node includes a processor and a memory communicatively coupled to the processor and adapted to store instructions. When executed by the processor, the instructions cause the network node to perform operations according to some embodiments described herein.

[0028] According to some embodiments, a non-transitory computer-readable medium on which a computer program is stored is provided. When the computer program is executed by a collection of one or more processors of a network node in a communication network, the computer program causes the network node to perform operations of some embodiments described herein.

[0029] Certain embodiments of this disclosure may provide one or more technical advantages. For example, certain embodiments may provide methods, systems, techniques, and solutions applicable when using 14 HARQ procedure features in scenarios that result in additional PDSCH scheduling delays. A selective PDSCH scheduling delay counting strategy has been developed in tabular form, providing the cumulative delay when “14 HARQ procedures in a HARQ-ACK bundled DL are used for a Cat M1HD-FDD UE”.

[0030] Other advantages may be apparent to those skilled in the art. Some embodiments may lack, have some, or have all of the listed advantages. Attached Figure Description

[0031] The present disclosure is best understood by way of example, referring to the following description and accompanying drawings which illustrate embodiments thereof. In the drawings:

[0032] Figure 1 This is a flowchart illustrating a method implemented by a UE in a communication network according to some embodiments of the present disclosure;

[0033] Figure 2 This is a flowchart illustrating a method implemented by a network node in a communication network according to some embodiments of the present disclosure;

[0034] Figure 3 This is a block diagram illustrating a user equipment for delayed processing according to some embodiments of the present disclosure;

[0035] Figure 4 This is a block diagram illustrating a network node for delay processing according to some embodiments of the present disclosure; and

[0036] Figure 5 This is another block diagram illustrating a network node for delayed processing according to some embodiments of the present disclosure. Detailed Implementation

[0037] The following detailed description describes methods and apparatus for delay processing. Numerous specific details, such as the logical implementation, type, and interrelationships of system components, are set forth in this detailed description to provide a more thorough understanding of this disclosure. However, those skilled in the art will appreciate that this disclosure can be practiced without such specific details. In other instances, control structures, circuits, and instruction sequences are not shown in detail so as not to obscure this disclosure. Using the included description, those skilled in the art will be able to implement appropriate functionality without excessive experimentation.

[0038] References to "an embodiment," "an embodiment," "an exemplary embodiment," etc., in the specification indicate that the described embodiment may include specific features, structures, or characteristics, but each embodiment may not necessarily include those specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is believed that, whether explicitly described or not, its influence on such feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art.

[0039] The text within parentheses and boxes with dashed borders (e.g., large dashes, small dashes, dotted lines, and dots) may be used herein to illustrate optional operations for adding additional features to embodiments of this disclosure. However, such notation should not be construed as implying that these are the only options or optional operations, and / or that in some embodiments of this disclosure, boxes with solid borders are not optional.

[0040] In the following detailed description and claims, the terms “coupled” and “connected” together with their derivatives may be used. It should be understood that these terms are not intended to be synonyms with each other. “Coupled” is used to indicate that two or more elements cooperate or interact with each other, which may or may not be in direct physical or electrical contact with each other. “Connected” is used to indicate the establishment of communication between two or more elements coupled to each other.

[0041] Electronic devices use machine-readable media (also known as computer-readable media) to store and transmit (internal and / or with other electronic devices) code (which consists of software instructions and is sometimes referred to as computer program code or computer program) and / or data, such as machine-readable storage media (e.g., magnetic disks, optical disks, read-only memory (ROM), flash memory devices, phase-change memory) and machine-readable transmission media (also known as carriers) (e.g., electrical, optical, radio, acoustic, or other forms of propagation signals… such as carrier waves, infrared signals). Thus, an electronic device (e.g., a computer) includes hardware and software, such as a collection of one or more processors coupled to one or more machine-readable storage media, to store code for execution on the collection of processors and / or to store data. For example, an electronic device may include non-volatile memory containing code, because non-volatile memory retains code / data even when the electronic device is turned off (when power is removed), while when the electronic device is turned on, the portion of code to be executed by one or more processors of the electronic device is typically copied from slower non-volatile memory to the volatile memory of the electronic device (e.g., dynamic random access memory (DRAM), static random access memory (SRAM)). A typical electronic device also includes a set of one or more physical interfaces for establishing connections with other electronic devices (to transmit and / or receive code and / or data using propagation signals). One or more portions of embodiments of this disclosure may be implemented using different combinations of software, firmware, and / or hardware.

[0042] The embodiments disclosed herein relate to at least the following situations for supporting the 14HARQ procedure in the DL for HD-FDD Cat M1 UE:

[0043] Case 1: PUCCH duplicates and invalid BL / CE DL subframes;

[0044] Case 2: PUCCH duplication, invalid BL / CE DL subframes, and invalid BL / CE UL subframes;

[0045] • Case 3: PUCCH repetition, invalid BL / CE DL subframe, invalid BL / CE UL subframe, and measurement gap.

[0046] As discussed above, the Rel-17 target for introducing a 14-HARQ procedure in the DL for HD-FDD Cat M1 UEs does not account for the further delays that occur when this feature happens to coexist with PUCCH duplication, invalid BL / CE DL subframes, invalid BL / CE UL subframes, and measurement gaps, which would affect PDSCH scheduling delays. Therefore, methods, systems, and techniques are provided, according to certain embodiments disclosed herein, to support the introduction of an N-HARQ procedure in the DL for HD-FDD Cat M1 UEs in the presence of PUCCH duplication, invalid BL / CE DL subframes, invalid BL / CE UL subframes, and / or measurement gaps. For illustrative purposes and to maintain consistency with Rel-17 WID, the methods, systems, and techniques disclosed herein are described based on a 14-HARQ procedure. However, it is recognized that the same design principles (partially or entirely) can be applied to any number N HARQ procedures.

[0047] The term “invalid BL / CE DL subframe” is used herein and generally corresponds to the term “non-BL / CE DL subframe” in the 3GPP technical specifications. Furthermore, the term “cross-UL transmission” is used herein to describe the situation of DL data scheduling in a specific DL HARQ procedure, where uplink (UL) PUCCH transmissions occur between the MPDCCH carrying the DL license and the associated PDSCH carrying the DL data.

[0048] Case 1: The introduction of 14 HARQ procedures using HARQ-ACK bundles in the presence of PUCCH duplication and invalid BL / CE DL subframes.

[0049] HARQ-ACK bundling will be part of a framework supporting 14 HARQ procedures in the DL for HD-FDD Cat M1 UEs. When using HARQ-ACK bundling, each PUCCH can multiplex up to 4 transport blocks (TB). This means that 14 HARQ procedures in the DL can be supported using 3 PUCCHs. Recall that while there are a total of 14 HARQ procedures, the increase in peak data rate is estimated using 12 HARQ procedures, as 2 of the 14 procedures require transmission across the UL. Tables 2A and 2B above provide further explanation.

[0050] In the context of Case 1, Parts I and II below describe proposed solutions that strictly consider 3 bundles (i.e., using 3 PUCCHs) and any number of bundles (i.e., using 1, 2, or 3 PUCCHs), respectively.

[0051] I. The 14 HARQ procedures using HARQ-ACK bundles can only be used with 3 bundles (only 3 PUCCHs) in cases of PUCCH duplication and invalid BL / CE DL subframes.

[0052] According to some embodiments, a 2-bit field in DCI format 6-1A is used to indicate the PDSCH scheduling delay, which takes advantage of the fact that up to two HARQ processes can be scheduled across UL transmissions.

[0053] In a particular embodiment, taking advantage of the fact that up to two HARQ processes can be scheduled across UL transmissions, the DCI field in DCI format 6-1A, which indicates the number of PDSCH repetitions (described as the “Repetition number – 2 bits” field in subclause 7.1.11 of 3GPP TS 36.212v16.1.0), is slightly modified (repurposed) to indicate the PDSCH scheduling delay.

[0054] In a particular embodiment, the PDSCH scheduling delay when there are PUCCH duplicates and invalid BL / CE DL subframes in the “14-HARQ procedure using HARQ-ACK bundles” is determined according to Table 3, which allows only 3 bundles.

[0055] Table 3

[0056]

[0057]

[0058] The existence of PUCCH repetition is described by the term Rpucch.

[0059] In a further specific embodiment, the symbol "+" means "followed" to indicate the order in which the delays are counted.

[0060] In a further specific embodiment, the definition of BL / CE DL subframes remains the same as in the previous methods and techniques, while the definition of an absolute subframe refers to any type of subframe.

[0061] In a further specific embodiment, the expression "(2 absolute subframes + 3 * Rpucch on absolute subframes)" refers to 2 absolute subframes used for DL ​​to UL and UL to DL switching respectively, while the +3 * pucch-NumRepetitionCE-format1 absolute subframe is used for PUCCH transmission.

[0062] In a further specific embodiment, it is assumed that an invalid BL / CE DL subframe can be used to perform DL to UL handover, UL to DL handover, or for transmission in UL (e.g., PUCCH).

[0063] Examples illustrating the applicability of Table 3 are described below in Tables 4A and 4B. In the examples in Tables 4A and 4B, the bit sequence 1110011110 is used as a periodic downlink subframe bitmap, where “1” indicates a valid subframe and “0” indicates an invalid subframe, and the 2-bit field in DCI format 6-1A (shown in the last row of Tables 4A and 4B) determines the PDSCH scheduling delay according to Table 3.

[0064] Table 4A

[0065]

[0066]

[0067] Table 4B shows the continuous time progression.

[0068] Table 4B

[0069]

[0070] Based on the examples in Tables 4A and 4B, in subframe #0, MPDCCH 0 has already been used to schedule PDSCH 0, which begins on the second BL / CE DL subframe after the last subframe in which MPDCCH is transmitted. According to the combination "00" in Table 3, the PDSCH scheduling delay = 2 BL / CE DL subframes, which will be associated with MPDCCH 0.

[0071] Based on the examples in Tables 4A and 4B, in subframe #1, MPDCCH 1 has already been used to schedule PDSCH 1, which also begins on the second BL / CE DL subframe after the last subframe in which MPDCCH is transmitted. Note that the use of the term "BL / CE DL subframe" when counting PDSCH scheduling delays allows the presence of invalid BL / CE DL subframes to be skipped. In other words, the counting terminology in Table 3 ensures that invalid BL / CE DL subframes do not contribute to the PDSCH scheduling delay. Therefore, according to the combination "00" in Table 3, the PDSCH scheduling delay = 2 BL / CE DL subframes, which will be associated with MPDCCH 1.

[0072] According to the examples in Tables 4A and 4B, the situation is different in subframe #15 because HARQ procedure #10 is subject to cross scheduling. That is, MPDCCH 10 and PDSCH 10 are transmitted separately via UL. For this reason, Table 3 uses the combination "01" to describe an adjacent BL / CE DL subframe, followed by an absolute subframe for DL ​​to UL handover, then Rpucch on 3*absolute subframes (taking PUCCH repetition into account, if any), followed by an absolute subframe for UL to DL handover, and finally a BL / CE DL subframe. Based on the above, in this example, according to the combination "01" in Table 3, the PDSCH scheduling delay = 7 subframes, which will be associated with MPDCCH 10.

[0073] Based on the examples in Tables 4A and 4B, in subframe #16, HARQ procedure #11 also follows cross-scheduling, differing from HARQ procedure #10 only in that the DL to UL handover is adjacent to it, and because of this, Table 3 utilizes combination "10". According to combination "10" in Table 3, the PDSCH scheduling delay = 7 subframes, which will be associated with MPDCCH 11. Recall that the proposed counting strategy allows skipping the presence of invalid subframes.

[0074] II: 14 HARQ procedures using HARQ-ACK bundles, which can be used with any number of bundles (i.e., 1, 2, or 3 PUCCHs) in the presence of PUCCH duplication and invalid BL / CE DL subframes:

[0075] Following the same principle described in Section I above, Table 5 below corresponds to an extension of Table 3, where bundles 1, 2, or 3 can be used.

[0076] In a particular embodiment, the PDSCH scheduling delay when there are PUCCH duplicates and invalid BL / CE DL subframes in the “14-HARQ process using HARQ-ACK bundles” is determined according to Table 5, which allows any number of bundles.

[0077] Table 5

[0078]

[0079]

[0080] Examples illustrating the applicability of Table 5 are described below in Tables 6A and 6B. In the examples in Tables 6A and 6B, two bundles (i.e., two PUCCHs) and the bit sequence 1100001111 are used as a periodic downlink subframe bitmap, where “1” indicates a valid subframe and “0” indicates an invalid subframe, and 1 bit (new or borrowed from other fields in the DCI) + the “Repetition number” field in DCI format 6-1A (shown in the last row of Tables 6A and 6B) determines the PDSCH scheduling delay according to Table 5.

[0081] Table 6A

[0082]

[0083] Table 6B

[0084]

[0085] Case 2: The introduction of 14 HARQ procedures bundled with HARQ-ACK in the presence of PUCCH duplication, invalid BL / CE DL subframes and invalid BL / CE UL subframes.

[0086] In addition to invalid BL / CE DL subframes, there may also be scenarios where invalid BL / CE UL subframes exist. To account for the presence of PUCCH duplication, invalid BL / CE DL subframes, and invalid BL / CE UL subframes, some embodiments are described as relating to Case 2, which uses Case 1 as a framework and incorporates additional terminology to prevent invalid BL / CE UL subframes from causing further PDSCH scheduling delays.

[0087] Using Table 3 as a framework, in a specific embodiment, the PDSCH scheduling delay is determined according to Table 7, which allows only 3 bundles, when there are PUCCH duplicates, invalid BL / CE DL subframes, and invalid BL / CE UL subframes in the "14-HARQ procedure using HARQ-ACK bundles".

[0088] Table 7

[0089]

[0090]

[0091] In a further specific embodiment, the symbol "+" means "followed" to indicate the order in which the delays are counted.

[0092] In a further specific embodiment, the definitions of BL / CE DL subframes and BL / CE UL subframes remain the same as in the previous methods and techniques, while the definition of an absolute subframe refers to any type of subframe.

[0093] In a further specific embodiment, it is assumed that an invalid BL / CE DL subframe can be used to perform DL to UL handover, UL to DL handover, or for transmission in UL (e.g., PUCCH).

[0094] In a further specific embodiment, it is assumed that an invalid BL / CE UL subframe can be used to perform DL-to-UL handover, UL-to-DL handover, or for transmission in DL (e.g., MPDCCH or PDSCH).

[0095] Examples illustrating the applicability of Table 7 are described below in Tables 8A and 8B. In the examples in Tables 8A and 8B, the bit sequences 1011111110 and 1110011110 are used as periodic uplink and downlink subframe bitmaps, respectively, where “0” indicates an invalid subframe, and the “Repetition number” field in DCI format 6-1A (shown in the last row of the table below) determines the PDSCH scheduling delay according to Table 7.

[0096] Table 8A

[0097]

[0098]

[0099] Table 8B

[0100]

[0101] In a particular embodiment, Table 7 may use Table 5 as a framework so that case 2 is not limited to use with only 3 bundles, but can be used with any number of bundles.

[0102] Case 3: The introduction of 14 HARQ procedures bundled with HARQ-ACK in the presence of PUCCH repetition, invalid BL / CE DL subframes, invalid BL / CE UL subframes, and measurement gaps.

[0103] In addition to taking into account the presence of PUCCH repetitions, invalid BL / CE DL subframes, and invalid BL / CE UL subframes, certain embodiments described herein with reference to Case 3 use Case 2 as a framework and incorporate additional terminology to prevent further delays caused by the measurement gap (MG). The measurement gap duration and its periodicity are defined by the variable measurement gap length (MGL) and measurement gap repetition period (MGRP) as defined in 3GPP TS 36.133.

[0104] When the MG fully or partially overlaps with a BL / CE UL subframe or a BL / CE DL subframe, there will be no DL transmission on the subframe containing the MGL, and also (i.e., respectively) no UL transmission on the same MGL+1 subframe. The +1 subframe is because it is assumed that the Cat-M1 UE cannot transmit anything in the UL in a subframe after the measurement gap. The MG affects the PDSCH scheduling delay with and without "cross-UL transmission" scheduling.

[0105] Using Table 3 as a framework, in a specific embodiment, the PDSCH scheduling delay is determined according to Table 9, which allows only 3 bundles, when there are PUCCH duplicates, invalid BL / CE DL subframes, invalid BL / CE UL subframes, and measurement gaps in the "14-HARQ procedure using HARQ-ACK bundles".

[0106] Table 9

[0107]

[0108] In a further specific embodiment, the symbol "+" means "followed" to indicate the order in which the delays are counted.

[0109] In a further specific embodiment, the definitions of BL / CE DL subframe, BL / CE UL subframe, and measurement gap remain the same as in the previous techniques and methods, while the definition of an absolute subframe refers to any type of subframe.

[0110] In a further specific embodiment, it is assumed that an invalid BL / CE DL subframe can be used to perform DL to UL handover, UL to DL handover, or for transmission in UL (e.g., PUCCH).

[0111] In a further specific embodiment, it is assumed that an invalid BL / CE UL subframe can be used to perform DL-to-UL handover, UL-to-DL handover, or for transmission in DL (e.g., MPDCCH or PDSCH).

[0112] In a further specific embodiment, the word "including" in Table 9 relies on the assumption that the UL to DL handover can occur during the measurement interval. This involves two consecutive DL-related actions on the UE side, the measurement, and the subsequent monitoring.

[0113] Examples illustrating the applicability of Table 9 are described below in Tables 10A and 10B. In the examples in Tables 10A and 10B, the bit sequences 1011111110 and 1110011110 are used as periodic uplink and downlink subframe bitmaps, respectively, where “0” indicates an invalid subframe, and the “Repetition number” field in DCI format 6-1A (shown in the last row of the table below) determines the PDSCH scheduling delay according to Table 9.

[0114] Table 10A

[0115]

[0116] Table 10B

[0117]

[0118] In a particular embodiment, Table 9 may use Table 5 as a framework so that case 3 is not limited to use with only 3 bundles, but can be used with any number of bundles.

[0119] In a particular embodiment, the PDSCH scheduling delay counting strategy for supporting the 14 HARQ processes in the DL can be described as a set of rules or any other form / format other than the tabular format used in this disclosure (e.g., Tables 3, 5, 7, and 9).

[0120] Figure 1 An example method 100 implemented by a UE in a communication network according to certain embodiments is shown. Method 100 is illustrated by way of example only and may be performed in the UE, and is not limited thereto.

[0121] In one embodiment, method 100 may begin at step 101 when the UE receives a delay indicator from the network node indicating the scheduling delay of the PDSCH. Then, in step 102, the UE counts the scheduling delay of the PDSCH based on the received indicator.

[0122] In a particular embodiment, counting the scheduling delay of the PDSCH based on the received indicator includes: if the HARQ process is subject to cross-scheduling in response to the presence of PUCCH repetition, then the scheduling delay is counted by taking into account the repetition of the uplink control channel.

[0123] In a particular embodiment, method 100 further includes: receiving the number of PUCCH repetitions in Radio Resource Control (RRC) signaling from a network node. And based on the number of PUCCH repetitions Count the scheduling delay of PDSCH.

[0124] In a particular embodiment, counting the scheduling delay based on the received indicator includes: counting the scheduling delay by further taking into account the number of PUCCH bundles in response to the presence of a bundle of PUCCHs.

[0125] In a particular embodiment, method 100 further includes: receiving the number N of PUCCH bundles in downlink control information (DCI) from the network node. 捆 And based on the number N of PUCCH bundles 捆 Count the scheduling delay of PDSCH.

[0126] In a particular embodiment, the number N of PUCCH bundles is... 捆 It can be any one of 3, 2, and 1.

[0127] In a particular embodiment, in response to the presence of an invalid downlink subframe, the scheduling delay can be counted as follows:

[0128] D1 = 1 BL / CE DL subframe + (2 absolute subframes + N) 捆 *On absolute subframes )+1 BL / CEDL subframe, or

[0129] D2 = (2 absolute subframes + N) 捆 *On absolute subframes )+2 BL / CE DL subframes;

[0130] In this example, D1 is the scheduling delay of the first HARQ procedure subject to the crossing schedule, D2 is the scheduling delay of the HARQ procedure after the first HARQ procedure, absolute subframe refers to any type of subframe, and N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

[0131] In a particular embodiment, in response to the presence of invalid downlink subframes and invalid uplink subframes, the scheduling delay can be counted as follows:

[0132] D1 = 1 BL / CE DL subframe + 1 absolute subframe + N 捆 *On the BL / CE UL subframe One absolute subframe + 1 BL / CE DL subframe, or

[0133] D2 = 1 absolute subframe + N 捆 *On the BL / CE UL subframe One absolute subframe + 2 BL / CEDL subframes;

[0134] In this example, D1 is the scheduling delay of the first HARQ procedure subject to cross-scheduling, D2 is the scheduling delay of the HARQ procedure after the first HARQ procedure, absolute subframe refers to any type of subframe, and N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

[0135] In a particular embodiment, in response to the presence of invalid downlink subframes, invalid uplink subframes, and measurement gaps, the scheduling delay can be counted as follows:

[0136] • D0 = 2 BL / CE DL subframes that do not overlap with the measurement gap;

[0137] • D1 = 1 valid downlink subframe that does not overlap with any measurement gap in the measurement gap + 1 absolute subframe, unless it overlaps with any measurement gap in the measurement gap + (N 捆 * BL / CE UL subframes that do not overlap with any measurement gaps in the measurement gap And 1 absolute subframe (in the case of any measurement gap preceding it) + 1 absolute subframe including overlapping measurement gaps + 1 BL / CE DL subframe that does not overlap with any measurement gap; or

[0138] • D2 = 1 absolute subframe, unless it overlaps with any measurement gap in the measurement gap + (N 捆 * BL / CE UL subframes that do not overlap with any measurement gaps in the measurement gap One absolute subframe (in the case of any measurement gap preceding it) + 1 absolute subframe including any overlapping measurement gaps + 2 BL / CE DL subframes that do not overlap with measurement gaps.

[0139] In this example, D0 is the scheduling delay of a HARQ procedure that does not comply with cross-scheduling, D1 is the scheduling delay of a first HARQ procedure that complies with cross-scheduling, D2 is the scheduling delay of HARQ procedures after the first HARQ procedure, absolute subframe refers to any type of subframe, N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

[0140] Figure 2 An example method 200, implemented by a network node in a communication network according to certain embodiments, is shown. Method 200 is illustrated by way of example only and can be executed in a network node; it is not limited thereto.

[0141] According to some embodiments, method 200 may begin at step 201 when the network node sets a delay indicator that indicates the scheduling delay of the PDSCH. In step 202, the network node sends the delay indicator to notify the UE of the scheduling delay.

[0142] In a particular embodiment, if the HARQ procedure is subject to cross-scheduling in response to the presence of PUCCH repetition, the scheduling delay takes into account uplink control channel repetition.

[0143] In a particular embodiment, method 200 further includes: sending the number of PUCCH repetitions to the UE in RRC signaling. And notify the UE based on the number of PUCCH repetitions. Count the scheduling delay of PDSCH.

[0144] In a particular embodiment, in response to the presence of a PUCCH bundle, the scheduling delay further takes into account the number of PUCCH bundles.

[0145] In a particular embodiment, method 200 further includes sending N bundles of PUCCH to the UE in the DCI. 捆 and notify the UE based on the number N of bundles in the PUCCH. 捆 Count the scheduling delay of PDSCH.

[0146] In a further specific embodiment, the number N of the PUCCH bundles 捆 It can be any one of 3, 2, and 1.

[0147] In a particular embodiment, in response to the presence of an invalid downlink subframe, the network node sends a delay indicator to notify the UE of the following scheduling delay:

[0148] D1 = 1 BL / CE DL subframe + (2 absolute subframes + N) 捆 *On absolute subframes )+1 BL / CEDL subframe, or

[0149] D2 = (2 absolute subframes + N) 捆 *On absolute subframes )+2 BL / CE DL subframes;

[0150] In this example, D1 is the scheduling delay of the first HARQ procedure subject to cross-scheduling, D2 is the scheduling delay of the HARQ procedure after the first HARQ procedure, absolute subframe refers to any type of subframe, and N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

[0151] In a particular embodiment, in response to the presence of invalid downlink subframes and invalid uplink subframes, the network node sends a delay indicator to notify the UE of the following scheduling delay:

[0152] D1 = 1 BL / CE DL subframe + 1 absolute subframe + N 捆 *On the BL / CE UL subframe One absolute subframe + 1 BL / CE DL subframe, or

[0153] D2 = 1 absolute subframe + N 捆 *On the BL / CE UL subframe One absolute subframe + 2 BL / CEDL subframes;

[0154] In this example, D1 is the scheduling delay of the first HARQ procedure subject to cross-scheduling, D2 is the scheduling delay of the HARQ procedure after the first HARQ procedure, absolute subframe refers to any type of subframe, and N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

[0155] In a particular embodiment, in response to the presence of an invalid downlink subframe, an invalid uplink subframe, and a measurement gap, the network node may send a delay indicator to notify the UE of the following scheduling delay:

[0156] • D0 = 2 BL / CE DL subframes that do not overlap with the measurement gap;

[0157] • D1 = 1 valid downlink subframe that does not overlap with any measurement gap in the measurement gap + 1 absolute subframe, unless it overlaps with any measurement gap in the measurement gap + (N 捆 * BL / CE UL subframes that do not overlap with any measurement gaps in the measurement gap And 1 absolute subframe (in the case of any measurement gap preceding it) + 1 absolute subframe including overlapping measurement gaps + 1 BL / CE DL subframe that does not overlap with any measurement gap; or

[0158] • D2 = 1 absolute subframe, unless it overlaps with any measurement gap in the measurement gap + (N 捆 BL / CE UL subframes that do not overlap with any measurement gaps in the measurement gap One absolute subframe (in the case of any measurement gap preceding it) + 1 absolute subframe including any overlapping measurement gaps + 2 BL / CE DL subframes that do not overlap with measurement gaps.

[0159] In this example, D0 is the scheduling delay of a HARQ procedure that does not comply with cross-scheduling, D1 is the scheduling delay of a first HARQ procedure that complies with cross-scheduling, D2 is the scheduling delay of HARQ procedures after the first HARQ procedure, absolute subframe refers to any type of subframe, N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

[0160] Figure 3 An example user equipment 300 for delay processing according to certain embodiments is shown. It should be understood that user equipment 300 can use, in addition to... Figure 3 It is implemented using components other than those shown, and is not limited to them.

[0161] exist Figure 3 In the example, user equipment 300 may include at least a processor 301, a memory 302, an interface 303, and a communication medium 304. The processor 301, memory 302, and interface 303 may be communicatively coupled to each other via the communication medium 304.

[0162] Processor 301 may include one or more processing units. A processing unit may be a physical device or article of manufacture including one or more integrated circuits that read data and instructions from a computer-readable medium, such as memory 302, and selectively execute instructions. In various embodiments, processor 301 may be implemented in various ways. As an example, processor 301 may be implemented as one or more processing cores. As another example, processor 301 may include one or more separate microprocessors. In yet another example, processor 301 may include an application-specific integrated circuit (ASIC) that provides specific functionality. In yet another example, processor 301 may provide specific functionality by using an ASIC and / or by executing computer-executable instructions.

[0163] The memory 302 may include one or more computer-usable or computer-readable storage media capable of storing data and / or computer-executable instructions. It should be understood that the storage medium is preferably a non-transitory storage medium.

[0164] Interface 303 may be a device or article of manufacture that enables user equipment 300 to send data to or receive data from external devices.

[0165] Communication medium 304 facilitates communication between processor 301, memory 302, and interface 303. Communication medium 304 can be implemented in various ways. For example, communication medium 304 may include a Peripheral Component Interconnect (PCI) bus, a PCI Express bus, an Accelerated Graphics Port (AGP) bus, a Serial Advanced Technology Attachment (ATA) interconnect, a Parallel ATA interconnect, a Fibre Channel interconnect, a USB bus, a Small Computer System Interface (SCSI) interface, or another type of communication medium.

[0166] exist Figure 3 In the example, the instructions stored in memory 302 may include, when executed by processor 301, causing user device 300 to implement about Figure 1 The instructions described in the method. For example, the instructions stored in memory 302 may include the following instructions, which, when executed by processor 301, cause user equipment 300 to receive a delay indicator from a network node indicating the scheduling delay of PDSCH and to count the scheduling delay of PDSCH based on the received indicator.

[0167] Figure 4 An example network node 400 for delay processing according to certain embodiments is shown. It should be understood that the network node 400 can use, in addition to... Figure 4 It is implemented using components other than those shown, and is not limited to them.

[0168] exist Figure 4 In the example, network node 400 may include at least processor 401, memory 402, interface 403, and communication medium 404. Processor 401, memory 402, and interface 403 may be communicatively coupled to each other via communication medium 404.

[0169] Processor 401 may include one or more processing units. A processing unit may be a physical device or article of manufacture including one or more integrated circuits that read data and instructions from a computer-readable medium, such as memory 402, and selectively execute instructions. In various embodiments, processor 401 may be implemented in various ways. For example, processor 401 may be implemented as one or more processing cores. As another example, processor 401 may include one or more separate microprocessors. In yet another example, processor 401 may include an application-specific integrated circuit (ASIC) that provides specific functionality. In yet another example, processor 401 may provide specific functionality by using an ASIC and / or by executing computer-executable instructions.

[0170] The memory 402 may include one or more computer-usable or computer-readable storage media capable of storing data and / or computer-executable instructions. It should be understood that the storage medium is preferably a non-transitory storage medium.

[0171] Interface 403 may be a device or article that enables network node 400 to send data to or receive data from external devices.

[0172] Communication medium 404 facilitates communication between processor 401, memory 402, and interface 403. Communication medium 404 can be implemented in various ways. For example, communication medium 404 may include a Peripheral Component Interconnect (PCI) bus, a PCI Express bus, an Accelerated Graphics Port (AGP) bus, a Serial Advanced Technology Attachment (ATA) interconnect, a Parallel ATA interconnect, a Fibre Channel interconnect, a USB bus, a Small Computer System Interface (SCSI) interface, or another type of communication medium.

[0173] exist Figure 4 In the example, the instructions stored in memory 402 may include, when executed by processor 401, causing network node 400 to implement about Figure 2 The instructions described in the method. For example, the instructions stored in memory 402 may include instructions that, when executed by processor 401, cause network node 400 to set a delay indicator indicating a scheduling delay of PDSCH and send the delay indicator to notify the UE of the scheduling delay.

[0174] Figure 5 An example radio node 500 for delay processing according to certain embodiments is shown. It should be understood that the radio node 500 can use, in addition to... Figure 5 It is implemented with components other than those shown, and is not limited thereto. It will be further appreciated that, in certain embodiments, radio node 500 may include user equipment such as user equipment 300 or network node such as network node 400.

[0175] refer to Figure 5 The radio node 500 may include at least a selection unit 501 and a determination unit 502. The selection unit 501 may be adapted to perform at least the following functions: Figure 1 Box 101 or Figure 2 The operations described in box 201. Determining unit 502 may be adapted to at least perform... Figure 1 box 102 or Figure 2 The operations described in box 202.

[0176] Some units in Figure 5The units are illustrated as separate units. However, this merely indicates that functionality is separate. These units may be provided as individual components. However, other arrangements are possible; for example, some of them may be combined into a single unit. Any combination of these units may be implemented in any suitable location using any combination of software, hardware, and / or firmware. For example, there may be multiple controllers configured separately, or there may be only one controller for all components.

[0177] Figure 5 The units shown can be configured as machine-executable instructions embodied in, for example, a machine-readable medium, which, when executed by a machine, will cause the machine to perform the described operations. Furthermore, any of these units can be implemented as hardware, such as an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a field-programmable gate array (FPGA), etc.

[0178] Furthermore, it should be understood that the arrangements described herein are merely illustrative examples. Other arrangements may be used in addition to or instead of those shown (e.g., more controllers or more detectors, etc.), and some units may be omitted entirely. References Figure 1 Or 2, correspondingly, describes the functionality and collaboration of these units in more detail.

[0179] Some parts of the foregoing detailed description have been presented based on the symbolic representation and algorithms of transactions on data bits within computer memory. These algorithmic descriptions and representations are the most efficient way for those skilled in the art of signal processing to communicate the essence of their work to others skilled in the art. Algorithms, here and in general, are considered as self-consistent sequences of transactions that lead to desired results. These transactions are those that require physical manipulation of physical quantities. Typically, though not always necessary, these quantities take the form of electrical or magnetic signals that can be stored, transformed, combined, compared, and otherwise manipulated. It has proven convenient to sometimes refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc., primarily for general use.

[0180] However, it should be understood that all these and similar terms are to be associated with appropriate physical quantities and are merely convenient labels applied to those quantities. Unless otherwise stated in detail, it is evident from the foregoing discussion that throughout the description, discussions using terms such as “processing” or “computing or calculating” or “determining” or “displaying” refer to the actions and processes of computer systems or similar electronic computing devices that manipulate and convert data represented as physical (electronic) quantities within the registers and memories of the computer system into other data similarly represented as physical quantities in the computer system's memory or registers or other such information storage, transmission, or display devices.

[0181] The algorithms and displays presented herein are not inherently related to any particular computer or other device. Various general-purpose systems can be used with the program based on the teachings herein, or it may prove convenient to construct more specialized devices to perform the required methodological transactions. The required structures of various such systems will become apparent from the above description. Furthermore, no particular programming language is referenced in describing embodiments of this disclosure. It should be understood that the teachings of embodiments of this disclosure as described herein can be implemented using various programming languages.

[0182] Embodiments of this disclosure may be an article of manufacture in which a non-transitory machine-readable medium (such as microelectronic memory) has stored thereon instructions (e.g., computer code) that program one or more signal processing components (collectively referred to herein as a "processor") to perform the operations described above. In other embodiments, some of these operations may be performed by specific hardware components containing hard-wired logic (e.g., dedicated digital filter blocks and state machines). These operations may alternatively be performed by any combination of programmed signal processing components and fixed hard-wired circuit components.

[0183] In the foregoing detailed description, embodiments of the present disclosure have been described with reference to specific exemplary embodiments. It will be apparent that various modifications may be made thereto without departing from the spirit and scope of the present disclosure as set forth in the appended claims. Therefore, the specification and drawings should be viewed in an illustrative rather than restrictive sense.

[0184] Throughout this description, some embodiments of the present disclosure have been presented by way of flowcharts. It should be understood that the transactions and their order described in these flowcharts are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Those skilled in the art will recognize that changes can be made to the flowcharts without departing from the spirit and scope of the present disclosure as set forth in the appended claims.

Claims

1. A method performed by a user equipment (UE) in a communication network, the method comprising: A delay indicator that indicates the scheduling delay of the Physical Downlink Shared Channel (PDSCH) is received from the downlink control information (DCI) from the network node. as well as The scheduling delay of the PDSCH is counted according to the received indicator, wherein different bit values ​​of the bit field of the indicator in the DCI indicate different counting methods of the scheduling delay of the PDSCH, and wherein the bit value changes when the Hybrid Automatic Repeat Request (HARQ) procedure is subject to cross-scheduling, the cross-scheduling referring to the separation of the subframe carrying the DCI and the PDSCH through uplink transmission.

2. The method as described in claim 1, wherein, The step of counting the scheduling delay of the PDSCH according to the received indicator includes: when the Hybrid Automatic Repeat Request (HARQ) procedure is subject to cross-scheduling in response to the presence of repeated Physical Uplink Control Channel (PUCCH), counting the scheduling delay by taking into account the repeated uplink control channel.

3. The method of claim 2, further comprising: The number of PUCCH repetitions received from the Radio Resource Control (RRC) signaling from the network node ; as well as According to the number of times PUCCH is repeated. The scheduling delay of PDSCH is counted.

4. The method of claim 1, wherein, The step of counting the scheduling delay based on the received indicator includes: in response to the presence of a PUCCH bundle, counting the scheduling delay by further taking into account the number of PUCCH bundles.

5. The method of claim 4, further comprising: The number of PUCCH bundles received from the downlink control information (DCI) from the network node. N 捆 ; as well as According to the quantity stated in the PUCCH bundle N 捆 The scheduling delay of PDSCH is counted.

6. The method of claim 5, wherein, The quantity of bundles of PUCCH N 捆 It can be any one of 3, 2, and 1.

7. The method of claim 1, wherein, In response to the presence of an invalid downlink subframe, the scheduling delay D1 or D2 is counted as follows: D1 = 1 low-complexity downlink BL / CE DL subframe with reduced bandwidth or enhanced coverage + (2 absolute subframes + ... N 捆 *On absolute subframes ) +1 BL / CE DL subframe, or D2 = (2 absolute subframes + N 捆 *On absolute subframes ) + 2 BL / CE DL subframes; Wherein, D1 is the scheduling delay of the first HARQ procedure subject to cross-scheduling. D2 is the scheduling delay of the HARQ process following the first HARQ process, and the absolute subframe refers to any type of subframe. N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

8. The method of claim 1, wherein, In response to the presence of invalid downlink subframes and invalid uplink subframes, the scheduling delay D1 or D2 is counted as follows: D1 = 1 low-complexity downlink BL / CE DL subframe with reduced bandwidth or enhanced coverage + 1 absolute subframe + N 捆 *BL / CE UL subframe +1 absolute subframe +1 BL / CE DL subframe, or D2 = 1 absolute subframe + N 捆 *BL / CE UL subframe +1 absolute subframe + 2 BL / CE DL subframes; Wherein, D1 is the scheduling delay of the first HARQ procedure subject to cross-scheduling. D2 is the scheduling delay of the HARQ process following the first HARQ process, and the absolute subframe refers to any type of subframe. N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

9. The method of claim 1, wherein, Counting the scheduling delay in response to the presence of invalid downlink subframes, invalid uplink subframes, and measurement gaps includes: D0 = 2 low-complexity or coverage-enhanced downlink BL / CE DL subframes with reduced bandwidth that do not overlap with the measurement gap; D1 = 1 valid downlink subframe that does not overlap with any of the measurement gaps + 1 absolute subframe, unless it overlaps with any of the measurement gaps + ( N 捆 * BL / CE UL subframes that do not overlap with any of the measurement gaps. , and 1 absolute subframe (in the case of any measurement gap preceding it) + 1 absolute subframe including overlapping measurement gaps + 1 BL / CE DL subframe not overlapping with any measurement gap; or D2 = 1 absolute subframe, unless it overlaps with any measurement gap in the measurement gap + ( N 捆 * BL / CE UL subframes that do not overlap with any of the measurement gaps. +1 absolute subframe (in the case of any measurement gap preceding it) +1 absolute subframe including any measurement gaps overlapping the measurement gaps +2 BL / CE DL subframes that do not overlap with the measurement gaps. Wherein, D0 is the scheduling delay of a HARQ process that does not comply with cross-scheduling, D1 is the scheduling delay of a first HARQ process that complies with cross-scheduling, and D2 is the scheduling delay of a HARQ process following the first HARQ process. The absolute subframe refers to any type of subframe. N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

10. A method performed by a network node in a communication network, the method comprising: Set a delay indicator that indicates the scheduling delay of the Physical Downlink Shared Channel (PDSCH); as well as The delay indicator is transmitted in the downlink control information (DCI) to notify the user equipment (UE) of the scheduling delay, wherein different bit values ​​of the bit field of the indicator in the DCI indicate different counting methods of the scheduling delay of the PDSCH, and wherein the bit value changes when the hybrid automatic repeat request (HARQ) procedure is subject to cross-scheduling, the cross-scheduling referring to the separation of the subframe carrying the DCI and the PDSCH through uplink transmission.

11. The method of claim 10, wherein, When the Hybrid Automatic Repeat Request (HARQ) procedure is subject to cross-scheduling in response to the presence of repeated Physical Uplink Control Channel (PUCCH), the scheduling delay takes into account the repeated uplink control channel.

12. The method of claim 11, further comprising: The number of PUCCH repetitions sent to the UE in the Radio Resource Control (RRC) signaling. ; as well as The UE is notified of the number of times the PUCCH is repeated. The scheduling delay of PDSCH is counted.

13. The method of claim 10, wherein, In response to the presence of a PUCCH bundle, the scheduling delay further takes into account the number of PUCCH bundles.

14. The method of claim 13, further comprising: The number of PUCCH bundles sent to the UE in the downlink control information (DCI) N 捆 ; as well as The UE is notified of the quantity of the bundle according to the PUCCH. N 捆 The scheduling delay of the PDSCH is counted.

15. The method of claim 14, wherein, The quantity of bundles of PUCCH N 捆 It can be any one of 3, 2, and 1.

16. The method of claim 10, wherein, In response to the presence of an invalid downlink subframe, the delay indicator is sent to notify the UE of the scheduling delay D1 or D2 as follows: D1 = 1 low-complexity downlink BL / CE DL subframe with reduced bandwidth or enhanced coverage + (2 absolute subframes + ... N 捆 *On absolute subframes ) +1 BL / CE DL subframe, or D2 = (2 absolute subframes + N 捆 *On absolute subframes ) + 2 BL / CE DL subframes; Where D1 is the scheduling delay of the first HARQ procedure subject to cross-scheduling, D2 is the scheduling delay of the HARQ procedure following the first HARQ procedure, and the absolute subframe refers to any type of subframe. N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

17. The method of claim 10, wherein, In response to the presence of invalid downlink subframes and invalid uplink subframes, the delay indicator is sent to notify the UE of the scheduling delay D1 or D2 as follows: D1 = 1 low-complexity downlink BL / CE DL subframe with reduced bandwidth or enhanced coverage + 1 absolute subframe + N 捆 *BL / CE UL subframe +1 absolute subframe +1 BL / CE DL subframe, or D2 = 1 absolute subframe + N 捆 *BL / CE UL subframe +1 absolute subframe + 2 BL / CE DL subframes; Where D1 is the scheduling delay of the first HARQ procedure subject to cross-scheduling, D2 is the scheduling delay of the HARQ procedure following the first HARQ procedure, and the absolute subframe refers to any type of subframe. N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

18. The method of claim 10, wherein, In response to the presence of invalid downlink subframes, invalid uplink subframes, and measurement gaps, the delay indicator is sent to notify the UE of the scheduling delay D0, D1, or D2 as follows: D0 = 2 low-complexity or coverage-enhanced downlink BL / CE DL subframes with reduced bandwidth that do not overlap with the measurement gap; D1 = 1 valid downlink subframe that does not overlap with any of the measurement gaps + 1 absolute subframe, unless it overlaps with any of the measurement gaps + ( N 捆 * BL / CE UL subframes that do not overlap with any of the measurement gaps. , and 1 absolute subframe (in the case of any measurement gap preceding it) + 1 absolute subframe including overlapping measurement gaps + 1 BL / CE DL subframe not overlapping with any measurement gap; or D2 = 1 absolute subframe, unless it overlaps with any measurement gap in the measurement gap + ( N 捆 * BL / CE UL subframes that do not overlap with any of the measurement gaps. + 1 absolute subframe (in the case of any measurement gap preceding it) + 1 absolute subframe including any measurement gaps overlapping the measurement gaps + 2 BL / CE DL subframes that do not overlap with the measurement gaps. Wherein, D0 is the scheduling delay of a HARQ process that does not comply with cross-scheduling, D1 is the scheduling delay of a first HARQ process that complies with cross-scheduling, and D2 is the scheduling delay of a HARQ process following the first HARQ process. The absolute subframe refers to any type of subframe. N 捆 This refers to the number of bundles of PUCCH, and This refers to the number of times PUCCH is repeated.

19. A user equipment (UE) in a communication network, the UE comprising: processor; as well as A memory communicatively coupled to the processor and adapted to store instructions that, when executed by the processor, cause the network node to perform the operation of the method according to any one of claims 1 to 9.

20. A network node in a communication network, the network node comprising: processor; as well as A memory communicatively coupled to the processor and adapted to store instructions that, when executed by the processor, cause the network node to perform the operation of the method according to any one of claims 10 to 18.

21. A computer program product comprising a computer-readable storage medium storing instructions that, when executed by at least one processor of a computing system, cause the computing system to perform the method of any one of claims 1-18.

Images