WO2022217606A1

WO2022217606A1 - Communication methods, terminal device, network device, and computer-readable media

Info

Publication number: WO2022217606A1
Application number: PCT/CN2021/087892
Authority: WO
Inventors: Gang Wang
Original assignee: Nec Corporation
Priority date: 2021-04-16
Filing date: 2021-04-16
Publication date: 2022-10-20
Also published as: CN117413602A

Abstract

Embodiments of the present disclosure relate to methods for communication, terminal device, network device and computer readable media. In the method, the terminal device receives from a network device, downlink control information, DCI, on a physical downlink control channel, PDCCH. The DCI is used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device. The plurality of PDSCH transmissions is associated with respective priorities. The terminal device then determines a resource for hybrid automatic repeat request, HARQ, feedbacks of the plurality of PDSCH transmissions, the HARQ feedbacks being multiplexed on a feedback codebook. After that, the terminal device transmits the HARQ feedbacks to the network device on the resource. With this solution, a solution for transmitting HARQ feedbacks of the plurality of PDSCH transmissions associated with different priorities is provided. Further, with this solution, a single DCI in PDCCH is able to be used for scheduling two PDSCH transmissions associated with different priorities and the corresponding HARQ-ACK feedbacks are transmitted on a PUCCH resource, therefore the provided suitable interpretation for the common DCI field in the multi-cell scheduling DCI for PDSCH transmission associated with different priorities achieves a balance between scheduling flexibility and smaller DCI size.

Description

COMMUNICATION METHODS, TERMINAL DEVICE, NETWORK DEVICE, AND COMPUTER-READABLE MEDIA

TECHNICAL FIELD

Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to communication methods, devices, and computer-readable medium.

BACKGROUND

The fifth generation, 5G, networks offers three services that could transform current industries and create new industries which are enhanced mobile broadband (eMBB) , ultra-reliable low latency communications (URLLC) and machine type communication (mMTC) . eMBB provides faster speeds for use cases requiring high data rates like large-scale video streaming, and virtual reality. Ultra-reliable low latency communications (URLLC) is of low latency for mission-critical services. mMTC provides internet access for sensing, metering, and monitoring devices.

3rd Generation Partnership Project (3GPP) has specified URLLC as a key feature for Release 15 5G new radio (NR) , in addition to eMBB. As per 3GPP 5G-NR, URLLC is a set of features that provide low latency and ultra-high reliability for mission critical applications such as industrial internet, smart grids, remote surgery and intelligent transportation systems.

SUMMARY

In general, example embodiments of the present disclosure provide a solution for communication.

In a first aspect, there is provided a communication method. The method comprises: receiving, at a terminal device from a network device, downlink control information, DCI, on a physical downlink control channel, PDCCH, the DCI being used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions being associated with respective priorities; determining a resource for hybrid automatic repeat request, HARQ, feedbacks of the plurality of PDSCH transmissions, the HARQ feedbacks being multiplexed on a feedback codebook; and transmitting the HARQ feedbacks to the network device on the resource.

In a second aspect, there is provided a communication method. The method comprises: transmitting, at a network device to a terminal device, downlink control information, DCI, on a physical downlink control channel, PDCCH, the DCI being used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities; and receiving, hybrid automatic repeat request, HARQ feedbacks from the terminal device on a resource for HARQ feedbacks of the plurality of PDSCH transmissions, the HARQ feedbacks being multiplexed on a feedback codebook.

In a third aspect, there is provided a communication method. The method comprises receiving, at a terminal device from a network device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities; multiplexing, hybrid automatic repeat request, HARQ feedbacks of the plurality of PDSCH transmissions on a feedback codebook, wherein the HARQ feedbacks of the plurality of PDSCH transmissions are indicated to be transmitted in a same slot or sub-slot by the respective DCIs; determining a resource for the feedback codebook; and transmitting the HARQ feedbacks to the network device on the resource.

In a fourth aspect, there is provided a communication method. The method comprises transmitting, at a network device to a terminal device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities; and receiving hybrid automatic repeat request, HARQ, feedbacks from the terminal device on a resource for the feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being multiplexed on a feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being indicated to be transmitted in a same slot or sub-slot by the respective DCIs.

In a fifth aspect, there is provided a terminal device. The terminal device includes a processor; and a memory coupled to the processor and storing instructions thereon, the instructions, when executed by the processor, causing the terminal device to perform the method according to the first aspect or the third aspect.

In a sixth aspect, there is provided a network device. The terminal device includes a processor; and a memory coupled to the processor and storing instructions thereon, the instructions, when executed by the processor, causing the terminal device to perform the method according to the second aspect or the fourth aspect.

In a seventh aspect, there is provided a computer-readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the first aspect or the third aspect.

In an eighth aspect, there is provided a computer-readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the second aspect or the fourth aspect.

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 example 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, where:

Fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented;

Fig. 2 illustrates a signaling flow for determining resource for HARQ feedbacks according to some embodiments of the present disclosure;

Figs. 3A-3E illustrate diagrams of determination of resource for HRAQ feedbacks according to some embodiments of the present disclosure;

Fig. 4 illustrates a signaling flow for determining resource for HARQ feedbacks according to some embodiments of the present disclosure;

Fig. 5 illustrates a diagram of determination of resource for HRAQ feedbacks according to some embodiments of the present disclosure;

Fig. 6 illustrates a flow chart of an example method of communication implemented at a terminal device according to some embodiments of the present disclosure;

Fig. 7 illustrates a flow chart of an example method of communication implemented at a network device according to some embodiments of the present disclosure;

Fig. 8 illustrates a flow chart of an example method of communication implemented at a terminal device according to some embodiments of the present disclosure;

Fig. 9 illustrates a flow chart of an example method of communication implemented at a network device according to some embodiments of the present disclosure; and

