CN117413602A

CN117413602A - Communication method, terminal device, network device, and computer-readable medium

Info

Publication number: CN117413602A
Application number: CN202180098779.3A
Authority: CN
Inventors: 王刚
Original assignee: NEC Corp
Current assignee: NEC Corp
Priority date: 2021-04-16
Filing date: 2021-04-16
Publication date: 2024-01-16
Also published as: WO2022217606A1

Abstract

Embodiments of the present disclosure relate to a method, a terminal device, a network device, and a computer-readable medium for communication. In the method, a terminal device receives downlink control information, DCI, on a physical downlink control channel, PDCCH, from a network device. The DCI is used to schedule multiple physical downlink shared channel PDSCH transmissions on a single cell or multiple cells provided by a network device for serving a terminal device. Multiple PDSCH transmissions are associated with respective priorities. Then, the terminal device determines resources for hybrid automatic repeat request, HARQ, feedback for the multiple PDSCH transmissions, the HARQ feedback being multiplexed on a feedback codebook. The terminal device then transmits HARQ feedback to the network device over the resource. With this solution, a solution is provided for transmitting HARQ feedback for multiple PDSCH transmissions associated with different priorities. Furthermore, with this solution, a single DCI in the PDCCH can be used to schedule two PDSCH transmissions associated with different priorities and corresponding HARQ-ACK feedback is transmitted on PUCCH resources, thus a balance between scheduling flexibility and smaller DCI size is achieved for the appropriate interpretation provided for the common DCI field in the multi-cell scheduling DCI for PDSCH transmissions associated with different priorities.

Description

Communication method, terminal device, network device, and computer-readable medium

Technical Field

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

Background

The fifth generation 5G network provides three services that can change the current industry and create new industries, namely enhanced mobile broadband (emmbb), ultra-reliable low latency communication (URLLC), and machine type communication (mctc). ebb provides faster speeds for use cases requiring high data rates, such as large-scale video streaming and virtual reality. Ultra-reliable low latency communications (URLLC) have low latency for mission critical services. mctc provides internet access for sensing, metering and monitoring devices.

The third generation partnership project (3 GPP) has specified URLLC as a key feature of release 15 g New Radio (NR) other than emmbb. According to 3gpp 5g-NR, URLLC is a group of features that provide low latency and ultra high reliability for mission critical applications such as industrial internet, smart grid, tele-surgery and intelligent transportation systems.

Disclosure of Invention

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

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

In a second aspect, a communication method is provided. The method comprises the following steps: transmitting, at the network device, downlink control information, DCI, on a physical downlink control channel, PDCCH, to the terminal device, the DCI being used to schedule 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 terminal device, the plurality of PDSCH transmissions being associated with respective priorities; and receiving HARQ feedback from the terminal device on resources for hybrid automatic repeat request, HARQ, feedback for the plurality of PDSCH transmissions, the HARQ feedback being multiplexed on a feedback codebook.

In a third aspect, a communication method is provided. The method comprises the following steps: at a terminal device, receiving a plurality of downlink control information, DCIs, on a plurality of physical downlink control channels, PDCCHs, from a network device, each of the plurality of DCIs being used to schedule a corresponding PDSCH transmission of a plurality of PDSCH transmissions on a single cell or multiple cells provided by the network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities; multiplexing hybrid automatic repeat request, HARQ, feedback of multiple PDSCH transmissions on a feedback codebook, the HARQ feedback of multiple PDSCH transmissions being indicated by the corresponding DCI as being transmitted in the same time slot or sub-slot; determining resources for a feedback codebook; and transmitting HARQ feedback to the network device on the resource.

In a fourth aspect, a communication method is provided. The method comprises the following steps: transmitting, at the network device, a plurality of downlink control information, DCIs, on a plurality of physical downlink control channels, PDCCHs, to the terminal device, each of the plurality of DCIs being used to schedule a corresponding PDSCH transmission of a plurality of PDSCH transmissions on a single cell or multiple cells provided by the network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities; and receiving hybrid automatic repeat request, HARQ, feedback from the terminal device on resources for a feedback codebook, HARQ feedback for the plurality of PDSCH transmissions being multiplexed on the feedback codebook, HARQ feedback for the plurality of PDSCH transmissions being indicated by the respective DCI as being transmitted in the same time slot or sub-slot.

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

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

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

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

Other features of the present disclosure will become apparent from the following description.

Drawings

The foregoing and other objects, features, and advantages of the disclosure will be apparent from the following more particular description of certain exemplary embodiments of the disclosure, as illustrated in the accompanying drawings in which:

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

fig. 2 illustrates a signaling flow for determining resources for HARQ feedback according to some embodiments of the present disclosure;

3A-3E illustrate diagrams of determination of resources for HRAQ feedback according to some embodiments of the present disclosure;

fig. 4 illustrates a signaling flow for determining resources for HARQ feedback according to some embodiments of the present disclosure;

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

fig. 6 illustrates a flow chart of an example communication method implemented at a terminal device in accordance with some embodiments of the present disclosure;

FIG. 7 illustrates a flowchart of an example communication method implemented at a network device, according to some embodiments of the present disclosure;

fig. 8 illustrates a flow chart of an example communication method implemented at a terminal device in accordance with some embodiments of the present disclosure;

fig. 9 illustrates a flowchart of an example communication method implemented at a network device, according to some embodiments of the present disclosure; and

fig. 10 is a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements.

Detailed Description

