Method and device for reporting channel state information

Abstract

The embodiment of the invention provides a channel state information reporting method and device, and the method comprises the steps: terminal equipment receives DCI (Downlink Control Information) format used for scheduling a PUSCH (Physical Uplink Shared Channel) on one or more cells and / or uplink carriers, and the DCI format requests or triggers non-periodic CSI (Channel State Information) reporting; and the terminal equipment sends the CSI report. According to the embodiment of the invention, the non-periodic CSI reporting and the semi-persistent CSI reporting based on the PUSCH under the condition that the DCI format can schedule the PUSCH of a plurality of cells are realized.

Description

Method and device for reporting channel state information Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] The Physical Downlink Shared Channel (PDSCH) is a type of physical downlink channel in a wireless communication system, used to carry downlink data. The Physical Uplink Shared Channel (PUSCH) is a type of physical uplink channel in a wireless communication system, used to carry uplink data. PDSCH and PUSCH can be scheduled using downlink control information (DCI). In the current new radio (NR) system, a variety of DCI formats are defined for scheduling PDSCH or PUSCH. Different DCI formats include different specific information and / or sizes to meet different scheduling requirements.

[0003] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.

[0004] Summary of the Invention

[0005] The inventors found that, at present, DCI format 0_1 ​​and DCI format 0_2 can be used to trigger / activate / deactivate non-periodic CSI report and PUSCH-based SP CSI report, and both DCI format 0_1 ​​and DCI format 0_2 can only schedule the PUSCH of one cell (or uplink carrier). In the standardization work of Rel-18NR that has just begun, as one of the goals of multi-carrier enhancement, it will be considered how to further support the scheduling of PUSCH of multiple cells (or uplink carriers) through one DCI to reduce the resource overhead of DCI and improve system throughput. This DCI that supports scheduling multiple cells (or uplink carriers) may be a new DCI format (such as DCI format 0_3, but not limited to this) or an enhancement of the existing DCI format (such as DCI format 0_1 ​​and DCI format 0_2).

[0006] However, since the existing methods for triggering / activating / deactivating aperiodic CSI reporting and PUSCH-based SP CSI reporting are designed based on the assumption that the DCI format can only schedule the PUSCH of one cell (or uplink carrier), they cannot be directly applied to the case where the DCI format can schedule the PUSCH of multiple cells (or uplink carriers).

[0007] To address at least one of the above problems, an embodiment of the present application provides a method and apparatus for reporting channel state information to support non-periodic CSI reporting and semi-persistent CSI reporting based on PUSCH when the DCI format can schedule PUSCH of multiple cells (or uplink carriers).

[0008] According to one aspect of an embodiment of the present application, an aperiodic CSI reporting apparatus is provided, the apparatus including:

[0009] a receiving unit configured to receive a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic CSI reporting;

[0010] A sending unit, which sends a CSI report.

[0011] According to another aspect of an embodiment of the present application, a device for receiving a CSI report is provided, the device including:

[0012] a transmitting unit configured to transmit a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic CSI reporting;

[0013] A receiving unit receives a CSI report.

[0014] According to another aspect of an embodiment of the present application, a semi-persistent CSI reporting apparatus is provided, the apparatus comprising:

[0015] a receiving unit configured to receive a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent CSI reporting;

[0016] A sending unit, which sends a CSI report.

[0017] According to another aspect of an embodiment of the present application, a device for receiving a CSI report is provided, the device including:

[0018] a transmitting unit configured to transmit a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent CSI reporting;

[0019] A receiving unit receives a CSI report.

[0020] According to another aspect of an embodiment of the present application, a device for releasing or deactivating semi-persistent CSI reporting is provided, the device including:

[0021] a receiving unit configured to receive a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format releases or deactivates semi-persistent CSI reporting;

[0022] A processing unit deactivates semi-persistent CSI reporting.

[0023] According to another aspect of an embodiment of the present application, a device for releasing or deactivating semi-persistent CSI reporting is provided, the device including:

[0024] A sending unit is configured to send a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format releases or deactivates semi-persistent CSI reporting.

[0025] One of the beneficial effects of the embodiments of the present application is that according to the embodiments of the present application, aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting are implemented when the DCI format can schedule PUSCHs of multiple cells.

[0026] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0027] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0028] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0030] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0031] FIG2 is a schematic diagram of the timing relationship of aperiodic CSI reporting;

[0032] FIG3 is a schematic diagram of the timing relationship of SP CSI reporting based on PUSCH;

[0033] FIG4 is a schematic diagram of an aperiodic CSI reporting method according to an embodiment of the present application;

[0034] 5 to 12 are schematic diagrams of examples of aperiodic CSI reporting;

[0035] FIG13 is a schematic diagram of a method for receiving a CSI report according to an embodiment of the present application;

[0036] FIG14 is a schematic diagram of a semi-persistent CSI reporting method according to an embodiment of the present application;

[0037] Figures 15 to 22 are schematic diagrams of examples of semi-persistent CSI reporting;

[0038] FIG23 is a schematic diagram of a method for receiving a CSI report according to an embodiment of the present application;

[0039] FIG24 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application;

[0040] FIG25 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application;

[0041] FIG26 is a schematic diagram of an aperiodic CSI reporting apparatus according to an embodiment of the present application;

[0042] FIG27 is a schematic diagram of a CSI report receiving apparatus according to an embodiment of the present application;

[0043] FIG28 is a schematic diagram of a semi-persistent CSI reporting apparatus according to an embodiment of the present application;

[0044] FIG29 is a schematic diagram of a CSI report receiving apparatus according to an embodiment of the present application;

[0045] FIG30 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application;

[0046] FIG31 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application;

[0047] FIG32 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application;

[0048] Figure 33 is a schematic diagram of the structure of the network device of an embodiment of the present application. DETAILED DESCRIPTION

[0049] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0050] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0051] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0052] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed ​​Packet Access (HSPA, High-Speed ​​Packet Access), 5G (5Generation) New Radio (NR, New Radio), etc.

[0053] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0054] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0055] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0056] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0057] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0058] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0059] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0060] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0061] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation taking a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and a terminal device 102. For simplicity, FIG1 illustrates only one network device and one terminal device as an example, but the embodiments of the present application are not limited thereto.

[0062] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal device 102. For example, these services may include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC).

[0063] In NR, the overall process of UE reporting CSI includes the following steps:

[0064] The gNB sends CSI-RS and / or SSB;

[0065] The UE measures the CSI-RS and / or DMRS of the PBCH (in the SSB), including channel state measurement, interference measurement, and L1-RSRP measurement, and then reports the measurement results to the gNB.

[0066] The gNB performs beam management and scheduling based on the CSI measurement results reported by the UE.

[0067] In NR, the overall CSI framework includes CSI resource settings and CSI reporting settings. The CSI resource settings define the CSI-RS structure, occupied bandwidth, and time domain characteristics (periodic, semi-persistent, or aperiodic). The CSI reporting settings define the CSI resource settings associated with the measurement report, the time domain characteristics of the report (periodic, semi-persistent, or aperiodic), the number of reports, and the frequency domain configuration of the report.

[0068] Currently, CSI reporting types include periodic CSI reporting, aperiodic CSI reporting, semi-persistent (SP) CSI reporting on PUCCH, and semi-persistent CSI reporting on PUSCH. Both aperiodic CSI reporting and SP CSI reporting on PUSCH are triggered or activated by a DCI format and the CSI report is sent on PUSCH.

[0069] The inventors discovered that since the existing methods for triggering / activating / deactivating aperiodic CSI reporting and PUSCH-based SP CSI reporting are designed based on the assumption that the DCI format can only schedule the PUSCH of one cell (or uplink carrier), they cannot be directly applied to situations where the DCI format can schedule the PUSCH of multiple cells (or uplink carriers).

[0070] To address at least one of the above problems, an embodiment of the present application provides a method and apparatus for reporting channel state information.

[0071] In the embodiment of the present application, DCI format 0_X refers to a DCI format for supporting PUSCH scheduling of multiple cells (or uplink carriers) through one DCI. There is no limitation on the name of the DCI format, and it can be DCI format 0_1, and / or DCI format 0_2, and / or DCI format 0_3, and so on.

[0072] For example, the network device configures the cells that can be scheduled by DCI format 0_X through higher-layer signaling or parameters. For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier. Depending on the configuration of the higher-layer signaling or parameters, the value of this field corresponds to one or more cells and / or uplink carriers. Thus, when this field indicates multiple cells and / or uplink carriers, scheduling of multiple cells and / or uplink carriers can be achieved through a single DCI.

[0073] In some embodiments, DCI format 0_X includes one or more fields for indicating a cell and / or an uplink carrier.

[0074] In some embodiments, a cell may be configured with one uplink carrier, namely, (N)UL ((normal)UL), or two uplink carriers, namely, (N)UL and SUL (supplementary UL).

[0075] In some embodiments, DCI format 0_X includes both a field for indicating a cell and a field for indicating an uplink carrier. That is, the above-mentioned field for indicating a cell and / or an uplink carrier may include a field for indicating a cell and a field for indicating an uplink carrier within a cell. For example, if one or more cells in the cells that can be scheduled by DCI format 0_X include 2 uplink carriers (e.g., (N)UL and SUL), DCI format 0_X may include one or more fields for indicating a cell (e.g., carrier indicator) and one or more fields for indicating an uplink carrier within a cell (e.g., UL-SUL indicator) to indicate on which uplink carrier the scheduled PUSCH is. Wherein, in the case of including multiple fields for indicating an uplink carrier within a cell, different fields for indicating an uplink carrier within a cell correspond to different cells or different cell sets / cell groups.

[0076] In some embodiments, DCI format 0_X includes only one field for indicating a cell and / or an uplink carrier. For example, if all cells that can be scheduled by DCI format 0_X include only one uplink carrier, DCI format 0_X may include only a field for indicating the cell, or in other words, only a field for indicating the uplink carrier. In this case, indicating a cell is equivalent to indicating the uplink carrier of the cell.

[0077] In the embodiment of the present application, “scheduling a cell and / or an uplink carrier” is equivalent to “scheduling an uplink transmission (eg, PUSCH) on the cell and / or the uplink carrier”.

[0078] In the embodiments of the present application, a plurality refers to more than one, or two or more.

[0079] In the embodiment of the present application, “DCI format 0_X is scrambled by a certain RNTI” includes “CRC (cyclic redundancy check) check bits of the DCI format are scrambled by the RNTI”.

[0080] In the embodiment of the present application, a DCI format “used to schedule PUSCHs on one or more cells and / or uplink carriers” means: the DCI format can / is capable of / has the ability to schedule PUSCHs on more than one cell and / or uplink carrier at a time / simultaneously, where the more than one cell and / or uplink carriers respectively have one or more scheduled PUSCHs; and the DCI format can / is capable of / has the ability to schedule PUSCHs on one cell and / or uplink carrier at a time, where the one cell and / or uplink carrier has one or more scheduled PUSCHs; or means: the DCI format can / is capable of / has the ability to schedule PUSCHs on more than one cell and / or uplink carrier at a time / simultaneously, where the more than one cell and / or uplink carriers respectively have one or more scheduled PUSCHs; and the DCI format cannot / is not capable of / has no ability to schedule PUSCHs on only one cell and / or uplink carrier at a time.

[0081] The embodiments of the present application are described below with reference to the accompanying drawings and specific implementation methods.

[0082] Embodiments of the first aspect

[0083] An embodiment of the present application provides a non-periodic CSI reporting method, which is applied on the terminal device side.

[0084] FIG4 is a schematic diagram of an aperiodic CSI reporting method according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0085] 401. A terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, where the DCI format requests or triggers aperiodic CSI reporting.

[0086] 402. The terminal device sends a CSI report.

[0087] It is worth noting that FIG4 above is merely a schematic illustration of an embodiment of the present application, using a terminal device as an example, but the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, other operations may be added or some operations may be reduced, and the objects of the aforementioned operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG4 above.

[0088] According to the embodiment of the present application, aperiodic CSI reporting is implemented when the DCI format is capable of scheduling PUSCHs of multiple cells.

[0089] In the above embodiment, the aperiodic CSI reporting based on DCI format 0_X includes the following steps:

[0090] The base station configures one or more trigger states (trigger state list) through higher-layer signaling or parameters (e.g., CSI-AperiodicTriggerStateList), and each trigger state corresponds to or is associated with one or more CSI report configurations;

[0091] The UE monitors DCI format 0_X and determines which triggering state (CSI aperiodic triggering state) is triggered according to the value of the CSI request field therein.

[0092] In addition, possible CSI-RS configurations for aperiodic CSI reporting include aperiodic CSI-RS, periodic CSI-RS, and semi-persistent CSI-RS. The timing relationship of aperiodic CSI reporting is shown in Figure 2, where the reference signal used for measurement is omitted.

[0093] In this embodiment, the trigger state refers to the CSI aperiodic trigger state, and the CSI reporting refers to the aperiodic CSI reporting.

[0094] In an embodiment of the present application, the high-level parameters used to configure the trigger status list are specific to DCI format 0_X, or shared by DCI format 0_X and another DCI format. Specific means that it is only for DCI format 0_X. Shared means that, when monitoring another DCI format for triggering aperiodic CSI reporting is configured, for the other DCI format, DCI format 0_X and the other DCI format are simultaneously or not simultaneously targeted. Simultaneously means that, when monitoring DCI format 0_X (and DCI format 0_X is used to trigger aperiodic CSI reporting) and another DCI format for triggering aperiodic CSI reporting are configured, the high-level parameters are for both DCI format 0_X and the other DCI format. "Not at the same time" means that the two DCI formats cannot be configured to both require monitoring, or cannot be configured to both require monitoring and be used to trigger aperiodic CSI reporting. Furthermore, in a specific DCI format configuration, the high-layer parameter only targets DCI format 0_X or the other DCI format, but not both DCI format 0_X and the other DCI format.

[0095] In the embodiments of the present application, in some embodiments, the above-mentioned DCI format schedules a PUSCH on a cell and / or uplink carrier, and the terminal device sends the above-mentioned CSI report on the cell and / or uplink carrier.

[0096] In other embodiments, when the aforementioned DCI format requests or triggers aperiodic CSI reporting, the DCI format schedules the PUSCH on only one cell and / or uplink carrier. Consequently, the terminal device can send CSI reports on this single cell and / or uplink carrier. This maximizes the reuse of existing methods, reduces complexity, and lowers device upgrade costs.

