WO2023000147A1

WO2023000147A1 - Method, device and computer storage medium of communication

Info

Publication number: WO2023000147A1
Application number: PCT/CN2021/107190
Authority: WO
Inventors: Gang Wang; Yukai GAO; Xiaohong Zhang; Lin Liang
Original assignee: Nec Corporation
Priority date: 2021-07-19
Filing date: 2021-07-19
Publication date: 2023-01-26

Abstract

Embodiments of the present disclosure relate to methods, devices and computer readable media for communication. A terminal device receives, from a network device, first DCI scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions. If the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, the terminal device determines a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain. In this way, an in-order scheduling or HARQ transmission restriction is obeyed.

Description

METHOD, DEVICE AND COMPUTER STORAGE MEDIUM OF COMMUNICATION

TECHNICAL FIELD

Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication during scheduling of multi-transmission time interval (TTI) by downlink control information (DCI) on a single downlink control channel.

BACKGROUND

Currently, to support new radio (NR) from 52.6GHz to 71GHz, it is proposed to employ multi-TTI based scheduling, where one physical downlink control channel (PDCCH) is used to schedule multiple physical uplink shared channels (PUSCHs) . In this way, the control signaling overhead can be reduced. Thus, the multi-TTI based scheduling is being also extended to the scheduling of multiple physical downlink shared channels (PDSCHs) by DCI on a single PDCCH.

For multiple PDSCHs or PUSCHs scheduled by single DCI, it is reasonable that an in-order scheduling or hybrid automatic repeat request (HARQ) transmission restriction needs to be followed. However, details on how to follow the in-order restriction are still incomplete.

SUMMARY

In general, embodiments of the present disclosure provide methods, devices and computer storage media for communication during scheduling of multi-TTI in one downlink control channel.

In a first aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device and from a network device, first DCI scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions; and in accordance with a determination that the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, determining a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain.

In a second aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device and from a network device, third DCI scheduling a plurality of data transmissions; receiving, from the network device, fourth DCI indicating a slot format comprising a set of symbols; and in accordance with a determination that at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions, cancelling the first data transmission.

In a third aspect, there is provided a method of communication. The method comprises: transmitting, at a network device and to a terminal device, first DCI scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions; and in accordance with a determination that the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, determining a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain.

In a fourth aspect, there is provided a method of communication. The method comprises: transmitting, at a network device and to a terminal device, third DCI scheduling a plurality of data transmissions; transmitting, to the terminal device, fourth DCI indicating a slot format comprising a set of symbols; and in accordance with a determination that at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions, cancelling the first data transmission.

In a fifth aspect, there is provided a terminal device. The terminal device comprises a processor and a memory coupled to the processor. The memory stores instructions that when executed by the processor, cause the terminal device to perform the method according to the first or second aspect of the present disclosure.

In a sixth aspect, there is provided a network device. The network device comprises a processor and a memory coupled to the processor. The memory stores instructions that when executed by the processor, cause the network device to perform the method according to the third or fourth aspect of the present disclosure.

In a seventh aspect, there is provided a computer readable medium having instructions stored thereon. The instructions, when executed on at least one processor, cause the at least one processor to perform the method according to the first or second aspect of the present disclosure.

In an eighth aspect, there is provided a computer readable medium having instructions stored thereon. The instructions, when executed on at least one processor, cause the at least one processor to perform the method according to the third or fourth aspect of the present disclosure.

Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:

FIG. 1 illustrates an example communication network in which some embodiments of the present disclosure can be implemented;

FIG. 2A illustrates a schematic diagram illustrating a process for scheduling one data transmission by single DCI according to embodiments of the present disclosure;

FIG. 2B illustrates a schematic diagram illustrating a process for scheduling multiple data transmissions by single DCI according to embodiments of the present disclosure;

FIG. 2C illustrates a schematic diagram illustrating an issue in following an in-order scheduling when one or more data transmissions scheduled by single DCI fall in one or more gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure;

FIG. 2D illustrates a schematic diagram illustrating an issue in following an in-order HARQ transmission when one or more data transmissions scheduled by single DCI fall in one or more gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure;

FIG. 3 illustrates a schematic diagram illustrating a process for communication in following an in-order restriction for scheduling or HARQ transmission according to embodiments of the present disclosure;

FIG. 4A illustrates a schematic diagram illustrating a scenario in which one or more data transmissions scheduled by single DCI fall in symbol-level gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure;

FIG. 4B illustrates a schematic diagram illustrating a scenario in which one or more data transmissions scheduled by single DCI fall in slot-level gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure;

FIG. 5A illustrates a schematic diagram illustrating an example determination of a reference transmission for an in-order scheduling according to embodiments of the present disclosure;

FIG. 5B illustrates a schematic diagram illustrating an example scenario in which an in-order scheduling is violated according to embodiments of the present disclosure;

FIG. 6A illustrates a schematic diagram illustrating another example determination of a reference transmission for an in-order scheduling according to embodiments of the present disclosure;

FIG. 6B illustrates a schematic diagram illustrating another example scenario in which an in-order scheduling is violated according to embodiments of the present disclosure;

FIG. 7 illustrates a schematic diagram illustrating another example scenario in which an in-order scheduling is obeyed according to embodiments of the present disclosure;

FIG. 8A illustrates a schematic diagram illustrating an example determination of a reference transmission for an in-order HARQ transmission according to embodiments of the present disclosure;

FIG. 8B illustrates a schematic diagram illustrating an example scenario in which an in-order HARQ transmission is violated according to embodiments of the present disclosure;

FIG. 9A illustrates a schematic diagram illustrating another example determination of a reference transmission for an in-order HARQ transmission according to embodiments of the present disclosure;

FIG. 9B illustrates a schematic diagram illustrating another example scenario in which an in-order HARQ transmission is violated according to embodiments of the present disclosure;

FIG. 10 illustrates a schematic diagram illustrating another example scenario in which an in-order HARQ transmission is obeyed according to embodiments of the present disclosure;

FIG. 11 illustrates a schematic diagram illustrating another process for communication upon at least one symbol is unavailable for a data transmission in multiple data transmissions scheduled by single DCI according to embodiments of the present disclosure;

FIG. 12 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure;

FIG. 13 illustrates another example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure;

FIG. 14 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure;

FIG. 15 illustrates another example method of communication implemented at a network device in accordance with some embodiments of the present disclosure; and

FIG. 16 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitations as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

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