The principles of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described merely for the purpose of illustrating and helping those skilled in the art understand and practice the present disclosure and are not meant to limit the scope of the present disclosure in any way. The disclosure described herein may be implemented in various other ways besides those 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 skill 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 terminal devices include, but are not limited to, user Equipment (UE), personal computers, desktops, cell phones, cellular phones, smartphones, personal Digital Assistants (PDAs), portable computers, tablet computers, wearable devices, internet of things (IoT) devices, internet of everything (IoE) devices, machine Type Communication (MTC) devices, in-vehicle devices for V2X communication (where X represents a pedestrian, a vehicle, or an infrastructure/network), or image capturing devices (such as digital cameras), gaming devices, music storage and playback devices, or internet devices that support wireless or wired internet access and browsing, and the like.

The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. Furthermore, the term "network device" refers to a device that is capable of providing or hosting a cell or coverage area in which a terminal device may communicate. Examples of network devices include, but are 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 so on.

In one embodiment, a terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be in the primary node and the other may be in the 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 an eNB and the second RAT device is a gNB. Information related to the different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device to the terminal device directly or via the first network device. In one embodiment, information related to the configuration configured by the second network device for the terminal device may be transmitted from the second network device via the first network device. The reconfiguration related information configured by the second network device for the terminal device may be transmitted from the second network device to the terminal device directly or via the first network device.

The term "circuitry" as used herein may refer to hardware circuitry and/or a combination of hardware circuitry and software. For example, the circuitry may be a combination of analog and/or digital hardware circuitry and software/firmware. As a further example, circuitry may be any portion of a hardware processor (including digital signal processor(s), software, and memory (s)) with software that work together to cause an apparatus, such as a terminal device or network device, to perform various functions. In yet another example, the circuitry may be hardware circuitry and/or a processor, such as a microprocessor or a portion of a microprocessor, that requires software/firmware to operate, but software may not be present when operation is not required. As used herein, the term circuitry also encompasses hardware circuitry alone or a processor(s) or a portion of a hardware circuit or processor(s) and implementations of 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 "comprising" and variants thereof should be understood as open-ended terms, meaning "including, but not limited to. The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". The terms "first," "second," and the like, may refer to different or the same object. Other definitions (explicit and implicit) may be included below.

In some examples, a value, process, or apparatus is referred to as "best," "lowest," "highest," "smallest," "largest," or the like. It should be understood that such description is intended to indicate that a selection may be made among many functional alternatives in use, and that such selection need not be better, smaller, higher or otherwise preferred than the other selections.

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

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

In the communication system 100, the network device 120 and the terminal device 110 may transmit data and control information to each other. The number of terminal devices 110 and network devices 120 shown in fig. 1 is given for illustrative purposes and is not limiting.

Communication in communication system 100 may be implemented in accordance with any suitable communication protocol(s) including, but not limited to, first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), etc., cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc., and/or any other protocol currently known or to be developed in the future. Further, the communication may utilize any suitable wireless communication technology including, but not limited to: code Division Multiple Access (CDMA), frequency Division Multiple Access (FDMA), time Division Multiple Access (TDMA), frequency Division Duplex (FDD), time Division Duplex (TDD), multiple Input Multiple Output (MIMO), orthogonal Frequency Division Multiplexing (OFDMA), and/or any other technique currently known or developed in the future.

In 3GPP Rel-15/Rel-16, only single cell PDSCH scheduling via DCI is supported. However, in future releases (e.g., rel-17, workitem Dynamic Spectrum Sharing (DSS)), multi-cell PDSCH scheduling via a single DCI may be introduced to increase PDCCH scheduling capacity and reduce PDCCH blocking. Thus, multi-cell PDSCH scheduling via a single DCI may be applied to many cases (e.g., URLLC), which has not been investigated. In other words, currently, there is no solution for multi-cell PDSCH scheduling via a single DCI.

Furthermore, for DCI formats for multi-cell PDSCH scheduling, it is still unclear whether a Physical Uplink Control Channel (PUCCH) -related DCI field is shared/shared by two PDSCH transmissions on two cells to minimize DCI size. For example, for multi-cell PDSCH scheduling via a single DCI, when PUCCH-related DCI fields, e.g., PUCCH Resource Indicator (PRI) and PDSCH-to-HARQ feedback timing indicator (k 1), are shared by two PDSCHs, there is still no solution as to how to determine resources for a HARQ-ACK codebook including HARQ-ACKs (which may also be referred to as HARQ feedback, which may be ACKs or NACKs) for multi-cell PDSCH transmissions scheduled by a single DCI.

However, when the terminal device 110 is provided with a plurality of services (e.g., the above-described eMBB and/or URLLC services), each of the services having the 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 a PUCCH resource set and a K1 set.

For example, when two services (e.g., emmbb and URLLC) are provided for the terminal device 110 and two PUCCH configurations are defined in NR. For terminal device 110, an embb (i.e., a service with a lower priority (e.g., priority index of 0)) will be assigned one of the PUCCH configurations in the PUCCH configuration list. Meanwhile, URLLC (i.e., a service with a higher priority (e.g., with priority index 1)) will be assigned another one of the PUCCH configurations in the PUCCH configuration list.

Furthermore, in conventional solutions, if the terminal device 110 is provided with a pdsch-HARQ-ACK-codebook list, the terminal device 110 may be instructed to generate one or two HARQ-ACK codebooks by the pdsch-HARQ-ACK-codebook list. If terminal equipment 110 is instructed to generate a HARQ-ACK codebook, the HARQ-ACK codebook is associated with HARQ-ACK information with priority index 0. If the terminal device 110 is provided with a pdsch-HARQ-ACK-codebook list, the terminal device 110 (e.g., UE) multiplexes only HARQ-ACK information associated with the same priority index in the same HARQ-ACK codebook, e.g., a first HARQ-ACK codebook is associated with HARQ-ACK information having a priority index of 0 and a second HARQ-ACK codebook is associated with HARQ-ACK information having a priority index of 1.

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