[0097] For example, the DCI format includes a field (or information field) for requesting or triggering CSI reporting, such as a CSI request field, and the value of the field corresponds to a CSI non-periodic trigger state. When the value of the field corresponds to a CSI non-periodic trigger state, the DCI format only schedules the PUSCH on one cell and / or uplink carrier, and the terminal device sends the corresponding CSI report on the PUSCH of the one cell and / or uplink carrier.

[0098] In the above embodiment, the length of the CSI request field is N TS (including N TSbits), which is configured by the network device through high-level parameters (such as reportTriggerSize), and can indicate a maximum of When the network device does not exceed the CSI aperiodic trigger state configured by the above-mentioned high-level signaling or parameters, The CSI request field directly indicates which state is requested. When the number of triggering states is not more than 1, the network device also selects no more than 1 through MAC CE (eg, CSI aperiodic trigger state subset selection MAC CE). The CSI non-periodic trigger state is selected, and the CSI request field indicates which state is requested. There is a certain delay between the terminal device receiving the above MAC CE command and the command taking effect. If the HARQ-ACK corresponding to the PDSCH carrying the MAC CE is sent on time slot n, the effective time slot selected by the CSI non-periodic trigger state is

[0099] In the above embodiment, in some implementation methods, the length of the above CSI request field is configured by a higher-layer parameter, which may be specific to DCI format 0_X or shared by DCI format 0_X and another DCI format. Specific means that it is only for DCI format 0_X. Shared means that, when monitoring another DCI format for triggering CSI reporting is configured, the higher-layer parameter is configured for the other DCI format, either simultaneously or at different times. Simultaneously means that, when monitoring DCI format 0_X (and DCI format 0_X is used to trigger CSI reporting) and another DCI format for triggering CSI reporting are configured, the higher-layer parameter is configured for both DCI format 0_X and the other DCI format. "Not simultaneously" means that the two DCI formats cannot be configured to both require monitoring, or cannot be configured to both require monitoring and be used to trigger CSI reporting. Furthermore, in a specific DCI format configuration, the high-layer parameter only targets DCI format 0_X or the other DCI format, and does not target both DCI format 0_X and the other DCI format.

[0100] In the above embodiment, in other implementations, the length of the above CSI request field is not determined by high-level parameters, but is determined by the terminal device according to the number of trigger states in the corresponding configured trigger state list.

[0101] In some further embodiments, the above-mentioned DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; the terminal device sends a CSI report on the cell and / or uplink carrier indicated by the field.

[0102] For example, DCI format 0_X includes fields for indicating cells and / or uplink carriers, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. However, when DCI format 0_X requests or triggers aperiodic CSI reporting, this field only indicates one cell and / or uplink carrier.

[0103] FIG5 is a schematic diagram of an example of aperiodic CSI reporting.

[0104] As shown in Figure 5, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, the CSI request field indicates the trigger status, and the carrier indication field indicates the cell and / or uplink carrier. The left side of Figure 5 illustrates the case where the indicated cell is a Pcell, and the right side of Figure 5 illustrates the case where the indicated cell is an Scell. The terminal device can send a CSI report on the cell and / or uplink carrier indicated by the carrier indication field. In this example, the PUSCH carries or does not carry UL-SCH data.

[0105] FIG6 is a schematic diagram of another example of aperiodic CSI reporting.

[0106] As shown in Figure 6, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, the CSI request field indicates the triggered status, and the carrier indication field indicates the cell and / or uplink carrier. The left side of Figure 6 illustrates the case where the indicated cell is a Pcell, and the right side of Figure 6 illustrates the case where the indicated cell is an Scell. The terminal device can send a CSI report on the cell and / or uplink carrier indicated by the carrier indication field. In this example, the PUSCH carries or does not carry UL-SCH data. In this example, unlike the example of Figure 5, the DCI format 0_X schedules two PUSCHs.

[0107] In some further embodiments, the terminal device sends the CSI report on a default cell and / or uplink carrier configured by signaling for sending the CSI report.

[0108] In the above embodiment, in some implementation manners, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0109] For example, DCI format 0_X includes fields for indicating the scheduled cell and / or uplink carrier, such as a carrier indication field, which can indicate one or more cells and / or uplink carriers. However, when DCI format 0_X requests or triggers non-periodic CSI reporting, this field does not indicate the cell and / or uplink carrier. For example, the bits of this field are set to a specific value, and the specific value does not correspond to any cell and / or uplink carrier. The terminal device sends the CSI report in the default cell and / or uplink carrier configured by signaling (for example, RRC and / or MAC CE and / or DCI, etc.) for sending the CSI report.

[0110] FIG7 is a schematic diagram of an example of aperiodic CSI reporting.

[0111] As shown in Figure 7, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, the CSI request field indicates the triggered status, and the carrier indication field does not indicate the cell and / or uplink carrier. The left side of Figure 7 illustrates the case where the indicated cell is a Pcell, and the right side of Figure 7 illustrates the case where the indicated cell is an Scell. The terminal device can send a CSI report on the default cell and / or uplink carrier configured by signaling. In this example, the PUSCH carries or does not carry UL-SCH data.

[0112] FIG8 is a schematic diagram of another example of aperiodic CSI reporting.

[0113] As shown in Figure 8, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, the CSI request field indicates the triggered status, and the carrier indication field does not indicate the cell and / or uplink carrier. The left side of Figure 8 illustrates the case where the indicated cell is a Pcell, and the right side of Figure 8 illustrates the case where the indicated cell is an Scell. The terminal device can send a CSI report on the default cell and / or uplink carrier configured by signaling. In this example, the PUSCH carries or does not carry UL-SCH data. In this example, unlike the example of Figure 7, the DCI format 0_X schedules two PUSCHs.

[0114] In some other implementations, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores this field.

[0115] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. When DCI format 0_X requests or triggers aperiodic CSI reporting, the terminal device ignores this field. The terminal device sends a CSI report in the default cell and / or uplink carrier configured by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.) for sending the CSI report.

[0116] In some further embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0117] In the above implementation manner, in some examples, the DCI format does not include the above field for indicating the cell and / or uplink carrier when requesting or triggering aperiodic CSI reporting.

[0118] For example, when DCI format 0_X does not request or trigger non-periodic CSI reporting, the DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which can indicate one or more cells and / or uplink carriers. When DCI format 0_X requests or triggers non-periodic CSI reporting, the DCI format 0_X does not include the carrier indication field. The field for requesting or triggering CSI reporting (CSI request field) precedes the field for indicating the cell and / or uplink carrier (carrier indication field). The terminal device sends a CSI report on the cell and / or uplink carrier configured by default or by signaling (such as RRC and / or MAC CE and / or DCI, etc.) for sending the CSI report.

[0119] In the aforementioned embodiments, the default cell for sending CSI reports may be a Pcell (primary cell) or a Pscell (primary secondary cell) or a PUCCH Scell ​​(Physical Uplink Control Channel Secondary Cell), but the present application is not limited thereto.

[0120] If the default cell includes only one uplink carrier, the default uplink carrier is the uplink carrier of the cell; if the default cell includes more than one uplink carrier, for example, including NUL and SUL, on which uplink carrier of the cell the CSI report is sent is, for example, indicated by a field (for example, UL-SUL indicator) in DCI format 0_X used to indicate an uplink carrier in the cell, or the CSI report is sent on the default uplink carrier of the cell, where the default uplink carrier is, for example, NUL, SUL, or a carrier on which the PUCCH is configured among the more than one uplink carriers.

[0121] In an embodiment of the present application, in some other embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; the terminal device sends a CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0122] For example, when DCI format 0_X triggers aperiodic CSI reporting, it schedules PUSCH on one or more cells and / or uplink carriers. When scheduling PUSCH on multiple cells and / or uplink carriers, the terminal device sends a CSI report on the PUSCH of one of the cells and / or uplink carriers. When scheduling PUSCH on one cell and / or uplink carrier, the terminal device sends the CSI report using the same method as the aforementioned embodiment. This allows for a certain degree of reuse of existing methods, and because network devices can schedule UL-SCH data transmission for multiple cells using the same DCI while triggering CSI reporting, scheduling flexibility and data transmission throughput can be increased.

[0123] In the above embodiment, the DCI format may include a field (or information field) for requesting or triggering CSI reporting, such as a CSI request field, and the value of the field corresponds to a CSI non-periodic trigger state. When the value of the field corresponds to a CSI non-periodic trigger state, the DCI schedules a PUSCH on one or more cells and / or uplink carriers, and the terminal device sends a corresponding CSI report on the PUSCH of a cell and / or uplink carrier.

[0124] The length of this field can be configured by a high-level parameter or determined by the terminal device based on the number of trigger states in the configured trigger state list. Here, the high-level parameter can be specific to the DCI format or shared by the DCI format and other DCI formats. Since the CSI request field has been described in the previous embodiment, its content is merged here and will not be repeated here.

[0125] In some embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports. That is, the terminal device sends the CSI report in the default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0126] In the above embodiment, the DCI format may further include a field for indicating a cell and / or an uplink carrier. The above-mentioned default or signaling-configured cell and / or uplink carrier for sending the CSI report may be within the range of one or more cells and / or uplink carriers indicated by the field, or may not be within the range of one or more cells and / or uplink carriers indicated by the field.

[0127] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which can indicate one or more cells and / or uplink carriers. When DCI format 0_X requests or triggers non-periodic CSI reporting, if the field indicates multiple cells and / or uplink carriers, the terminal device sends a CSI report on the PUSCH on one of the cells and / or uplink carriers. One of the cells and / or uplink carriers is the default cell and / or uplink carrier configured by signaling (such as RRC and / or MAC CE and / or DCI, etc.) for sending the CSI report.

[0128] FIG9 is a schematic diagram of an example of aperiodic CSI reporting.

[0129] As shown in Figure 9, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, the CSI request field indicates the triggered status, and the carrier indication field indicates the cell and / or uplink carrier. The left side of Figure 9 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 9 illustrates the case where the indicated cells are two Scells. The terminal device can send CSI reports on the default cell and / or uplink carrier configured by signaling. In this example, the PUSCH carries or does not carry UL-SCH data. In addition, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other does not carry a CSI report.

[0130] FIG10 is a schematic diagram of another example of aperiodic CSI reporting.

[0131] As shown in Figure 10, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, the CSI request field indicates the triggered status, and the carrier indication field indicates the cell and / or uplink carrier. The left side of Figure 10 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 10 illustrates the case where the indicated cells are two Scells. The terminal device can send CSI reports on the default cell and / or uplink carrier configured by signaling. In this example, the PUSCH carries or does not carry UL-SCH data. In addition, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other does not carry a CSI report. Unlike the example of Figure 9, in the example of Figure 10, the two PUSCHs are staggered in the time domain.

[0132] In the examples of Figures 9 and 10 above, the case where a cell and / or uplink carrier has multiple PUSCHs is not shown, but this embodiment of the present application does not exclude this case. That is, Figures 9 and 10 only show that there is only one PUSCH on a cell and / or uplink carrier. In the embodiments of the present application, a cell and / or uplink carrier may also have other PUSCHs.

[0133] In the above embodiment, the default cell for sending the CSI report may be: the cell with the smallest serving cell identification number among the scheduled cells; and / or the cell where the first PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain among the scheduled PUSCHs is located; and / or the cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the aperiodic CSI reporting timing requirements in the time domain among the scheduled PUSCHs is located. The present application is not limited to this, and the default cell for sending the CSI report may also be other cells defined according to other rules.

[0134] In the above embodiment, the default cell for sending the CSI report may be a Pcell, a PScell, or a PUCCH Scell, but the present application is not limited thereto.

[0135] In other embodiments, the terminal device sends the CSI report on the default PUCCH.

[0136] In the above embodiment, the DCI format may further include a field for indicating a cell and / or an uplink carrier.

[0137] For example, DCI format 0_X includes fields for indicating cells and / or uplink carriers, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. When DCI format 0_X requests or triggers aperiodic CSI reporting, if the field indicates multiple cells and / or uplink carriers, the terminal device sends the CSI report on one of the default PUSCHs.

[0138] FIG11 is a schematic diagram of an example of aperiodic CSI reporting.

[0139] As shown in Figure 11, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, the CSI request field indicates the triggered status, the carrier indication field indicates the cell and / or uplink carrier, the left side of Figure 11 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 11 illustrates the case where the indicated cells are two Scells. The terminal device can send a CSI report on the default PUSCH. In this example, the PUSCH carries or does not carry UL-SCH data. In addition, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other does not carry a CSI report. Unlike the example of Figure 9, in the example of Figure 11, the two PUSCHs are staggered in the time domain.

[0140] In the example of FIG11 above, the case where a cell and / or uplink carrier has multiple PUSCHs is not shown, but this embodiment of the present application does not exclude this case. In other words, FIG11 only shows that there is only one PUSCH on a cell and / or uplink carrier. In the embodiment of the present application, a cell and / or uplink carrier may also have other PUSCHs.

[0141] In the above embodiment, the default PUSCH may be: the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells; and / or, the first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirements among the scheduled PUSCHs; and / or, the PUSCH of the cell with the smallest serving cell identification number among the cells in which the first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirements is located among the scheduled PUSCHs. The present application is not limited thereto, and the default PUSCH may also be another PUSCH defined according to other rules.

[0142] In the above embodiment, the cell where the default PUSCH is located may be a Pcell, a PScell, or a PUCCH Scell, but the present application is not limited thereto.

[0143] In the embodiments of the present application, in some further embodiments, the DCI format schedules PUSCH on more than one cell and / or uplink carrier; the terminal device sends a CSI report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

[0144] For example, when DCI format 0_X triggers non-periodic CSI reporting, it schedules PUSCH on one or more cells and / or uplink carriers. When scheduling PUSCH on multiple cells and / or uplink carriers, the terminal device sends a CSI report on the PUSCH of one, some, or all of the cells and / or uplink carriers; when scheduling PUSCH on one cell and / or uplink carrier, the terminal device uses the same method as the above embodiment to send a CSI report. Therefore, since the network device triggers the terminal device to send a CSI report in one or more or all of the cells and / or uplink carriers through the same DCI, and can schedule UL-SCH data transmission of multiple cells through the same DCI while triggering CSI reporting, when the bandwidth of each carrier is small, the CSI feedback efficiency can be improved, and the scheduling flexibility and data transmission throughput can be increased.

[0145] In the above embodiment, the DCI format may include a field for indicating a cell and / or an uplink carrier, where the field indicates more than one cell and / or uplink carrier.

[0146] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. In the case where multiple cells and / or uplink carriers are indicated to be scheduled, the terminal device sends a CSI report on the PUSCH of more than one cell and / or uplink carrier.