As used herein, the term “terminal device” refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, or image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device. In addition, the term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an Evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a Transmission Reception Point (TRP) , a Remote Radio Unit (RRU) , a radio head (RH) , a remote radio head (RRH) , a low power node such as a femto node, a pico node, and the like.

In one embodiment, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In one embodiment, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In one embodiment, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.

As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.

In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.

Currently, it is agreed that a time domain resource assignment (TDRA) table in DCI may schedule multiple PDSCHs or PUSCHs, and a row of the TDRA table may indicate PDSCHs or PUSCHs that are in consecutive or non-consecutive slots. The legacy in-order scheduling or HARQ transmission restriction in Rel-15 and Rel-16 should be supported for multiple PUSCH and PDSCH scheduled by a single DCI.

In some scenarios, multiple PDSCHs or PUSCHs scheduled by single DCI may be in non-consecutive slots or symbols. If there is another single or multiple PDSCHs or PUSCHs scheduled by another DCI falling in one or more gaps caused by the non-consecutive slots or symbols, how to follow an in-order scheduling restriction becomes an issue.

In some other scenarios, multiple PDSCHs scheduled by single DCI may be in non-consecutive slots or symbols. If there is another single or multiple PDSCHs scheduled by another DCI falling in one or more gaps caused by the non-consecutive slots or symbols, how to follow an in-order HARQ feedback transmission restriction also becomes an issue.

Embodiments of the present disclosure provide solutions for solving the above and other potential issues. In one aspect, a reference transmission is defined for the above scenarios to obey an in-order scheduling or HARQ transmission restriction. In this way, multiple PDSCHs or PUSCHs may be scheduled flexibly and ambiguity in the in-order scheduling or HARQ transmission restriction may be eliminated.

In another aspect, if a PDSCH or PUSCH among multiple PDSCHs or PUSCHs scheduled by single DCI is collided with an uplink or downlink symbol indicated by DCI format 2_0, the PDSCH or PUSCH is not received or transmitted. In this way, an uplink or downlink symbol indicated by DCI format 2_0 colliding with TDRA table is considered and multiple PDSCHs or PUSCHs may be scheduled flexibly.

Principles and implementations of the present disclosure will be described in detail below with reference to the figures.

EXAMPLE OF COMMUNICATION NETWORK

FIG. 1 illustrates a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure can be implemented. As shown in FIG. 1, the communication network 100 may include a terminal device 110 and a network device 120. In some embodiments, the terminal device 110 may be served by the network device 120. It is to be understood that the number of devices in FIG. 1 is given for the purpose of illustration without suggesting any limitations to the present disclosure. The communication network 100 may include any suitable number of network devices and/or terminal devices adapted for implementing implementations of the present disclosure.

As shown in FIG. 1, the terminal device 110 may communicate with the network device 120 via a channel such as a wireless communication channel. The communications in the communication network 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like. Furthermore, the communications may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols.

In some embodiments, the terminal device 110 may transmit uplink data to the network device 120 via an uplink data channel transmission. For example, the uplink data channel transmission may be a PUSCH transmission. Of course, any other suitable forms are also feasible. In some embodiments, the terminal device 110 may receive downlink data from the network device 120 via a downlink data channel transmission. For example, the downlink data channel transmission may be a PDSCH transmission. Of course, any other suitable forms are also feasible.

In some embodiments, the terminal device 110 may receive DCI, e.g., data transmission configuration from the network device 120 via a downlink control channel transmission. For example, the downlink control channel transmission may be a PDCCH transmission. Of course, any other suitable forms are also feasible. In some embodiments, the terminal device 110 may transmit uplink control information (UCI) , e.g., HARQ feedback information to the network device 120 via an uplink channel transmission. For example, the uplink channel transmission may be a PUCCH or PUSCH transmission. Of course, any other suitable forms are also feasible.

In some embodiments, the network device 120 may provide a plurality of serving cells (not shown herein) for the terminal device 110, for example, a primary cell (PCell) , a primary secondary cell (PSCell) , a secondary cell (SCell) , a special cell (sPCell) or the like. Each of the serving cells may correspond to a CC. The terminal device 110 may perform transmission with the network device 120 via a CC. Of course, the terminal device 110 may perform transmission with the network device 120 via multiple CCs, for example, in case of CA.

In some embodiments, the network device 120 may schedule one data transmission by DCI on a single downlink control channel for the terminal device 110. FIG. 2A illustrates a schematic diagram illustrating a process 200A for scheduling one downlink data channel by single DCI according to embodiments of the present disclosure. As shown in FIG. 2A, single DCI schedules a single PDSCH or PUSCH.

In some embodiments, the network device 120 may schedule multiple data transmissions by DCI on a single downlink control channel for the terminal device 110. FIG. 2B illustrates a schematic diagram illustrating a process 200B for scheduling multiple downlink data channels by a single DCI according to embodiments of the present disclosure. As shown in FIG. 2B, single DCI 200 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 201 to 208. It is to be understood that the number of PDSCHs scheduled in single DCI is not limited to the above example, and any other integer larger than one is also feasible.

In some scenarios, the network device 120 may schedule a first set of data transmissions by first DCI and a second set of data transmissions by second DCI for the terminal device 110. The first set of data transmissions may be scheduled to be performed on a first set of scheduled resources, and the second set of data transmissions may be scheduled to be performed on a second set of scheduled resources. In some cases, the second set of scheduled resources may be in a set of gaps among the first set of scheduled resources in time domain. FIG. 2C illustrates a schematic diagram 200C illustrating an issue in following an in-order scheduling when one or more data transmissions scheduled by single DCI fall in one or more gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure.

As shown in FIG. 2C, DCI 210 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 211 to 218. DCI 220 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

221 and 222. PDSCH or PUSCH 221 and PDSCH or PUSCH 214 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 222 and PDSCH or PUSCH 215 are scheduled to be performed on different symbols in the same slot.

According to an in-order scheduling restriction, if the terminal device 110 is scheduled to start a first PDSCH or PUSCH transmission starting in symbol j by a PDCCH ending in symbol i, the terminal device 110 is not expected to be scheduled to perform a second PDSCH or PUSCH transmission starting earlier than the end of the first PDSCH or PUSCH transmission by a PDCCH ending later than symbol i. In this case, there is ambiguity in the example of FIG. 2C. Specifically, DCI 210 is earlier than DCI 220. PDSCHs or PUSCHs 211 to 214 scheduled by DCI 210 start earlier than PDSCHs or

PUSCHs

221 and 222 scheduled by DCI 220. However, PDSCHs or PUSCHs 216 to 218 scheduled by DCI 210 start later than PDSCHs or