Thus, if the terminal device 110 (e.g., UE) is configured with both the eMBB and URLLC services, then the individual/dedicated PUCCH configurations (e.g., PUCCH resource set and K1 set) will be configured. If two PDSCH transmissions associated with different priorities are scheduled by a single DCI, the PUCCH-related field in the DCI is common to both PDSCH transmissions and there is still no solution as to how to determine the resources for the HARQ-ACK codebook (which includes HARQ feedback for both PDSCH transmissions). Therefore, a solution is needed as to how to determine the resources for HARQ feedback for the PDSCH transmissions described above.

In order to solve at least part of the above problems, a solution is provided for determining uplink resources for multi-cell PDSCH scheduling via a single DCI. In this solution, terminal device 110 receives DCI from network device 120 on the PDCCH. The DCI is used to schedule multiple PDSCH transmissions on a single cell or multiple cells provided by network device 120 to serve a terminal device. Multiple PDSCH transmissions are associated with respective priorities. Although the DCI may have only common PUCCH-related DCI fields for two PDSCH transmissions (e.g., PUCCH Resource Indicator (PRI) and PDSCH-to-HARQ feedback timing indicator (k 1)), the terminal device determines the resources for HARQ feedback for multiple PDSCH transmissions and the HARQ feedback is multiplexed on the feedback codebook. The terminal device 110 then transmits HARQ feedback to the network device 120 over the resource.

Accordingly, a solution is provided for transmitting HARQ feedback for multiple PDSCH transmissions associated with different priorities on PUCCH resources. Furthermore, with this solution, a single DCI in the PDCCH can be used to schedule two PDSCH transmissions associated with different priorities and corresponding HARQ-ACK feedback is transmitted on PUCCH resources, thus a balance between scheduling flexibility and smaller DCI size is achieved with appropriate interpretation provided for a common DCI field for PUCCH indication in multi-cell scheduling DCI for PDSCH transmissions associated with different priorities.

Example embodiments of the present disclosure will be described in detail below with reference to fig. 2-9. Referring now to fig. 2, fig. 2 illustrates a signaling flow 200 for determining resources for HARQ feedback in accordance with some example embodiments of the present disclosure. Further, fig. 3A-3E illustrate diagrams of determination of resources for HRAQ feedback according to some embodiments of the present disclosure. For discussion purposes, signaling flow 200A will be described with reference to fig. 1 and 3. The signaling flow 200A involves the terminal device 110 and the network device 120 as shown in fig. 1.

As shown in fig. 2, network device 120 transmits 205DCI on a PDCCH to terminal device 110. The DCI is used to schedule multiple PDSCH transmissions on a single cell or multiple cells provided by network device 120 for serving a terminal device, and the multiple PDSCH transmissions are associated with respective priorities. For example, the respective priorities may be different priorities, e.g., different priorities with a priority index of 0 or 1.

Referring now to fig. 3A, fig. 3A illustrates a schematic diagram of a determination of resources for HARQ feedback in accordance with some embodiments of the present disclosure. In some examples, as shown in fig. 3A, terminal device 110 may receive DCI on a PDCCH and the DCI may be used to schedule two PDSCH transmissions on two cells. Each of the two PDSCH transmissions may be associated with a different priority (e.g., with a priority index of 0 or 1). As shown, one PDSCH transmission (e.g., PDSCH transmission 1) of the two PDSCH transmissions 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 PDSCH transmission (e.g., PDSCH transmission 2) of the two PDSCH transmissions 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 an example, PDSCH transmission 1 associated with priority 0 may be used for an eMBB service, while PDSCH transmission 2 with priority 1 may be used for a URLLC service, for example. It should be understood that fig. 3A is for illustrative purposes only and that the scope of the present disclosure is not limited in this respect. For example, there may be other numbers of PDSCH transmissions (details of which will be described in detail later with reference to fig. 3D), priorities, CCs, etc.

Then, upon receiving 210 the DCI, the terminal device 110 determines 220 resources for HARQ feedback for the multiple PDSCH transmissions. HARQ feedback is multiplexed on the feedback codebook. In some examples, with continued reference to fig. 3A, terminal device 110 may determine PUCCH resources for HARQ feedback 1 and 2 for PDSCH transmissions 1 and 2. In such an example, HARQ feedback 1 for PDSCH transmission 1 and HARQ feedback 2 for PDSCH transmission 2 may be multiplexed on the feedback codebook.

The terminal device then transmits 230HARQ feedback to the network device 120 on the resource accordingly. For example, terminal device 110 may transmit HARQ feedback 1 and 2 to network device 120 on PUCCH resources. Thus, the network device 120 receives 235 HARQ feedback from the terminal device 110.

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

In some embodiments, after determining the K1 set and the PUCCH resource set, terminal device 110 may determine resources for HARQ feedback based on DCI indications from the offset set and the PUCCH resource set.

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

With the above solution, even if the PDSCH-to-HARQ feedback timing indicator (k 1) and PRI values in the DCI are shared/shared by two PDSCH transmissions associated with different priorities, separate PUCCH configurations (e.g., k1 set and PUCCH resource set) of different priorities are configured, terminal device 110 (e.g., UE) can determine the association between PDSCH-to-HARQ feedback timing indicator (k 1) and PRI values and PUCCH configurations based on the priority/one priority/a single priority of the physical uplink control channel PUCCH, thereby achieving a balance between scheduling flexibility and smaller DCI size.

In some embodiments, the priority of the physical uplink control channel PUCCH may be determined by terminal device 110 in various ways. For example, the priority of PUCCH (i.e. priority of HARQ feedback) may be determined based on predefined rules, higher layer configuration or via dynamic indication, details of which will be shown in the following section.

In some embodiments, for example, the priority of the PUCCH may be predetermined. Referring now to fig. 3B, fig. 3B illustrates a diagram of a determination of resources for HRAQ feedback in accordance with some embodiments of the present disclosure.