[0147] In the above embodiment, the contents of CSI reports on different PUSCHs may be the same or different.

[0148] In some embodiments, the above-mentioned DCI format includes a field for requesting or triggering CSI reporting, the CSI reports on different PUSCHs are the same, and / or, different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or, different PUSCHs are used to carry different parts of the CSI report.

[0149] For example, DCI format 0_X includes a field for requesting or triggering CSI, such as a CSI request field, and the CSI reports on different PUSCHs are the same (repeated), and / or different PUSCHs are used to carry different CSI reports corresponding to the triggering status indicated by the field (wherein one triggering status may correspond to one or more CSI reports), and / or different PUSCHs are used to carry different parts of the CSI report (for example, Part 1 and Part 2, respectively).

[0150] In some implementations, the DCI format includes multiple fields for requesting or triggering CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0151] For example, DCI format 0_X includes multiple fields for requesting or triggering CSI, such as a CSI request field, and different fields correspond to different cells and / or uplink carriers. That is, different PUSCHs are used to carry CSI reports corresponding to the triggering states indicated by different fields for requesting or triggering CSI.

[0152] FIG12 is a schematic diagram of an example of aperiodic CSI reporting.

[0153] As shown in Figure 12, in this example, the CRC of DCI format 0_X is scrambled by C-RNTI or MCS-C-RNTI, one or more CSI request fields indicate the triggered status, and the carrier indication field indicates the cell and / or uplink carrier. The left side of Figure 12 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 12 illustrates the case where the indicated cells are two Scells. The terminal device can send CSI reports on two cells and / or uplink carriers, and the contents of the CSI reports on the two cells and / or uplink carriers can be the same or different. In this example, the PUSCH carries or does not carry UL-SCH data. In this example, the DCI format 0_X schedules two PUSCHs.

[0154] In an embodiment of the present application, the CRC of the DCI format may be scrambled by C-RNTI or MCS-C-RNTI, but the present application is not limited thereto.

[0155] In an embodiment of the present application, the terminal device may also receive configuration information for configuring the terminal device to monitor the DCI format in a UE-specific search space. The present application does not limit the specific configuration method. For relevant content of the configuration information, reference may be made to related technologies.

[0156] In an embodiment of the present application, the terminal device may also receive configuration information for configuring whether the above DCI format supports triggering CSI reporting or whether the above DCI format is used to trigger CSI reporting. This application does not limit the specific configuration method. For relevant content of the configuration information, reference may be made to related technologies.

[0157] In an embodiment of the present application, the terminal device may also receive configuration information for configuring cells and / or uplink carriers that can be scheduled by the above-mentioned DCI format. This application does not limit the specific configuration method. For relevant content of the configuration information, reference may be made to related technologies.

[0158] In the embodiment of the present application, the above-mentioned more than one uplink carriers may belong to different cells respectively, or at least two of the above-mentioned more than one uplink carriers may belong to different cells, but the present application is not limited thereto.

[0159] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0160] It can be seen from the above embodiment that aperiodic CSI reporting is achieved when the DCI format is capable of scheduling PUSCHs of multiple cells.

[0161] Embodiments of the second aspect

[0162] An embodiment of the present application provides a method for receiving a CSI report, which is applied to a network device side and is a processing on the network device side corresponding to the method of the embodiment of the first aspect, wherein the same contents as those of the embodiment of the first aspect are not repeated.

[0163] FIG13 is a schematic diagram of a method for receiving a CSI report according to an embodiment of the present application. As shown in FIG13 , the method includes:

[0164] 1301. A network device sends a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, where the DCI format requests or triggers aperiodic CSI reporting.

[0165] 1302. The network device receives a CSI report.

[0166] It is worth noting that FIG13 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG13 above.

[0167] According to the embodiment of the present application, aperiodic CSI reporting is implemented when the DCI format is capable of scheduling PUSCHs of multiple cells.

[0168] In some embodiments, the DCI format schedules a PUSCH on a cell and / or uplink carrier, and the network device receives the CSI report on the cell and / or uplink carrier.

[0169] In some embodiments, when the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules a PUSCH on one cell and / or uplink carrier.

[0170] In some embodiments, the DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; the network device receives a CSI report on the cell and / or uplink carrier indicated by the field.

[0171] In some embodiments, the network device receives the CSI report on a default cell and / or uplink carrier configured by signaling for receiving the CSI report.

[0172] In the above embodiment, in some implementation manners, the above DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0173] In the above embodiment, in some other implementations, the above DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores the field.

[0174] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0175] In some embodiments, the DCI format does not include a field for indicating a cell and / or uplink carrier when requesting or triggering aperiodic CSI reporting.

[0176] In some embodiments, the default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0177] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; and the network device receives the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0178] In the aforementioned embodiments, the DCI format may include a field for requesting or triggering CSI reporting, and the value of the field corresponds to a CSI aperiodic triggering state.

[0179] In the above embodiment, the length of the above field can be configured by a high-level parameter or determined by the terminal device according to the number of trigger states in the configured trigger state list. The above-mentioned high-level parameter can be specific to the DCI format or shared by the DCI format and other DCI formats.

[0180] In some embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0181] In the above embodiment, the default cell for sending the CSI report may be at least one of the following:

[0182] The cell with the smallest serving cell identification number among the scheduled cells;

[0183] The cell where the first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirements is located among the scheduled PUSCHs;

[0184] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0185] In the above embodiment, the default cell for sending the CSI report may be: a Pcell, a PScell, or a PUCCH Scell.

[0186] In some embodiments, the network device receives the CSI report on a default PUSCH.

[0187] In the above embodiment, the default PUSCH may be at least one of the following:

[0188] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0189] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0190] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0191] In the above embodiment, the cell where the default PUSCH is located may be: a Pcell, a PScell, or a PUCCH Scell.

[0192] In some embodiments, the DCI format includes fields for indicating a cell and / or an uplink carrier.

[0193] In the above embodiment, the aforementioned default cell and / or uplink carrier for sending CSI reports or configured by signaling is within the range of one or more cells and / or uplink carriers indicated by the above field, or is not within the range of one or more cells and / or uplink carriers indicated by the above field.

[0194] In some embodiments, the DCI format schedules PUSCHs on more than one cell and / or uplink carrier; the network device receives CSI reports on one or more cells and / or uplink carriers.

[0195] In the above embodiment, the DCI format may include a field for indicating a cell and / or an uplink carrier, where the field indicates more than one cell and / or uplink carrier.

[0196] In the above embodiment, the contents of CSI reports on different PUSCHs may be the same or different.

[0197] In the above embodiment, the above DCI format may include a field for requesting or triggering CSI reporting, the CSI reports on different PUSCHs are the same, and / or, different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or, different PUSCHs are used to carry different parts of the CSI report.

[0198] In the above embodiment, the DCI format may include multiple fields for requesting or triggering CSI reporting, and different PUSCHs are respectively used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0199] In the aforementioned embodiments, the CRC of the DCI format may be scrambled by the C-RNTI or the MCS-C-RNTI.

[0200] In the aforementioned embodiments, the network device may further send configuration information for configuring the terminal device to monitor the above-mentioned DCI format in a UE-specific search space.

[0201] In the aforementioned embodiments, the network device may further send configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.

[0202] In the aforementioned embodiments, the network device may further send configuration information for configuring cells and / or uplink carriers that can be scheduled by the DCI format.

[0203] In the aforementioned embodiments, the more than one uplink carriers may belong to different cells respectively, or at least two of the more than one uplink carriers may belong to different cells.

[0204] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0205] It can be seen from the above embodiment that aperiodic CSI reporting is achieved when the DCI format is capable of scheduling PUSCHs of multiple cells.

[0206] Embodiments of the third aspect

[0207] An embodiment of the present application provides a semi-continuous CSI reporting method, which is applied on the terminal device side.

[0208] FIG14 is a schematic diagram of a semi-persistent CSI reporting method according to an embodiment of the present application. As shown in FIG14 , the method includes:

[0209] 1401. A terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, where the DCI format triggers or activates semi-persistent CSI reporting.

[0210] 1402. The terminal device sends a CSI report.

[0211] It is worth noting that FIG14 above is merely a schematic illustration of an embodiment of the present application, using a terminal device as an example, but the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, other operations may be added or some operations may be reduced, and the objects of the aforementioned operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG14 above.

[0212] According to the embodiment of the present application, semi-persistent CSI reporting is implemented when the DCI format can schedule PUSCHs of multiple cells.

[0213] For SP CSI reporting on PUSCH, the base station configures the reporting period, slot offset, etc. through higher-layer signaling or parameters, and triggers it through the DCI format scrambled by SP-CSI-RNTI.

[0214] SP CSI reporting based on DCI format 0_X includes the following steps:

[0215] The base station configures one or more trigger states (trigger state list) through high-layer signaling or parameters (e.g., CSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state corresponds to / is associated with one or more CSI report configurations;

[0216] The UE monitors DCI format 0_X scrambled by the SP-CSI-RNTI and determines which trigger state (SP-CSI trigger state) is triggered or activated based on the value of the CSI request field. A CSI request field value of 0 corresponds to the first trigger state in the above list, a CSI request field value of 1 corresponds to the second trigger state in the above list, and so on.

[0217] Among them, the possible CSI-RS configurations for SP CSI reporting include periodic CSI-RS, semi-persistent CSI-RS, etc. The timing relationship of PUSCH-based SP CSI reporting is shown in Figure 3, in which the reference signal used for measurement is omitted.

[0218] In an embodiment of the present application, the high-level parameters used to configure the trigger status list are specific to DCI format 0_X, or shared by DCI format 0_X and another DCI format. Specific means that it is only for DCI format 0_X. Shared means that, when monitoring another DCI format for triggering SP-CSI reporting is configured, for the other DCI format, DCI format 0_X and the other DCI format are targeted at the same time or at different times. Simultaneously means that, when monitoring DCI format 0_X (and DCI format 0_X is used to trigger SP-CSI reporting) and another DCI format for triggering SP-CSI reporting are configured, the high-level parameters are targeted at both DCI format 0_X and the other DCI format. "Not at the same time" means that the two DCI formats cannot be configured to both require monitoring, or cannot be configured to both require monitoring and be used to trigger SP-CSI reporting. Furthermore, in the specific DCI format configuration, the high-level parameter only targets DCI format 0_X or the other DCI format, and does not target both DCI format 0_X and the other DCI format at the same time.

[0219] In this embodiment, the trigger state refers to a semi-persistent CSI trigger state, and the CSI reporting refers to semi-persistent CSI reporting.

[0220] In the embodiments of the present application, in some embodiments, the above-mentioned DCI format schedules a PUSCH on a cell and / or uplink carrier, and the terminal device sends the above-mentioned CSI report on the cell and / or uplink carrier.

[0221] In other embodiments, when the aforementioned DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules the PUSCH on one cell and / or uplink carrier. Consequently, the terminal device can send CSI reports on this single cell and / or uplink carrier. This maximizes the reuse of existing methods, reduces complexity, and lowers device upgrade costs.

[0222] For example, the DCI format includes a field (or information field) for triggering or activating CSI reporting, such as a CSI request field, and the value of the field corresponds to the CSI trigger state. When the value of the field corresponds to a CSI trigger state, the DCI format only schedules the PUSCH on one cell and / or uplink carrier, and the terminal device sends the corresponding CSI report on the PUSCH of the one cell and / or uplink carrier.

[0223] In the above embodiment, the length of the CSI request field is N TS (including N TS bits), which is configured by the network device through high-level parameters (such as reportTriggerSize), and can indicate a maximum of When the network device does not exceed the CSI trigger state through the above-mentioned high-level signaling or parameter configuration The CSI request field directly indicates which state is requested. When the network device further selects no more than The CSI trigger state is then indicated by the CSI request field, which state is requested. There is a certain delay between the terminal device receiving the above MAC CE command and the command taking effect. If the HARQ-ACK corresponding to the PDSCH carrying the MAC CE is sent on time slot n, the effective time slot selected by the CSI trigger state is

[0224] In the above embodiment, in some implementation methods, the length of the CSI request field is configured by a higher-layer parameter. The higher-layer parameter may be specific to DCI format 0_X or shared by DCI format 0_X and another DCI format. Specific means that it applies only to DCI format 0_X. Shared means that, when monitoring another DCI format for triggering CSI reporting is configured, the higher-layer parameter applies to both DCI format 0_X and the other DCI format simultaneously or at different times for the other DCI format. Simultaneously means that, when monitoring DCI format 0_X (and DCI format 0_X is used to trigger CSI reporting) and another DCI format for triggering CSI reporting are configured, the higher-layer parameter applies to both DCI format 0_X and the other DCI format. "Not simultaneously" means that the two DCI formats cannot be configured to both require monitoring, or cannot be configured to both require monitoring and be used to trigger CSI reporting. Furthermore, in a specific DCI format configuration, the high-layer parameter only targets DCI format 0_X or the other DCI format, and does not target both DCI format 0_X and the other DCI format.

[0225] In the above embodiment, in other implementations, the length of the above CSI request field is not determined by high-level parameters, but is determined by the terminal device according to the number of trigger states in the corresponding configured trigger state list.

[0226] In some further embodiments, the above-mentioned DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; the terminal device sends a CSI report on the cell and / or uplink carrier indicated by the field.

[0227] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. However, when semi-persistent CSI reporting is triggered or activated by DCI format 0_X, this field only indicates one cell and / or uplink carrier.

[0228] FIG15 is a schematic diagram of an example of semi-persistent CSI reporting.

[0229] As shown in Figure 15, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, the CSI request field indicates the trigger status, and the carrier indication field indicates the cell and / or uplink carrier. The left side of Figure 15 illustrates the case where the indicated cell is a Pcell, and the right side of Figure 15 illustrates the case where the indicated cell is an Scell. The terminal device can send a CSI report on the cell and / or uplink carrier indicated by the carrier indication field. As shown in Figure 15, the CSI report is semi-continuous. In this example, the PUSCH carries or does not carry UL-SCH data.

[0230] FIG16 is a schematic diagram of another example of semi-persistent CSI reporting.

[0231] As shown in Figure 16, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, the CSI request field indicates the triggered status, the carrier indication field indicates the cell and / or uplink carrier, the left side of Figure 16 illustrates the case where the indicated cell is Pcell, and the right side of Figure 16 illustrates the case where the indicated cell is Scell. The terminal device can send a CSI report on the cell and / or uplink carrier indicated by the carrier indication field. As shown in Figure 16, the CSI report is semi-continuous. In this example, the PUSCH carries or does not carry UL-SCH data. In this example, unlike the example of Figure 15, the DCI format 0_X schedules two PUSCHs.

[0232] In some further embodiments, the terminal device sends the CSI report on a default cell and / or uplink carrier configured by signaling for sending the CSI report.

[0233] In the above embodiment, in some implementation manners, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0234] For example, DCI format 0_X includes fields for indicating the scheduled cell and / or uplink carrier, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. However, when DCI format 0_X triggers or activates semi-persistent CSI reporting, this field does not indicate the cell and / or uplink carrier. For example, the bits of this field are set to a specific value, and the specific value does not correspond to any cell and / or uplink carrier. The terminal device sends a CSI report in the default cell and / or uplink carrier configured for sending the CSI report by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0235] FIG17 is a schematic diagram of an example of semi-persistent CSI reporting.