PUSCHs

221 and 222 scheduled by DCI 220. Thus, it is indefinite whether PDSCHs or

PUSCHs

221 and 222 scheduled by DCI 220 follow the in-order scheduling restriction or not.

In some scenarios, the network device 120 may schedule a first HARQ feedback for a first set of data transmissions by first DCI and a second HARQ feedback for a second set of data transmissions by second DCI for the terminal device 110. The first HARQ feedback may be scheduled to be performed on a third scheduled resource, and the second HARQ feedback may be scheduled to be performed on a fourth scheduled resource. FIG. 2D illustrates a schematic diagram 200D illustrating an issue in following an in-order HARQ transmission when one or more data transmissions scheduled by single DCI fall in one or more gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure.

As shown in FIG. 2D, a HARQ feedback for PDSCHs or PUSCHs 231 to 238 are scheduled by single DCI (not shown) to be performed on PUCCH or PUSCH 230. A HARQ feedback for PDSCHs or

PUSCHs

241 and 242 are scheduled by another single DCI (not shown) to be performed on PUCCH or PUSCH 240. PDSCH or PUSCH 234 and PDSCH or PUSCH 241 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 235 and PDSCH or PUSCH 242 are scheduled to be performed on different symbols in the same slot.

According to an in-order HARQ transmission restriction, the terminal device 110 is not expected to receive a first PDSCH transmission and a second PDSCH transmission, starting later than the first PDSCH transmission, with its corresponding HARQ feedback assigned to be transmitted on a resource ending before the start of a different resource for a HARQ feedback assigned to be transmitted for the first PDSCH transmission. In this case, there is ambiguity in the example of FIG. 2D. Specifically, PUCCH or PUSCH 230 is later than PUCCH or PUSCH 240. PDSCHs or PUSCHs 236 to 238 associated with PUCCH or PUSCH 230 start later than PDSCHs or

PUSCHs

241 and 242 associated with PUCCH or PUSCH 240. However, PDSCHs or PUSCHs 231 to 234 associated with PUCCH or PUSCH 230 start earlier than PDSCHs or

PUSCHs

241 and 242 associated with PUCCH or PUSCH 240. Thus, it is also indefinite whether PDSCHs or

PUSCHs

241 and 242 associated with PUCCH or PUSCH 240 follow the in-order HARQ transmission restriction or not.

In view of this, embodiments of the present disclosure provide a solution for following the in-order scheduling and HARQ transmission restrictions. This will be described in detail with reference to FIGs. 3 to 10.

EXAMPLE IMPLEMENTATION OF IN-ORDER SCHEDULING

FIG. 3 illustrates a schematic diagram illustrating a process 300 for communication in following an in-order restriction for scheduling or HARQ transmission according to embodiments of the present disclosure. For the purpose of discussion, the process 300 will be described with reference to FIG. 1. The process 300 may involve the terminal device 110 and the network device 120 as illustrated in FIG. 1.

As shown in FIG. 3, the network device 120 transmits 310, to the terminal device 110, first DCI scheduling a first set of data transmissions and transmits 320, to the terminal device 110, second DCI scheduling a second set of data transmissions. In some embodiments, the transmission 310 may be earlier than the transmission 320. In some embodiments, the transmission 310 may be later than the transmission 320. In some embodiments, the transmission 310 and the transmission 320 may be performed simultaneously.

In some embodiments, the first set of data transmissions may comprise single or multiple data transmissions. For example, the first set of data transmissions may comprise multiple PDSCHs. As another example, the first set of data transmissions may comprise multiple PUSCHs. In some embodiments, the second set of data transmissions may comprise single or multiple data transmissions. For example, the second set of data transmissions may comprise multiple PDSCHs. As another example, the second set of data transmissions may comprise multiple PUSCHs.

The terminal device 110 determines 330 whether the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed. The second set of scheduled resources is in a set of gaps among the first set of scheduled resources in time domain.

In some embodiments, a gap in the set of gaps is in a symbol level. FIG. 4A illustrates a schematic diagram illustrating a scenario 400A in which one or more data transmissions scheduled by single DCI fall in symbol-level gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure. As shown in FIG. 4A, DCI 410 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 411 to 418 in consecutive slots. DCI 420 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

421 and 422. PDSCH or PUSCH 421 and PDSCH or PUSCH 414 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 422 and PDSCH or PUSCH 415 are scheduled to be performed on different symbols in the same slot. That is, PDSCHs or

PUSCHs

421 and 422 are performed in symbol gaps among PDSCHs or PUSCHs 411 to 418.

In some embodiments, a gap in the set of gaps is in a slot level. FIG. 4B illustrates a schematic diagram illustrating a scenario 400B in which one or more data transmissions scheduled by single DCI fall in slot-level gaps among multiple data transmissions scheduled by another single DCI according to embodiments of the present disclosure. As shown in FIG. 4B, DCI 430 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 431 to 438 in non-consecutive slots. DCI 440 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

441 and 442. PDSCH or PUSCH 441 is scheduled to be performed on a slot gap between PDSCH or PUSCH 434 and PDSCH or PUSCH 435, and PDSCH or PUSCH 442 is scheduled to be performed on a slot gap between PDSCH or PUSCH 436 and PDSCH or PUSCH 437. That is, PDSCHs or

PUSCHs

441 and 442 are performed in slot gaps among PDSCHs or PUSCHs 431 to 438. For convenience, the following description will be given by taking the symbol-level gaps as an example.

Returning to FIG. 3, if the first set of data transmissions on the first set of scheduled resources and the second set of data transmissions on the second set of scheduled resources are to be performed, the terminal device 110 determines 340 a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling. Some example determination of the first and second reference transmissions will be described in connection with Embodiments 1-2.

Embodiment 1

In this embodiment, the first reference transmission is the first data transmission in the first set of data transmissions and the second reference transmission is the first data transmission in the second set of data transmissions. In some embodiments, the first data transmission in the second set of data transmissions may start later than an ending symbol of the first data transmission in the first set of data transmissions, and the second DCI may end later than an ending symbol of the first DCI. In this way, an in-order scheduling may be achieved. For clarity, some examples will be described with reference to FIGs. 5A and 5B.

FIG. 5A illustrates a schematic diagram 500A illustrating an example determination of a reference transmission for an in-order scheduling according to embodiments of the present disclosure. As shown in FIG. 5A, DCI 510 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 511 to 518 in consecutive slots. DCI 520 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