For example, as shown in fig. 3B, when the priority of the PUCCH (i.e. the priority of HARQ feedback) is predetermined as a high priority, based on the high priority of the PUCCH, the terminal device 110 may determine a second PUCCH configuration corresponding to the high priority for the feedback codebook as the PUCCH configuration. Accordingly, terminal device 110 may determine the K1 set and the PUCCH resource set in the second 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 an example, when determining resources, in particular, terminal device 110 may determine slots/sub-slots for PUCCH transmission of HARQ-ACK bits for two PDSCH based on the value of PDSCH-to-HARQ feedback timing indicator in DCI from the K1 set of the determined PUCCH configuration (i.e. the K1 set in the second PUCCH configuration) associated with the high priority. Terminal device 110 may then determine a PUCCH resource set from the high priority PUCCH resource set (i.e. the PUCCH resource set in the second PUCCH configuration) in the slot/sub-slot. Also, terminal device 110 may determine resources (i.e., PUCCH resources) from the PUCCH resource set based on the value of PRI in the DCI.

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

With this solution, considering that the high priority of PUCCH is predetermined, the performance of URLLC HARQ feedback transmission with high requirements on delay and reliability can be guaranteed.

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

Thus, for a terminal device 110 having multiple services (e.g., eMBB, ul lc, etc.) and separate PUCCH configurations (e.g., K1 set and PUCCH resource set) 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 may determine a slot/sub-slot for PUCCH transmission of HARQ feedback bits for two PDSCH transmissions based on the PDSCH-to-HARQ feedback timing indicator value in DCI from the K1 set of priorities (e.g., high priority or low priority) configured by RRC. In such an example, terminal device 110 may determine a PUCCH resource set from among PUCCH resource sets of priorities configured by RRC in the slot/sub-slot. Finally, the terminal device may determine resources from the PUCCH resource set based on the value of PRI in the DCI.

Thus, the solution is more flexible, as the priority of the PUCCH may be configured by the network device 120, e.g. via RRC messages. Thus, when the network device 120 knows that PDSCH of URLLC service is less transmitted than the eMBB service, the network device 120 may select low-priority or high-priority PUCCH resources based on the number of low-priority HARQ-ACK bits and the number of high-priority HARQ-ACK bits, and the low-priority PUCCH configuration may be configured such that uplink resources (i.e., PUCCH resources) may be utilized in a more efficient manner.

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

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

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

In such embodiments, specifically, for example, for a terminal device 110 having multiple services and separate PUCCH configurations (e.g., K1 set and PUCCH resource set) 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 a slot/sub-slot of PUCCH transmission of HARQ feedback bits for two PDSCH transmissions based on a value of a PDSCH-to-HARQ-feedback timing indicator in the DCI from the K1 set of priorities implicitly indicated by the DCI (e.g., priorities of PDSCH transmissions scheduled earlier in the time domain (e.g., indicated by priority index)). Terminal device 110 may then determine the PUCCH resource set from the PUCCH resource set of the priority implicitly indicated by the DCI, e.g., the priority of PDSCH as the earlier scheduled PDSCH transmission in the time domain (e.g., indicated by the priority index). Finally, terminal device 110 may determine PUCCH resources from the PUCCH resource set based on the value of PRI in the DCI.

In some embodiments, the priority of the PUCCH may be determined based on a priority of a portion of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined CC index associated with the one of the plurality of cells. That is, the priority of the PUCCH may be the priority of PDSCH transmission scheduled on CCs having 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., lower CC index) or 2 (i.e., higher CC index).

In such embodiments, for example, for a terminal device 110 having multiple services and separate PUCCH configurations (e.g., a K1 set and a PUCCH resource set) 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 a slot/sub-slot for PUCCH transmission of HARQ feedback bits for two PDSCH transmissions based on a value of a PDSCH-to-HARQ-timing indicator in DCI from a K1 set of priorities (e.g., indicated by priority index) of PDSCH transmissions scheduled on cells with predetermined CC indices (e.g., lower CC or higher CC indices)) implicitly indicated by the DCI.

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