[0236] As shown in Figure 17, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, the CSI request field indicates the triggered status, and the carrier indication field does not indicate the cell and / or uplink carrier. The left side of Figure 17 illustrates the case where the indicated cell is a Pcell, and the right side of Figure 17 illustrates the case where the indicated cell is an Scell. The terminal device can send a CSI report on the default cell and / or uplink carrier configured by signaling. As shown in Figure 17, the CSI report is semi-continuous. In this example, the PUSCH carries or does not carry UL-SCH data.

[0237] FIG18 is a schematic diagram of another example of semi-persistent CSI reporting.

[0238] As shown in Figure 18, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, the CSI request field indicates the triggered status, and the carrier indication field does not indicate the cell and / or uplink carrier. The left side of Figure 18 illustrates the case where the indicated cell is a Pcell, and the right side of Figure 18 illustrates the case where the indicated cell is an Scell. The terminal device can send a CSI report on the default cell and / or uplink carrier configured by signaling. As shown in Figure 18, the CSI report is semi-continuous. In this example, the PUSCH carries or does not carry UL-SCH data. In this example, unlike the example of Figure 17, the DCI format 0_X schedules two PUSCHs.

[0239] In some other implementations, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores this field.

[0240] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. When DCI format 0_X triggers or activates semi-persistent CSI reporting, the terminal device ignores this field. The terminal device sends the CSI report in the default cell and / or uplink carrier configured by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.) for sending the CSI report.

[0241] In some further embodiments, the DCI format includes a field for triggering or activating CSI reporting, and the field for triggering or activating CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0242] In the above implementation manner, in some examples, the DCI format does not include the above field for indicating the cell and / or uplink carrier when triggering or activating semi-persistent CSI reporting.

[0243] For example, when DCI format 0_X does not trigger or activate semi-persistent CSI reporting, the DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which can indicate one or more cells and / or uplink carriers. When DCI format 0_X triggers or activates semi-persistent CSI reporting, the DCI format 0_X does not include the carrier indication field. The field for triggering or activating CSI reporting (CSI request field) precedes the field for indicating a cell and / or uplink carrier (carrier indication field). The terminal device sends a CSI report in the cell and / or uplink carrier configured by default or by signaling (such as RRC and / or MAC CE and / or DCI, etc.) for sending the CSI report.

[0244] In the aforementioned embodiments, the default cell for sending the CSI report may be a Pcell, a Pscell, or a PUCCH Scell, but the present application is not limited thereto.

[0245] Among them, if the default cell includes only one uplink carrier, the default uplink carrier is the uplink carrier of the cell; if the default cell includes more than one uplink carrier, for example, including NUL and SUL, the default uplink carrier is, for example, NUL, SUL or a carrier configured with PUCCH among the more than one uplink carriers.

[0246] In an embodiment of the present application, in some other embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; the terminal device sends a CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0247] For example, when DCI format 0_X triggers or activates semi-persistent CSI reporting, it schedules PUSCH on one or more cells and / or uplink carriers. When scheduling PUSCH on multiple cells and / or uplink carriers, the terminal device sends a CSI report on the PUSCH of one of the cells and / or uplink carriers. When scheduling PUSCH on one cell and / or uplink carrier, the terminal device sends the CSI report using the same method as the aforementioned embodiment. As a result, the existing method can be reused to a certain extent, and because the network device can schedule UL-SCH data transmission for multiple cells through the same DCI while triggering or activating semi-persistent CSI reporting, it can increase scheduling flexibility and data transmission throughput.

[0248] In the above embodiment, the DCI format may include a field (or information field) for triggering or activating CSI reporting, such as a CSI request field, and the value of the field corresponds to a CSI trigger state. When the value of the field corresponds to a CSI trigger state, the DCI schedules a PUSCH on one or more cells and / or uplink carriers, and the terminal device sends a corresponding CSI report on the PUSCH of a cell and / or uplink carrier.

[0249] The length of this field can be configured by a high-level parameter or determined by the terminal device based on the number of trigger states in the configured trigger state list. Here, the high-level parameter can be specific to the DCI format or shared by the DCI format and other DCI formats. Since the CSI request field has been described in the previous embodiment, its content is merged here and will not be repeated here.

[0250] In some embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports. That is, the terminal device sends the CSI report in the default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0251] In the above embodiment, the DCI format may further include a field for indicating a cell and / or an uplink carrier. The above-mentioned default or signaling-configured cell and / or uplink carrier for sending the CSI report may be within the range of one or more cells and / or uplink carriers indicated by the field, or may not be within the range of one or more cells and / or uplink carriers indicated by the field.

[0252] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. When DCI format 0_X triggers or activates semi-persistent CSI reporting, if the field indicates multiple cells and / or uplink carriers, the terminal device sends a CSI report on the PUSCH on one of the cells and / or uplink carriers. The one of the cells and / or uplink carriers is the default cell and / or uplink carrier configured by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.) for sending the CSI report.

[0253] FIG19 is a schematic diagram of an example of semi-persistent CSI reporting.

[0254] As shown in Figure 19, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, the CSI request field indicates the triggered status, the carrier indication field indicates the cell and / or uplink carrier, and the left side of Figure 19 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 19 illustrates the case where the indicated cells are two Scells. The terminal device can send CSI reports on the default cell and / or uplink carrier configured by signaling. As shown in Figure 19, the CSI report is semi-continuous. In this example, the PUSCH carries or does not carry UL-SCH data. In addition, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other does not carry a CSI report.

[0255] FIG20 is a schematic diagram of another example of semi-persistent CSI reporting.

[0256] As shown in Figure 20, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, the CSI request field indicates the triggered status, the carrier indication field indicates the cell and / or uplink carrier, the left side of Figure 20 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 20 illustrates the case where the indicated cells are two Scells. The terminal device can send CSI reports on the default cell and / or uplink carrier configured by signaling. As shown in Figure 20, the CSI report is semi-continuous. In this example, the PUSCH carries or does not carry UL-SCH data. In addition, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other does not carry a CSI report. Unlike the example of Figure 19, in the example of Figure 20, the two PUSCHs are staggered in the time domain.

[0257] In the examples of Figures 19 and 20 above, the case where a cell and / or uplink carrier has multiple PUSCHs is not shown, but this embodiment of the present application does not exclude this situation. That is, Figures 19 and 20 only show that there is only one PUSCH on a cell and / or uplink carrier. In the embodiments of the present application, a cell and / or uplink carrier may also have other PUSCHs.

[0258] In the above embodiment, the default cell for sending the CSI report may be: the cell with the smallest serving cell identification number among the scheduled cells; and / or the cell where the first PUSCH that meets the semi-persistent CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located; and / or the cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the semi-persistent CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located. The present application is not limited thereto, and the default cell for sending the CSI report may also be other cells defined according to other rules.

[0259] In the above embodiment, the default cell for sending the CSI report may be a Pcell, a PScell, or a PUCCH Scell, but the present application is not limited thereto.

[0260] In other embodiments, the terminal device sends the CSI report on the default PUCCH.

[0261] In the above embodiment, the DCI format may further include a field for indicating a cell and / or an uplink carrier.

[0262] For example, DCI format 0_X includes fields for indicating cells and / or uplink carriers, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. When DCI format 0_X triggers or activates semi-persistent CSI reporting, if the field indicates multiple cells and / or uplink carriers, the terminal device sends the CSI report on one of the default PUSCHs.

[0263] FIG21 is a schematic diagram of an example of semi-persistent CSI reporting.

[0264] As shown in Figure 21, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, the CSI request field indicates the triggered status, the carrier indication field indicates the cell and / or uplink carrier, and the left side of Figure 21 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 21 illustrates the case where the indicated cells are two Scells. The terminal device can send a CSI report on the default PUSCH. As shown in Figure 21, the CSI report is semi-continuous. In this example, the PUSCH carries or does not carry UL-SCH data. In addition, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other does not carry a CSI report. Unlike the example of Figure 19, in the example of Figure 21, the two PUSCHs are staggered in the time domain.

[0265] In the example of FIG. 21 above, the case where a cell and / or uplink carrier has multiple PUSCHs is not shown, but this embodiment of the present application does not exclude this case. In other words, FIG. 21 only shows that there is only one PUSCH on a cell and / or uplink carrier. In the embodiment of the present application, a cell and / or uplink carrier may also have other PUSCHs.

[0266] In the above embodiment, the default PUSCH may be: the PUSCH of the cell with the smallest serving cell identification number among the scheduled cells; and / or, the first PUSCH in the time domain among the scheduled PUSCHs that meets the semi-persistent CSI reporting timing requirements; and / or, the PUSCH of the cell with the smallest serving cell identification number among the cells in which the first PUSCH in the time domain that meets the semi-persistent CSI reporting timing requirements is located. The present application is not limited to this, and the default PUSCH may also be another PUSCH defined according to other rules.

[0267] In the above embodiment, the cell where the default PUSCH is located may be a Pcell, a PScell, or a PUCCH Scell, but the present application is not limited thereto.

[0268] In the embodiments of the present application, in some further embodiments, the DCI format schedules PUSCH on more than one cell and / or uplink carrier; the terminal device sends a CSI report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

[0269] For example, when DCI format 0_X triggers or activates semi-continuous CSI reporting, it schedules PUSCH on one or more cells and / or uplink carriers. When scheduling PUSCH on multiple cells and / or uplink carriers, the terminal device sends a CSI report on the PUSCH of one, part, or all of the cells and / or uplink carriers; when scheduling PUSCH on one cell and / or uplink carrier, the terminal device sends a CSI report using the same method as the aforementioned embodiment. Therefore, since the network device triggers the terminal device to send a CSI report in one or more or all of the cells and / or uplink carriers through the same DCI, and can schedule UL-SCH data transmission of multiple cells through the same DCI while triggering CSI reporting, when the bandwidth of each carrier is small, the CSI feedback efficiency can be improved, and the scheduling flexibility and data transmission throughput can be increased.

[0270] In the above embodiment, the DCI format may include a field for indicating a cell and / or an uplink carrier, where the field indicates more than one cell and / or uplink carrier.

[0271] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier, such as a carrier indication field, which may indicate one or more cells and / or uplink carriers. In the case where multiple cells and / or uplink carriers are indicated to be scheduled, the terminal device sends a CSI report on the PUSCH of more than one cell and / or uplink carrier.

[0272] In the above embodiment, the contents of CSI reports on different PUSCHs may be the same or different.

[0273] In some embodiments, the above-mentioned DCI format includes a field for triggering or activating CSI reporting, the CSI reports on different PUSCHs are the same, and / or, different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or, different PUSCHs are used to carry different parts of the CSI report.

[0274] For example, DCI format 0_X includes a field for triggering or activating CSI, such as a CSI request field, and the CSI reports on different PUSCHs are the same (repeated), and / or different PUSCHs are used to carry different CSI reports corresponding to the triggering status indicated by the field (wherein one triggering status may correspond to one or more CSI reports), and / or different PUSCHs are used to carry different parts of the CSI report (for example, Part 1 and Part 2, respectively).

[0275] In some implementations, the DCI format includes multiple fields for triggering or activating CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for triggering or activating CSI reporting.

[0276] For example, DCI format 0_X includes multiple fields for triggering or activating CSI, such as a CSI request field, and different fields correspond to different cells and / or uplink carriers. That is, different PUSCHs are used to carry CSI reports corresponding to the triggering status indicated by different fields for triggering or activating CSI.

[0277] FIG22 is a schematic diagram of an example of semi-persistent CSI reporting.

[0278] As shown in Figure 22, in this example, the CRC of DCI format 0_X is scrambled by SP-CSI-RNTI, one or more CSI request fields indicate the triggered status, and the carrier indication field indicates the cell and / or uplink carrier. The left side of Figure 22 illustrates the case where the indicated cells are Pcell and Scell, and the right side of Figure 22 illustrates the case where the indicated cells are two Scells. The terminal device can send CSI reports on two cells and / or uplink carriers, and the contents of the CSI reports on the two cells and / or uplink carriers can be the same or different. In this example, the PUSCH carries or does not carry UL-SCH data. In this example, the DCI format 0_X schedules two PUSCHs.

[0279] In Figures 15 to 22, the same SP-CSI reporting period on different cells and / or uplink carriers is taken as an example, but the present application is not limited to this. The SP-CSI reporting period on different cells and / or uplink carriers may be the same or different.

[0280] In an embodiment of the present application, the CRC of the DCI format may be scrambled by SP-CSI-RNTI, but the present application is not limited thereto.

[0281] In an embodiment of the present application, the terminal device may also determine / validate the validity of the above-mentioned DCI format for semi-persistent CSI activation.

[0282] In some embodiments, the terminal device determines / confirms (validates) the above validity based on the field used to indicate the cell and / or uplink carrier and / or the field used to indicate the HARQ (hybrid automatic repeat request) process ID and / or the field used to indicate the RV (redundancy version) in the above DCI format.

[0283] For example, the above-mentioned DCI format includes multiple fields for indicating the HARQ process ID, and the terminal device determines / confirms (validates) the above-mentioned validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0284] For another example, the above-mentioned DCI format includes multiple fields for indicating RV, and the terminal device determines / confirms (validates) the above-mentioned validity based on some or all of the fields for indicating RV in the DCI format.

[0285] For another example, the above DCI format includes one or more fields for indicating a cell and / or an uplink carrier, and the terminal device determines / validates the above validity based on some or all of the fields for the cell and / or uplink carrier in the DCI format.

[0286] In the aforementioned embodiments, the aforementioned embodiments for determining / validating the aforementioned validity may be used individually or in combination, and this application does not impose any limitation thereto. In the aforementioned embodiments, if the DCI format is confirmed to be invalid, the terminal device ignores or discards the DCI format. In other words, if the DCI format is confirmed to be invalid, the terminal device assumes that the CRC of the DCI format does not match, or assumes that the CRC check fails.