521 and 522. PDSCH or PUSCH 521 and PDSCH or PUSCH 514 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 522 and PDSCH or PUSCH 515 are scheduled to be performed on different symbols in the same slot. That is, PDSCHs or

PUSCHs

521 and 522 are performed in symbol gaps among PDSCHs or PUSCHs 511 to 518.

In the example of FIG. 5A, the first reference transmission is the first one of the PDSCHs or PUSCHs 511 to 518 (i.e., the PDSCH or PUSCH 511) and the second reference transmission is the first one of the PDSCHs or PUSCHs 521 to 522 (i.e., the PDSCH or PUSCH 521) . As shown in FIG. 5A, the PDSCH or PUSCH 521 starts later than an ending symbol of the PDSCH or PUSCH 511, and the DCI 520 ends later than an ending symbol of the DCI 510. Thus, an in-order scheduling restriction is obeyed.

FIG. 5B illustrates a schematic diagram 500B illustrating an example scenario in which an in-order scheduling is violated according to embodiments of the present disclosure. As shown in FIG. 5B, DCI 530 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 531 to 538 in consecutive slots. DCI 540 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

541 and 542. PDSCH or PUSCH 541 and PDSCH or PUSCH 534 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 542 and PDSCH or PUSCH 535 are scheduled to be performed on different symbols in the same slot. That is, PDSCHs or

PUSCHs

541 and 542 are performed in symbol gaps among PDSCHs or PUSCHs 531 to 538.

In the example of FIG. 5B, the first reference transmission is the first one of the PDSCHs or PUSCHs 531 to 538 (i.e., the PDSCH or PUSCH 531) and the second reference transmission is the first one of the PDSCHs or PUSCHs 541 to 542 (i.e., the PDSCH or PUSCH 541) . As shown in FIG. 5B, the PDSCH or PUSCH 531 starts earlier than an ending symbol of the PDSCH or PUSCH 541, but DCI 530 ends later than an ending symbol of the DCI 540. Thus, an in-order scheduling restriction is violated.

It is to be understood that FIGs. 5A and 5B are merely for illustration, and are not for limitation.

Embodiment 2

In this embodiment, the first reference transmission is the last data transmission in the first set of data transmissions and the second reference transmission is the last data transmission in the second set of data transmissions. In some embodiments, the last data transmission in the first set of data transmissions may start later than an ending symbol of the last data transmission in the second set of data transmissions, and the first DCI may end later than an ending symbol of the second DCI. In this way, an in-order scheduling may also be achieved. For clarity, some examples will be described with reference to FIGs. 6A and 6B.

FIG. 6A illustrates a schematic diagram 600A illustrating another example determination of a reference transmission for an in-order scheduling according to embodiments of the present disclosure. As shown in FIG. 6A, DCI 610 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 611 to 618 in consecutive slots. DCI 620 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

621 and 622. PDSCH or PUSCH 621 and PDSCH or PUSCH 614 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 622 and PDSCH or PUSCH 615 are scheduled to be performed on different symbols in the same slot. That is, PDSCHs or

PUSCHs

621 and 622 are performed in symbol gaps among PDSCHs or PUSCHs 611 to 618.

In the example of FIG. 6A, the first reference transmission is the last one of the PDSCHs or PUSCHs 611 to 618 (i.e., the PDSCH or PUSCH 618) and the second reference transmission is the last one of the PDSCHs or PUSCHs 621 to 622 (i.e., the PDSCH or PUSCH 622) . As shown in FIG. 6A, the PDSCH or PUSCH 618 starts later than an ending symbol of the PDSCH or PUSCH 622, and the DCI 610 ends later than an ending symbol of the DCI 620. Thus, an in-order scheduling restriction is obeyed.

FIG. 6B illustrates a schematic diagram 600B illustrating an example scenario in which an in-order scheduling is violated according to embodiments of the present disclosure. As shown in FIG. 6B, DCI 630 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 631 to 638 in consecutive slots. DCI 640 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

641 and 642. PDSCH or PUSCH 641 and PDSCH or PUSCH 634 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 642 and PDSCH or PUSCH 635 are scheduled to be performed on different symbols in the same slot. That is, PDSCHs or

PUSCHs

641 and 642 are performed in symbol gaps among PDSCHs or PUSCHs 631 to 638.

In the example of FIG. 6B, the first reference transmission is the last one of the PDSCHs or PUSCHs 611 to 618 (i.e., the PDSCH or PUSCH 618) and the second reference transmission is the last one of the PDSCHs or PUSCHs 621 to 622 (i.e., the PDSCH or PUSCH 622) . As shown in FIG. 6B, the PDSCH or PUSCH 642 starts earlier than an ending symbol of the PDSCH or PUSCH 638, but DCI 640 ends later than an ending symbol of the DCI 630. Thus, an in-order scheduling restriction is violated.

It is to be understood that FIGs. 6A and 6B are merely for illustration, and are not for limitation.

So far, determination of the first and second reference transmissions is made to follow an in-order scheduling restriction. It is to be understood that any other suitable ways are also feasible to follow an in-order scheduling restriction. An example will be given in connection with Embodiment 3.

Embodiment 3

In this embodiment, the first DCI and the second DCI ends at the same time. In this way, the first set of data transmissions and the second set of data transmissions may be performed with an in-order scheduling.

FIG. 7 illustrates a schematic diagram 700 illustrating another example scenario in which an in-order scheduling is obeyed according to embodiments of the present disclosure. As shown in FIG. 7, DCI 710 schedules eight PDSCHs or PUSCHs, i.e., PDSCHs or PUSCHs 711 to 718 in consecutive slots. DCI 720 schedules two PDSCHs or PUSCHs, i.e., PDSCHs or

PUSCHs

721 and 722. PDSCH or PUSCH 721 and PDSCH or PUSCH 714 are scheduled to be performed on different symbols in the same slot, and PDSCH or PUSCH 722 and PDSCH or PUSCH 715 are scheduled to be performed on different symbols in the same slot. That is, PDSCHs or

PUSCHs

721 and 722 are performed in symbol gaps among PDSCHs or PUSCHs 711 to 718.

In the example of FIG. 7, the

DCI

710 and 720 ends at the same time. In this case, the PDSCHs or PUSCHs 711 to 718 and the PDSCHs or

PUSCHs

721 and 722 are performed in order. Thus, an in-order scheduling restriction is also obeyed.

EXAMPLE IMPLEMENTATION OF IN-ORDER HARQ TRANSMISSION