Fig. 10 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 is not limited to, user equipments (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 and the second network device. In one embodiment, a first information may be transmitted to the terminal device from the first network device and a 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.

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 (memories) 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.

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.

Fig. 1 illustrates a schematic diagram of a communication system 100 in which embodiments of the present disclosure can be implemented. The communication system 100, which is a part of a communication network, includes a terminal device 110-1, a terminal device 110-2, ..., a terminal device 110-N, which can be collectively referred to as “terminal device (s) 110. ” The number N may be any suitable integer number.

The communication system 100 further includes a network device 120. In some embodiments, the network device 120 may be a gNB. Alternatively, the network device 120 may be IAB. Although not shown, there may also be more than one network device 120 in the communication system 100.

In the communication system 100, the network device 120 and the terminal devices 110 may communicate data and control information to each other. The numbers of terminal devices 110 and network device 120 shown in Fig. 1 are given for the purpose of illustration without suggesting any limitations.

Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , including, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: code divided multiple address (CDMA) , frequency divided multiple address (FDMA) , time divided multiple address (TDMA) , frequency divided duplexer (FDD) , time divided duplexer (TDD) , multiple-input multiple-output (MIMO) , orthogonal frequency divided multiple access (OFDMA) and/or any other technologies currently known or to be developed in the future.

In 3GPP Rel-15/Rel-16, only single-cell PDSCH scheduling via a DCI is supported. However, in future releases (e.g., Rel-17, the work item dynamic spectrum sharing (DSS) ) , multi-cell PDSCH scheduling via a single DCI may be introduced to increase PDCCH scheduling capacity and reduce PDCCH blockage. As such, multi-cell PDSCH scheduling via a single DCI may be applied to many use cases (e.g., URLLC) , which has not yet been investigated. In other words, currently, there is no solution for multi-cell PDSCH scheduling via a single DCI.

Furthermore, for DCI format for multi-cell PDSCH scheduling, it is still unclear whether physical uplink control channel (PUCCH) related DCI field is shared/common or not by the two PDSCH transmissions on two cells to minimize the DCI size. For example, for multi-cell PDSCH scheduling via a single DCI, when the PUCCH related DCI field (e.g., PUCCH resource indicator (PRI) and PDSCH-to-HARQ feedback timing indicator (k1) ) are shared by two PDSCHs, there is still no solution on how to determine a resource for a HARQ-ACK codebook including HARQ-ACK (may also be referred to as HARQ feedback which may be ACK or NACK) for the multi-cell PDSCH transmissions scheduled by the single DCI.

However, when a terminal device 110 is provided with multiple services (e.g., eMBB and /or URLLC services mentioned above) , each of the services with a corresponding priority is provided with a PUCCH configuration in the PUCCH configuration list. Each of the PUCCH configurations in the PUCCH configuration list includes parameters such as PUCCH resource sets and K1 set.

For example, when there are two services (e.g., eMBB and URLLC) provided for the terminal device 110 and there are two PUCCH configurations defined in NR. For the terminal device 110, eMBB, which is a service provided with a lower priority (e.g., with priority index 0) , will be allocated with one of the PUCCH configuration in the PUCCH configuration lists. Meanwhile, URLLC, which is a service with a higher priority (e.g., with priority index 1) , will be allocated with the other one of the PUCCH configuration in the PUCCH configuration list.

Further, in conventional solutions, if a terminal device 110 is provided pdsch-HARQ-ACK-CodebookList, the terminal device 110 can be indicated by pdsch-HARQ-ACK-CodebookList to generate one or two HARQ-ACK codebooks. If the terminal device 110 is indicated to generate one HARQ-ACK codebook, the HARQ-ACK codebook is associated with HARQ-ACK information of priority index 0. If a terminal device 110 is provided pdsch-HARQ-ACK-CodebookList, the terminal device 110 (e.g., UE) multiplexes in a same HARQ-ACK codebook only HARQ-ACK information associated with a same priority index, for example, the first HARQ-ACK codebook is associated with HARQ-ACK information of priority index 0, the second HARQ-ACK codebook is associated with HARQ-ACK information of priority index 1.

If the terminal device 110 is indicated to generate two HARQ-ACK codebooks a first HARQ-ACK codebook is associated with a PUCCH of priority index 0 and a second HARQ-ACK codebook is associated with a PUCCH of priority index 1. All in all, one HARQ-ACK codebook (may also be referred to as feedback codebook herein) is associated with a PUCCH of one priority (e.g., priority index 0 or 1) .

As such, if a terminal device 110 (e.g., a UE) is configured with both eMBB and URLLC services, separate/dedicated PUCCH configuration (e.g., PUCCH resource sets and K1 set) will be configured. If two PDSCH transmissions, associated with different priorities, are scheduled by a single DCI, the PUCCH related fields in the DCI are common for the two PDSCH transmissions, and there is still no solution on how to determine a resource for a HARQ-ACK codebook including HARQ feedbacks for these two PDSCH transmissions. As a result, a solution on how to determine a resource for HARQ feedbacks for such the PDSCH transmissions mentioned above is needed.

In order to solve at least part of the above-mentioned problems, a solution for determining uplink resource for multi-cell PDSCH scheduling via a single DCI is provided. In this solution, a terminal device 110 receives, from a network device 120, DCI on a PDCCH. The DCI is used for scheduling a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device 120 for serving the terminating device. The plurality of PDSCH transmissions are associated with respective priorities. While the DCI may only have a common PUCCH related DCI field (e.g., PUCCH resource indicator (PRI) and PDSCH-to-HARQ feedback timing indicator (k1) ) for the two PDSCHs transmissions, the terminal device determines a resource for HARQ feedbacks of the plurality of the PDSCH transmissions, and the HARQ feedbacks are multiplexed on a feedback codebook. After that, the terminal device 110 transmits the HARQ feedbacks to the network device 120 on the resource.

As such, a solution for transmitting HARQ feedbacks of the plurality of PDSCH transmissions associated with different priorities on a PUCCH resource is provided. Further, with this solution, a single DCI in PDCCH is able to be used for scheduling two PDSCH transmissions associated with different priorities and the corresponding HARQ-ACK feedbacks are transmitted on a PUCCH resource, therefore the provided suitable interpretation for the common DCI field of PUCCH indication in the multi-cell scheduling DCI for PDSCH transmissions associated with different priorities achieves a balance between scheduling flexibility and smaller DCI size.

Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings 2-9. Reference is now made to Fig. 2, which shows a signaling flow 200 for determining resource for HARQ feedbacks according to some example embodiments of the present disclosure. In addition, Figs. 3A-3E illustrate diagrams of determination of resource for HRAQ feedbacks according to some embodiments of the present disclosure. For the purpose of discussion, the signaling flow 200A will be described with reference to Figs. 1 and 3. The signaling flow 200A involves the terminal device 110 and the network device 120 as illustrated in Fig. 1.

As shown in Fig. 2, a network device 120 transmits 205 to, a terminal device 110, DCI on a PDCCH. The DCI is used for scheduling a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device 120 for serving the terminating device, and the plurality of PDSCH transmissions are associated with respective priorities. For example, the respective priorities may be different priorities, for example, with

priority index

0 or 1.

Reference is now made to Fig. 3A, which shows a diagram of determination of resource for HARQ feedbacks according to some embodiments of the present disclosure. In some examples, as shown in Fig. 3A, the terminal device 110 may receive a DCI on a PDCCH, and the DCI may be used for scheduling two PDSCH transmissions on two cells. Each of the two PDSCH transmissions may be associated with a different priority (e.g., with priority index 0 or 1) . As shown, one of the two PDSCH transmissions (e.g., PDSCH transmission 1) may be on one cell (e.g., corresponding to a CC with CC index = 1 (i.e., CC #1) and associated with priority 0. The other one of the two PDSCH transmissions (e.g., PDSCH transmission 2) is on another cell (e.g., corresponding to a CC with CC index =2 (i.e., CC #2) and associated with priority 1.

In such examples, for example, PDSCH transmission 1 associated with priority 0 may be for eMBB service and PDSCH transmission 2 with priority 1 may be for URLLC service. It should be appreciated that Fig. 3A is shown only for the purpose of illustration and the scope of the present disclosure is not limited in this regard. For example, there may be other number of PDSCH transmissions (the details of which will be elaborated more in a latter part with reference to Fig. 3D) , priorities, CCs and the like.

Then, upon receiving 210 the DCI, the terminal device 110 determines 220 a resource for HARQ feedbacks of the plurality of PDSCH transmissions. The HARQ feedbacks are multiplexed on a feedback codebook. In some examples, continuing to refer to Fig. 3A, the terminal device 110 may determine a PUCCH resource for the HARQ feedbacks 1 and 2 of the

PDSCH transmissions

1 and 2. In such examples, the HARQ feedback 1 of the PDSCH transmission 1 and HARQ feedback 2 of the PDSCH transmission 2 may be multiplexed on a feedback codebook.

After that, accordingly, the terminal device transmits 230 the HARQ feedbacks to the network device 120 on the resource. For example, the terminal device 110 may transmit

HARQ feedbacks

1 and 2 to the network device 120 on the PUCCH resource. Accordingly, the network device 120 receives 235 the HARQ feedbacks from the terminal device 110.

In some embodiments, the resource for the HARQ feedbacks may be determined as follows. The terminal device 110 may determine, a PUCCH configuration associated with a determined priority for the feedback codebook. In such embodiments, the terminal device 110 may then determine, a set of offsets related to the PDSCH-to-HARQ feedback timing indicator and PUCCH resource sets from the PUCCH configuration. It should be noted that the set of offsets may also be referred to as K1 set or the dl-DataToUL-ACK set as defined in the PUCCH configuration information element and may be used interchangeably throughout the present disclosure.

In some embodiments, upon determining the K1 set and PUCCH resource set, the terminal device 110 may determine the resource for HARQ feedbacks based on the DCI indication from the set of offsets and the PUCCH resource sets.

In such embodiments, for example, the slot/sub-slot for PUCCH transmission for HARQ feedback bits (i.e., HARQ feedbacks) of the two PDSCH transmissions may be determined based on the value of PDSCH-to-HARQ feedback timing indicator in the DCI from the K1 set of the determined PUCCH configuration associated with high priority. The terminal device 110 may then determine, in the slot/sub-slot, a PUCCH resource set from PUCCH resource sets in the determined PUCCH configuration associated with high priority. Accordingly, after that, the terminal device 110 may determine the resource (i.e., PUCCH resource) from the PUCCH resource set based on the value of PRI in the DCI.

With the above solution, even the value of PDSCH-to-HARQ feedback timing indicator (k1) and PRI in the DCI are shared/common by two PDSCH transmission associated with different priorities, separate PUCCH configuration (e.g., K1 sets and PUCCH resource sets) of different priorities are configured, a terminal device 110 (e.g., UE) is able to determine the association between the value of PDSCH-to-HARQ feedback timing indicator (k1) and PRI and a PUCCH configuration based on a/one/single priority for a physical uplink control channel, PUCCH, thereby achieving a balance between scheduling flexibility and smaller DCI size.

In some embodiments, the priority for a physical uplink control channel, PUCCH may be determined by the terminal device 110 in a variety of ways. For example, the priority for the PUCCH (i.e., for the HARQ feedbacks) may be determined based on a predefined rule, a higher layer configuration or via dynamic indication, the detail of which will be illustrated in the following part.

In some embodiments, for example, the priority for the PUCCH may be predetermined. Reference is now made to Fig. 3B, which shows a diagram of determination of resource for HRAQ feedbacks according to some embodiments of the present disclosure.

For example, as shown in Fig. 3B, when the priority for the PUCCH (i.e., for the HARQ feedbacks) is predetermined as a high priority, based on the high priority for the PUCCH, the terminal device 110 may determine, for the feedback codebook, the 2 ^nd PUCCH configuration corresponding to the high priority as the PUCCH configuration. Accordingly, the terminal device 110 may determine the K1 set and the PUCCH resource set in the 2 ^nd PUCCH configuration, and then determine the resource (i.e., PUCCH resource) based on the DCI indication from the K1 set and the PUCCH resource set.

In such example, when determining the resource, specifically, the terminal device 110 may determine the slot/sub-slot for PUCCH transmission for HARQ-ACK bits of the two PDSCHs based on the value of PDSCH-to-HARQ feedback timing indicator in the DCI from the K1 set of the determined PUCCH configuration associated with high priority (i.e., the K1 set in the 2 ^nd PUCCH configuration) . The terminal device 110 may then determine a PUCCH resource set from the PUCCH resource sets of high priority (i.e., PUCCH resource set in the 2 ^nd PUCCH configuration) in the slot/sub-slot. And the terminal device 110 may determine the resource (i.e., PUCCH resource) from the PUCCH resource set based on the value of PRI in the DCI.

It should be appreciated that, the priority for the PUCCH may also be predetermined to be a low priority and the scope of the present disclosure is not limited in this regard.

With this solution, considering high priority for PUCCH is predetermined, performance of the URLLC HARQ feedback transmission, which has high requirements for latency and reliability, can be guaranteed.

In some other embodiments, the terminal device 110 may receive, from the network device 120, information related to the priority for the PUCCH. In such embodiments, for example, the terminal device 110 may receive the information related to the priority via a radio resource control (RRC) message.

Accordingly, for a terminal device 110 with multiple services (e.g., eMBB, uRLLC and the like) and separate PUCCH configuration (e.g., K1 set and PUCCH resource sets) for HARQ feedback of different priorities, if two PDSCH transmission associated with different priorities on two cells are scheduled by a single DCI, the terminal device may determine the slot/sub-slot for PUCCH transmission for HARQ feedback bits of the two PDSCH transmissions based on the value of PDSCH-to-HARQ feedback timing indicator in the DCI from the K1 set of the priority configured by RRC (e.g., high priority or low priority) . In such example, the terminal device 110 may determine, in the slot/sub-slot, a PUCCH resource set from PUCCH resource sets of the priority configured by RRC. The terminal device may finally determine the resource from the PUCCH resource set based on the value of PRI in the DCI.

As such, the solution is more flexible since the priority for PUCCH can be configured by the network device 120, for example, via a RRC message. Accordingly, when the network device 120 knows PDSCHs of URLLC service is less transmitted compared with eMBB service, then the network device 120 can select a PUCCH resource of low or high priority based on the number of low priority HARQ-ACK bits and the number of high priority HARQ-ACK bits, a PUCCH configuration of low priority may be configured, such that the uplink resource (i.e. PUCCH resource) may be utilized in a more efficient way.

Alternatively, for example, the priority for PUCCH may be reset via RRC reset message. Accordingly, the priority for PUCCH may be configured more flexibly.

It should also be appreciated that the information related to the priority may also be received via other method rather than via RCC. For example, the information related to the priority may also be received in the DCI or MAC CE, for example, in a new field in the DCI or reuse an existing field in the DCI. The scope of present disclosure is not limited in this regard.

In some embodiments, the priority may be determined based on a priority associated with one of the plurality of PDSCH transmissions, where transmitting the one of the plurality of PDSCH transmissions precedes than other PDSCH transmissions of the plurality of PDSCH transmission in time domain. That is, a PDSCH transmission which is an earlier scheduled PDSCH transmission in time domain.

In such embodiments, specifically, for example, for a terminal device 110 with multiple services and separate PUCCH configuration (e.g., K1 set and PUCCH resource sets) for HARQ feedback of different priorities, if two PDSCH transmissions associated with different priorities on two cells are scheduled by a single DCI, the terminal device 110 may determine, the slot/sub-slot for PUCCH transmission for HARQ feedback bits of the two PDSCH transmissions based on the value of PDSCH-to-HARQ feedback timing indicator in the DCI from the K1 set of the priority implicitly indicated by the DCI, e.g., the priority (e.g., indicated by a priority index) of a PDSCH which is an earlier scheduled PDSCH transmission in time domain. The terminal device 110 may then determine a PUCCH resource set from PUCCH resource sets of the priority implicitly indicated by the DCI e.g., the priority (e.g., indicated by a priority index) of a PDSCH which is an earlier scheduled PDSCH transmission in time domain. Finally, the terminal device 110 may determine a PUCCH resource from the PUCCH resource set based on the value of PRI in the DCI.

In some embodiments, the priority for PUCCH may be determined based on a priority of a part of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined CC index related to one of the plurality of cells. That is, the priority for PUCCH may be the priority of the PDSCH transmission scheduled on a CC with a predetermined CC index.

In some examples, the predetermined CC index may be a lower CC index or a higher CC index. For example, the predetermined CC index may be 1 (i.e., the lower CC index) or 2 (i.e., the higher CC index) .

In such embodiments, for example, for a terminal device 110 with multiple services and separate PUCCH configuration (e.g., K1 set and PUCCH resource sets) for HARQ feedback of different priorities, if two PDSCH transmission associated with different priorities on two cells are scheduled by a single DCI, the terminal device 110 may determine the slot/sub-slot for PUCCH transmission for HARQ feedback bits of the two PDSCH transmissions based on the value of PDSCH-to-HARQ feedback timing indicator in the DCI from the K1 set of the priority implicitly indicated by the DCI, e.g., the priority (e.g., indicated by a priority index) of a PDSCH transmission scheduled on a cell having a predetermined CC index (e.g., a lower CC or a higher CC index) .

In some embodiments, the terminal device 110 may then determine a PUCCH resource set from PUCCH resource sets of the priority implicitly indicated by the DCI e.g., the priority (e.g., indicated by a priority index) of a PDSCH scheduled on a cells having a predetermined CC index (e.g., a lower CC or a higher CC index) .

In some other embodiments, the priority for PUCCH may be determined based on a priority of a PDSCH transmission on the scheduling cell, which is the cell for a PDCCH transmission for scheduling the plurality of PDSCH transmissions. Reference is now made to Fig. 3C, which shows a diagram of determination of resource for HRAQ feedbacks according to some embodiments of the present disclosure.

As shown in the table of Fig. 3C, the priority indicator in the DCI may occupy two bits and are independent for separate PDSCH transmissions (i.e., PDSCH transmissions 1 and 2) on two cells (i.e., CC #1 and CC #2) . In such case, the priority index of the PDSCH on the scheduling CC is 1, indicating high priority. As a result, 2 ^nd PUCCH configuration associated with the high priority may be determined as shown in Fig. 3C. Accordingly, K1 set and PUCCH resource set may be determined from the 2 ^nd PUCCH configuration, and then the resource (i.e., PUCCH resource) may be determined based on the DCI from the K1 set and the PUCCH resource set. It should be noted that, the detailed steps in such example for determining the PUCCH resource is similar to those mentioned above, thus will not be repeated here.

In the above part, methods of determining the priority for a PUCCH for HARQ-ACK bits of two PDSCHs on two cells associated with different priorities have been introduced. With the above solution, for multi-cell PDSCH scheduling via a single DCI, the field PRI and PDSCH-to-HARQ feedback timing indicator (k1) are shared by the two PDSCHs, or a terminal device 110 (e.g., UE) with multiple services, e.g., eMBB and URLLC, separate configuration of K1 set and PUCCH resource sets are configured for HARQ-ACK of different priorities, while if two PDSCH transmission associated with different priorities on two cells are scheduled by a single DCI, it is clear for the terminal device the one value of PDSCH-to-HARQ feedback timing indicator in the DCI is associated with K1 set of the determined PUCCH configuration with low priority or K1 set of the determined PUCCH configuration associated with high priority, and it is also clear the one value of PRI is associated with PUCCH resource sets of low priority or PUCCH resource sets of high priority.

That is, for example, the association between one value of PDSCH-to-HARQ feedback timing indicator/PRI in the DCI shared by two PDSCHs associated with different priorities and separate K1 sets and PUCCH resource sets of different priorities can be determined by a predefined rule, a higher layer configuration or a dynamic indication (via DCI) as introduced in the above part.

In the following part, other solutions according to the embodiments of the present disclosure will be introduced. In some embodiments, the priority indicator field may be shared by the two PDSCH transmissions on two cells. It means only one common priority indicator field in the scheduling DCI. As such, the terminal device 110 does not expect the two PDSCH transmissions on two cells scheduled by a single DCI to be associated with different priorities. This solution is simple but limits the flexibility.

In some embodiments, the terminal device 110 may receive, from the network device 120, an indication indicating that whether a priority indicator in the DCI is common or dedicated for the plurality of PDSCH transmissions. In such embodiments, for example, the indication information may be carried by RRC signaling. As such, in response to the indication indicating that the priority indicator is common, the terminal device 110 may determine the PUCCH configuration associated with the priority index indicated by the priority indicator field for the feedback codebook.

In such embodiments, the priority indicator may be 2 bits if a higher layer parameter dedicatedpriorityIndicatorDCI-1-1 is configured, for example, the 1 MSB bit may be for PDSCH on CC with lower CC index, the 1 LSB bit may be for PDSCH on CC with higher CC index. Otherwise 1 or 0 bit as defined in Clause 9 in [TS 38.213] and clause 7 in [TS 38.212] .

In some embodiments, if higher layer parameter dedicatedpriorityIndicatorDCI-1-1 is not configured, two PDSCH transmissions on two cells scheduled by a single DCI associated with different priorities may be disabled. In some other embodiments, if higher layer parameter dedicatedpriorityIndicatorDCI-1-1 is configured, two PDSCH transmissions on two cells scheduled by a single DCI associated with different priorities may be enabled. In such embodiments, for example, the terminal device 110 may receive, at a terminal device 110 from a network device 120, DCI on a PDCCH, the DCI is used for scheduling a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device 120 for serving the terminating device, and the plurality of PDSCH transmissions are associated with respective priorities. Then the terminal device 110 may determine a resource for HARQ feedbacks of the plurality of PDSCH transmissions, where the HARQ feedbacks are multiplexed on a feedback codebook. After that, the terminal device 110 may transmit the HARQ feedbacks to the network device 120 on the resource. In such example, the PUCCH configuration for the feedback coodbook may be determined using the method introduced in a previous part of the present disclosure and the details will not be repeated here.

Reference is now made to Fig. 3D, which shows a diagram of determination of resource for HRAQ feedbacks according to some embodiments of the present disclosure. As mentioned above, there may be other number of PDSCH transmissions. In some examples, as shown in Fig. 3D, there may be three PDSCH transmissions (

PDSCH transmission

1, 2 and 3) .

In such examples, as shown in Fig. 3D, the terminal device 110 may receive a DCI on a PDCCH, and the DCI may be used for scheduling three PDSCH transmissions on three cells. Each of the three PDSCH transmissions may be associated with a different priority (e.g., with priority index 0 or 1) . As shown, the first one of the three PDSCH transmissions (e.g., PDSCH transmission 1) may be on one cell (e.g., corresponding to a CC with CC index = 1 (i.e., CC #1) and associated with priority 0. The second one of the three PDSCH transmissions (e.g., PDSCH transmission 2) is on a 2 ^nd cell (e.g., corresponding to a CC with CC index =2 (i.e., CC #2) and associated with priority 1. The third one of the three PDSCH transmissions (e.g., PDSCH transmission 3) is on a 3 ^rd cell (e.g., corresponding to a CC with CC index =3 (i.e., CC #3) and associated with priority 0.

Reference is now made to Fig. 3E, which shows a signaling flow 200 for determining resource for HARQ feedbacks according to some example embodiments of the present disclosure.

In some embodiments, as shown in Fig. 3E, there may be a plurality of (e.g., 2 as shown) PDSCH transmission within a plurality of slots/mini-slots on a single cell scheduled by a single DCI. For such case, as mentioned above, a terminal device 110 may receive, from a network device 120, DCI on a PDCCH. The DCI may be used for scheduling the two PDSCH transmissions on the single cell (having a corresponding CC index, e.g., CC #1) provided by the network device 120 for serving the terminating device. The two PDSCH transmissions are associated with respective priorities. Then the terminal device 110 may determine resource for HARQ feedbacks of the two of PDSCH transmissions, and the HARQ feedbacks are multiplexed on a feedback codebook. After that, the terminal device 110 may transmit the HARQ feedbacks to the network device 120 on the resource.

It should be appreciated that ways on determining the priority for a PUCCH may be similar to those mentioned above, thus the details will not be repeated here. For example, the priority for a PUCCH may be determined based on a predefined rule (e.g., predetermined) . In another example, the priority for a PUCCH may also be configured per higher layer configuration, e.g., via a RRC message. Alternatively, the priority for a PUCCH may also be determined with a dynamic indication, e.g., via a DCI field in DCI and the like.

In some embodiments, for multi-cell PDSCH scheduling via a single DCI, the terminal device 110 may receive an indication indicating that whether a PUCCH related DCI fields is common for the plurality of PDSCH transmissions.

In such embodiments, for example, it may be configured for per group DCI fields, e.g., the higher layer parameter DciFieldsforPucch= dedicated, separate indication for TPC command for scheduled PUCCH, Downlink assignment index, PDSCH-to-HARQ_feedback timing indicator and PRI in the DCI for two PDSCHs on two cells. Alternatively, it may be configured for per group DCI fields the higher layer parameter DciFieldsforPucch= common, common indication for TPC command for scheduled PUCCH, Downlink assignment index, PDSCH-to-HARQ_feedback timing indicator and PRI in the DCI for two PDSCH transmissions on two cells.

In some other examples, it may be cconfigured for any of a DCI field. For example, if the higher layer parameter dedicatedPucchResourceIndicator is configured, separate indication for the field PRI in the DCI for two PDSCH transmissions on two cells, otherwise, the field PRI in the DCI is common and shared by the two PDSCH transmissions.

When the dedicatedPucchResourceIndicator is configured, for the PRI field in DCI there will be 3 most significant bits (MSB bits) for the 1 ^st PDSCH transmission, and there will be 3 least significant bits (LSB bits) for the 2 ^nd PDSCH transmission. When the dedicatedPucchResourceIndicator is not configured, for the PRI field in DCI, there will be 3 bits shared by the two PDSCH transmissions.

Reference is now made to Fig. 4, which shows a signaling flow 400 for determining resource for HARQ feedbacks according to some example embodiments of the present disclosure. For the purpose of discussion, the signaling flow 400A will be described with reference to Fig. 1. The signaling flow 400 involves the terminal device 110 and the network device 120 as illustrated in Fig. 1.

As shown in Fig. 4, the network device 120 transmits 405, to a terminal device 110, a plurality of DCI on a plurality of PDCCH. Each of the plurality of DCI are used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device 120 for serving the terminating device. The plurality of PDSCH transmissions is associated with respective priorities.

Accordingly, upon receiving 410 the plurality of DCI, the terminal device 110 then multiplexes 420 HARQ feedbacks of the plurality of PDSCH transmissions on a feedback codebook, where the HARQ feedbacks of the plurality of PDSCH transmissions are indicated to be transmitted in a same slot or sub-slot by the respective DCIs. After that, the terminal device 110 determines 430 a resource for the feedback codebook and transmits 440 the HARQ feedbacks to the network device 120 on the resource. Accordingly the network device 120 receives 445 the HRAQ feedbacks from the terminal device 110.

With this solution, complexity of terminal device 110 processing is able to be reduced since the judgment of the collision between two PUCCHs for HARQ-ACK with different priority index is skipped and multiplexing is done directly.

Reference will be made to Fig. 5. Fig. 5 illustrates a diagram of determination of resource for HRAQ feedbacks according to some embodiments of the present disclosure. As shown in Fig. 5, the network device 120 may transmit, to a terminal device 110, two DCI on two PDCCH. Each of the two of DCIs may be used for scheduling a corresponding one of two PDSCH transmissions on a single cell provided by the network device 120 for serving the terminating device. The two PDSCH transmissions are associated with respective priorities (e.g., priority 0 or 1) . Upon receiving the two DCI, the terminal device 110 may then multiplex HARQ feedbacks of the two PDSCH transmissions on a feedback codebook. The HARQ feedbacks of the plurality of PDSCH transmissions are indicated to be transmitted in a same slot or sub-slot by the respective DCIs. After that, the terminal device 110 may determine a resource for the feedback codebook and transmit the HARQ feedbacks to the network device 120 on the resource.

It should be appreciated, though not shown, each of the two of DCIs may be used for scheduling a corresponding one of two PDSCH transmissions on a plurality of cells provided by the network device 120 for serving the terminating device. The scope of the present disclosure is not limited in this regard.

In some embodiments, the terminal device 110 may determine, a set of offsets (i.e., K1 sets) related to the PDSCH-to-HARQ feedback timing indicator and PUCCH resource sets from a PUCCH configuration associated with a priority. The terminal device 110 may then determine the resource based on the DCI from the set of offsets and the PUCCH resource sets.

In some embodiments, the priority may be predetermined, such that the PUCCH resource may be determined based on this predetermined priority. For example, the priority may be predetermined to be a high priority (e.g., corresponding to URLLC) . As such, the PUCCH resource (e.g., K1 set and PUCCH resource sets) may be determined from a PUCCH configuration for this high priority.

In some other embodiments, the terminal device 110 may receive from the network device 120, information related to the priority, such that the PUCCH configuration may be determined based on the information related to the priority. For example, the information may be transmitted in a RRC message.

Alternatively, the priority for the PUCCH resource may be determined based on the priority indication from a predetermined one of the plurality of downlink control channels. For example, the priority indication of an earlier PDCCH reception or a later PDCCH reception.

In some other embodiments, the priority for the PUCCH resource may be determined based on a priority indication by one of the plurality of downlink control channels, one of the plurality of downlink control channels is for scheduling one of the plurality of PDSCH transmissions on one of the plurality of cells having a predetermined CC index. For example, the downlink control channel (i.e., PDCCH) of PDSCH on the CC with a lower index (e.g., CC#1) or a higher index (e.g., CC#2) .

With this solution, complexity of terminal device 110 processing is able to be reduced since the judgment of the collision between two PUCCHs for HARQ-ACK with different priority index is skipped and multiplexing is done directly, so the terminal device 110 (e.g., UE) complexity is reduced.

Fig. 6 illustrates a flowchart of an example method 600 according to some embodiments of the present disclosure. The method 600 can be implemented at a terminal device 110 as shown in Fig. 1. It is to be understood that the method 600 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. For the purpose of discussion, the method 600 will be described from the perspective of the terminal device 110 with reference to Fig. 1.

At block 610, the terminal device receives from a network device, downlink control information, DCI, on a physical downlink control channel, PDCCH. The DCI is used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device. The plurality of PDSCH transmissions is associated with respective priorities. At block 620, the terminal device then determines a resource for hybrid automatic repeat request, HARQ, feedbacks of the plurality of PDSCH transmissions, the HARQ feedbacks being multiplexed on a feedback codebook. At block 630, the terminal device transmits the HARQ feedbacks to the network device on the resource.

In some embodiments, determining the resource comprises: determining, a set of offsets related to the PDSCH-to-HARQ feedback timing indicator and PUCCH resource sets from a PUCCH configuration associated with a priority; and determining the resource based on the DCI from the set of offsets and the PUCCH resource sets

In some embodiments, the priority is predetermined.

In some embodiments, the method 600 may further comprise receiving, from the network device, information related to the priority; and determining the priority based on the information.

In some embodiments, the information is transmitted in a radio resource control, RRC, message.

In some embodiments, the priority is determined based on at least one of the following: information related to the priority in the DCI, a priority associated with one of the plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions preceding than other PDSCH transmissions of the plurality of PDSCH transmission in time domain; a priority of a part of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined component carrier index related to one of the plurality of cells, and a priority of a PDSCH transmission associated with a cell for a PDCCH transmission for scheduling the plurality of PDSCH transmissions.

In some embodiments, the method 600 may further comprise receiving an indication indicating that at least one of PUCCH related DCI fields is common for the plurality of PDSCH transmissions.

In some embodiments, the PUCCH related DCI field comprises at least one of the following: a transmission power control, TPC, command for the resource, a PRI, a PDSCH-to-HARQ feedback timing indicator, and a downlink assignment index, DAI.

In some embodiments, the method 600 may further comprise receiving, from the network device, an indication indicating that whether a priority indicator in the DCI is common or dedicated for the plurality of PDSCH transmissions; wherein the indication is configured by a radio resource control message.

Fig. 7 illustrates a flowchart of an example method 700 according to some embodiments of the present disclosure. The method 700 can be implemented at the network device 120 as shown in Fig. 1. It is to be understood that the method 700 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. For the purpose of discussion, the method 700 will be described from the perspective of the network device 120 with reference to Fig. 1.

At block 710, the network device transmits, to a terminal device, downlink control information, DCI, on a physical downlink control channel, PDCCH. The DCI is used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device. The plurality of PDSCH transmissions is associated with respective priorities. At block 720, the network device receives, hybrid automatic repeat request, HARQ feedbacks from the terminal device on a resource for HARQ feedbacks of the plurality of PDSCH transmission, the HARQ feedbacks being multiplexed on a feedback codebook.

In some embodiments, the priority is predetermined.

In some embodiments, the method 700 further comprises transmitting, to the terminal device, information related to the priority.

In some embodiments, the method 700 further comprises transmitting an indication indicating that at least one of PUCCH related DCI fields is common for the plurality of PDSCH transmissions.

In some embodiments, the PUCCH related DCI field comprises at least one of the following: a transmission power control, TPC, command for the resource, a PUCCH resource indicator, PRI, a PDSCH-to-HARQ feedback timing indicator, and a downlink assignment index, DAI.

Fig. 8 illustrates a flowchart of an example method 800 according to some embodiments of the present disclosure. The method 800 can be implemented at the terminal device 110 as shown in Fig. 1. It is to be understood that the method 800 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. For the purpose of discussion, the method 800 will be described from the perspective of the terminal device 110 with reference to Fig. 1.

At block 810, a terminal device receives, from a network device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities. At block 820, the terminal device multiplexes, hybrid automatic repeat request, HARQ feedbacks of the plurality of PDSCH transmissions on a feedback codebook. The HARQ feedbacks of the plurality of PDSCH transmissions are indicated to be transmitted in a same slot or sub-slot by the respective DCIs. At block 830, the terminal device then determines a resource for the feedback codebook. At block 840, the terminal device transmits the HARQ feedbacks to the network device on the resource.

In some embodiments, determining the resource comprises: determining, a set of offsets related to the PDSCH-to-HARQ feedback timing indicator and PUCCH resource sets from a PUCCH configuration associated with a priority; and determining the resource based on the DCI from the set of offsets and the PUCCH resource sets.

In some embodiments, the priority is predetermined.

In some embodiments, the method 800 may further comprise receiving, from the network device, information related to the priority; and determining the priority based on the information.

In some embodiments, the priority is determined based on at least one of the following: information related to the priority in the DCI, a priority indication by a predetermined one of the plurality of downlink control channels, and a priority indication by one of the plurality of downlink control channels, one of the plurality of downlink control channels is for scheduling one of the plurality of PDSCH transmissions on one of the plurality of cells having a predetermined component carrier index.

Fig. 9 illustrates a flowchart of an example method 900 according to some embodiments of the present disclosure. The method 900 can be implemented at the network device 120 as shown in Fig. 1. It is to be understood that the method 900 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. For the purpose of discussion, the method 900 will be described from the perspective of the network device 120 with reference to Fig. 1.

At block 910, the network device transmits, to a terminal device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities. At block 920, the network device, receive hybrid automatic repeat request, HARQ, feedbacks from the terminal device on a resource for the feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions are multiplexed on a feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being indicated to be transmitted in a same slot or sub-slot by the respective DCIs.

In some embodiments, the priority is predetermined.

In some embodiments, the method 900 further comprises transmitting, to the terminal device, information related to the priority.

In some embodiments, the priority is determined based on at least one of the following: information related to the priority in the DCI, a priority indication by a predetermined one of the plurality of downlink control channels, and a priority indication by one of the plurality of downlink control channels, one of the plurality of downlink control channels being for scheduling one of the plurality of PDSCH transmissions on one of the plurality of cells having a predetermined component carrier index.

In some embodiments, a terminal device (for example, the terminal device 110) comprising circuitry configured to: receive from a network device, downlink control information, DCI, on a physical downlink control channel, PDCCH, the DCI is used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities; determine a resource for hybrid automatic repeat request, HARQ, feedbacks of the plurality of PDSCH transmissions, the HARQ feedbacks being multiplexed on a feedback codebook; and transmit the HARQ feedbacks to the network device on the resource.

In some embodiments, determining the resource comprises: determining a PUCCH configuration associated with a determined priority for the feedback codebook; determining, a set of offsets related to the PDSCH-to-HARQ feedback timing indicator and PUCCH resource sets from the PUCCH configuration; and determining the resource based on the DCI from the set of offsets and the PUCCH resource sets.

In some embodiments, the priority is predetermined.

In some embodiments, the circuitry is further configured to: receive, from the network device, information related to the priority; and determine the priority based on the information.

In some embodiments, the priority is determined based on at least one of the following: information related to the priority in the DCI, a priority associated with one of the plurality of PDSCH transmissions, where transmitting the one of the plurality of PDSCH transmissions preceding than other PDSCH transmissions of the plurality of PDSCH transmission in time domain, a priority of a part of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined component carrier index related to one of the plurality of cells, and a priority of a PDSCH transmission associated with a cell for a PDCCH transmission for scheduling of the plurality of PDSCH transmissions.

In some embodiments, the circuitry is further configured to: receive an indication indicating that at least one of PUCCH related DCI fields is common for the plurality of PDSCH transmissions.

In some embodiments, the circuitry is further configured to: receive, from the network device, an indication indicating that whether a priority indicator in the DCI is common or dedicated for the plurality of PDSCH transmissions, where the indication is configured by a radio resource control message.

In some embodiments, a network device (for example, the network device 120) comprising circuitry configured to: transmit, to a terminal device, downlink control information, DCI, on a physical downlink control channel, PDCCH, the DCI being used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities; and receive, hybrid automatic repeat request, HARQ feedbacks from the terminal device on a resource for HARQ feedbacks of the plurality of PDSCH transmission, the HARQ feedbacks being multiplexed on a feedback codebook.

In some embodiments, the priority is predetermined.

In some embodiments, the circuitry is further configured to transmit, to the terminal device, information related to the priority.

In some embodiments, the priority is determined based on at least one of the following: information related to the priority in the DCI, a priority associated with one of the plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions preceding than other PDSCH transmissions of the plurality of PDSCH transmission in time domain, a priority of a part of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined component carrier index related to one of the plurality of cells, and a priority of a PDSCH transmission associated with a cell for a PDCCH transmission for scheduling the plurality of PDSCH transmissions.

In some embodiments, the circuitry is further configured to transmit an indication indicating that at least one of PUCCH related DCI fields is common for the plurality of PDSCH transmissions.

In some embodiments, a terminal device (for example, the terminal device 110) comprising circuitry configured to: receive, from a network device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities; multiplex, hybrid automatic repeat request, HARQ feedbacks of the plurality of PDSCH transmissions on a feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being indicated to be transmitted in a same slot or sub-slot by the respective DCIs; determine a resource for the feedback codebook; and transmit the HARQ feedbacks to the network device on the resource.

In some embodiments, the priority is predetermined.

In some embodiments, a network device (for example, the network device 120) comprising circuitry configured to: transmit, to a terminal device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions are associated with respective priorities; and receive hybrid automatic repeat request, HARQ, feedbacks from the terminal device on a resource for the feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being multiplexed on a feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being indicated to be transmitted in a same slot or sub-slot by the respective DCIs.

In some embodiments, the priority is predetermined.

In some embodiments, the circuitry is further configured to: transmit, to the terminal device, information related to the priority.

Fig. 10 is a simplified block diagram of a device 1000 that is suitable for implementing embodiments of the present disclosure. The device 1000 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 1000 can be implemented at or as at least a part of the terminal device 110 or the network device 120.

As shown, the device 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX/RX 1040. The memory 1010 stores at least a part of a program 1030. The TX/RX 1040 is for bidirectional communications. The TX/RX 1040 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 interface for bidirectional communications between eNBs, S1 interface for communication between a Mobility Management Entity (MME) /Serving Gateway (S-GW) and the eNB, Un interface for communication between the eNB and a relay node (RN) , or Uu interface for communication between the eNB and a terminal device.

The program 1030 is assumed to include program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate according to the embodiments of the present disclosure, as discussed herein with reference to Figs. 2-9. The embodiments herein may be implemented by computer software executable by the processor 1010 of the device 1000, or by hardware, or by a combination of software and hardware. The processor 1010 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1010 and memory 1010 may form processing means 1050 adapted to implement various embodiments of the present disclosure.

The memory 1010 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 1010 is shown in the device 1000, there may be several physically distinct memory modules in the device 1000. The processor 1010 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 1000 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.

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. 2-9. 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 should 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 communication method comprising:

receiving, at a terminal device from a network device, downlink control information, DCI, on a physical downlink control channel, PDCCH, the DCI being used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions being associated with respective priorities;

determining a resource for hybrid automatic repeat request, HARQ, feedbacks of the plurality of PDSCH transmissions, the HARQ feedbacks being multiplexed on a feedback codebook; and

transmitting the HARQ feedbacks to the network device on the resource.
The method of claim 1, wherein determining the resource comprises:

determining, a set of offsets related to the PDSCH-to-HARQ feedback timing indicator and PUCCH resource sets from a PUCCH configuration associated with a priority; and

determining the resource based on the DCI from the set of offsets and the PUCCH resource sets.
The method of claim 2, wherein the priority is predetermined.
The method of claim 2, further comprising:

receiving, from the network device, information related to the priority.
The method of claim 4, wherein the information is transmitted in a radio resource control, RRC, message.
The method of claim 2, wherein the priority is determined based on at least one of the following:

information related to the priority in the DCI,

a priority associated with one of the plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions preceding than other PDSCH transmissions of the plurality of PDSCH transmission in time domain,

a priority of a part of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined component carrier index related to one of the plurality of cells, and

a priority of a PDSCH transmission associated with a cell for a PDCCH transmission for scheduling the plurality of PDSCH transmissions.
The method of claim 1, further comprising:

receiving an indication indicating that at least one of PUCCH related DCI fields is common for the plurality of PDSCH transmissions.
The method of claim 7, wherein the PUCCH related DCI field comprises at least one of the following:

a transmission power control, TPC, command for the resource,

a PUCCH resource indicator, PRI,

a PDSCH-to-HARQ feedback timing indicator, and

a downlink assignment index, DAI.
The method of claim 1, further comprising:

receiving, from the network device, an indication indicating that whether a priority indicator in the DCI is common or dedicated for the plurality of PDSCH transmissions wherein the indication is configured by a radio resource control message.
A communication method comprising:

transmitting, at a network device to a terminal device, downlink control information, DCI, on a physical downlink control channel, PDCCH, the DCI being used for scheduling a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions being associated with respective priorities; and

receiving, hybrid automatic repeat request, HARQ feedbacks from the terminal device on a resource for HARQ feedbacks of the plurality of PDSCH transmission, the HARQ feedbacks being multiplexed on a feedback codebook.
The method of claim 10, wherein the priority is predetermined.
The method of claim 10, further comprising:

transmitting, to the terminal device, information related to the priority.
The method of claim 12, wherein the information is transmitted in a radio resource control, RRC, message.
The method of claim 10, wherein the priority is determined based on at least one of the following:

information related to the priority in the DCI,

a priority associated with one of the plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions preceding than other PDSCH transmissions of the plurality of PDSCH transmission in time domain,

a priority of a part of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined component carrier index related to one of the plurality of cells, and

a priority of a PDSCH transmission associated with a cell for a PDCCH transmission for scheduling the plurality of PDSCH transmissions.
The method of claim 10, further comprising:

transmitting an indication indicating that at least one of PUCCH related DCI fields is common for the plurality of PDSCH transmissions.
The method of claim 15, wherein the PUCCH related DCI field comprises at least one of the following:

a transmission power control, TPC, command for the resource,

a PUCCH resource indicator, PRI,

a PDSCH-to-HARQ feedback timing indicator, and

a downlink assignment index, DAI.
A communication method comprising:

receiving, at a terminal device from a network device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions being associated with respective priorities;

multiplexing, hybrid automatic repeat request, HARQ feedbacks of the plurality of PDSCH transmissions on a feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being indicated to be transmitted in a same slot or sub-slot by the respective DCIs;

determining a resource for the feedback codebook; and

transmitting the HARQ feedbacks to the network device on the resource.
The method of claim 17, wherein determining the resource comprises:

determining, a set of offsets related to the PDSCH-to-HARQ feedback timing indicator and PUCCH resource sets from a PUCCH configuration associated with a priority; and

determining the resource based on the DCI from the set of offsets and the PUCCH resource sets.
The method of claim 18, wherein the priority is predetermined.
The method of claim 18, further comprising:

receiving, from the network device, information related to the priority.
The method of claim 20, wherein the information is transmitted in a radio resource control, RRC, message.
The method of claim 18, wherein the priority is determined based on at least one of the following:

information related to the priority in the DCI,

a priority indication by a predetermined one of the plurality of downlink control channels, and

a priority indication by one of the plurality of downlink control channels, one of the plurality of downlink control channels being for scheduling one of the plurality of PDSCH transmissions on one of the plurality of cells having a predetermined component carrier index.
A communication method comprising:

transmitting, at a network device to a terminal device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCH, each of the plurality of DCI being used for scheduling a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device for serving the terminating device, the plurality of PDSCH transmissions being associated with respective priorities; and

receiving hybrid automatic repeat request, HARQ, feedbacks from the terminal device on a resource for the feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being multiplexed on a feedback codebook, the HARQ feedbacks of the plurality of PDSCH transmissions being indicated to be transmitted in a same slot or sub-slot by the respective DCIs.
The method of claim 23, wherein the priority is predetermined.
The method of claim 23, further comprising:

transmitting, to the terminal device, information related to the priority.
The method of claim 25, wherein the information is transmitted in a radio resource control, RRC, message.
The method of claim 23, wherein the priority is determined based on at least one of the following:

information related to the priority in the DCI,

a priority indication by a predetermined one of the plurality of downlink control channels, and

a priority indication by one of the plurality of downlink control channels, one of the plurality of downlink control channels being for scheduling one of the plurality of PDSCH transmissions on one of the plurality of cells having a predetermined component carrier index.
A terminal device, comprising:

a processing unit; and

a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the device to perform the method according to any of claims 1-9 or any of claims 17-22.
A computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to any of claims 10-16 or any of claims 23-27.