[0287] In the aforementioned embodiments, the above fields in the valid DCI format should meet certain conditions.

[0288] For example, the field used to indicate a cell and / or uplink carrier may indicate a cell and / or uplink carrier, and / or the cell and / or uplink carrier indicated by the field may be a Pcell, a PScell, or a PUCCH Scell. For another example, the field may be a specific value that does not correspond to any cell and / or uplink carrier.

[0289] In addition, if the DCI format 0_X includes multiple fields for indicating the HARQ process ID (e.g., the HARQ process number field) and / or multiple fields for indicating the RV (e.g., the Redundancy version field), the multiple fields should meet the following conditions. Alternatively, the field for indicating the cell and / or uplink carrier indicated by the field for indicating the cell and / or uplink carrier and the field for indicating the HARQ process ID and / or the field for indicating the RV should meet the following conditions. Optionally, the terminal device ignores other fields for indicating the HARQ process ID and / or the fields for indicating the RV.

[0290] These conditions refer to the configuration shown in the table below.

[0291] DCI format 0_1HARQ process numberset to all'0'sRedundancy versionset to'00'

[0292] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0293] It can be seen from the above embodiment that semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCHs of multiple cells.

[0294] Embodiments of the fourth aspect

[0295] An embodiment of the present application provides a method for receiving a CSI report, which is applied to a network device side and is a processing on the network device side corresponding to the method of the embodiment of the third aspect, wherein the contents identical to those of the embodiment of the third aspect are not repeated.

[0296] FIG23 is a schematic diagram of a method for receiving a CSI report according to an embodiment of the present application. As shown in FIG23 , the method includes:

[0297] 2301. The network device sends a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, where the DCI format triggers or activates semi-persistent CSI reporting.

[0298] 2302. The network device receives a CSI report.

[0299] It is worth noting that FIG23 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG23 above.

[0300] According to the embodiment of the present application, semi-persistent CSI reporting is implemented when the DCI format can schedule PUSCHs of multiple cells.

[0301] In some embodiments, the DCI format schedules a PUSCH on a cell and / or uplink carrier, and the network device receives a CSI report on the cell and / or uplink carrier.

[0302] In some embodiments, when the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules the PUSCH on one cell and / or uplink carrier.

[0303] In some embodiments, the DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; the network device receives a CSI report on the cell and / or uplink carrier indicated by the field.

[0304] In some embodiments, the network device receives the CSI report on a default cell and / or uplink carrier configured by signaling for sending the CSI report.

[0305] In the above embodiment, in some implementation manners, the above DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0306] In the above embodiment, in some implementation methods, the above DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores this field.

[0307] In the above embodiment, in some implementation methods, the above DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0308] In the above embodiment, the DCI format does not include a field for indicating a cell and / or an uplink carrier when triggering or activating semi-persistent CSI reporting.

[0309] In the above embodiment, the default cell for sending the CSI report may be: a Pcell, a PScell, or a PUCCH Scell.

[0310] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; the network device receives a CSI report on one of the one or more cells and / or uplink carriers.

[0311] In the aforementioned embodiments, the DCI format may include a field for requesting or triggering CSI reporting, and the value of the field corresponds to the CSI triggering state.

[0312] In the above embodiment, the length of the field may be configured by a higher-layer parameter, and the higher-layer parameter is specific to the above DCI format, or is shared by the above DCI format and other DCI formats.

[0313] In the above embodiment, the length of the field may also be determined by the terminal device according to the number of trigger states in the configured trigger state list.

[0314] In the aforementioned embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0315] For example, the default cell for sending the CSI report may be at least one of the following:

[0316] The cell with the smallest serving cell identification number among the scheduled cells;

[0317] The cell where the first PUSCH in the time domain that meets the semi-persistent CSI reporting timing requirements is located among the scheduled PUSCHs;

[0318] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the semi-persistent CSI reporting timing requirement in the time domain is located in the scheduled PUSCH.

[0319] For another example, the default cell for sending the CSI report may be: Pcell, PScell, or PUCCH Scell.

[0320] In some embodiments, the network device receives the CSI report on a default PUSCH.

[0321] For example, the default PUSCH may be at least one of the following:

[0322] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0323] The first PUSCH in the time domain among the scheduled PUSCHs that meets the semi-persistent CSI reporting timing requirements;

[0324] The first PUSCH in the time domain that meets the semi-persistent CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number among the cells in which it is located.

[0325] For another example, the cell where the default PUSCH is located may be: Pcell, PScell, or PUCCH Scell.

[0326] In some embodiments, the DCI format includes fields for indicating a cell and / or an uplink carrier.

[0327] In the above embodiment, the above-mentioned default cell and / or uplink carrier configured by signaling for sending CSI reports is within the range of one or more cells and / or uplink carriers indicated by the above field, or is not within the range of one or more cells and / or uplink carriers indicated by the above field.

[0328] In some embodiments, the DCI format schedules PUSCHs on more than one cell and / or uplink carrier; the network device receives CSI reports on one or more cells and / or uplink carriers.

[0329] In the above embodiment, the DCI format may further include a field for indicating a cell and / or an uplink carrier, where the field indicates more than one cell and / or uplink carrier.

[0330] In the above embodiment, the contents of CSI reports on different PUSCHs may be the same or different.

[0331] In the above embodiment, the above DCI format may further include a field for triggering or activating CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0332] In the above embodiment, the DCI format may further include multiple fields for triggering or activating CSI reporting, and different PUSCHs are respectively used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0333] In the aforementioned embodiments, the CRC of the DCI format may be scrambled by the SP-CSI-RNTI.

[0334] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0335] It can be seen from the above embodiment that semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCHs of multiple cells.

[0336] Embodiments of the fifth aspect

[0337] An embodiment of the present application provides a method for releasing or deactivating semi-continuous CSI reporting, which is applied on the terminal device side.

[0338] FIG24 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application. As shown in FIG24 , the method includes:

[0339] 2401. A terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format releases or deactivates semi-persistent CSI reporting.

[0340] 2402. The terminal device deactivates semi-continuous CSI reporting.

[0341] It is worth noting that FIG24 above is merely a schematic illustration of an embodiment of the present application, using a terminal device as an example, but the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, other operations may be added or some operations may be reduced, and the objects of the aforementioned operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG24 above.

[0342] According to an embodiment of the present application, the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format is capable of scheduling PUSCHs of multiple cells.

[0343] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell or an uplink carrier, and / or the cell and / or uplink carrier indicated by the field is a Pcell, a PScell, or a PUCCH Scell, and / or the field is a specific value that does not correspond to any cell and / or uplink carrier.

[0344] In the above embodiment, the terminal device also considers the field for indicating the scheduled cell and / or uplink carrier during validation.

[0345] In some embodiments, the terminal device determines / validates the validity of the above-mentioned DCI format for semi-persistent CSI release / deactivation.

[0346] For example, the terminal device can determine / confirm (validates) the above validity based on the fields for indicating the cell and / or uplink carrier and / or the field for indicating the HARQ process ID and / or the field for indicating the RV and / or multiple fields for indicating the MCS and / or multiple fields for indicating the frequency domain resource (RB) allocation in the above DCI format.

[0347] In the above example, the above DCI format may include multiple fields for indicating the HARQ process ID, and the terminal device may determine / validate the above validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0348] In the above example, the DCI format may include multiple fields for indicating the RV, and the terminal device may determine / validate the above validity based on some or all of the fields for indicating the RV in the DCI format.

[0349] In the above example, the above DCI format may also include one or more fields for indicating the cell and / or uplink carrier, and the terminal device may determine / validate the above validity based on some or all of the fields for the cell and / or uplink carrier in the DCI format.

[0350] In the above example, the above DCI format may also include multiple fields for indicating MCS, and the terminal device may determine / validate the above validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0351] In the above example, the above DCI format may also include a field for indicating frequency domain resource (RB) allocation, and the terminal device may determine / validate the above validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0352] In the aforementioned examples, if the DCI format is invalid, the terminal device may ignore or discard the DCI format. Alternatively, if the DCI format is confirmed to be invalid, the terminal device assumes that the CRC of the DCI format does not match or that the CRC check fails.

[0353] In an embodiment of the present application, if the DCI format 0_X includes multiple fields for indicating the HARQ process ID (e.g., the HARQ process number field) and / or multiple fields for indicating the RV (e.g., the Redundancy version field) and / or multiple fields for supporting MCS and / or multiple fields for indicating frequency domain resource (RB) allocation, then the multiple fields should all meet the following conditions. Alternatively, the fields for indicating the scheduled cell and / or uplink carrier corresponding to the cell and / or uplink carrier indicated by the above-mentioned fields should meet the following conditions. Optionally, the terminal device ignores other fields for indicating the HARQ process ID.

[0354] These conditions refer to the configurations listed in the following table.

[0355]

[0356] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0357] It can be seen from the above embodiment that the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCHs of multiple cells.

[0358] Embodiments of the sixth aspect

[0359] An embodiment of the present application provides a method for releasing or deactivating semi-continuous CSI reporting, which is applied to the network device side and is a processing on the network device side corresponding to the method of the embodiment of the fifth aspect, wherein the content that is the same as the embodiment of the fifth aspect is not repeated.

[0360] FIG. 25 is a schematic diagram of a method for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application. As shown in FIG. 25 , the method includes:

[0361] 2501. The network device sends a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, where the DCI format releases or deactivates semi-persistent CSI reporting.

[0362] It is worth noting that FIG25 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG25 above.

[0363] According to an embodiment of the present application, the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format is capable of scheduling PUSCHs of multiple cells.

[0364] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell or an uplink carrier, and / or the cell and / or uplink carrier indicated by the field is a Pcell, a PScell, or a PUCCH Scell, and / or the field is a specific value that does not correspond to any cell and / or uplink carrier.

[0365] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0366] It can be seen from the above embodiment that the release or deactivation of semi-persistent CSI reporting is achieved when the DCI format can schedule PUSCHs of multiple cells.

[0367] In the embodiments of the first to sixth aspects above, a DCI format (denoted as DCI format 0_X) supporting PUSCH scheduling of one or more cells and / or uplink carriers through one DCI is described. The following table is a specific example of the fields of DCI format 0_X.

[0368] Table: Summary of fields for DCI format 0_X

[0369]

[0370]

[0371] In the above example, the "type-1 field" is a single field that indicates common information to all co-scheduled cells, or a single field that indicates separate information to each co-scheduled cell via joint indication, or a single field that indicates information to only one of the co-scheduled cells. In DCI format 0_X, only one of this field is included.

[0372] In the above example, the "type-2 field" is a separate field for each co-scheduled cell, or a separate field for each subgroup that includes one or more co-scheduled cells, where a single field is generally applied to co-scheduled cells belonging to the same subgroup. In DCI format 0_X, multiple such fields are included.

[0373] In the above example, the "type-3 field" is shared or separated with each co-scheduled cell or each subgroup. In DCI format 0_X, one or more of these fields are included, depending on explicit configuration or implicit determination, such as intra-band or inter-band CA, FR1 or FR2.

[0374] In the above example, the UL-SCH indicator is used to indicate whether the PUSCH used to carry the CSI report also carries UL-SCH data.

[0375] In the above examples, domain refers to field, which can also be called information domain.

[0376] Embodiments of the seventh aspect

[0377] The embodiment of the present application provides an aperiodic CSI reporting device, which may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device, and the contents identical to those in the first to second aspects of the embodiment will not be repeated.

[0378] FIG26 is a schematic diagram of an aperiodic CSI reporting apparatus according to an embodiment of the present application. As shown in FIG26 , the aperiodic CSI reporting apparatus 2600 according to an embodiment of the present application includes:

[0379] A receiving unit 2601 receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic CSI reporting; and

[0380] The sending unit 2602 sends a CSI report.

[0381] In some embodiments, the DCI format schedules a PUSCH on a cell and / or uplink carrier, and the sending unit 2602 sends the CSI report on the cell and / or uplink carrier.

[0382] In some embodiments, when the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules a PUSCH on one cell and / or uplink carrier.

[0383] In some embodiments, the DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; and the sending unit 2602 sends the CSI report on the cell and / or uplink carrier indicated by the field.

[0384] In some embodiments, the sending unit 2602 sends the CSI report on a default cell and / or uplink carrier configured by signaling for sending the CSI report.

[0385] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0386] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the sending unit 2602 ignores the field.

[0387] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0388] In some embodiments, the DCI format does not include a field for indicating a cell and / or uplink carrier when requesting or triggering aperiodic CSI reporting.

[0389] In some embodiments, the default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0390] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; and the sending unit 2602 sends the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0391] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the value of the field corresponds to a CSI aperiodic triggering state.

[0392] In some embodiments, the length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0393] In some embodiments, the length of the field is determined by the terminal device according to the number of trigger states in a configured trigger state list.

[0394] In some embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0395] In some embodiments, the default cell for sending the CSI report is at least one of the following:

[0396] The cell with the smallest serving cell identification number among the scheduled cells;

[0397] The cell where the first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirements is located among the scheduled PUSCHs;

[0398] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0399] In some embodiments, the default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0400] In some embodiments, the sending unit 2602 sends the CSI report on a default PUSCH.

[0401] In some embodiments, the default PUSCH is at least one of the following:

[0402] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0403] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0404] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0405] In some embodiments, the cell where the default PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0406] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier.

[0407] In some embodiments, the default or signaling configured cell and / or uplink carrier for sending CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0408] In some embodiments, the DCI format schedules PUSCH on more than one cell and / or uplink carrier; the sending unit 2602 sends the CSI report on one or more cells and / or uplink carriers among the more than one cell and / or uplink carrier.

[0409] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0410] In some embodiments, the contents of CSI reports on different PUSCHs are the same or different.

[0411] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0412] In some embodiments, the DCI format includes multiple fields for requesting or triggering CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0413] In some embodiments, the CRC of the DCI format is scrambled by C-RNTI or MCS-C-RNTI.

[0414] In some embodiments, the receiving unit 2601 further receives configuration information for configuring the terminal device to listen to the DCI format in a UE-specific search space.

[0415] In some embodiments, the receiving unit 2601 further receives configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.

[0416] In some embodiments, the receiving unit 2601 further receives configuration information for configuring cells and / or uplink carriers that can be scheduled by the DCI format.

[0417] In some embodiments, the more than one uplink carriers are from different cells respectively, or at least two of the more than one uplink carriers are from different cells.

[0418] The present application also provides a device for receiving CSI reports. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. The contents identical to those in the first and second aspects of the embodiments are not repeated here.