Returning to FIG. 3, in some embodiments where a first HARQ feedback for the first set of data transmissions on a third scheduled resource and a second HARQ feedback for the second set of data transmissions on a fourth scheduled resource are to be transmitted from the terminal device 110 to the network device 120, the terminal device 110 may determine 350 a third reference transmission from the first set of data transmissions and a fourth reference transmission from the second set of data transmissions to follow an in-order HARQ transmission. Some example determination of the third and fourth reference transmissions will be described in connection with Embodiments 4-5.

Embodiment 4

In this embodiment, the third reference transmission is the last data transmission in the first set of data transmissions and the fourth reference transmission is the last data transmission in the second set of data transmissions. In some embodiments, the last data transmission in the first set of data transmissions may start later than the last data transmission in the second set of data transmissions, and the fourth scheduled resource may end before a start of the third scheduled resource. In this way, an in-order HARQ transmission may be achieved. For clarity, some examples will be described with reference to FIGs. 8A and 8B.

FIG. 8A illustrates a schematic diagram 800A illustrating an example determination of a reference transmission for an in-order HARQ transmission according to embodiments of the present disclosure. As shown in FIG. 8A, a HARQ feedback for eight PDSCHs 811 to 818 is scheduled to be transmitted on PUCCH or PUSCH 810. A HARQ feedback for two PDSCHs 821 and 822 is scheduled to be transmitted on PUCCH or PUSCH 820. The PDSCHs 811 to 818 is scheduled by single DCI (not shown) and the

PDSCHs

821 and 822 is scheduled by another single DCI (not shown) . The PDSCH or PUSCH 821 and PDSCH 814 are scheduled to be performed on different symbols in the same slot, and PDSCH 822 and PDSCH 815 are scheduled to be performed on different symbols in the same slot. That is, the

PDSCHs

821 and 822 are performed in symbol gaps among the PDSCHs 811 to 818.

In the example of FIG. 8A, the third reference transmission is the last one of the PDSCHs 811 to 818 (i.e., the PDSCH 818) and the fourth reference transmission is the last one of the PDSCHs 821 to 822 (i.e., the PDSCH 822) . As shown in FIG. 8A, the PDSCH 822 starts earlier than the PDSCH 818, and the PUCCH or PUSCH 820 ends before a start of the PUCCH or PUSCH 810. Thus, an in-order HARQ transmission restriction is obeyed.

FIG. 8B illustrates a schematic diagram 800B illustrating an example scenario in which an in-order HARQ transmission is violated according to embodiments of the present disclosure. As shown in FIG. 8B, a HARQ feedback for eight PDSCHs 831 to 838 is scheduled to be transmitted on PUCCH or PUSCH 830. A HARQ feedback for two PDSCHs 841 and 842 is scheduled to be transmitted on PUCCH or PUSCH 840. The PDSCHs 831 to 838 is scheduled by single DCI (not shown) and the

PDSCHs

841 and 842 is scheduled by another single DCI (not shown) . The PDSCH or PUSCH 841 and PDSCH 834 are scheduled to be performed on different symbols in the same slot, and PDSCH 842 and PDSCH 835 are scheduled to be performed on different symbols in the same slot. That is, the

PDSCHs

841 and 842 are performed in symbol gaps among the PDSCHs 831 to 838.

In the example of FIG. 8B, the third reference transmission is the last one of the PDSCHs 831 to 838 (i.e., the PDSCH 838) and the fourth reference transmission is the last one of the PDSCHs 841 to 842 (i.e., the PDSCH 842) . As shown in FIG. 8B, the PDSCH or PUSCH 838 starts later than the PDSCH 842, but the PUCCH or PUSCH 830 ends earlier than a start of the PUCCH or PUSCH 840. Thus, an in-order HARQ transmission restriction is violated.

It is to be understood that FIGs. 8A and 8B are merely for illustration, and are not for limitation.

Embodiment 5

In this embodiment, the third reference transmission is the first data transmission in the first set of data transmissions and the fourth reference transmission is the first data transmission in the second set of data transmissions. In some embodiments, the first data transmission in the second set of data transmissions may start later than the first data transmission in the first set of data transmissions, and the third scheduled resource may end before a start of the fourth scheduled resource. In this way, an in-order HARQ transmission may be achieved. For clarity, some examples will be described with reference to FIGs. 9A and 9B.

FIG. 9A illustrates a schematic diagram 900A illustrating another example determination of a reference transmission for an in-order HARQ transmission according to embodiments of the present disclosure. As shown in FIG. 9A, a HARQ feedback for eight PDSCHs 911 to 918 is scheduled to be transmitted on PUCCH or PUSCH 910. A HARQ feedback for two PDSCHs 921 and 922 is scheduled to be transmitted on PUCCH or PUSCH 920. The PDSCHs 911 to 918 is scheduled by single DCI (not shown) and the

PDSCHs

921 and 922 is scheduled by another single DCI (not shown) . The PDSCH or PUSCH 921 and PDSCH 914 are scheduled to be performed on different symbols in the same slot, and PDSCH 922 and PDSCH 915 are scheduled to be performed on different symbols in the same slot. That is, the

PDSCHs

921 and 922 are performed in symbol gaps among the PDSCHs 911 to 918.

In the example of FIG. 9A, the third reference transmission is the first one of the PDSCHs 911 to 918 (i.e., the PDSCH 911) and the fourth reference transmission is the first one of the PDSCHs 921 to 922 (i.e., the PDSCH 921) . As shown in FIG. 9A, the PDSCH 911 starts earlier than the PDSCH 921, and the PUCCH or PUSCH 910 ends before a start of the PUCCH or PUSCH 920. Thus, an in-order HARQ transmission restriction is obeyed.

FIG. 9B illustrates a schematic diagram 900B illustrating an example scenario in which an in-order HARQ transmission is violated according to embodiments of the present disclosure. As shown in FIG. 9B, a HARQ feedback for eight PDSCHs 931 to 938 is scheduled to be transmitted on PUCCH or PUSCH 930. A HARQ feedback for two PDSCHs 941 and 942 is scheduled to be transmitted on PUCCH or PUSCH 940. The PDSCHs 931 to 938 is scheduled by single DCI (not shown) and the

PDSCHs

941 and 942 is scheduled by another single DCI (not shown) . The PDSCH or PUSCH 941 and PDSCH 934 are scheduled to be performed on different symbols in the same slot, and PDSCH 942 and PDSCH 935 are scheduled to be performed on different symbols in the same slot. That is, the

PDSCHs

941 and 942 are performed in symbol gaps among the PDSCHs 931 to 938.

