CSI REPORTING CONFIGURATION

Abstract

A communication system is disclosed in which an access network node determines a CSI feedback occasion in respect of a terminal device, determines if a PUSCH data transmission can be scheduled earlier than a PUCCH data transmission or if a PDSCH data transmission is to be scheduled; and if a PUSCH data transmission cannot be scheduled earlier than a PUCCH data transmission or a PDSCH data transmission is to be scheduled, transmits a downlink DCI of Downlink DCI format to the terminal device, the downlink DCI being configured to trigger generation by the terminal device of CSI reporting data; wherein the downlink DCI is further configured to schedule either a PUSCH or a PUCCH data transmission to support transmission of the CSI reporting data, depending on PUCCH availability when the CSI feedback occasion is determined.

Description

Claims

1] A method performed by an access network node of a communication system, the method comprising for a Channel State Information (CSI) feedback occasion in respect of a terminal device, transmitting a downlink Downlink Control Information (DCI) of a Downlink DCI format to the terminal device, the downlink DCI being configured to trigger generation by the terminal device of CSI reporting data,wherein the downlink DCI is further configured to schedule either a Physical Uplink Shared Channel (PUSCH) data transmission or a Physical Uplink Control Channel (PUCCH) data transmission, depending on PUCCH availability.

2] The method according to claim 1, wherein the CSI feedback occasion is an aperiodic CSI feedback occasion.

3] The method according to claim 1, further comprising: determining if the PUSCH data transmission can be scheduled earlier than a the PUCCH data transmission or if a Physical Downlink Shared Channel (PDSCH) data transmission is to be scheduled, wherein the transmitting is performed if it is determined that the PUSCH data transmission cannot be scheduled earlier than the PUCCH data transmission or the PDSCH data transmission is to be scheduled.

4] The method according to claim 1, further comprising, if the PUSCH data transmission can be scheduled earlier than the PUCCH data transmission or there is no PDSCH data to be scheduled, transmitting an uplink DCI of a Uplink DCI format to the terminal device, wherein the uplink DCI is configured to trigger generation by the terminal device of the CSI reporting data and to schedule the PUSCH data transmission.

5] (canceled)

6] The method according to claim 1, wherein the downlink DCI includes a PUCCH resource allocation field for allocating a PUCCH resource for transmission by the terminal device of Hybrid Automatic Repeat Request -Acknowledgement (HARQ-ACK) feedback data, and the method further comprising: if the PUSCH data transmission cannot be scheduled earlier than the PUCCH data transmission or a PDSCH data transmission is to be scheduled, determining if a PUCCH resource is allocated by the PUCCH resource allocation field of the downlink DCI for transmission of multiplexed CSI reporting data and HARQ-ACK feedback data, and wherein the downlink DCI includes an indicator field to indicate to the terminal device whether to use the PUCCH resource or a PUSCH resource.

7] The method according to claim 6, wherein a PUSCH resource allocation is preconfigured for the downlink DCI.

8] The method according to claim 6, wherein the downlink DCI format includes a PUSCH resource allocation field which, when populated, acts to allocate a PUSCH resource for transmission by the terminal device of the CSI reporting data.

9] The method according to claim 6, wherein the indicator field is configured to hold a first value to indicate, to the terminal device, that the PUCCH data transmission is to be used to transmit the CSI reporting data, and a second value if the PUSCH resource is to be used to transmit the CSI reporting data.

10] An access network node of a communication system, the access network node comprising: a controller; anda transceiver, wherein the controller is configured to control the transceiver to: transmit a downlink Downlink Control Information (DCI) of a Downlink DCI format to a terminal device in order to trigger a Channel State Information (CSI) occasion in respect of the terminal device, configured to, the downlink DCI being configured to trigger generation by the terminal device of CSI reporting data;wherein the downlink DCI is further configured to schedule either a Physical Uplink Chared Channel (PUSCH) data transmission or a Physical Uplink Control Channel (PUCCH) data transmission to support transmission of said-the CSI reporting data, depending on PUCCH availability when said CSI feedback occasion is determined availability.

11] The access network node according to claim 10, wherein the controller is further configured to: determine if the PUSCH data transmission can be scheduled earlier than the PUCCH data transmission or if a Physical Downlink Shared Channel (PDSCH) data transmission is to be scheduled; andcontrol the transceiver to transmit the downlink DCI of the Downlink DCI format to the terminal device, if it is determined that the PUSCH data transmission cannot be scheduled earlier than the PUCCH data transmission or the Physical Downlink Shared Channel (PDSCH) data transmission is to be scheduled.

12] The access network node according to claim 10, wherein the downlink DCI includes a PUCCH resource allocation field for allocating a PUCCH resource for transmission by the terminal device of Hybrid Automatic Repeat Request - Acknowledgement (HARQ-ACK) feedback data, and the controller is configured to: if the PUSCH data transmission cannot be scheduled earlier than the PUCCH data transmission or a PDSCH data transmission is to be scheduled, determine if a PUCCH resource is allocated by the PUCCH resource allocation field of the downlink DCI for transmission of multiplexed CSI reporting data and HARQ-ACK feedback data, and wherein the downlink DCI includes an indicator field to indicate to the terminal device whether to use the PUCCH resource or a PUSCH resource.

13] The access network node according to claim 11, wherein the downlink DCI includes a PUSCH resource allocation field, andthe controller is configured to allocate a PUSCH resource in the PUSCH resource allocation field for scheduling the PUSCH data transmission if the downlink DCI indicates that the PUSCH data transmission is to be used to support transmission of the CSI reporting data.

14] The access network node according to claim 11, wherein a PUSCH resource allocation is preconfigured for the downlink DCI.

15] A method performed by a terminal device configured to communicate with an access network node of a communication system, the method comprising: receiving a downlink Downlink Control Information (DCI) of downlink DCI format, the downlink DCI being configured to trigger generation by the terminal device of Channel State Information (CSI) reporting data; wherein the downlink DCI is further configured to schedule either a Physical Uplink Shared Channel (PUSCH) data transmission or a PUCCH Physical Uplink Control Channel (PUCCH) data transmission to support transmission of the CSI reporting data; andtransmitting the CSI reporting data to the access network node by means of a the PUCCH data transmission or the PUSCH data transmission, depending on a resource allocation in the downlink DCI.

16] A terminal device configured to communicate with an access network node of a communication system, the terminal device comprising: a controller; anda transceiver, wherein the controller is configured to: control the transceiver to receive a downlink Downlink Control Information (DCI) of a downlink DCI format, the downlink DCI being configured to trigger generation by the terminal device of Channel State Information (CSI) reporting data; wherein the downlink DCI is further configured to schedule either a Physical Uplink Shared Channel (PUSCH) data transmission or a Physical Uplink Control Channel (PUCCH) data transmission to support transmission of said-the CSI reporting data; andcontrol the transceiver to transmit the CSI reporting data to the access network node by means of the PUCCH data transmission or the PUSCH data transmission, depending on a resource allocation in the downlink DCI.

17-20] (canceled)