[0419] FIG27 is a schematic diagram of a CSI report receiving apparatus according to an embodiment of the present application. As shown in FIG27 , the CSI report receiving apparatus 2700 according to the embodiment of the present application includes:

[0420] A sending unit 2701 is configured to send a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic CSI reporting;

[0421] The receiving unit 2702 receives the CSI report.

[0422] In some embodiments, the DCI format schedules a PUSCH on a cell and / or uplink carrier, and the receiving unit 2702 receives the CSI report on the cell and / or uplink carrier.

[0423] In some embodiments, when the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules a PUSCH on one cell and / or uplink carrier.

[0424] In some embodiments, the DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; the receiving unit 2702 receives the CSI report on the cell and / or uplink carrier indicated by the field.

[0425] In some embodiments, the receiving unit 2702 receives the CSI report on a default cell and / or uplink carrier configured by signaling for receiving the CSI report.

[0426] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0427] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores the field.

[0428] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0429] In some embodiments, the DCI format does not include a field for indicating a cell and / or uplink carrier when requesting or triggering aperiodic CSI reporting.

[0430] In some embodiments, the default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0431] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; the receiving unit 2702 receives the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0432] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the value of the field corresponds to a CSI aperiodic triggering state.

[0433] In some embodiments, the length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0434] In some embodiments, the length of the field is determined by the terminal device according to the number of trigger states in a configured trigger state list.

[0435] In some embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for receiving CSI reports.

[0436] In some embodiments, the default cell for receiving CSI reports is at least one of the following:

[0437] The cell with the smallest serving cell identification number among the scheduled cells;

[0438] The cell where the first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirements is located among the scheduled PUSCHs;

[0439] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0440] In some embodiments, the default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0441] In some embodiments, the receiving unit 2702 receives the CSI report on a default PUSCH.

[0442] In some embodiments, the default PUSCH is at least one of the following:

[0443] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0444] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0445] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0446] In some embodiments, the cell where the default PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0447] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier.

[0448] In some embodiments, the default or signaling configured cell and / or uplink carrier for receiving CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0449] In some embodiments, the DCI format schedules PUSCH on more than one cell and / or uplink carrier; and the network device receives the CSI report on one or more cells and / or uplink carriers among the more than one cell and / or uplink carrier.

[0450] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0451] In some embodiments, the contents of CSI reports on different PUSCHs are the same or different.

[0452] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0453] In some embodiments, the DCI format includes multiple fields for requesting or triggering CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0454] In some embodiments, the CRC of the DCI format is scrambled by C-RNTI or MCS-C-RNTI.

[0455] In some embodiments, the sending unit 2701 further sends configuration information for configuring the terminal device to listen to the DCI format in a UE-specific search space.

[0456] In some embodiments, the sending unit 2701 further sends configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.

[0457] In some embodiments, the sending unit 2701 further sends configuration information for configuring cells and / or uplink carriers that can be scheduled by the DCI format.

[0458] In some embodiments, the more than one uplink carriers are from different cells respectively, or at least two of the more than one uplink carriers are from different cells.

[0459] The embodiment of the present application further provides a semi-persistent CSI reporting device, which may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device, and the contents identical to those in the third to fourth aspects of the embodiment will not be repeated.

[0460] FIG28 is a schematic diagram of a semi-persistent CSI reporting apparatus according to an embodiment of the present application. As shown in FIG28 , the semi-persistent CSI reporting apparatus 2800 according to an embodiment of the present application includes:

[0461] a receiving unit 2801 configured to receive a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent CSI reporting;

[0462] The sending unit 2802 sends a CSI report.

[0463] In some embodiments, the DCI format schedules a PUSCH on a cell and / or uplink carrier, and the sending unit 2802 sends the CSI report on the cell and / or uplink carrier.

[0464] In some embodiments, when the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules the PUSCH on one cell and / or uplink carrier.

[0465] In some embodiments, the DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; and the sending unit 2802 sends the CSI report on the cell and / or uplink carrier indicated by the field.

[0466] In some embodiments, the sending unit 2802 sends the CSI report on a default cell and / or uplink carrier configured by signaling for sending the CSI report.

[0467] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0468] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the sending unit 2802 ignores the field.

[0469] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0470] In some embodiments, the DCI format does not include a field for indicating a cell and / or an uplink carrier when triggering or activating semi-persistent CSI reporting.

[0471] In some embodiments, the default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0472] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; and the sending unit 2802 sends the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0473] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the value of the field corresponds to a CSI triggering state.

[0474] In some embodiments, the length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0475] In some embodiments, the length of the field is determined by the terminal device according to the number of trigger states in a configured trigger state list.

[0476] In some embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0477] In some embodiments, the default cell for sending the CSI report is at least one of the following:

[0478] The cell with the smallest serving cell identification number among the scheduled cells;

[0479] The cell where the first PUSCH in the time domain that meets the semi-persistent CSI reporting timing requirements is located among the scheduled PUSCHs;

[0480] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the semi-persistent CSI reporting timing requirement in the time domain is located in the scheduled PUSCH.

[0481] In some embodiments, the default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0482] In some embodiments, the sending unit 2802 sends the CSI report on a default PUSCH.

[0483] In some embodiments, the default PUSCH is at least one of the following:

[0484] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0485] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0486] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0487] In some embodiments, the cell where the default PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0488] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier.

[0489] In some embodiments, the default or signaling configured cell and / or uplink carrier for sending CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0490] In some embodiments, the DCI format schedules PUSCH on more than one cell and / or uplink carrier; the sending unit 2802 sends the CSI report on one or more cells and / or uplink carriers among the more than one cell and / or uplink carrier.

[0491] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0492] In some embodiments, the contents of CSI reports on different PUSCHs are the same or different.

[0493] In some embodiments, the DCI format includes a field for triggering or activating CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0494] In some embodiments, the DCI format includes multiple fields for triggering or activating CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0495] In some embodiments, the CRC of the DCI format is scrambled by the SP-CSI-RNTI.

[0496] In some embodiments, as shown in FIG28 , the apparatus 2800 further includes:

[0497] The determining / validating unit 2803 determines / validates the validity of the DCI format for semi-persistent CSI activation.

[0498] In some embodiments, the determination / confirmation unit 2803 determines / confirms (validates) the validity based on the field for indicating the cell and / or uplink carrier and / or the field for indicating the HARQ process ID and / or the field for indicating the RV in the DCI format.

[0499] In some embodiments, the DCI format includes multiple fields for indicating the HARQ process ID, and the determination / confirmation unit 2803 determines / confirms (validates) the validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0500] In some embodiments, the DCI format includes multiple fields for indicating RV, and the determination / confirmation unit 2803 determines / confirms (validates) the validity according to some or all of the fields for indicating RV in the DCI format.

[0501] In some embodiments, the DCI format includes one or more fields for indicating a cell and / or an uplink carrier, and the determination / confirmation unit 2803 determines / confirms (validates) the validity based on some or all of the fields in the DCI format for the cell and / or uplink carrier.

[0502] In some embodiments, if the DCI format is invalid, the receiving unit 2801 ignores / discards the DCI format.

[0503] The present application also provides a device for receiving CSI reports. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. The contents identical to those in the third to fourth aspects of the embodiments are not repeated here.

[0504] FIG29 is a schematic diagram of a CSI report receiving apparatus according to an embodiment of the present application. As shown in FIG29 , the CSI report receiving apparatus 2900 according to the embodiment of the present application includes:

[0505] a transmitting unit 2901 configured to transmit a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent CSI reporting;

[0506] The receiving unit 2902 receives the CSI report.

[0507] In some embodiments, the DCI format schedules a PUSCH on a cell and / or uplink carrier, and the receiving unit 2902 receives the CSI report on the cell and / or uplink carrier.

[0508] In some embodiments, when the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules the PUSCH on one cell and / or uplink carrier.

[0509] In some embodiments, the DCI format includes a field for indicating a cell and / or uplink carrier, where the field indicates a cell and / or uplink carrier; the receiving unit 2902 receives the CSI report on the cell and / or uplink carrier indicated by the field.

[0510] In some embodiments, the receiving unit 2902 receives the CSI report on a default cell and / or uplink carrier configured by signaling for receiving the CSI report.

[0511] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0512] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores the field.

[0513] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating the cell and / or uplink carrier.

[0514] In some embodiments, the DCI format does not include a field for indicating a cell and / or an uplink carrier when triggering or activating semi-persistent CSI reporting.

[0515] In some embodiments, the default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0516] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers; the receiving unit 2902 receives the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0517] In some embodiments, the DCI format includes a field for requesting or triggering CSI reporting, and the value of the field corresponds to a CSI triggering state.

[0518] In some embodiments, the length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0519] In some embodiments, the length of the field is determined by the terminal device according to the number of trigger states in a configured trigger state list.

[0520] In some embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for receiving CSI reports.

[0521] In some embodiments, the default cell for receiving CSI reports is at least one of the following:

[0522] The cell with the smallest serving cell identification number among the scheduled cells;

[0523] The cell where the first PUSCH in the time domain that meets the semi-persistent CSI reporting timing requirements is located among the scheduled PUSCHs;

[0524] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the semi-persistent CSI reporting timing requirement in the time domain is located in the scheduled PUSCH.

[0525] In some embodiments, the default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0526] In some embodiments, the receiving unit 2902 receives the CSI report on a default PUSCH.

[0527] In some embodiments, the default PUSCH is at least one of the following:

[0528] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0529] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0530] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0531] In some embodiments, the cell where the default PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0532] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier.

[0533] In some embodiments, the default or signaling configured cell and / or uplink carrier for receiving CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0534] In some embodiments, the DCI format schedules PUSCH on more than one cell and / or uplink carrier;

[0535] The network device receives the CSI report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

[0536] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0537] In some embodiments, the contents of CSI reports on different PUSCHs are the same or different.

[0538] In some embodiments, the DCI format includes a field for triggering or activating CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0539] In some embodiments, the DCI format includes multiple fields for triggering or activating CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0540] In some embodiments, the CRC of the DCI format is scrambled by the SP-CSI-RNTI.

[0541] The embodiment of the present application further provides a device for releasing or deactivating semi-persistent CSI reporting. The device may be, for example, a terminal device, or one or more components or assemblies configured on the terminal device. The contents identical to those in the fifth to sixth aspects of the embodiment are not repeated here.

[0542] FIG30 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application. As shown in FIG30 , the device for releasing or deactivating semi-persistent CSI reporting 3000 according to an embodiment of the present application includes:

[0543] A receiving unit 3001 is configured to receive a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format releases or deactivates semi-persistent CSI reporting;

[0544] The processing unit 3002 deactivates semi-persistent CSI reporting.

[0545] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicates a cell or an uplink carrier, and / or the cell and / or uplink carrier indicated by the field is a Pcell or a PScell ​​or a PUCCH Scell, and / or the field is a specific value, and the specific value does not correspond to any cell and / or uplink carrier.

[0546] In some embodiments, as shown in FIG30 , the apparatus 3000 further includes:

[0547] The determining / validating unit 3003 determines / validates the validity of the DCI format for semi-persistent CSI release / deactivation.

[0548] In some embodiments, the determination / confirmation unit 3003 determines / confirms (validates) the validity based on the field for indicating the cell and / or uplink carrier and / or the field for indicating the HARQ process ID and / or the field for indicating the RV and / or multiple fields for indicating the MCS and / or multiple fields for indicating the frequency domain resource (RB) allocation in the DCI format.

[0549] In some embodiments, the DCI format includes multiple fields for indicating the HARQ process ID, and the determination / confirmation unit 3003 determines / confirms (validates) the validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0550] In some embodiments, the DCI format includes multiple fields for indicating RV, and the determination / confirmation unit 3003 determines / confirms (validates) the validity according to some or all of the fields for indicating RV in the DCI format.

[0551] In some embodiments, the DCI format includes one or more fields for indicating a cell and / or an uplink carrier, and the determination / confirmation unit 3003 determines / confirms (validates) the validity based on some or all of the fields for the cell and / or uplink carrier in the DCI format.

[0552] In some embodiments, the DCI format includes multiple fields for indicating a modulation and coding scheme (MCS), and the determination / confirmation unit 3003 determines / confirms (validates) the validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0553] In some embodiments, the DCI format includes a field for indicating frequency domain resource (e.g., resource block RB) allocation (Frequency domain resource assignment), and the determination / confirmation unit 3003 determines / confirms (validates) the validity based on part or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0554] In some embodiments, if the DCI format is invalid, the determination / confirmation unit 3003 ignores / discards the DCI format.

[0555] The embodiment of the present application further provides a device for releasing or deactivating semi-persistent CSI reporting. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. The contents identical to those in the fifth to sixth aspects of the embodiment are not repeated here.

[0556] FIG31 is a schematic diagram of a device for releasing or deactivating semi-persistent CSI reporting according to an embodiment of the present application. As shown in FIG31 , the device for releasing or deactivating semi-persistent CSI reporting 3100 according to an embodiment of the present application includes:

[0557] The sending unit 3101 sends a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, where the DCI format releases or deactivates semi-persistent CSI reporting.

[0558] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicates a cell or an uplink carrier, and / or the cell and / or uplink carrier indicated by the field is a Pcell or a PScell ​​or a PUCCH Scell, and / or the field is a specific value, and the specific value does not correspond to any cell and / or uplink carrier.

[0559] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0560] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. Apparatuses 2600, 2700, 2800, 2900, 3000, and 3100 may also include other components or modules. For details of these components or modules, reference may be made to the relevant art.

[0561] In addition, for the sake of simplicity, Figures 26 to 31 only illustrate the connection relationships or signal paths between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0562] It can be seen from the above embodiments that aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting are implemented when the DCI format can schedule PUSCHs of multiple cells.

[0563] Embodiments of the eighth aspect

[0564] An embodiment of the present application also provides a communication system, and reference may be made to FIG1 . The contents identical to those in the embodiments of the first to sixth aspects will not be repeated here.

[0565] In some embodiments, the communication system 100 may include at least a network device and a terminal device, wherein the network device is configured to execute the method described in the embodiment of the second aspect, the fourth aspect or the sixth aspect; and the terminal device is configured to execute the method described in the embodiment of the first aspect, the third aspect or the fifth aspect.

[0566] The contents regarding the network device and the terminal device have been described in detail in the embodiments of the first to sixth aspects, and their contents are incorporated herein and will not be repeated here.