In the example of FIG. 9B, the third reference transmission is the first one of the PDSCHs 931 to 938 (i.e., the PDSCH 931) and the fourth reference transmission is the first one of the PDSCHs 941 to 942 (i.e., the PDSCH 941) . As shown in FIG. 9B, the PDSCH 941 starts later than the PDSCH 931, but the PUCCH or PUSCH 940 ends before a start of the PUCCH or PUSCH 930. Thus, an in-order HARQ transmission restriction is violated.

It is to be understood that FIGs. 9A and 9B are merely for illustration, and are not for limitation.

So far, determination of the third and fourth reference transmissions is made to follow an in-order HARQ transmission restriction. It is to be understood that any other suitable ways are also feasible to follow an in-order HARQ transmission restriction. An example will be given in connection with Embodiment 6.

Embodiment 6

In this embodiment, the third scheduled resource and the fourth scheduled resource are in the same slot. In this way, the first HARQ feedback and the second HARQ feedback may be performed with an in-order HARQ transmission. In some embodiments, the first HARQ feedback on the third scheduled resource and the second HARQ feedback on the fourth scheduled resource may be multiplexed in a PUCCH or PUSCH slot.

FIG. 10 illustrates a schematic diagram 1000 illustrating another example scenario in which an in-order HARQ transmission is obeyed according to embodiments of the present disclosure. As shown in FIG. 10, a HARQ feedback for eight PDSCHs 1011 to 1018 is scheduled to be transmitted on PUCCH or PUSCH 1010. A HARQ feedback for two

PDSCHs

1021 and 1022 is scheduled to be transmitted on PUCCH or PUSCH 1020. The PDSCHs 1011 to 1018 is scheduled by single DCI (not shown) and the

PDSCHs

1021 and 1022 is scheduled by another single DCI (not shown) . The PDSCH or PUSCH 1021 and PDSCH 1014 are scheduled to be performed on different symbols in the same slot, and PDSCH 1022 and PDSCH 1015 are scheduled to be performed on different symbols in the same slot. That is, the

PDSCHs

1021 and 1022 are performed in symbol gaps among the PDSCHs 1011 to 1018.

In the example of FIG. 10, the PUCCH or PUSCH 1010 and the PUCCH or PUSCH 1020 are in the same slot and may be multiplexed in a PUCCH or PUSCH slot. In this case, an in-order scheduling restriction is also obeyed.

So far, solutions for following an in-order restriction of scheduling or HARQ transmission are described. In some alternative embodiments, the terminal device 110 may not expect a scheduling pattern in which the network device 120 transmits downlink data or uplink data in the slot or symbol level gap among multiple data transmissions scheduled by single DCI. In this way, an in-order restriction for scheduling or HARQ transmission is obeyed.

EXAMPLE IMPLEMENTATION OF HANDLING COLLISION WITH CONFIGURED SYMBOL

In some scenarios, a data transmission among multiple data transmissions scheduled by single DCI may be collided with a configured uplink or downlink symbol indicated by DCI format 2_0. In this case, how to handle the collision needs to be discussed.

Embodiments of the present disclosure provide a solution for handling the above collision. This will be described in detail with reference to FIG. 11. FIG. 11 illustrates a schematic diagram illustrating another process 1100 for communication upon at least one symbol is unavailable for a data transmission in multiple data transmissions scheduled by single DCI. For the purpose of discussion, the process 1100 will be described with reference to FIG. 1. The process 1100 may involve the terminal device 110 and the network device 120 as illustrated in FIG. 1.

As shown in FIG. 11, the network device 120 transmits 1110, to the terminal device 110, DCI (for convenience, also referred to as third DCI herein) scheduling a plurality of data transmissions. The network device 120 also transmits 1120, to the terminal device 110, another DCI (for convenience, also referred to as fourth DCI herein) indicating a slot format comprising a set of symbols.

In some embodiments, the transmission 1110 may be earlier than the transmission 1120. In some embodiments, the transmission 1110 may be later than the transmission 1120. In some embodiments, the transmission 1110 and the transmission 1120 may be performed simultaneously. It is to be understood that the present disclosure does not limit this aspect.

The terminal device 110 determines 1130 whether at least one symbol in the set of symbols is unavailable for a data transmission (for convenience, also referred to as a first data transmission herein) in the plurality of data transmissions. If the at least one symbol in the set of symbols is unavailable for the first data transmission, the terminal device 110 cancels 1140 the first data transmission.

For example, If the terminal device 110 is scheduled by a DCI format to receive PDSCH over multiple slots, and if a slot format indicator (SFI) -index field value in DCI format 2_0 indicates that, for one or more slots in the multiple slots, at least one symbol from a set of symbols where the terminal device 110 is scheduled PDSCH reception in the one or more slots is an uplink symbol, the terminal device 110 does not receive the PDSCH in the one or more slots.

As another example, if the terminal device 110 is scheduled by a DCI format to transmit PUSCH over multiple slots, and if an SFI-index field value in DCI format 2_0 indicates that, for one or more slots in the multiple slots, at least one symbol from a set of symbols where the terminal device 110 is scheduled PUSCH transmission in the one or more slots is a downlink symbol, the terminal device 110 does not transmit the PUSCH in the one or more slots.

In this way, one or more symbols indicated by SFI-index colliding with TDRA table is considered, and thus multiple data transmissions are scheduled flexibly.

EXAMPLE IMPLEMENTATION OF METHODS

Accordingly, embodiments of the present disclosure provide methods of communication implemented at a terminal device and a network device. These methods will be described below with reference to FIGs. 12 to 15.

FIG. 12 illustrates an example method 1200 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 1200 may be performed at the terminal device 110 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1200 will be described with reference to FIG. 1. It is to be understood that the method 1200 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

At block 1210, the terminal device 110 receives, from the network device 120, first DCI scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions.

At block 1220, the terminal device 110 determines whether the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain.

If determining that the first set of data transmissions on the first set of scheduled resources and the second set of data transmissions on the second set of scheduled resources are to be performed, at block 1230, the terminal device 110 determines a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling. In some embodiments, a gap in the set of gaps may be in a slot level. In some embodiments, a gap in the set of gaps is in a symbol level.

In some embodiments where the first reference transmission is the first data transmission in the first set and the second reference transmission is the first data transmission in the second set, the first data transmission in the second set starts later than an ending symbol of the first data transmission in the first set, and the second DCI ends later than an ending symbol of the first DCI.