In some other embodiments, the priority of the PUCCH may be determined based on the priority of PDSCH transmissions on a scheduling cell, which is a cell for scheduling PDCCH transmissions of multiple PDSCH transmissions. Referring now to fig. 3C, fig. 3C illustrates a diagram of a determination of resources for HRAQ feedback in accordance with 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 is independent for separate PDSCH transmissions (i.e., PDSCH transmissions 1 and 2) on two cells (i.e., CC #1 and CC # 2). In this case, the priority index of PDSCH on the scheduling CC is 1, indicating a high priority. Thus, a second PUCCH configuration associated with a high priority may be determined, as shown in fig. 3C. Thus, the K1 set and the PUCCH resource set may be determined from the second PUCCH configuration, and then the resources (i.e., PUCCH resources) may be determined based on DCI from the K1 set and the PUCCH resource set. It should be noted that the detailed steps for determining PUCCH resources in this example are similar to the steps mentioned above and are therefore not repeated here.

In the above section, a method of determining the priority of PUCCH for HARQ-ACK bits of two PDSCH on two cells associated with different priorities has been described. With the above solution, for multi-cell PDSCH scheduling via a single DCI, the fields PRI and PDSCH-to-HARQ feedback timing indicator (K1) are shared by two PDSCH or by a terminal device 110 (e.g., UE) with multiple services (e.g., eMBB and URLLC), the separate configurations of the K1 set and PUCCH resource set are configured for HARQ-ACKs of different priorities, whereas if two PDSCH transmissions associated with different priorities on two cells are scheduled by a single DCI, it is clear to the terminal device that one value of the PDSCH-to-HARQ feedback timing indicator in the DCI is associated with the K1 set of the determined PUCCH configuration with low priority or with the K1 set of the determined PUCCH configuration associated with high priority, and it is also clear that one value of PRI is associated with the PUCCH resource set of low priority or the PUCCH resource set of high priority.

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

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

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

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

In some embodiments, if the higher layer parameter, dedimedpriority indicator DCI-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 the higher layer parameter, dedimedicatedpriority indicator DCI-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, terminal device 110 may receive DCI from network device 120 on a PDCCH at terminal device 110, the DCI being used to schedule multiple PDSCH transmissions on a single cell or multiple cells provided by network device 120 for serving the terminal device, and the multiple PDSCH transmissions being associated with respective priorities. The terminal device 110 may then determine resources for HARQ feedback for the multiple PDSCH transmissions, where the HARQ feedback is multiplexed on a feedback codebook. The terminal device 110 may then transmit HARQ feedback to the network device 120 over the resource. In such an example, the PUCCH configuration of the feedback codebook may be determined using the method introduced in the previous part of the disclosure, and details will not be repeated here.

Referring now to fig. 3D, fig. 3D illustrates a diagram of a determination of resources for HRAQ feedback in accordance with some embodiments of the present disclosure. As described above, there may be other numbers of PDSCH transmissions. In some examples, as shown in fig. 3D, there may be three PDSCH transmissions (PDSCH transmissions 1, 2, and 3).

In such an example, as shown in fig. 3D, terminal device 110 may receive DCI on a PDCCH and the DCI may be used to schedule three PDSCH transmissions on three cells. Each of the three PDSCH transmissions may be associated with a different priority (e.g., with a priority index of 0 or 1). As shown, a first PDSCH transmission (e.g., PDSCH transmission 1) of the three PDSCH transmissions may be on one cell (e.g., corresponding to a CC with CC index=1 (i.e., CC # 1) and associated with priority 0. A second PDSCH transmission (e.g., PDSCH transmission 2) of the three PDSCH transmissions is on a second cell (e.g., corresponding to a CC having a CC index=2 (i.e., CC # 2) and associated with priority 1. A third PDSCH transmission (e.g., PDSCH transmission 3) of the three PDSCH transmissions is on a third cell (e.g., corresponding to a CC with CC index=3 (i.e., CC # 3) and associated with priority 0.

Referring now to fig. 3E, fig. 3E illustrates a signaling flow 200 for determining resources for HARQ feedback according to some example embodiments of the present disclosure.

In some embodiments, as shown in fig. 3E, there may be multiple (e.g., 2 as shown) PDSCH transmissions within multiple slots/minislots on a single cell scheduled by a single DCI. For this case, as described above, terminal device 110 may receive DCI from network device 120 on the PDCCH. The DCI may be used to schedule two PDSCH transmissions on a single cell (with a corresponding CC index, e.g., CC # 1) provided by network device 120 for serving the terminal device. The two PDSCH transmissions are associated with respective priorities. The terminal device 110 may then determine the resources for HARQ feedback for both PDSCH transmissions and multiplex the HARQ feedback on a feedback codebook. The terminal device 110 may then transmit HARQ feedback to the network device 120 over the resource.

It should be appreciated that the manner of determining the priority of the PUCCH may be similar to that described above, and thus is not described in detail herein. For example, the priority of the PUCCH may be determined based on a predefined rule (e.g., a predetermined rule). In another example, the priority of the PUCCH may also be configured in a higher layer configuration, e.g., via an RRC message. Alternatively, the priority of the PUCCH may also be determined by dynamic indication, e.g., via a DCI field in the DCI or the like.

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

In such an embodiment, it may be configured, for example, by a group DCI field, e.g., dedicated separate indication of TPC command for higher layer parameter dciheldsforpucch = scheduled PUCCH, downlink allocation index, PDSCH-to-harq_feedback timing indicator, and PRI in DCI for two PDSCH on two cells. Alternatively, it may be configured in a group DCI field, the higher layer parameter dciheldsforpucch = common, common indication of TPC commands for scheduled PUCCH, downlink allocation index, PDSCH-to-harq_feedback timing indicator, and PRI in DCI for two PDSCH transmissions on two cells.

In other examples, any DCI field may be configured with it. For example, if the higher layer parameter dediocatedPucchResourceindicator is configured, then separate indications of the fields PRI in the DCI for two PDSCH transmissions on two cells, otherwise, the fields PRI in the DCI are common and shared by the two PDSCH transmissions.

When the dedicated pucchresource indicator is configured, the first PDSCH transmission will have 3 most significant bits (MSB bits) and the second PDSCH transmission will have three least significant bits (LSB bits) for the PRI field in the DCI. When the dedicated pucchresource indicator is not configured, the two PDSCH transmissions will share 3 bits for the PRI field in the DCI.

Referring now to fig. 4, fig. 4 illustrates a signaling flow 400 for determining resources for HARQ feedback in accordance with some example embodiments of the present disclosure. For discussion purposes, 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 shown in fig. 1.

As shown in fig. 4, network device 120 transmits 405 a plurality of DCIs to terminal device 110 on a plurality of PDCCHs. Each DCI of the plurality of DCIs is to schedule a corresponding PDSCH transmission of the plurality of PDSCH transmissions on a single cell or multiple cells provided by the network device 120 to serve the terminal device. Multiple PDSCH transmissions are associated with respective priorities.

Thus, upon receiving 410 the plurality of DCIs, the terminal device 110 then multiplexes 420 HARQ feedback for the plurality of PDSCH transmissions on a feedback codebook, wherein the HARQ feedback for the plurality of PDSCH transmissions is indicated by the respective DCI as being transmitted in the same or a sub-slot. The terminal device 110 then determines 430 the resources for the feedback codebook and transmits 440HARQ feedback to the network device 120 on the resources. Accordingly, network device 120 receives 445HRAQ feedback from terminal device 110.

With this solution, since the judgment of collision between two PUCCHs for HARQ-ACKs having different priority indexes is skipped and multiplexing is directly performed, the complexity of the terminal device 110 processing can be reduced.

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

It should be appreciated that although not shown, each of the two DCIs may be used to schedule a corresponding one of the two PDSCH transmissions on a plurality of cells provided by network device 120 for serving the terminal device. The scope of the present disclosure is not limited in this respect.

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

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

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

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

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

With this solution, since the judgment of collision between two PUCCHs for HARQ-ACKs having different priority indexes is skipped and multiplexing is directly performed, the complexity of processing by the terminal device 110 can be reduced, thereby reducing the complexity of the terminal device 110 (e.g., UE).

Fig. 6 illustrates a flowchart of an example method 600 according to some embodiments of the present disclosure. The method 600 may be implemented at the terminal device 110 as shown in fig. 1. It should be understood that method 600 may include additional blocks not shown and/or that some blocks shown may be omitted, and that the scope of the disclosure is not limited in this respect. For discussion purposes, the method 600 will be described with reference to fig. 1 from the perspective of the terminal device 110.

In block 610, the terminal device receives downlink control information, DCI, from the network device on a physical downlink control channel, PDCCH. The DCI is used to schedule multiple physical downlink shared channel, PDSCH, transmissions on a single cell or multiple cells provided by a network device to serve a terminal device. Multiple PDSCH transmissions are associated with respective priorities. The terminal device then determines resources for hybrid automatic repeat request, HARQ, feedback for the multiple PDSCH transmissions, the HARQ feedback being multiplexed on a feedback codebook, block 620. At block 630, the terminal device transmits HARQ feedback to the network device over the resource.

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

In some embodiments, the priority is predetermined.

In some embodiments, method 600 may further include receiving information related to priority from a network device; and determining a 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 method includes transmitting, in a DCI, information related to a priority, the priority associated with one of a plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions precedes, in a time domain, other ones of the plurality of PDSCH transmissions, a priority of a portion of the plurality of PDSCH transmissions scheduled on one of a plurality of cells having a predetermined component carrier index associated with the one of the plurality of cells, and the priority of a PDSCH transmission associated with a cell for PDCCH transmission used to schedule the plurality of PDSCH transmissions.

In some embodiments, method 600 may further include receiving an indication indicating that at least one of the PUCCH-related DCI fields is common to multiple PDSCH transmissions.

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

In some embodiments, method 600 may further include receiving an indication from the network device indicating that the priority indicator in the DCI is common or dedicated to multiple PDSCH transmissions, wherein the indication is configured by the 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 may be implemented at the network device 120 as shown in fig. 1. It should be understood that method 700 may include additional blocks not shown and/or may omit some of the blocks shown, and that the scope of the present disclosure is not limited in this respect. For discussion purposes, the method 700 will be described with reference to fig. 1 from the perspective of the network device 120.

In block 710, the network device transmits downlink control information, DCI, to the terminal device on a physical downlink control channel, PDCCH. The DCI is used to schedule multiple physical downlink shared channel, PDSCH, transmissions on a single cell or multiple cells provided by a network device to serve a terminal device. Multiple PDSCH transmissions are associated with respective priorities. At block 720, the network device receives HARQ feedback from the terminal device on resources for hybrid automatic repeat request, HARQ, feedback for a plurality of PDSCH transmissions, the HARQ feedback being multiplexed on a feedback codebook.

In some embodiments, the priority is predetermined.

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

In some embodiments, method 700 further includes transmitting an indication indicating that at least one of the PUCCH-related DCI fields is common to multiple PDSCH transmissions.

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

Fig. 8 illustrates a flowchart of an example method 800 according to some embodiments of the present disclosure. The method 800 may be implemented at a terminal device 110 as shown in fig. 1. It should be understood that method 800 may include additional blocks not shown and/or that some blocks shown may be omitted, and that the scope of the disclosure is not limited in this respect. For discussion purposes, the method 800 will be described with reference to fig. 1 from the perspective of the terminal device 110.

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

In some embodiments, the priority is predetermined.

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

In some embodiments, the priority is determined based on at least one of: the method includes the steps of providing, in the DCI, information related to a priority, an indication of the priority by a predetermined one of a plurality of downlink control channels, and an indication of the priority by one of the plurality of downlink control channels, the one of the plurality of downlink control channels being for scheduling one of a plurality of PDSCH transmissions on one of a 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 may be implemented at the network device 120 as shown in fig. 1. It should be understood that method 900 may include additional blocks not shown and/or may omit some of the blocks shown, and that the scope of the present disclosure is not limited in this respect. For discussion purposes, the method 900 will be described with reference to fig. 1 from the perspective of the network device 120.

At block 910, the network device transmits a plurality of downlink control information, DCIs, to the terminal device on a plurality of physical downlink control channels, PDCCHs, each of the plurality of DCIs to schedule a corresponding one of a plurality of PDSCH transmissions on a single cell or a plurality of cells provided by the network device to serve the terminal device, the plurality of PDSCH transmissions being associated with respective priorities. At block 920, the network device receives hybrid automatic repeat request, HARQ, feedback from the terminal device on resources for a feedback codebook on which HARQ feedback for multiple PDSCH transmissions is multiplexed, the HARQ feedback for multiple PDSCH transmissions being indicated by the respective DCI as being transmitted in the same time slot or sub-slot.

In some embodiments, the priority is predetermined.

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

In some embodiments, a terminal device (e.g., terminal device 110) includes circuitry configured to: receiving downlink control information, DCI, on a physical downlink control channel, PDCCH, from a network device, the DCI being used to schedule a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or multiple cells provided by the network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities; determining resources for hybrid automatic repeat request, HARQ, feedback for a plurality of PDSCH transmissions, the HARQ feedback being multiplexed on a feedback codebook; and transmitting HARQ feedback to the network device on the resource.

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

In some embodiments, the priority is predetermined.

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

In some embodiments, the priority is determined based on at least one of: the method includes transmitting, in a DCI, information related to a priority, the priority associated with one of a plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions precedes, in a time domain, other ones of the plurality of PDSCH transmissions, the priority of a portion of the plurality of PDSCH transmissions, the portion of PDSCH transmissions being scheduled on one of a plurality of cells, the one cell having a predetermined component carrier index associated with the one of the plurality of cells, and the priority of PDSCH transmissions associated with a cell for PDCCH transmissions used to schedule the plurality of PDSCH transmissions.

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

In some embodiments, the circuitry is further configured to: an indication is received from a network device indicating that a priority indicator in DCI is common or dedicated to multiple PDSCH transmissions, wherein the indication is configured by a radio resource control message.

In some embodiments, a network device (e.g., network device 120) includes circuitry configured to: transmitting downlink control information, DCI, on a physical downlink control channel, PDCCH, to a terminal device, the DCI being used to schedule a plurality of physical downlink shared channel, PDSCH, transmissions on a single cell or a plurality of cells provided by a network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities; and receiving HARQ feedback from the terminal device on resources for hybrid automatic repeat request, HARQ, feedback for the plurality of PDSCH transmissions, the HARQ feedback being multiplexed on a feedback codebook.

In some embodiments, the priority is predetermined.

In some embodiments, the circuitry is further configured to: and transmitting information related to the priority to the terminal equipment.

In some embodiments, the priority is determined based on at least one of: the method includes transmitting, in a DCI, information related to a priority, the priority associated with one of a plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions precedes, in a time domain, other ones of the plurality of PDSCH transmissions, the priority of a portion of the plurality of PDSCH transmissions, the portion of PDSCH transmissions being scheduled on one of a plurality of cells, the one cell having a predetermined component carrier index associated with the one of the plurality of cells, and the priority of PDSCH transmissions associated with the cell for PDCCH transmissions, the PDCCH transmissions being used to schedule the plurality of PDSCH transmissions.

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

In some embodiments, a terminal device (e.g., terminal device 110) includes circuitry configured to: receiving, from a network device, a plurality of downlink control information, DCIs, on a plurality of physical downlink control channels, PDCCHs, each of the plurality of DCIs being used to schedule a corresponding PDSCH transmission of a plurality of PDSCH transmissions on a single cell or multiple cells provided by the network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities; multiplexing hybrid automatic repeat request, HARQ, feedback of multiple PDSCH transmissions on a feedback codebook, the HARQ feedback of multiple PDSCH transmissions being indicated by the corresponding DCI as being transmitted in the same time slot or sub-slot; determining resources for a feedback codebook; and transmitting the HARQ feedback to the network device over the resource.

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

In some embodiments, the priority is predetermined.

In some embodiments, the priority is determined based on at least one of: the method includes the steps of providing, in the DCI, information related to a priority, an indication of the priority by a predetermined one of a plurality of downlink control channels, and an indication of the priority by one of the plurality of downlink control channels, the one of the plurality of downlink control channels being used to schedule one of a plurality of PDSCH transmissions, the one PDSCH transmission being on one of a plurality of cells having a predetermined component carrier index.

In some embodiments, a network device (e.g., network device 120) includes circuitry configured to: transmitting, to a terminal device, a plurality of downlink control information, DCI, on a plurality of physical downlink control channels, PDCCHs, each DCI of the plurality of DCIs being used to schedule a corresponding PDSCH transmission of a plurality of PDSCH transmissions on a single cell or multiple cells provided by a network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities; and receiving hybrid automatic repeat request, HARQ, feedback from the terminal device on resources for a feedback codebook, HARQ feedback for the plurality of PDSCH transmissions being multiplexed on the feedback codebook, HARQ feedback for the plurality of PDSCH transmissions being indicated by the respective DCI as being transmitted in the same time slot or sub-slot.

In some embodiments, the priority is predetermined.

Fig. 10 is a simplified block diagram of an apparatus 1000 suitable for implementing embodiments of the disclosure. Device 1000 may be viewed as yet another example implementation of terminal device 110 or network device 120 as shown in fig. 1. Thus, device 1000 may be implemented at terminal device 110 or network device 120 or as at least a portion of terminal device 110 or network device 120.

As shown, device 1000 includes a processor 1010, a memory 1020 coupled to processor 1010, suitable Transmitters (TX) and Receivers (RX) 1040 coupled to processor 1010, and a communication interface coupled to TX/RX 1040. Memory 1020 stores at least a portion of program 1030. TX/RX 1040 is used for two-way communication. TX/RX 1040 has at least one antenna to facilitate communications, but in practice there may be multiple access nodes as referred to in this application. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bi-directional communication between enbs, an S1 interface for communication between a Mobility Management Entity (MME)/serving gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a Relay Node (RN), or a Uu interface for communication between an eNB and a terminal equipment.

The program 1030 is assumed to include program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate in accordance with embodiments of the present disclosure, as discussed herein with reference to any one of fig. 2-9. 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. Further, the combination of the processor 1010 and the memory 1010 may form a processing component 1050 suitable for implementing 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 non-transitory computer readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory, as non-limiting examples. Although only one memory 1010 is shown in device 1000, there may be multiple physically distinct memory modules within device 1000. The processor 1010 may be of any type suitable to the local technology network and may include one or more of general purpose computers, special purpose computers, microprocessors, digital Signal Processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The device 1000 may have multiple processors, such as an application specific integrated circuit chip that is temporally subject to a clock that synchronizes the main processor.

In general, the various embodiments of the disclosure may be implemented using 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 the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that 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 comprises computer executable instructions, such as instructions included in program modules, that are executed in a device on a target physical or virtual processor to perform the processes or methods described above with reference to fig. 2-9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions of program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote memory storage media.

Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program code 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 code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the 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 program code described above may be embodied on a machine-readable medium, which may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is 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 a 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 described in a particular order, this should not be construed 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 some cases, multitasking and parallel processing may be advantageous. Also, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the 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 can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

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

Claims

1. A method of communication, comprising:

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

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

and transmitting the HARQ feedback to the network equipment on the resource.

2. The method of claim 1, wherein determining the resource comprises:

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

Based on the DCI, the resources are determined from the offset set and the PUCCH resource set.

3. The method of claim 2, wherein the priority is predetermined.

4. The method of claim 2, further comprising:

information related to the priority is received from the network device.

5. The method of claim 4, wherein the information is transmitted in a radio resource control, RRC, message.

6. The method of claim 2, wherein the priority is determined based on at least one of:

information in the DCI related to the priority,

a priority associated with one of the plurality of PDSCH transmissions, wherein transmitting the one of the plurality of PDSCH transmissions precedes other ones of the plurality of PDSCH transmissions in the time domain,

priority of a portion of the plurality of PDSCH transmissions scheduled on one of the plurality of cells having a predetermined component carrier index associated with the one of the plurality of cells, an

Priority of PDSCH transmissions associated with a cell for PDCCH transmissions used to schedule the plurality of PDSCH transmissions.

7. The method of claim 1, further comprising:

an indication is received indicating that at least one of the PUCCH-related DCI fields is common to the plurality of PDSCH transmissions.

8. The method of claim 7, wherein the PUCCH-related DCI field comprises at least one of:

the transmit power for the resource controls TPC commands,

the PUCCH resource indicator PRI is a physical uplink control channel,

PDSCH-to-HARQ feedback timing indicator

The downlink allocation index DAI.

9. The method of claim 1, further comprising:

an indication is received from the network device indicating that a priority indicator in the DCI is common or dedicated to the plurality of PDSCH transmissions, wherein the indication is configured by a radio resource control message.

10. A method of communication, comprising:

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

On resources for hybrid automatic repeat request, HARQ, feedback for the plurality of PDSCH transmissions, HARQ feedback is received from the terminal device, the HARQ feedback being multiplexed on a feedback codebook.

11. The method of claim 10, wherein the priority is predetermined.

12. The method of claim 10, further comprising:

and transmitting information related to the priority to the terminal equipment.

13. The method of claim 12, wherein the information is transmitted in a radio resource control, RRC, message.

14. The method of claim 10, wherein the priority is determined based on at least one of:

information in the DCI related to the priority,

15. The method of claim 10, further comprising:

an indication of transmission indicating that at least one of the PUCCH-related DCI fields is common to the plurality of PDSCH transmissions.

16. The method of claim 15, wherein the PUCCH-related DCI field comprises at least one of:

the transmit power for the resource controls TPC commands,

the PUCCH resource indicator PRI is a physical uplink control channel,

PDSCH-to-HARQ feedback timing indicator

The downlink allocation index DAI.

17. A method of communication, comprising:

at a terminal device, receiving a plurality of downlink control information, DCIs, on a plurality of physical downlink control channels, PDCCHs, from a network device, each of the plurality of DCIs being used to schedule a corresponding PDSCH transmission of a plurality of PDSCH transmissions on a single cell or multiple cells provided by the network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities;

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

Determining resources for the feedback codebook; and

and transmitting the HARQ feedback to the network equipment on the resource.

18. The method of claim 17, wherein determining the resource comprises:

19. The method of claim 18, wherein the priority is predetermined.

20. The method of claim 18, further comprising:

information related to the priority is received from the network device.

21. The method of claim 20, wherein the information is transmitted in a radio resource control, RRC, message.

22. The method of claim 18, wherein the priority is determined based on at least one of:

information in the DCI related to the priority,

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

a priority indication by one of the plurality of downlink control channels, the one of the plurality of downlink control channels being used to schedule one of the plurality of PDSCH transmissions on one of the plurality of cells having a predetermined component carrier index.

23. A method of communication, comprising:

transmitting, at a network device, a plurality of downlink control information, DCIs, on a plurality of physical downlink control channels, PDCCHs, to a terminal device, each of the plurality of DCIs being used to schedule a corresponding PDSCH transmission of a plurality of PDSCH transmissions on a single cell or multiple cells provided by the network device for serving the terminal device, the plurality of PDSCH transmissions being associated with respective priorities; and

on resources for the feedback codebook, hybrid automatic repeat request, HARQ, feedback is received from the terminal device, the HARQ feedback of the plurality of PDSCH transmissions being multiplexed on the feedback codebook, the HARQ feedback of the plurality of PDSCH transmissions being indicated by the respective DCI as being transmitted in the same time slot or sub-slot.

24. The method of claim 23, wherein the priority is predetermined.

25. The method of claim 23, further comprising:

and transmitting information related to the priority to the terminal equipment.

26. The method of claim 25, wherein the information is transmitted in a radio resource control, RRC, message.

27. The method of claim 23, wherein the priority is determined based on at least one of:

information in the DCI related to the priority,

28. A terminal device, comprising:

a processing unit; and

a memory coupled to the processing unit and storing instructions thereon that, when executed by the processing unit, cause the apparatus to perform the method of any of claims 1-9 or any of claims 17-22.

29. A computer readable medium having instructions stored thereon, which when executed on at least one processor, cause the at least one processor to perform the method of any of claims 10 to 16 or any of claims 23 to 27.