[0567] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0568] Figure 32 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 32 , the terminal device 3200 may include a processor 3210 and a memory 3220. The memory 3220 stores data and programs and is coupled to the processor 3210. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0569] For example, the processor 3210 may be configured to execute a program to implement the method described in the embodiments of the first aspect, the third aspect, or the fifth aspect.

[0570] As shown in Figure 32 , the terminal device 3200 may further include: a communication module 3230, an input unit 3240, a display 3250, and a power supply 3260. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 3200 does not necessarily include all of the components shown in Figure 32 , and these components are not essential. Furthermore, the terminal device 3200 may also include components not shown in Figure 32 , for which reference may be made to the prior art.

[0571] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0572] Figure 33 is a schematic diagram of the structure of a network device according to an embodiment of the present application. As shown in Figure 33, network device 3300 may include a processor 3310 (e.g., a central processing unit (CPU)) and a memory 3320; the memory 3320 is coupled to the processor 3310. The memory 3320 may store various data and may also store an information processing program 3330, which is executed under the control of the processor 3310.

[0573] For example, the processor 3310 can be configured to execute a program to implement the method as described in the embodiments of the second aspect, the fourth aspect, or the sixth aspect.

[0574] In addition, as shown in Figure 33, network device 3300 may also include: a transceiver 3340 and an antenna 3350; wherein, the functions of the above components are similar to those in the prior art and are not further described here. It is worth noting that network device 3300 does not necessarily include all the components shown in Figure 33; in addition, network device 3300 may also include components not shown in Figure 33, and reference may be made to the prior art.

[0575] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect, the third aspect, or the fifth aspect.

[0576] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect, the third aspect, or the fifth aspect.

[0577] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect, the fourth aspect, or the sixth aspect.

[0578] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect, the fourth aspect, or the sixth aspect.

[0579] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0580] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0581] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0582] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0583] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0584] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0585] 1. A method for reporting aperiodic CSI, comprising:

[0586] The terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic CSI reporting;

[0587] The terminal device sends a CSI report.

[0588] 2. The method according to Supplement 1, wherein:

[0589] The DCI format schedules a PUSCH on a cell and / or uplink carrier, and the terminal device sends the CSI report on the cell and / or uplink carrier.

[0590] 3. The method according to Supplement 1 or 2, wherein:

[0591] In the case where the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules a PUSCH on one cell and / or uplink carrier.

[0592] 4. The method according to Supplementary Note 2, wherein:

[0593] The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell and / or an uplink carrier;

[0594] The terminal device sends the CSI report on the cell and / or uplink carrier indicated by the field.

[0595] 5. The method according to Supplementary Note 2, wherein:

[0596] The terminal device sends the CSI report on a default cell and / or uplink carrier configured by signaling for sending the CSI report.

[0597] 6. The method according to Supplement 5, wherein:

[0598] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0599] 7. The method according to Supplementary Note 5, wherein:

[0600] The DCI format includes fields for indicating a cell and / or an uplink carrier, and the terminal device ignores the fields.

[0601] 8. The method according to Supplement 1, wherein:

[0602] The DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating a cell and / or an uplink carrier.

[0603] 9. The method according to Supplement 5 or 8, wherein:

[0604] When requesting or triggering aperiodic CSI reporting, the DCI format does not include a field for indicating a cell and / or an uplink carrier.

[0605] 10. The method according to any one of Notes 5 to 9, wherein:

[0606] The default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0607] 11. The method according to Supplement 1, wherein:

[0608] The DCI format schedules a PUSCH on one or more cells and / or uplink carriers;

[0609] The terminal device sends the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0610] 12. The method according to Note 1, 2 or 11, wherein:

[0611] The DCI format includes a field for requesting or triggering CSI reporting, and a value of the field corresponds to a CSI aperiodic triggering state.

[0612] 13. The method according to Supplement 12, wherein:

[0613] The length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0614] 14. The method according to Supplement 12, wherein:

[0615] The length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.

[0616] 15. The method according to Supplementary Note 11, wherein:

[0617] The one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0618] 16. The method according to Supplement 15, wherein:

[0619] The default cell for sending the CSI report is at least one of the following:

[0620] The cell with the smallest serving cell identification number among the scheduled cells;

[0621] The cell where the first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirements is located among the scheduled PUSCHs;

[0622] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0623] 17. The method according to Supplement 15 or 16, wherein:

[0624] The default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0625] 18. The method according to Supplement 1, wherein:

[0626] The terminal device sends the CSI report on the default PUSCH.

[0627] 19. The method according to Supplement 18, wherein:

[0628] The default PUSCH is at least one of the following:

[0629] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0630] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0631] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0632] 20. The method according to Supplement 18 or 19, wherein:

[0633] The default cell where the PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0634] 21. The method according to Supplement 15, wherein:

[0635] The DCI format includes fields for indicating a cell and / or an uplink carrier.

[0636] 22. The method according to Supplementary Note 21, wherein:

[0637] The default cell and / or uplink carrier configured by signaling for sending CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0638] 23. The method according to Supplement 1, wherein:

[0639] The DCI format schedules PUSCHs on more than one cell and / or uplink carrier;

[0640] The terminal device sends the CSI report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

[0641] 24. The method according to Note 23, wherein:

[0642] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0643] 25. The method according to Supplement 23, wherein:

[0644] The contents of CSI reports on different PUSCHs may be the same or different.

[0645] 26. The method according to Note 23 or 25, wherein:

[0646] The DCI format includes a field for requesting or triggering CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0647] 27. The method according to Note 23 or 25, wherein:

[0648] The DCI format includes multiple fields for requesting or triggering CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0649] 28. The method according to any one of Notes 1 to 27, wherein:

[0650] The CRC of the DCI format is scrambled by the C-RNTI or the MCS-C-RNTI.

[0651] 29. The method according to any one of Notes 1 to 28, wherein:

[0652] The terminal device receives configuration information for configuring the terminal device to listen to the DCI format in a UE-specific search space.

[0653] 30. The method according to any one of Notes 1 to 29, wherein:

[0654] The terminal device receives configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.

[0655] 31. The method according to any one of Notes 1 to 30, wherein:

[0656] The terminal device receives configuration information for configuring cells and / or uplink carriers that can be scheduled by the DCI format.

[0657] 32. The method according to Note 1, wherein:

[0658] The more than one uplink carriers are from different cells respectively, or at least two of the more than one uplink carriers are from different cells.

[0659] 33. A method for receiving a CSI report, wherein the method comprises:

[0660] The network device sends a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic CSI reporting;

[0661] The network device receives a CSI report.

[0662] 34. The method according to Note 33, wherein:

[0663] The DCI format schedules a PUSCH on a cell and / or uplink carrier, and the network device receives the CSI report on the cell and / or uplink carrier.

[0664] 35. The method according to Note 33 or 34, wherein:

[0665] In the case where the DCI format requests or triggers aperiodic CSI reporting, the DCI format only schedules a PUSCH on one cell and / or uplink carrier.

[0666] 36. The method according to Note 34, wherein:

[0667] The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell and / or an uplink carrier;

[0668] The network device receives the CSI report on the cell and / or uplink carrier indicated by the field.

[0669] 37. The method according to Note 34, wherein:

[0670] The network device receives the CSI report on a default cell and / or uplink carrier configured by signaling for receiving the CSI report.

[0671] 38. The method according to Supplement 37, wherein:

[0672] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0673] 39. The method according to Supplement 37, wherein:

[0674] The DCI format includes fields for indicating a cell and / or an uplink carrier, and the terminal device ignores the fields.

[0675] 40. The method according to Note 1, wherein:

[0676] The DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating a cell and / or an uplink carrier.

[0677] 41. The method according to Note 37 or 40, wherein:

[0678] When requesting or triggering aperiodic CSI reporting, the DCI format does not include a field for indicating a cell and / or an uplink carrier.

[0679] 42. The method according to any one of Notes 37 to 41, wherein:

[0680] The default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0681] 43. The method according to Note 33, wherein:

[0682] The DCI format schedules a PUSCH on one or more cells and / or uplink carriers;

[0683] The network device receives the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0684] 44. The method according to Note 33, 34 or 43, wherein:

[0685] The DCI format includes a field for requesting or triggering CSI reporting, and a value of the field corresponds to a CSI aperiodic triggering state.

[0686] 45. The method according to Note 44, wherein:

[0687] The length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0688] 46. ​​The method according to Note 44, wherein:

[0689] The length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.

[0690] 47. The method according to Note 43, wherein:

[0691] The one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for receiving CSI reports.

[0692] 48. The method according to Note 47, wherein:

[0693] The default cell for receiving CSI reports is at least one of the following:

[0694] The cell with the smallest serving cell identification number among the scheduled cells;

[0695] The cell where the first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirements is located among the scheduled PUSCHs;

[0696] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0697] 49. The method according to Note 47 or 48, wherein:

[0698] The default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0699] 50. The method according to Note 1, wherein:

[0700] The network device receives the CSI report on a default PUSCH.

[0701] 51. The method according to Note 50, wherein:

[0702] The default PUSCH is at least one of the following:

[0703] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0704] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0705] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0706] 52. The method according to Note 50 or 51, wherein:

[0707] The default cell where the PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0708] 53. The method according to Supplement 47, wherein:

[0709] The DCI format includes fields for indicating a cell and / or an uplink carrier.

[0710] 54. The method according to Note 53, wherein:

[0711] The default cell and / or uplink carrier configured by signaling for receiving CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0712] 55. The method according to Note 1, wherein:

[0713] The DCI format schedules PUSCHs on more than one cell and / or uplink carrier;

[0714] The network device receives the CSI report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

[0715] 56. The method according to Note 55, wherein:

[0716] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0717] 57. The method according to Note 55, wherein:

[0718] The contents of CSI reports on different PUSCHs may be the same or different.

[0719] 58. The method according to Note 55 or 57, wherein:

[0720] The DCI format includes a field for requesting or triggering CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger status associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0721] 59. The method according to Note 56 or 57, wherein:

[0722] The DCI format includes multiple fields for requesting or triggering CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0723] 60. The method according to any one of Notes 33 to 59, wherein:

[0724] The CRC of the DCI format is scrambled by the C-RNTI or the MCS-C-RNTI.

[0725] 61. The method according to any one of Notes 33 to 60, wherein:

[0726] The network device sends configuration information for configuring the terminal device to listen to the DCI format in a UE-specific search space.

[0727] 62. The method according to any one of Notes 33 to 61, wherein:

[0728] The network device sends configuration information for configuring whether the DCI format supports triggering CSI reporting or whether the DCI format is used to trigger CSI reporting.

[0729] 63. The method according to any one of Notes 33 to 62, wherein:

[0730] The network device sends configuration information for configuring cells and / or uplink carriers that can be scheduled by the DCI format.

[0731] 64. The method according to Note 1, wherein:

[0732] The more than one uplink carriers are from different cells respectively, or at least two of the more than one uplink carriers are from different cells.

[0733] 1'. A semi-persistent CSI reporting method, wherein the method comprises:

[0734] The terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent CSI reporting;

[0735] The terminal device sends a CSI report.

[0736] 2'. The method according to Supplement 1', wherein

[0737] The DCI format schedules a PUSCH on a cell and / or uplink carrier, and the terminal device sends the CSI report on the cell and / or uplink carrier.

[0738] 3'. The method according to Note 1' or 2', wherein

[0739] In the case where the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules a PUSCH on one cell and / or uplink carrier.

[0740] 4 '. The method according to Note 2 ', wherein,

[0741] The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell and / or an uplink carrier;

[0742] The terminal device sends the CSI report on the cell and / or uplink carrier indicated by the field.

[0743] 5'. The method according to Note 2', wherein

[0744] The terminal device sends the CSI report on a default cell and / or uplink carrier configured by signaling for sending the CSI report.

[0745] 6'. The method according to Note 5', wherein

[0746] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0747] 7'. The method according to Note 5', wherein

[0748] The DCI format includes fields for indicating a cell and / or an uplink carrier, and the terminal device ignores the fields.

[0749] 8'. The method according to Supplement 1', wherein

[0750] The DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating a cell and / or an uplink carrier.

[0751] 9'. The method according to Note 5' or 8', wherein

[0752] When triggering or activating semi-persistent CSI reporting, the DCI format does not include a field for indicating a cell and / or an uplink carrier.

[0753] 10'. The method according to any one of Notes 5'-8', wherein

[0754] The default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0755] 11 '. The method according to Note 1 ', wherein,

[0756] The DCI format schedules a PUSCH on one or more cells and / or uplink carriers;

[0757] The terminal device sends the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0758] 12'. The method according to Note 1' or 2' or 11', wherein

[0759] The DCI format includes a field for requesting or triggering CSI reporting, and the value of the field corresponds to the CSI triggering state.

[0760] 13'. The method according to Note 12', wherein

[0761] The length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0762] 14'. The method according to Note 12', wherein

[0763] The length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.

[0764] 15'. The method according to Note 11', wherein

[0765] The one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending CSI reports.

[0766] 16'. The method according to Note 15', wherein

[0767] The default cell for sending the CSI report is at least one of the following:

[0768] The cell with the smallest serving cell identification number among the scheduled cells;

[0769] The cell where the first PUSCH in the time domain that meets the semi-persistent CSI reporting timing requirements is located among the scheduled PUSCHs;

[0770] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the semi-persistent CSI reporting timing requirement in the time domain is located in the scheduled PUSCH.

[0771] 17'. The method according to Note 15' or 16', wherein

[0772] The default cell for sending CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0773] 18'. The method according to Supplement 1', wherein

[0774] The terminal device sends the CSI report on the default PUSCH.

[0775] 19'. The method according to Note 18', wherein

[0776] The default PUSCH is at least one of the following:

[0777] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0778] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0779] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0780] 20'. The method according to Note 18' or 19', wherein

[0781] The default cell where the PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0782] 21'. The method according to Note 15', wherein

[0783] The DCI format includes fields for indicating a cell and / or an uplink carrier.

[0784] 22'. The method according to Note 21', wherein

[0785] The default cell and / or uplink carrier configured by signaling for sending CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0786] 23'. The method according to Supplement 1', wherein

[0787] The DCI format schedules PUSCHs on more than one cell and / or uplink carrier;

[0788] The terminal device sends the CSI report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

[0789] 24'. The method according to Note 23', wherein

[0790] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0791] 25'. The method according to claim 23', wherein

[0792] The contents of CSI reports on different PUSCHs may be the same or different.

[0793] 26'. The method according to Note 23' or 25', wherein

[0794] The DCI format includes a field for triggering or activating CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the triggering state associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0795] 27'. The method according to Note 23' or 25', wherein