In some embodiments where the first reference transmission is the last data transmission in the first set and the second reference transmission is the last data transmission in the second set, the last data transmission in the first set starts later than an ending symbol of the last data transmission in the second set, and the first DCI ends later than an ending symbol of the second DCI.

In some embodiments, the first DCI and the second DCI may end at the same time. In this way, an in-order scheduling restriction is obeyed.

In some embodiments, if a first HARQ feedback for the first set of data transmissions on a third scheduled resource and a second HARQ feedback for the second set of data transmissions on a fourth scheduled resource are to be transmitted to the network device, the terminal device 110 may determine a third reference transmission from the first set of data transmissions and a fourth reference transmission from the second set of data transmissions to follow an in-order HARQ transmission.

In some embodiments where the third reference transmission is the last data transmission in the first set and the fourth reference transmission is the last data transmission in the second set, the last data transmission in the first set starts later than the last data transmission in the second set, and the fourth scheduled resource ends before a start of the third scheduled resource.

In some embodiments where the third reference transmission is the first data transmission in the first set and the fourth reference transmission is the first data transmission in the second set, the first data transmission in the second set starts later than the first data transmission in the first set, and the third scheduled resource ends before a start of the fourth scheduled resource.

In some embodiments, the third scheduled resource and the fourth scheduled resource may be in the same slot. In this way, an in-order HARQ transmission restriction is obeyed.

FIG. 13 illustrates another example method 1300 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 1300 may be performed at the terminal device 110 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1300 will be described with reference to FIG. 1. It is to be understood that the method 1300 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

As shown in FIG. 13, at block 1310, the terminal device 110 receives, from the network device 120, third DCI scheduling a plurality of data transmissions. At block 1320, the terminal device 110 receives, from the network device 120, fourth DCI indicating a slot format comprising a set of symbols. For example, the fourth DCI may be DCI format 2_0.

At block 1330, the terminal device 110 determines whether at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions. If determining that the at least one symbol is unavailable for the first data transmission, at block 1340, the terminal device 110 cancels the first data transmission.

With the method 1300, one or more symbols indicated by SFI-index colliding with TDRA table is considered, and thus multiple data transmissions are performed flexibly.

FIG. 14 illustrates an example method 1400 of communication implemented at a network device in accordance with some embodiments of the present disclosure. For example, the method 1400 may be performed at the network device 120 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1400 will be described with reference to FIG. 1. It is to be understood that the method 1400 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

As shown in FIG. 14, at block 1410, the network device 120 transmits, to the terminal device 110, first DCI scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions.

At block 1420, the network device 120 determines whether the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain. In some embodiments, a gap in the set of gaps may be in a slot level. In some embodiments, a gap in the set of gaps is in a symbol level.

If the first set of data transmissions on the first set of scheduled resources and the second set of data transmissions on the second set of scheduled resources are to be performed, at block 1430, the network device 120 determines a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling.

In some embodiments, the first DCI and the second DCI end at the same time. In this way, an in-order scheduling restriction is obeyed.

In some embodiments, if a first HARQ feedback for the first set of data transmissions on a third scheduled resource and a second HARQ feedback for the second set of data transmissions on a fourth scheduled resource are to be received from the terminal device, the network device 120 may determine a third reference transmission from the first set of data transmissions and a fourth reference transmission from the second set of data transmissions to follow an in-order HARQ transmission.

In some embodiments where the third reference transmission is the last data transmission in the first set and the fourth reference transmission is the last data transmission in the second set, the last data transmission in the first set starts later than an ending symbol of the last data transmission in the second set, and the fourth scheduled resource ends before a start of the third scheduled resource.

In some embodiments where the third reference transmission is the first data transmission in the first set and the fourth reference transmission is the first data transmission in the second set, the first data transmission in the second set starts later than an ending symbol of the first data transmission in the first set, and the third scheduled resource ends before a start of the fourth scheduled resource.

FIG. 15 illustrates another example method 1500 of communication implemented at a network device in accordance with some embodiments of the present disclosure. For example, the method 1500 may be performed at the network device 120 as shown in FIG. 1. For the purpose of discussion, in the following, the method 1500 will be described with reference to FIG. 1. It is to be understood that the method 1500 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.

As shown in FIG. 15, at block 1510, the network device 120 transmits, to the terminal device 110, third DCI scheduling a plurality of data transmissions. At block 1520, the network device 120 transmits, to the terminal device 110, fourth DCI indicating a slot format comprising a set of symbols.

At block 1530, the network device 120 determines whether at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions. If determining that the at least one symbol is unavailable for the first data transmission, at block 1540, the network device 120 cancels the first data transmission.

With the method 1500, one or more symbols indicated by SFI-index colliding with TDRA table is considered, and thus multiple data transmissions are scheduled flexibly.

EXAMPLE IMPLEMENTATION OF DEVICE

FIG. 16 is a simplified block diagram of a device 1600 that is suitable for implementing embodiments of the present disclosure. The device 1600 can be considered as a further example implementation of the terminal device 110 or the network device 120 as shown in FIG. 1. Accordingly, the device 1600 can be implemented at or as at least a part of the terminal device 110 or the network device 120.

As shown, the device 1600 includes a processor 1610, a memory 1620 coupled to the processor 1610, a suitable transmitter (TX) and receiver (RX) 1640 coupled to the processor 1610, and a communication interface coupled to the TX/RX 1640. The memory 1610 stores at least a part of a program 1630. The TX/RX 1640 is for bidirectional communications. The TX/RX 1640 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.

The program 1630 is assumed to include program instructions that, when executed by the associated processor 1610, enable the device 1600 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 3 to 15. The embodiments herein may be implemented by computer software executable by the processor 1610 of the device 1600, or by hardware, or by a combination of software and hardware. The processor 1610 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1610 and memory 1620 may form processing means 1650 adapted to implement various embodiments of the present disclosure.

The memory 1620 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1620 is shown in the device 1600, there may be several physically distinct memory modules in the device 1600. The processor 1610 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

In some embodiments, a terminal device comprises circuitry configured to: receive, from a network device, first DCI scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions; and in accordance with a determination that the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, determine a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain. In some embodiments, a gap in the set of gaps is in a slot or symbol level.

In some embodiments, the first DCI and the second DCI end at the same time.

In some embodiments, the circuitry may be further configured to, in accordance with a determination that a first HARQ feedback for the first set of data transmissions on a third scheduled resource and a second HARQ feedback for the second set of data transmissions on a fourth scheduled resource are to be transmitted to the network device, determine a third reference transmission from the first set of data transmissions and a fourth reference transmission from the second set of data transmissions to follow an in-order HARQ transmission.

In some embodiments, the third scheduled resource and the fourth scheduled resource are in the same slot.

In some embodiments, a terminal device comprises circuitry configured to: receive, from a network device, third DCI scheduling a plurality of data transmissions; receive, from the network device, fourth DCI indicating a slot format comprising a set of symbols; and in accordance with a determination that at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions, cancel the first data transmission.

In some embodiments, a network device comprises circuitry configured to: transmit, to a terminal device, first DCI scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions; and in accordance with a determination that the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, determine a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain. In some embodiments, a gap in the set of gaps is in a slot or symbol level.

In some embodiments, the first DCI and the second DCI end at the same time.

In some embodiments, the circuitry may be further configured to: in accordance with a determination that a first HARQ feedback for the first set of data transmissions on a third scheduled resource and a second HARQ feedback for the second set of data transmissions on a fourth scheduled resource are to be received from the terminal device, determine a third reference transmission from the first set of data transmissions and a fourth reference transmission from the second set of data transmissions to follow an in-order HARQ transmission.

In some embodiments, a network device comprises circuitry configured to: transmit, to a terminal device, third DCI scheduling a plurality of data transmissions; transmit, to the terminal device, fourth DCI indicating a slot format comprising a set of symbols; and in accordance with a determination that at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions, cancel the first data transmission.

The term “circuitry” used herein may refer to hardware circuits and/or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 3 to 15. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include 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) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

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

Claims

A method of communication, comprising:

receiving, at a terminal device and from a network device, first downlink control information (DCI) scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions; and

in accordance with a determination that the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain,

determining a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling.
The method of claim 1, wherein a gap in the set of gaps is in a slot or symbol level.
The method of claim 1, wherein the first reference transmission is the first data transmission in the first set and the second reference transmission is the first data transmission in the second set, and

wherein the first data transmission in the second set starts later than an ending symbol of the first data transmission in the first set, and the second DCI ends later than an ending symbol of the first DCI.
The method of claim 1, wherein the first reference transmission is the last data transmission in the first set and the second reference transmission is the last data transmission in the second set, and

wherein the last data transmission in the first set starts later than an ending symbol of the last data transmission in the second set, and the first DCI ends later than an ending symbol of the second DCI.
The method of claim 1, wherein the first DCI and the second DCI end at the same time.
The method of claim 1, further comprising:

in accordance with a determination that a first hybrid automatic repeat request (HARQ) feedback for the first set of data transmissions on a third scheduled resource and a second HARQ feedback for the second set of data transmissions on a fourth scheduled resource are to be transmitted to the network device, determining a third reference transmission from the first set of data transmissions and a fourth reference transmission from the second set of data transmissions to follow an in-order HARQ transmission.
The method of claim 6, wherein the third reference transmission is the last data transmission in the first set and the fourth reference transmission is the last data transmission in the second set, and

wherein the last data transmission in the first set starts later than the last data transmission in the second set, and the fourth scheduled resource ends before a start of the third scheduled resource.
The method of claim 6, wherein the third reference transmission is the first data transmission in the first set and the fourth reference transmission is the first data transmission in the second set, and

wherein the first data transmission in the second set starts later than the first data transmission in the first set, and the third scheduled resource ends before a start of the fourth scheduled resource.
The method of claim 6, wherein the third scheduled resource and the fourth scheduled resource are in the same slot.
A method of communication, comprising:

receiving, at a terminal device and from a network device, third downlink control information (DCI) scheduling a plurality of data transmissions;

receiving, from the network device, fourth DCI indicating a slot format comprising a set of symbols; and

in accordance with a determination that at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions, cancelling the first data transmission.
A method of communication, comprising:

transmitting, at a network device and to a terminal device, first downlink control information (DCI) scheduling a first set of data transmissions and second DCI scheduling a second set of data transmissions; and

in accordance with a determination that the first set of data transmissions on a first set of scheduled resources and the second set of data transmissions on a second set of scheduled resources are to be performed, the second set of scheduled resources being in a set of gaps among the first set of scheduled resources in time domain,

determining a first reference transmission from the first set of data transmissions and a second reference transmission from the second set of data transmissions to follow an in-order scheduling.
The method of claim 11, wherein a gap in the set of gaps is in a slot or symbol level.
The method of claim 11, wherein the first reference transmission is the first data transmission in the first set and the second reference transmission is the first data transmission in the second set, and

wherein the first data transmission in the second set starts later than an ending symbol of the first data transmission in the first set, and the second DCI ends later than an ending symbol of the first DCI.
The method of claim 11, wherein the first reference transmission is the last data transmission in the first set and the second reference transmission is the last data transmission in the second set, and

wherein the last data transmission in the first set starts later than an ending symbol of the last data transmission in the second set, and the first DCI ends later than an ending symbol of the second DCI.
The method of claim 11, wherein the first DCI and the second DCI end at the same time.
The method of claim 11, further comprising:

in accordance with a determination that a first hybrid automatic repeat request (HARQ) feedback for the first set of data transmissions on a third scheduled resource and a second HARQ feedback for the second set of data transmissions on a fourth scheduled resource are to be received from the terminal device, determining a third reference transmission from the first set of data transmissions and a fourth reference transmission from the second set of data transmissions to follow an in-order HARQ transmission.
The method of claim 16, wherein the third reference transmission is the last data transmission in the first set and the fourth reference transmission is the last data transmission in the second set, and

wherein the last data transmission in the first set starts later than an ending symbol of the last data transmission in the second set, and the fourth scheduled resource ends before a start of the third scheduled resource.
The method of claim 16, wherein the third reference transmission is the first data transmission in the first set and the fourth reference transmission is the first data transmission in the second set, and

wherein the first data transmission in the second set starts later than an ending symbol of the first data transmission in the first set, and the third scheduled resource ends before a start of the fourth scheduled resource.
The method of claim 16, wherein the third scheduled resource and the fourth scheduled resource are in the same slot.
A method of communication, comprising:

transmitting, at a network device and to a terminal device, third downlink control information (DCI) scheduling a plurality of data transmissions;

transmitting, to the terminal device, fourth DCI indicating a slot format comprising a set of symbols; and

in accordance with a determination that at least one symbol in the set of symbols is unavailable for a first data transmission in the plurality of data transmissions, cancelling the first data transmission.
A terminal device comprising:

a processor configured to perform the method according to any of claims 1 to 9 or claim 10.
A network device comprising:

a processor configured to perform the method according to any of claims 11 to 19 or claim 20.