[0796] The DCI format includes multiple fields for triggering or activating CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0797] 28'. The method according to any one of Notes 1'-27', wherein

[0798] The CRC of the DCI format is scrambled by the SP-CSI-RNTI.

[0799] 29'. The method according to any one of Notes 1' to 28', wherein

[0800] The terminal device determines / validates the validity of the DCI format for semi-persistent CSI activation.

[0801] 30'. The method according to Note 29', wherein

[0802] The terminal device determines / validates the validity based on the field for indicating the cell and / or uplink carrier and / or the field for indicating the HARQ process ID and / or the field for indicating the RV in the DCI format.

[0803] 31'. The method according to Note 30', wherein

[0804] The DCI format includes multiple fields for indicating the HARQ process ID, and the terminal device determines / validates the validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0805] 32'. The method according to Note 30' or 31', wherein

[0806] The DCI format includes multiple fields for indicating the RV, and the terminal device determines / validates the validity based on some or all of the fields for indicating the RV in the DCI format.

[0807] 33'. The method according to any one of Notes 30'-32', wherein

[0808] The DCI format includes one or more fields for indicating a cell and / or an uplink carrier, and the terminal device determines / validates the validity based on some or all of the fields for the cell and / or uplink carrier in the DCI format.

[0809] 34'. The method according to any one of Notes 30'-33', wherein

[0810] If the DCI format is invalid, the terminal device ignores / discards the DCI format.

[0811] 35'. A method for receiving a CSI report, wherein the method comprises:

[0812] The network device sends a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent CSI reporting;

[0813] The network device receives a CSI report.

[0814] 36'. The method according to Note 35', wherein

[0815] The DCI format schedules a PUSCH on a cell and / or uplink carrier, and the network device receives the CSI report on the cell and / or uplink carrier.

[0816] 37'. The method according to Note 35' or 36', wherein

[0817] In the case where the DCI format triggers or activates semi-persistent CSI reporting, the DCI format only schedules a PUSCH on one cell and / or uplink carrier.

[0818] 38'. The method according to Note 36', wherein

[0819] The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell and / or an uplink carrier;

[0820] The network device receives the CSI report on the cell and / or uplink carrier indicated by the field.

[0821] 39'. The method according to Note 36', wherein

[0822] The network device receives the CSI report on a default cell and / or uplink carrier configured by signaling for receiving the CSI report.

[0823] 40'. The method according to Note 39', wherein

[0824] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field does not indicate a cell and / or an uplink carrier.

[0825] 41'. The method according to Note 39', wherein

[0826] The DCI format includes fields for indicating a cell and / or an uplink carrier, and the terminal device ignores the fields.

[0827] 42'. The method according to Note 35', wherein

[0828] The DCI format includes a field for requesting or triggering CSI reporting, and the field for requesting or triggering CSI reporting is located before the field for indicating a cell and / or an uplink carrier.

[0829] 43'. The method according to Note 39' or 42', wherein

[0830] When triggering or activating semi-persistent CSI reporting, the DCI format does not include a field for indicating a cell and / or an uplink carrier.

[0831] 44'. The method according to any one of Notes 39'-42', wherein

[0832] The default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0833] 45'. The method according to Note 35', wherein

[0834] The DCI format schedules a PUSCH on one or more cells and / or uplink carriers;

[0835] The network device receives the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0836] 46'. The method according to Note 35' or 36' or 45', wherein

[0837] The DCI format includes a field for requesting or triggering CSI reporting, and the value of the field corresponds to the CSI triggering state.

[0838] 47'. The method according to Note 46', wherein

[0839] The length of the field is configured by a higher-layer parameter, and the higher-layer parameter is specific to the DCI format or is shared by the DCI format and other DCI formats.

[0840] 48'. The method according to Note 46', wherein

[0841] The length of the field is determined by the terminal device according to the number of trigger states in the configured trigger state list.

[0842] 49'. The method according to Note 45', wherein

[0843] The one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for receiving CSI reports.

[0844] 50'. The method according to Note 49', wherein

[0845] The default cell for receiving CSI reports is at least one of the following:

[0846] The cell with the smallest serving cell identification number among the scheduled cells;

[0847] The cell where the first PUSCH in the time domain that meets the semi-persistent CSI reporting timing requirements is located among the scheduled PUSCHs;

[0848] The cell with the smallest serving cell identification number among the cells where the first PUSCH that meets the semi-persistent CSI reporting timing requirement in the time domain is located in the scheduled PUSCH.

[0849] 51'. The method according to Note 49' or 50', wherein

[0850] The default cell for receiving CSI reports is: Pcell, PScell ​​or PUCCH Scell.

[0851] 52'. The method according to Note 35', wherein

[0852] The network device receives the CSI report on a default PUSCH.

[0853] 53'. The method according to Note 52', wherein

[0854] The default PUSCH is at least one of the following:

[0855] The PUSCH of the cell with the smallest serving cell identification number among the scheduled cells;

[0856] The first PUSCH in the time domain among the scheduled PUSCHs that meets the aperiodic CSI reporting timing requirements;

[0857] The first PUSCH in the time domain that meets the aperiodic CSI reporting timing requirement among the scheduled PUSCHs is the PUSCH of the cell with the smallest serving cell identification number.

[0858] 54'. The method according to Note 52' or 53', wherein

[0859] The default cell where the PUSCH is located is: Pcell, PScell ​​or PUCCH Scell.

[0860] 55'. The method according to Note 49', wherein

[0861] The DCI format includes fields for indicating a cell and / or an uplink carrier.

[0862] 56'. The method according to Note 55', wherein

[0863] The default cell and / or uplink carrier configured by signaling for receiving CSI reports is within the range of one or more cells and / or uplink carriers indicated by the field, or is not within the range of one or more cells and / or uplink carriers indicated by the field.

[0864] 57'. The method according to Note 35', wherein

[0865] The DCI format schedules PUSCHs on more than one cell and / or uplink carrier;

[0866] The network device receives the CSI report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

[0867] 58'. The method according to Note 57', wherein

[0868] The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the more than one cell and / or uplink carrier.

[0869] 59'. The method according to claim 57', wherein

[0870] The contents of CSI reports on different PUSCHs may be the same or different.

[0871] 60'. The method according to Note 57' or 59', wherein

[0872] The DCI format includes a field for triggering or activating CSI reporting, the CSI reports on different PUSCHs are the same, and / or different PUSCHs are used to carry different CSI reports corresponding to the triggering state associated with the field, and / or different PUSCHs are used to carry different parts of the CSI report.

[0873] 61'. The method according to Note 57' or 59', wherein

[0874] The DCI format includes multiple fields for triggering or activating CSI reporting, and different PUSCHs are used to carry CSI reports corresponding to triggering states associated with different fields for requesting or triggering CSI reporting.

[0875] 62'. The method according to any one of Notes 35'-61', wherein

[0876] The CRC of the DCI format is scrambled by the SP-CSI-RNTI.

[0877] 1. A method for releasing or deactivating semi-persistent CSI reporting, the method comprising:

[0878] The terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format releases or deactivates semi-persistent CSI reporting;

[0879] The terminal device deactivates semi-continuous CSI reporting.

[0880] 2". The method according to Note 1", wherein:

[0881] The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell or an uplink carrier, and / or the cell and / or uplink carrier indicated by the field is a Pcell, a PScell, or a PUCCH Scell, and / or the field is a specific value that does not correspond to any cell and / or uplink carrier.

[0882] 3". The method according to Note 1" or 2", wherein:

[0883] The terminal device determines / validates the validity of the DCI format for semi-persistent CSI release / deactivation.

[0884] 4". The method according to Note 3", wherein:

[0885] The terminal device determines / confirms (validates) the validity based on the field for indicating the cell and / or uplink carrier and / or the field for indicating the HARQ process ID and / or the field for indicating the RV and / or multiple fields for indicating the MCS and / or multiple fields for indicating the frequency domain resource (RB) allocation in the DCI format.

[0886] 5". The method according to Note 4", wherein:

[0887] The DCI format includes multiple fields for indicating the HARQ process ID, and the terminal device determines / validates the validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0888] 6". The method according to Note 4" or 5", wherein:

[0889] The DCI format includes multiple fields for indicating the RV, and the terminal device determines / validates the validity based on some or all of the fields for indicating the RV in the DCI format.

[0890] 7". The method according to any one of Notes 4" to 6", wherein:

[0891] The DCI format includes one or more fields for indicating a cell and / or an uplink carrier, and the terminal device determines / validates the validity based on some or all of the fields for the cell and / or uplink carrier in the DCI format.

[0892] 8". The method according to any one of Notes 4" to 7", wherein:

[0893] The DCI format includes multiple fields for indicating MCS, and the terminal device determines / validates the validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0894] 9". The method according to any one of Notes 4" to 8", wherein:

[0895] The DCI format includes a field for indicating frequency domain resource (RB) allocation, and the terminal device determines / validates the validity based on some or all of the fields in the DCI format for indicating the cell and / or uplink carrier.

[0896] 10". The method according to any one of Notes 4" to 9", wherein:

[0897] If the DCI format is invalid, the terminal device ignores / discards the DCI format.

[0898] 11. A method for releasing or deactivating semi-persistent CSI reporting, the method comprising:

[0899] The network device sends a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, where the DCI format releases or deactivates semi-persistent CSI reporting.

[0900] 12". The method according to Note 11", wherein:

[0901] The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell or an uplink carrier, and / or the cell and / or uplink carrier indicated by the field is a Pcell, a PScell, or a PUCCH Scell, and / or the field is a specific value that does not correspond to any cell and / or uplink carrier.

[0902] 1a. A terminal device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 32, 1' to 34', and 1" to 10".

[0903] 2a. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 33 to 64, 35' to 62', and 11" to 12".

[0904] 3a. A communication system comprising a network device and a terminal device, wherein:

[0905] The network device is configured to:

[0906] Sending a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic CSI reporting;

[0907] Receive CSI reports;

[0908] The terminal device is configured as follows:

[0909] receiving the DCI format;

[0910] Send the CSI report.

[0911] 4a. A communication system comprising a network device and a terminal device, wherein:

[0912] The network device is configured to:

[0913] Sending a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent CSI reporting;

[0914] Receive CSI reports;

[0915] The terminal device is configured as follows:

[0916] receiving the DCI format;

[0917] Send the CSI report.

[0918] 5a. A communication system comprising a network device and a terminal device, wherein:

[0919] The network device is configured to:

[0920] Sending a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, wherein the DCI format releases or deactivates semi-persistent CSI reporting;

[0921] The terminal device is configured as follows:

[0922] receiving the DCI format;

[0923] Deactivate semi-persistent CSI reporting.

Claims

1. A non-periodic channel state information reporting device, wherein: The device comprises: a receiving unit configured to receive a DCI format for scheduling a physical uplink shared channel on one or more cells and / or uplink carriers, wherein the DCI format requests or triggers aperiodic channel state information reporting; A sending unit is configured to send a channel state information report.

2. The device according to claim 1, wherein The DCI format schedules a physical uplink shared channel on a cell and / or an uplink carrier, and the sending unit sends the channel state information report on the cell and / or the uplink carrier.

3. The device according to claim 1 or 2, wherein: In the case where the DCI format requests or triggers aperiodic channel state information reporting, the DCI format only schedules a physical uplink shared channel on one cell and / or uplink carrier.

4. The device according to claim 2, wherein The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell and / or an uplink carrier; The sending unit sends the channel state information report on the cell and / or uplink carrier indicated by the field.

5. The device according to claim 2, wherein The sending unit sends the channel state information report on a default cell and / or uplink carrier configured by signaling for sending the channel state information report.

6. The device according to claim 5, wherein The default cell for sending the channel state information report is: Pcell, PScell ​​or PUCCH Scell.

7. The device according to claim 1, wherein The DCI format schedules a physical uplink shared channel on one or more cells and / or uplink carriers; The sending unit sends the channel state information report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

8. The device according to claim 7, wherein The one cell and / or uplink carrier is a default cell and / or uplink carrier configured by signaling for sending a channel state information report.

9. The device according to claim 8, wherein The default cell for sending the channel state information report is at least one of the following: The cell with the smallest serving cell identification number among the scheduled cells; The cell where the first physical uplink shared channel in the scheduled physical uplink shared channel that meets the aperiodic channel state information reporting timing requirement in the time domain is located; The cell with the smallest serving cell identification number among the cells where the first physical uplink shared channel that meets the aperiodic channel state information reporting timing requirement in the time domain is located in the scheduled physical uplink shared channel.

10. The device according to claim 8, wherein The default cell for sending the channel state information report is: Pcell, PScell ​​or PUCCH Scell.

11. The device according to claim 1, wherein The DCI format schedules a physical uplink shared channel on more than one cell and / or uplink carrier; The sending unit sends the channel state information report on one or more cells and / or uplink carriers among the more than one cells and / or uplink carriers.

12. A semi-persistent channel state information reporting device, wherein: The device comprises: a receiving unit configured to receive a DCI format for scheduling a physical uplink shared channel on one or more cells and / or uplink carriers, wherein the DCI format triggers or activates semi-persistent channel state information reporting; A sending unit is configured to send a channel state information report.

13. The device according to claim 12, wherein The DCI format schedules a physical uplink shared channel on a cell and / or an uplink carrier, and the sending unit sends the channel state information report on the cell and / or the uplink carrier.

14. The device according to claim 12, wherein In the case where the DCI format triggers or activates semi-persistent channel state information reporting, the DCI format only schedules a physical uplink shared channel on one cell and / or uplink carrier.

15. The device according to claim 13, wherein The DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates a cell and / or an uplink carrier; The sending unit sends the channel state information report on the cell and / or uplink carrier indicated by the field.

16. The device according to claim 13, wherein The sending unit sends the channel state information report on a default cell and / or uplink carrier configured by signaling for sending the channel state information report.

17. The device according to claim 12, wherein The cyclic redundancy check of the DCI format is scrambled by SP-CSI-RNTI.

18. The device according to claim 12, wherein The device further comprises: A determination / confirmation unit is configured to determine / confirm the validity of the DCI format for semi-persistent channel state information activation.

19. The device according to claim 18, wherein The determining / confirming unit determines / confirms the validity according to a field for indicating a cell and / or an uplink carrier and / or a field for indicating a hybrid automatic repeat request process ID and / or a field for indicating a redundancy version in the DCI format.

20. The device according to claim 19, wherein The DCI format includes a plurality of fields for indicating redundancy versions, and the determination / confirmation unit determines / confirms the validity according to some or all of the fields for indicating redundancy versions in the DCI format.

Images