Method and apparatus for reporting channel state information

Abstract

In an embodiment of the present invention, a method and apparatus for reporting channel state information are provided, the method including: receiving, by a terminal device, a DCI format for scheduling PUSCHs on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and transmitting, by the terminal device, a CSI report. The embodiment of the present invention enables aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting when the DCI format can schedule PUSCHs of multiple cells.

Description

[Technical Field]

[0001] The present invention relates to the field of communications. [Background technology]

[0002] A physical downlink shared channel (PDSCH) is a type of physical downlink channel in a wireless communication system and is used to carry downlink data. A physical uplink shared channel (PUSCH) is a type of physical uplink channel in a wireless communication system and is used to carry uplink data. The PDSCH and PUSCH can be scheduled by downlink control information (DCI). In current new radio (NR) systems, multiple DCI formats are defined for scheduling the PDSCH or PUSCH, and the specific information and / or size included in different DCI formats vary to meet different scheduling needs.

[0003] It should be noted that the introduction of the above background art is intended to clearly and completely explain the technical solutions of the present invention and to facilitate understanding by those skilled in the art, and these technical solutions described in the background art of the present invention should not be construed as being known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]

[0004] The inventors have discovered that, currently, DCI format 0_1 and DCI format 0_2 can be used to trigger / activate / deactivate aperiodic CSI reports and PUSCH-based SP CSI reports, and both DCI format 0_1 and DCI format 0_2 can schedule the PUSCH of only one cell (or uplink carrier). However, in the just-started Rel-18 NR standardization work, one of the goals of multi-carrier enhancement will be to consider how to further support scheduling the PUSCHs of multiple cells (or uplink carriers) using one DCI in order to reduce the resource overhead of DCI and improve system throughput. This DCI supporting scheduling of multiple cells (or uplink carriers) may be a new DCI format (e.g., but not limited to, DCI format 0_3) or may be an enhancement of an existing DCI format (e.g., DCI format 0_1 and DCI format 0_2).

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

[0006] In view of at least one of the above-mentioned problems, embodiments of the present invention provide a method and apparatus for reporting channel state information to support aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting when a DCI format can schedule PUSCHs of multiple cells (or uplink carriers). [Means for solving the problem]

[0007] According to one aspect of an embodiment of the present invention, there is provided an aperiodic CSI reporting device, the device comprising: a receiving unit for receiving a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and It includes a transmitting unit for transmitting the CSI report.

[0008] According to another aspect of an embodiment of the present invention, there is provided a receiving apparatus for a CSI report, the receiving apparatus comprising: a transmitting unit for transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and and a receiving unit for receiving the CSI report.

[0009] According to another aspect of an embodiment of the present invention, there is provided a semi-persistent CSI reporting device, the device comprising: a receiving unit for receiving a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and It includes a transmitting unit for transmitting the CSI report.

[0010] According to another aspect of an embodiment of the present invention, there is provided a receiving apparatus for a CSI report, the receiving apparatus comprising: a transmitting unit for transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and and a receiving unit for receiving the CSI report.

[0011] According to another aspect of an embodiment of the present invention, there is provided an apparatus for releasing or deactivating semi-persistent CSI reporting, the apparatus comprising: A receiving unit for receiving a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format releasing or deactivating semi-persistent CSI reporting; and A processing unit for deactivating semi-persistent CSI reporting is included.

[0012] According to another aspect of an embodiment of the present invention, there is provided an apparatus for releasing or deactivating semi-persistent CSI reporting, the apparatus comprising: A transmitting unit for transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format including releasing or deactivating semi-persistent CSI reporting. [Effects of the Invention]

[0013] The advantageous effects of the embodiments of the present invention are at least as follows: the embodiments of the present invention enable aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting when the DCI format can schedule PUSCHs of multiple cells.

[0014] The following description and reference to the drawings disclose in detail particular embodiments of the present invention, illustrating ways in which the principles of the present invention may be employed, but the scope of the present invention is not limited thereto, and various changes, modifications, and alternatives may be included within the scope of the appended claims.

[0015] Additionally, 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, may be combined with features in the other embodiments, or may be substituted for features in the other embodiments.

[0016] It should be noted that when used in this specification, terms such as "comprise / have" refer to the presence of a feature, element, step, or assembly, but do not exclude the presence or addition of one or more other features, elements, steps, or assemblies. [Brief explanation of the drawings]

[0017] Elements and features described in one drawing or one embodiment of the invention may be combined with elements and features shown in one or more other drawings or embodiments, and in the drawings, like reference numerals are used to indicate corresponding parts in several drawings and to indicate corresponding parts used in multiple embodiments. [Figure 1] 1 is a diagram illustrating a communication system according to an embodiment of the present invention. [Figure 2] FIG. 1 illustrates the timing relationship for aperiodic CSI reporting. [Figure 3] FIG. 10 illustrates the timing relationship for PUSCH-based SP CSI reporting. [Figure 4] FIG. 1 is a diagram illustrating an aperiodic CSI reporting method according to an embodiment of the present invention. [Figure 5] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 6] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 7] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 8] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 9] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 10] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 11] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 12] FIG. 10 illustrates an example of aperiodic CSI reporting. [Figure 13] FIG. 10 is a diagram illustrating a method for receiving a CSI report in an embodiment of the present invention. [Figure 14]FIG. 1 is a diagram illustrating a semi-persistent CSI reporting method according to an embodiment of the present invention. [Figure 15] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 16] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 17] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 18] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 19] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 20] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 21] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 22] FIG. 10 illustrates an example of semi-persistent CSI reporting. [Figure 23] FIG. 10 is a diagram illustrating a method for receiving a CSI report in an embodiment of the present invention. [Figure 24] FIG. 1 illustrates a method for releasing or deactivating semi-persistent CSI reports in an embodiment of the present invention. [Figure 25] FIG. 1 illustrates a method for releasing or deactivating semi-persistent CSI reports in an embodiment of the present invention. [Figure 26] FIG. 1 illustrates an aperiodic CSI reporting device according to an embodiment of the present invention. [Figure 27] FIG. 1 illustrates a receiving device for a CSI report according to an embodiment of the present invention. [Figure 28] FIG. 1 illustrates a semi-persistent CSI reporting device in an embodiment of the present invention. [Figure 29] FIG. 1 illustrates a receiving device for a CSI report according to an embodiment of the present invention. [Figure 30] FIG. 1 illustrates a device for releasing or deactivating semi-persistent CSI reporting in an embodiment of the present invention. [Figure 31] FIG. 1 illustrates a device for releasing or deactivating semi-persistent CSI reporting in an embodiment of the present invention. [Figure 32] FIG. 2 is a configuration diagram of a terminal device according to an embodiment of the present invention. [Figure 33] FIG. 1 is a configuration diagram of a network device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0018] The foregoing and other features of the present invention will become more apparent from a consideration of the accompanying drawings and the following description. While the specification and drawings disclose particular embodiments of the present invention, they illustrate only some of the embodiments which may employ the principles of the present invention, and it is to be understood that the present invention is not limited to the described embodiments, but rather includes all modifications, variations, and alternatives which fall within the scope of the appended claims.

[0019] In embodiments of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.

[0020] Additionally, communications between devices in a communications system may be performed according to any level of communications protocol, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future-developed communications protocols.

[0021] In an embodiment of the present invention, the term "network equipment" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device. The network equipment may include, but is not limited to, a "node" and / or a "donor" in the IAB architecture, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a network gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0022] The base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a 5G base station (gNB), etc., and may further include a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay, or a low-power node (e.g., femto, pico, etc.). The term "base station" may include some or all of these functions, and each base station can provide communication coverage for a specific geographical area. For example, a 5G base station gNB may include one gNB CU and one or more gNB DUs, where a CU / DU is a logical node of the gNB that has some of the functions of the gNB. The term "cell" may refer to a base station and / or the area it covers, depending on the context in which the term is used.

[0023] In the embodiments of the present invention, the term "user equipment" (UE) or "terminal equipment" (TE) refers to a device that accesses a communication network and receives services from the network, for example, via network equipment. The user equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc. For example, it is a terminal equipment served by an IAB node or an IAB donor under the IAB architecture.

[0024] Among these, user equipment may include, but is not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, mobile devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, etc.

[0025] Furthermore, for example, in a scenario such as the Internet of Things (IoT), the user equipment may also be a monitoring or measuring device or apparatus, for example, including but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0026] Furthermore, the term "network side" or "network equipment side" refers to the network side, which may be a base station or may include one or more network equipment as described above. The term "user side" or "terminal side" or "terminal equipment side" refers to the user or terminal side, which may be a UE or may include one or more terminal equipment as described above.

[0027] Hereinafter, the scenario of the embodiment of the present invention will be described through an example, but the present invention is not limited thereto.

[0028] 1 is a diagram showing a communication system in an embodiment of the present invention, taking a terminal device and a network device as an example. As shown in FIG. 1, communication system 100 may include network device 101 and terminal device 102. For convenience, FIG. 1 illustrates an example in which only one network device and only one terminal device are included, but the embodiment of the present invention is not limited to this.

[0029] In an embodiment of the present invention, existing services (services / traffic) or future services may be transmitted between the network device 101 and the terminal device 102. For example, these services may be, but are not limited to, eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communication), URLLC (Ultra-Reliable and Low-Latency Communication), etc.

[0030] In NR, the overall process of UE reporting CSI includes the following steps: The gNB transmits CSI-RS and / or SSB; The UE measures the CSI-RS and / or DMRS of the PBCH (in the SSB), including channel state measurements, interference measurements, L1-RSRP measurements, etc., and then the UE reports the measurement results to the gNB; and The gNB performs beam management, scheduling, etc. based on the CSI measurement results reported by the UE.

[0031] In NR, the overall CSI framework includes CSI resource configuration and CSI reporting configuration. The CSI resource configuration defines the structure of the CSI-RS, its occupied bandwidth, time-domain characteristics (periodic, semi-persistent, aperiodic), etc. The CSI reporting configuration defines the CSI resource configuration for measurement reporting, the time-domain characteristics of the report (periodic, semi-persistent, aperiodic), the number of reports, the frequency-domain configuration of the report, etc.

[0032] 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, of which aperiodic CSI reporting and SP CSI reporting on PUSCH are all triggered or activated by a DCI format and transmitted on PUSCH.

[0033] The inventors have found that the existing methods for triggering / activating / deactivating aperiodic CSI reports and PUSCH-based SP CSI reports are designed based on the assumption that a DCI format can schedule the PUSCH of only one cell (or uplink carrier), and therefore cannot be directly applied to cases where a DCI format can schedule the PUSCH of multiple cells (or uplink carriers).

[0034] In view of at least one of the above problems, embodiments of the present invention provide a method and apparatus for reporting channel state information.

[0035] In an embodiment of the present invention, DCI format 0_X is used to represent a DCI format for supporting scheduling of PUSCHs of multiple cells (or uplink carriers) using one DCI, and the name of the DCI format is not limited, and may be DCI format 0_1, DCI format 0_2, and / or DCI format 0_3, etc.

[0036] For example, a network device may configure cells that can be scheduled by DCI format 0_X through higher layer signaling or parameters. For example, DCI format 0_X may include fields for indicating cells and / or uplink carriers. Through higher layer signaling or parameter configuration, the values of the fields may correspond to one or more cells and / or uplink carriers. Thus, when the fields indicate multiple cells and / or uplink carriers, scheduling of multiple cells and / or uplink carriers using one DCI can be realized.

[0037] In some embodiments, DCI format 0_X includes one or more fields for cell and / or uplink carrier indication.

[0038] In some embodiments, one cell may configure one uplink carrier, i.e., (N)UL ((normal)UL), or two uplink carriers, i.e., (N)UL and SUL (supplementary UL).

[0039] In some embodiments, DCI format 0_X includes both a field for indicating a cell and a field for indicating an uplink carrier. In other words, 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 that can be scheduled by DCI format 0_X include two 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 a PUSCH to be scheduled is located. Among them, if DCI format 0_X includes multiple fields for indicating uplink carriers within a cell, different fields for indicating uplink carriers within a cell correspond to different cells or different cell sets / cell groups.

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

[0041] In an embodiment of the present invention, "scheduling a cell and / or an uplink carrier" is equivalent to "scheduling uplink transmission (eg, PUSCH) on the cell and / or the uplink carrier."

[0042] In an embodiment of the present invention, "DCI format 0_X is scrambled with a certain RNTI" includes "CRC (Cyclic Redundancy Check) check bits of the DCI format are scrambled with the RNTI".

[0043] In an embodiment of the present invention, a DCI format "for scheduling PUSCHs on one or more cells and / or uplink carriers" has the following meaning: the DCI format is at least capable of scheduling / scheduling / has the ability to schedule PUSCHs on multiple cells and / or uplink carriers at once or simultaneously, and each of the multiple cells and / or uplink carriers has one or more scheduled PUSCHs; and the DCI format is capable of scheduling / scheduling / has the ability to schedule PUSCHs on one cell and / or uplink carrier at once, and each of the single cell and / or uplink carrier has one or more scheduled PUSCHs; or the DCI format is at least capable of scheduling / scheduling / has the ability to schedule PUSCHs on multiple cells and / or uplink carriers at once or simultaneously, and each of the multiple cells and / or uplink carriers has one or more scheduled PUSCHs; and The format does not / cannot / does not have the ability to schedule PUSCH on only one cell and / or uplink carrier at a time.

[0044] Hereinafter, embodiments of the present invention will be described in conjunction with the drawings and specific implementation modes.

[0045] <Example of the first aspect> In the embodiment of the present invention, an aperiodic CSI reporting method is provided, which is applied to the terminal device side.

[0046] FIG. 4 illustrates a method for reporting aperiodic CSI in an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps: 401: A terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and 402: The terminal device transmits a CSI report.

[0047] Note that the above-mentioned FIG. 4 is for illustrative purposes only and uses a terminal device as an example to explain an embodiment of the present invention, but the present invention is not limited to this. For example, it is possible to appropriately adjust the execution order between operations (steps), add or remove some operations, or adjust the target of each operation. Those skilled in the art will be able to make appropriate modifications based on the above content without being limited to the description of the above-mentioned FIG. 4.

[0048] According to an embodiment of the present invention, aperiodic CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

[0049] In the above embodiment, the aperiodic CSI reporting based on DCI format 0_X includes the following steps: The base station sets one or more trigger states (trigger state lists) through higher layer signaling or parameters (e.g., CSI-AperiodicTriggerStateList), each trigger state corresponding to or associated with one or more CSI reporting configurations; and The UE monitors the DCI format 0_X and determines which trigger state (CSI aperiodic trigger state) is triggered based on the value of the CSI request field therein.

[0050] 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 for aperiodic CSI reporting is, for example, as shown in Figure 2, where the reference signals for measurement are omitted.

[0051] In this embodiment, the trigger state refers to the CSI aperiodic trigger state, and the CSI report refers to the aperiodic CSI report.

[0052] In an embodiment of the present invention, the higher layer parameters for configuring the trigger state list are dedicated to DCI format 0_X or common (shared) to DCI format 0_X and another DCI format. "Dedicated" means that the higher layer parameters are for DCI format 0_X only. "Shared" means that, when monitoring of another DCI format for triggering aperiodic CSI reporting is configured, the higher layer parameters are for DCI format 0_X and the other DCI format, simultaneously or non-simultaneously, with respect to the other DCI format. "Simultaneous" means that, when monitoring of DCI format 0_X is configured (and DCI format 0_X is used to trigger aperiodic CSI reporting) and monitoring of the other DCI format for triggering aperiodic CSI reporting is also configured, the higher layer parameters are for DCI format 0_X and the other DCI format. "Non-simultaneous" refers to the fact that two DCI formats cannot all be configured as those that need to be monitored, or that all need to be monitored but cannot all be configured as those that trigger aperiodic CSI reporting, so that the higher layer parameters, in the case of a specific DCI format configuration, are only for DCI format 0_X or the other DCI format, and not for DCI format 0_X and the other DCI format at the same time.

[0053] In some embodiments of the present invention, the above-mentioned DCI format schedules a PUSCH on one cell and / or uplink carrier, and the terminal device transmits the above-mentioned CSI report on the one cell and / or uplink carrier.

[0054] In some other embodiments, when the above-mentioned DCI format requests or triggers aperiodic CSI reporting, the DCI format schedules a PUSCH on only one cell and / or uplink carrier, allowing a terminal device to transmit a CSI report on this one cell and / or uplink carrier, thereby maximizing reuse of existing methods, reducing complexity, and reducing equipment upgrade costs.

[0055] For example, the DCI format may include a field (or information field) for requesting or triggering a CSI report, such as a CSI request field, and the value of the field may correspond to a CSI aperiodic trigger state. When the value of the field corresponds to one CSI aperiodic trigger state, the DCI format schedules a PUSCH on only one cell and / or uplink carrier, and the terminal device transmits a corresponding CSI report on the PUSCH of the one cell and / or uplink carrier.

[0056] In the above embodiment, the length of the CSI request field is N TS (i.e., N TS bits) and is set by the network device using higher layer parameters (e.g., reportTriggerSize) and has a maximum

[0057]

number

[0058]

number

[0059]

number

[0060]

number

[0061]

number

[0062] In the above-described embodiments, in some implementation schemes, the length of the CSI request field is configured by a higher layer parameter, which may be dedicated to DCI format 0_X or may be common (shared) to DCI format 0_X and another DCI format. "Dedicated" refers to being dedicated to DCI format 0_X only. "Shared" refers to being dedicated to DCI format 0_X and another DCI format simultaneously or non-simultaneously when monitoring of another DCI format for triggering a CSI report is configured. "Simultaneous" refers to being dedicated to both DCI format 0_X and another DCI format when monitoring of DCI format 0_X (and DCI format 0_X is used to trigger a CSI report) and another DCI format for triggering a CSI report is configured. Non-simultaneous refers to the fact that two DCI formats cannot all be configured as needing to be monitored, or that all must be monitored but not all can be configured as being used to trigger CSI reporting, so that the higher layer parameters, in the case of a specific DCI format configuration, are only for DCI format 0_X or the other DCI format, and not for both DCI format 0_X and the other DCI format.

[0063] In the above-mentioned embodiment, in some other implementation manners, the length of the above-mentioned CSI request field is not determined by a higher layer parameter, but is determined by the terminal device based on the number of trigger states in the corresponding trigger state list configured.

[0064] In some other embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the terminal device transmits a CSI report on the cell and / or uplink carrier indicated by the field.

[0065] For example, DCI format 0_X includes a field for indicating a cell and / or an uplink carrier, such as a carrier indication field, which can indicate one or more cells and / or uplink carriers, but when DCI format 0_X requests or triggers aperiodic CSI reporting, the field indicates only one cell and / or uplink carrier.

[0066] FIG. 5 is a diagram illustrating an example of aperiodic CSI reporting.

[0067] As shown in Figure 5, in this example, the CRC of DCI format 0_X is scrambled by the C-RNTI or MCS-C-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cell indicated exemplarily on the left side of Figure 5 is a Pcell and the cell indicated exemplarily on the right side of Figure 5 is an Scell, the terminal device can transmit a CSI report on the cell and / or uplink carrier indicated by the carrier indication field. In this example, the PUSCH may or may not carry UL-SCH data.

[0068] FIG. 6 is a diagram illustrating another example of aperiodic CSI reporting.

[0069] As shown in Figure 6, in this example, the CRC of DCI format 0_X is scrambled by the C-RNTI or MCS-C-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cell indicated on the left side of Figure 6 is a Pcell and the cell indicated on the right side of Figure 6 is an Scell, the terminal device can transmit a CSI report on the cell and / or uplink carrier indicated by the carrier indication field. In this example, the PUSCH may or may not carry UL-SCH data. This example differs from the example of Figure 5 in that DCI format 0_X schedules two PUSCHs.

[0070] In some other embodiments, the terminal device transmits the CSI report on a cell and / or uplink carrier for transmitting the CSI report, which is set by default or by signaling.

[0071] In the above embodiment, in some implementations, 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.

[0072] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier to be scheduled, 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 aperiodic CSI reporting, the field does not indicate a cell and / or uplink carrier. For example, a bit in the field is set as a dedicated value, and the dedicated value does not correspond to any cell and / or uplink carrier. The terminal device transmits the CSI report on the cell and / or uplink carrier for transmission of the CSI report that is set by default or by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0073] FIG. 7 is a diagram illustrating an example of aperiodic CSI reporting.

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

[0075] FIG. 8 is a diagram illustrating another example of aperiodic CSI reporting.

[0076] As shown in Figure 8, in this example, the CRC of DCI format 0_X is scrambled by the C-RNTI or MCS-C-RNTI, the CSI request field indicates a triggered state, the carrier indication field does not indicate a cell and / or uplink carrier, and when the cell indicated exemplarily on the left side of Figure 8 is a Pcell and the cell indicated exemplarily on the right side of Figure 8 is an Scell, the terminal device can transmit a CSI report on a default cell and / or uplink carrier configured by signaling. In this example, the PUSCH may or may not carry UL-SCH data. This example differs from the example of Figure 7 in that DCI format 0_X schedules two PUSCHs.

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

[0078] For example, DCI format 0_X includes a field for indicating a cell and / or an 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 aperiodic CSI reporting, the terminal device ignores the field. The terminal device transmits the CSI report on the cell and / or uplink carrier for transmission of the CSI report by default or configured by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0079] In some other implementations, the DCI format includes a field for requesting or triggering a CSI report, and the field for requesting or triggering a CSI report is located before the field for indicating the cell and / or uplink carrier.

[0080] In the above-mentioned implementations, in some examples, the DCI format does not include a field for indicating the above-mentioned cell and / or uplink carrier when requesting or triggering aperiodic CSI reporting.

[0081] For example, when DCI format 0_X does not request or trigger aperiodic 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. However, when DCI format 0_X requests or triggers aperiodic CSI reporting, the DCI format 0_X does not include the carrier indication field. The field for requesting or triggering a CSI report (CSI request field) precedes the field for indicating a cell and / or uplink carrier (carrier indication field). The terminal device transmits a CSI report on a cell and / or uplink carrier for transmission of the CSI report that is set by default or by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0082] In each of the above-described embodiments, the cell for transmitting the default CSI report may be a Pcell (primary cell), a Pscell (primary secondary cell), or a PUCCH Scell (physical uplink control channel secondary cell), and the present invention is not limited thereto.

[0083] Among them, when the default cell includes only one uplink carrier, the default uplink carrier is the uplink carrier of the cell; when the default cell includes multiple uplink carriers, for example, NUL and SUL, which uplink carrier of the cell is used to transmit the CSI report is indicated, for example, by a field (for example, UL-SUL indicator) for indicating the uplink carrier in the cell included in DCI format 0_X; alternatively, the CSI report is transmitted on the default uplink carrier of the cell, and the default uplink carrier is, for example, NUL or SUL, or is set to be the PUCCH carrier among the multiple uplink carriers.

[0084] In some other embodiments of the present invention, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers, and the terminal device transmits a CSI report on one cell and / or uplink carrier of the one or more cells and / or uplink carriers.

[0085] For example, when DCI format 0_X triggers aperiodic CSI reporting, it schedules PUSCHs on one or more cells and / or uplink carriers, when scheduling PUSCHs on multiple cells and / or uplink carriers, the terminal device transmits a CSI report on the PUSCH of one of the cells and / or uplink carriers, and when scheduling PUSCHs on one cell and / or uplink carrier, the terminal device transmits the CSI report using the same method as in the above embodiment. This allows existing methods to be reused to some extent, and allows the network device to schedule UL-SCH data transmissions of multiple cells using the same DCI at the same time as triggering a CSI report, thereby increasing scheduling flexibility and data transmission throughput.

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

[0087] Wherein, the length of this field may be set by a higher layer parameter or may be determined by the terminal device based on the number of trigger states in the trigger state list configured. Here, the higher layer parameter may be specific to this DCI format or may be common (shared) with this DCI format and other DCI formats. Since the CSI request field has already been described in the previous embodiments, its content is incorporated herein and its detailed description is omitted here.

[0088] In some embodiments, the one cell and / or uplink carrier is a default or signaling-configured cell and / or uplink carrier for transmitting the CSI report, i.e., the terminal device transmits the CSI report on the default or signaling-configured cell and / or uplink carrier for transmitting the CSI report.

[0089] In the above-mentioned embodiment, the DCI format may further include a field for indicating a cell and / or an uplink carrier, and the cell and / or uplink carrier for transmitting the CSI report, which is set by default or by signaling, 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.

[0090] 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. However, when DCI format 0_X requests or triggers aperiodic CSI reporting, for example, when the field indicates multiple cells and / or uplink carriers, the terminal device transmits the CSI report on a 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 for transmitting the CSI report or is configured by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0091] FIG. 9 is a diagram illustrating an example of aperiodic CSI reporting.

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

[0093] FIG. 10 is a diagram illustrating another example of aperiodic CSI reporting.

[0094] As shown in FIG. 10 , in this example, the CRC of DCI format 0_X is scrambled by the C-RNTI or MCS-C-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cells indicated on the left side of FIG. 10 are a Pcell and an Scell, and the cells indicated on the right side of FIG. 10 are two Scells, the terminal device can transmit a CSI report on a default cell and / or an uplink carrier configured by signaling. In this example, the PUSCH may or may not carry UL-SCH data. Also, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other of which does not. The difference from the example of FIG. 9 is that the two PUSCHs in the example of FIG. 10 are shifted in the time domain.

[0095] 9 and 10, the case where one cell and / or uplink carrier has multiple PUSCHs is not shown, but embodiments of the present invention do not exclude such a case. That is, although Figures 9 and 10 show that one cell and / or uplink carrier has only one PUSCH, in embodiments of the present invention, one cell and / or uplink carrier may have additional PUSCHs.

[0096] In the above embodiment, the cell for transmitting the default CSI report may be the cell with the smallest serving cell indicator number among the scheduled cells; and / or the cell in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located; and / or the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located. The present invention is not limited thereto, and the cell for transmitting the default CSI report may be another cell defined by other rules.

[0097] In the above embodiment, the cell for transmitting the default CSI report may be a Pcell, a PScell, or a PUCCH Scell, and the present invention is not limited thereto.

[0098] In some other embodiments, the terminal device transmits the CSI report on the default PUCCH.

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

[0100] 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. However, when DCI format 0_X requests or triggers aperiodic CSI reporting, for example, when the field indicates multiple cells and / or uplink carriers, the terminal device transmits the CSI report on the default PUSCH of one of them.

[0101] FIG. 11 is a diagram illustrating an example of aperiodic CSI reporting.

[0102] As shown in Figure 11, in this example, the CRC of DCI format 0_X is scrambled by the C-RNTI or MCS-C-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cells indicated on the left side of Figure 11 are a Pcell and an Scell, and the cells indicated on the right side of Figure 11 are two Scells, the terminal device can transmit a CSI report on the default PUSCH. In this example, the PUSCH carries or does not carry UL-SCH data. Also, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other of which does not. The difference from the example of Figure 9 is that the two PUSCHs in the example of Figure 11 are shifted in the time domain.

[0103] Although the example of Fig. 11 above does not show a case where one cell and / or uplink carrier has multiple PUSCHs, embodiments of the present invention do not exclude such a case. That is, although Fig. 11 shows only one PUSCH in one cell and / or uplink carrier, embodiments of the present invention may show other PUSCHs in one cell and / or uplink carrier.

[0104] In the above embodiment, the default PUSCH may be the PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; and / or the first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and / or the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain is located. The present invention is not limited thereto, and the default PUSCH may be another PUSCH defined by another rule.

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

[0106] In some embodiments of the present invention, the DCI format schedules PUSCHs on multiple cells and / or uplink carriers, and the terminal device transmits a CSI report on one or more of the multiple cells and / or uplink carriers.

[0107] For example, when DCI format 0_X triggers aperiodic CSI reporting, it schedules PUSCHs on one or more cells and / or uplink carriers; when scheduling PUSCHs on multiple cells and / or uplink carriers, the terminal device transmits a CSI report on the PUSCHs of one, some, or all of the cells and / or uplink carriers; and when scheduling a PUSCH on one cell and / or uplink carrier, the terminal device transmits a CSI report using the same method as in the above embodiment. In this way, the network device can use the same DCI to trigger the terminal device to transmit a CSI report on one, some, or all of the cells and / or uplink carriers, and can also use the same DCI to schedule UL-SCH data transmissions for multiple cells while triggering the CSI report, thereby improving CSI feedback efficiency when the bandwidth of each carrier is relatively small, and also increasing scheduling flexibility and data transmission throughput.

[0108] In the above embodiment, the DCI format may include a field for indicating a cell and / or an uplink carrier, and the field indicates the above-mentioned multiple cells and / or uplink carriers.

[0109] 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 indicating that multiple cells and / or uplink carriers are scheduled, the terminal device transmits CSI reports on the PUSCHs of the multiple cells and / or uplink carriers.

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

[0111] In some implementations, the above-mentioned DCI format includes a field for requesting or triggering one CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are respectively used to carry different CSI reports corresponding to the trigger states associated with the field, and / or different PUSCHs are respectively used to carry different parts of the CSI report.

[0112] For example, DCI format 0_X includes one field for requesting or triggering CSI, e.g., a CSI request field, and CSI reports on different PUSCHs are identical (overlapping), and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger states indicated by the field (wherein one trigger state may correspond to one or more CSI reports), and / or different PUSCHs are used to carry different parts of the CSI report (e.g., carrying Part 1 and Part 2, respectively).

[0113] In some implementations, the above-mentioned DCI format includes multiple CSI report request or trigger fields, and different PUSCHs are used to carry CSI reports corresponding to trigger conditions associated with different CSI report request or trigger fields.

[0114] For example, DCI format 0_X includes multiple CSI request or trigger fields, e.g., CSI request fields, where different fields correspond to different cells and / or uplink carriers; in other words, different PUSCHs are used to carry CSI reports corresponding to trigger conditions indicated by different CSI request or trigger fields.

[0115] FIG. 12 is a diagram illustrating an example of aperiodic CSI reporting.

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

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

[0118] In an embodiment of the present invention, the terminal device may further receive configuration information for configuring the terminal device to monitor the DCI format in a search space dedicated to the UE. The present invention does not limit the specific configuration method. For details of the configuration information, please refer to the related art.

[0119] In an embodiment of the present invention, the terminal device may further receive configuration information for indicating whether the above-mentioned DCI format supports triggering of CSI reporting or whether the above-mentioned DCI format is for triggering CSI reporting. The present invention does not limit the specific configuration method. For details of the configuration information, please refer to the related art.

[0120] In an embodiment of the present invention, the terminal device may further receive configuration information for configuring cells and / or uplink carriers that can be scheduled using the above-mentioned DCI format. The present invention does not limit the specific configuration method, and reference may be made to the related art for the relevant content of the configuration information.

[0121] In an embodiment of the present invention, the above-mentioned multiple uplink carriers may be different cells, or at least two of the above-mentioned multiple uplink carriers may be different cells, and the present invention is not limited thereto.

[0122] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0123] As can be seen from the above embodiments, aperiodic CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

[0124] <Example of the second aspect> In an embodiment of the present invention, a method for receiving a CSI report is provided, which is applied to a network device side and is a process on the network device side corresponding to the method in the embodiment of the first aspect, and the description of the same content as in the embodiment of the first aspect will be omitted.

[0125] 13 is a diagram illustrating a method for receiving a CSI report in an embodiment of the present invention. As shown in FIG. 13, the method includes the following steps: 1301: A network device transmits a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering an aperiodic CSI report; and 1302: The network device receives a CSI report.

[0126] Note that, although the above-mentioned FIG. 13 is used to exemplify an embodiment of the present invention, the present invention is not limited thereto. For example, the execution order of each operation may be appropriately adjusted, or some operations may be added or removed. Those skilled in the art may make appropriate modifications based on the above content without being limited to the description of the above-mentioned FIG. 13.

[0127] According to an embodiment of the present invention, aperiodic CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

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

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

[0130] In some embodiments, the above-mentioned DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates one cell and / or uplink carrier, and the network device receives the CSI report on the cell and / or uplink carrier indicated by the field.

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

[0132] In the above-mentioned embodiment, in some implementations, the above-mentioned 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.

[0133] 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.

[0134] In some embodiments, the above-mentioned DCI format includes a field for requesting or triggering a CSI report, and the field for requesting or triggering a CSI report is located before a field for indicating a cell and / or an uplink carrier.

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

[0136] In some embodiments, the above-mentioned default cell for receiving the CSI report is a Pcell or a PScell or a PUCCH Scell.

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

[0138] In each of the above-mentioned embodiments, the above-mentioned DCI format may include a field for requesting or triggering a CSI report, and the value of the field corresponds to a CSI aperiodic trigger state.

[0139] In the above embodiment, the length of the above field may be set by a higher layer parameter or may be determined by the terminal device based on the number of trigger states in the configured trigger state list. The above higher layer parameter may be specific to the DCI format, or may be common (shared) between the DCI format and other DCI formats.

[0140] In some embodiments, the one cell and / or uplink carrier is a default or signaling-configured cell and / or uplink carrier for transmitting the CSI report.

[0141] In the above embodiment, the cell for transmitting the default CSI report may be at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain is located; and The cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

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

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

[0144] In the above embodiment, the default PUSCH may be at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

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

[0146] In some embodiments, the DCI format described above includes fields for cell and / or uplink carrier indication.

[0147] In the above-mentioned embodiments, the cell and / or uplink carrier for transmitting the CSI report, which is set by the default or signaling, may be within the range of one or more cells and / or uplink carriers indicated by the above-mentioned fields, or may not be within the range of one or more cells and / or uplink carriers indicated by the above-mentioned fields.

[0148] In some embodiments, the above-mentioned DCI format schedules PUSCH on multiple cells and / or uplink carriers, and the network device receives CSI reports on one or more of the multiple cells and / or uplink carriers.

[0149] In the above embodiment, the above DCI format may include a field for indicating a cell and / or an uplink carrier, and the field indicates the plurality of cells and / or uplink carriers.

[0150] In the above embodiments, the content of the CSI reports on different PUSCHs may be the same or different.

[0151] In the above-mentioned embodiments, the above-mentioned DCI format may include a field for requesting or triggering one CSI report, and the CSI report on different PUSCHs may be the same, and / or different PUSCHs may be used to carry different CSI reports corresponding to trigger conditions associated with the field, and / or different PUSCHs may be used to carry different parts of the CSI report.

[0152] In the above-described embodiment, the above-described DCI format may include multiple CSI report request or trigger fields, and different PUSCHs may be used to carry CSI reports corresponding to trigger conditions associated with different CSI report request or trigger fields.

[0153] In each of the above-described embodiments, the CRC of the DCI format may be scrambled by the C-RNTI or by the MCS-C-RNTI.

[0154] In each of the above-described embodiments, the network device may further transmit configuration information for configuring the terminal device to monitor the above-described DCI format in a search space dedicated to the UE.

[0155] In each of the above-mentioned embodiments, the network device may further transmit configuration information for configuring whether the above-mentioned DCI format supports triggering of CSI reporting or whether the above-mentioned DCI format is for triggering of CSI reporting.

[0156] In each of the above-described embodiments, the network device can further transmit configuration information for configuring cells and / or uplink carriers on which the above-described DCI formats can be scheduled.

[0157] In each of the above embodiments, the above-mentioned multiple uplink carriers may be in different cells, or at least two of the above-mentioned multiple uplink carriers may be in different cells.

[0158] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0159] As can be seen from the above embodiments, aperiodic CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

[0160] <Example of the third aspect> In an embodiment of the present invention, a semi-persistent CSI reporting method is provided, which is applied to the terminal device side.

[0161] 14 is a diagram illustrating a semi-persistent CSI reporting method according to an embodiment of the present invention. As shown in FIG. 14, the method includes the following steps: 1401: A terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and 1402: The terminal device transmits a CSI report.

[0162] Note that the above-mentioned Figure 14 is intended to exemplify an embodiment of the present invention, and uses a terminal device as an example, but the present invention is not limited to this. For example, it is possible to appropriately adjust the execution order between operations (steps), add or remove some operations, or adjust the target of each operation. Those skilled in the art will be able to make appropriate modifications based on the above content without being limited to the description of the above-mentioned Figure 14.

[0163] According to an embodiment of the present invention, semi-persistent CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

[0164] For SP CSI reporting on the PUSCH, the base station sets the reporting period, slot shift, etc. through higher layer signaling or parameters, and is triggered by the DCI format scrambled by the SP-CSI-RNTI.

[0165] SP CSI reporting based on DCI format 0_X includes the following steps: The base station configures one or more trigger states (trigger state lists) through higher layer signaling or parameters (e.g., CSI-SemiPersistentOnPUSCH-TriggerStateList), where each trigger state corresponds to / is associated with one or more CSI reporting configurations; and 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 therein. A CSI request field value equal to 0 corresponds to the first trigger state in the above list, and a CSI request field value equal to 1 corresponds to the second trigger state in the above list, and so on.

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

[0167] In an embodiment of the present invention, the higher layer parameters for configuring the trigger state list are dedicated to DCI format 0_X or common (shared) to DCI format 0_X and another DCI format. "Dedicated" means that the higher layer parameters are for DCI format 0_X only. "Common (shared)" means that when configured to monitor another DCI format for triggering an SP-CSI report, the higher layer parameters are for DCI format 0_X and the other DCI format, simultaneously or non-simultaneously, with respect to the other DCI format. "Simultaneous" means that when configured to monitor DCI format 0_X (and DCI format 0_X is used to trigger an SP-CSI report) and the other DCI format for triggering an SP-CSI report, the higher layer parameters are for both DCI format 0_X and the other DCI format. Non-simultaneous refers to the fact that two DCI formats cannot all be configured as needing to be monitored, or that all needing to be monitored but not all can be configured as being used to trigger SP-CSI reporting, so that the higher layer parameters are only for DCI format 0_X or the other DCI format in the case of a specific DCI format configuration, and not for DCI format 0_X and the other DCI format at the same time.

[0168] In this embodiment, the trigger state refers to the semi-persistent CSI trigger state, and the CSI report refers to the semi-persistent CSI report.

[0169] In some embodiments of the present invention, the above-mentioned DCI format schedules a PUSCH on one cell and / or uplink carrier, and the terminal device transmits the above-mentioned CSI report on the one cell and / or uplink carrier.

[0170] In some other embodiments, when the above-mentioned DCI format triggers or activates semi-persistent CSI reporting, the DCI format schedules a PUSCH on only one cell and / or uplink carrier, allowing a terminal device to transmit a CSI report on this one cell and / or uplink carrier, thereby maximizing reuse of existing methods, reducing complexity, and reducing equipment upgrade costs.

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

[0172] In the above embodiment, the length of the CSI request field is N TS (i.e., N TS bits), set by the network device using higher layer parameters (e.g., reportTriggerSize), up to

[0173]

number

[0174]

number

[0175]

number

[0176]

number

[0177]

number

[0178] In the above-described embodiments, in some implementations, the length of the CSI request field is configured by a higher layer parameter, which may be dedicated to DCI format 0_X or common (shared) to DCI format 0_X and another DCI format. "Dedicated" refers to being dedicated to DCI format 0_X only. "Common (shared)" refers to being dedicated to DCI format 0_X and another DCI format simultaneously or non-simultaneously when monitoring of another DCI format for triggering a CSI report is configured. "Simultaneous" refers to being dedicated to both DCI format 0_X and another DCI format when monitoring of DCI format 0_X (and DCI format 0_X is used to trigger a CSI report) and another DCI format for triggering a CSI report is configured. Non-simultaneous refers to the fact that two DCI formats cannot all be configured as needing to be monitored, or that all need to be monitored but not all can be configured as being used to trigger CSI reporting, so that the higher layer parameters are only for DCI format 0_X or the other DCI format in the case of a specific DCI format configuration, and not for DCI format 0_X and the other DCI format at the same time.

[0179] In the above-mentioned embodiment, in some other implementation manners, the length of the above-mentioned CSI request field is not determined by a higher layer parameter, but is determined by the terminal device based on the number of trigger states in the corresponding trigger state list configured.

[0180] In some other embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the terminal device transmits a CSI report on the cell and / or uplink carrier indicated by the field.

[0181] For example, DCI format 0_X includes a field for indicating a cell and / or an uplink carrier, such as a carrier indication field, which can indicate one or more cells and / or uplink carriers, but indicates only one cell and / or uplink carrier when DCI format 0_X triggers or activates semi-persistent CSI reporting.

[0182] FIG. 15 is a diagram illustrating an example of semi-persistent CSI reporting.

[0183] As shown in Figure 15, in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cell indicated exemplarily on the left side of Figure 15 is a Pcell and the cell indicated exemplarily on the right side of Figure 15 is an Scell, the terminal device can transmit 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-persistent. In this example, the PUSCH may or may not carry UL-SCH data.

[0184] FIG. 16 is a diagram illustrating another example of semi-persistent CSI reporting.

[0185] As shown in Figure 16, in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cell indicated on the left side of Figure 16 is a Pcell and the cell indicated on the right side of Figure 16 is an Scell, the terminal device can transmit 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-persistent. In this example, the PUSCH may or may not carry UL-SCH data. This example differs from the example of Figure 15 in that the DCI format 0_X schedules two PUSCHs.

[0186] In some other embodiments, the terminal device transmits the CSI report on a cell and / or uplink carrier for transmitting the CSI report by default or configured by signaling.

[0187] In the above embodiment, in some implementations, 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.

[0188] For example, DCI format 0_X includes a field for indicating a cell and / or uplink carrier to be scheduled, such as a carrier indication field, and the field can indicate one or more cells and / or uplink carriers. However, when DCI format 0_X triggers or activates semi-persistent CSI reporting, the field does not indicate a cell and / or uplink carrier. For example, a bit in the field is set as a dedicated value, and the dedicated value does not correspond to any cell and / or uplink carrier. The terminal device transmits the CSI report on the cell and / or uplink carrier for transmission of the CSI report that is set by default or by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0189] FIG. 17 is a diagram illustrating an example of semi-persistent CSI reporting.

[0190] As shown in Figure 17, in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, the CSI request field indicates a triggered state, the carrier indication field does not indicate a cell and / or uplink carrier, and the cell indicated exemplarily on the left side of Figure 17 is a Pcell and the cell indicated exemplarily on the right side of Figure 17 is an Scell, in which case the terminal device can transmit a CSI report on a default cell and / or uplink carrier configured by signaling. As shown in Figure 17, the CSI report is semi-persistent. In this example, the PUSCH may or may not carry UL-SCH data.

[0191] FIG. 18 is a diagram illustrating another example of semi-persistent CSI reporting.

[0192] As shown in Figure 18, in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, the CSI request field indicates a triggered state, the carrier indication field does not indicate a cell and / or uplink carrier, and the cell indicated exemplarily on the left side of Figure 18 is a Pcell and the cell indicated exemplarily on the right side of Figure 18 is an Scell, in which case the terminal device can transmit a CSI report on a default cell and / or uplink carrier configured by signaling. As shown in Figure 18, the CSI report is semi-persistent. In this example, the PUSCH may or may not carry UL-SCH data. This example differs from the example of Figure 17 in that the DCI format 0_X schedules two PUSCHs.

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

[0194] For example, DCI format 0_X includes a field for indicating a cell and / or an 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 triggers or activates semi-persistent CSI reporting, the terminal device ignores the field. The terminal device transmits the CSI report on the cell and / or uplink carrier for transmission of the CSI report that is set by default or by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0195] In some other implementations, the DCI format includes a field for triggering or activating a CSI report, and the field for triggering or activating a CSI report is located before the field for indicating the cell and / or uplink carrier.

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

[0197] 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. However, 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 a CSI report (CSI request field) is located before the field for indicating a cell and / or uplink carrier (carrier indication field). The terminal device transmits a CSI report on a cell and / or uplink carrier for transmission of the CSI report that is set by default or by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0198] In each of the above embodiments, the cell for transmitting the default CSI report may be a Pcell, a Pscell, or a PUCCH Scell, and the present invention is not limited thereto.

[0199] Wherein, 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 multiple uplink carriers, for example, NUL and SUL, the default uplink carrier is, for example, NUL and SUL, or the PUCCH carrier among the multiple uplink carriers is set.

[0200] In some other embodiments of the present invention, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers, and the terminal device transmits a CSI report on one cell and / or uplink carrier of the one or more cells and / or uplink carriers.

[0201] For example, when DCI format 0_X triggers or activates semi-persistent CSI reporting, it schedules PUSCHs on one or more cells and / or uplink carriers, when scheduling PUSCHs on multiple cells and / or uplink carriers, the terminal device transmits a CSI report on the PUSCH of one of the cells and / or uplink carriers, and when scheduling a PUSCH on one cell and / or uplink carrier, the terminal device transmits the CSI report using the same method as in the above embodiment. This allows existing methods to be reused to some extent, and allows the network device to schedule UL-SCH data transmissions of multiple cells using the same DCI at the same time as triggering or activating semi-persistent CSI reporting, thereby increasing scheduling flexibility and data transmission throughput.

[0202] In the above embodiment, the DCI format may include a field (or information field) for triggering or activating a CSI report, 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 one CSI trigger state, the DCI schedules a PUSCH on one or more cells and / or uplink carriers, and the terminal device transmits a corresponding CSI report on the PUSCH of one cell and / or uplink carrier.

[0203] Wherein, the length of this field may be set by a higher layer parameter or may be determined by the terminal device based on the number of trigger states in the trigger state list configured. Here, the higher layer parameter may be specific to this DCI format or may be common (shared) with this DCI format and other DCI formats. Since the CSI request field has already been described in the previous embodiments, its content is incorporated herein and its detailed description is omitted here.

[0204] In some embodiments, the one cell and / or uplink carrier is a default or signaling-configured cell and / or uplink carrier for transmitting the CSI report, i.e., the terminal device transmits the CSI report on the default or signaling-configured cell and / or uplink carrier for transmitting the CSI report.

[0205] In the above-mentioned embodiment, the DCI format may further include a field for indicating a cell and / or an uplink carrier, and the cell and / or uplink carrier for transmitting the CSI report, which is set by default or by signaling, 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.

[0206] 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. However, when DCI format 0_X triggers or activates semi-persistent CSI reporting, for example, when the field indicates multiple cells and / or uplink carriers, the terminal device transmits the CSI report on a 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 for transmitting the CSI report or is configured by signaling (e.g., RRC and / or MAC CE and / or DCI, etc.).

[0207] FIG. 19 is a diagram illustrating an example of semi-persistent CSI reporting.

[0208] As shown in FIG. 19 , in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cells indicated on the left side of FIG. 19 are a Pcell and an Scell, and the cells indicated on the right side of FIG. 19 are two Scells, the terminal device can transmit a CSI report on a default cell and / or an uplink carrier configured by signaling. As shown in FIG. 19 , the CSI report is semi-persistent. In this example, the PUSCH carries or does not carry UL-SCH data. Also, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other of which does not carry a CSI report.

[0209] FIG. 20 is a diagram illustrating another example of semi-persistent CSI reporting.

[0210] As shown in FIG. 20 , in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. In the example shown in FIG. 20 , the cells indicated are a Pcell and an Scell, and the cells indicated are two Scells. In this example, the terminal device can transmit a CSI report on a default cell and / or an uplink carrier configured by signaling. As shown in FIG. 20 , the CSI report is semi-persistent. In this example, the PUSCH may or may not carry UL-SCH data. Also, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other of which does not. The difference from the example shown in FIG. 19 is that the two PUSCHs in the example shown in FIG. 20 are shifted in the time domain.

[0211] 19 and 20, the case where one cell and / or uplink carrier has multiple PUSCHs is not shown, but embodiments of the present invention do not exclude such a case. That is, although Figures 19 and 20 show only one PUSCH in one cell and / or uplink carrier, embodiments of the present invention may include other PUSCHs in one cell and / or uplink carrier.

[0212] In the above embodiment, the cell for transmitting the default CSI report may be the cell with the smallest serving cell indicator number among the scheduled cells; and / or the cell in which the first PUSCH that satisfies 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 indicator number among the cells in which the first PUSCH that satisfies the semi-persistent CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located. The present invention is not limited thereto, and the cell for transmitting the default CSI report may be another cell defined by other rules.

[0213] In the above embodiment, the cell for transmitting the default CSI report may be a Pcell, a PScell, or a PUCCH Scell, and the present invention is not limited thereto.

[0214] In some other embodiments, the terminal device transmits the CSI report on the default PUCCH.

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

[0216] 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. However, when DCI format 0_X triggers or activates semi-persistent CSI reporting, for example, when the field indicates multiple cells and / or uplink carriers, the terminal device transmits the CSI report on one of the default PUSCHs.

[0217] FIG. 21 is a diagram illustrating an example of semi-persistent CSI reporting.

[0218] As shown in FIG. 21 , in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, the CSI request field indicates a triggered state, and the carrier indication field indicates a cell and / or an uplink carrier. When the cells indicated on the left side of FIG. 21 are a Pcell and an Scell, and the cells indicated on the right side of FIG. 21 are two Scells, the terminal device can transmit a CSI report on the default PUSCH. As shown in FIG. 21 , the CSI report is semi-persistent. In this example, the PUSCH may or may not carry UL-SCH data. Also, in this example, the DCI format 0_X is associated with two PUSCHs, one of which carries a CSI report and the other of which does not. The difference from the example of FIG. 19 is that the two PUSCHs in the example of FIG. 21 are shifted in the time domain.

[0219] Although the example of Figure 21 above does not show a case where one cell and / or uplink carrier has multiple PUSCHs, embodiments of the present invention do not exclude such a case. That is, although Figure 21 shows that one cell and / or uplink carrier has only one PUSCH, embodiments of the present invention may show that one cell and / or uplink carrier has additional PUSCHs.

[0220] In the above embodiment, the default PUSCH may be the PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; and / or the first PUSCH among the scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain; and / or the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH among the scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located. The present invention is not limited thereto, and the default PUSCH may be another PUSCH defined by another rule.

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

[0222] In some embodiments of the present invention, the DCI format schedules PUSCHs on multiple cells and / or uplink carriers, and the terminal device transmits a CSI report on one or more of the multiple cells and / or uplink carriers.

[0223] For example, when DCI format 0_X triggers or activates semi-persistent CSI reporting, it schedules PUSCHs on one or more cells and / or uplink carriers; when scheduling PUSCHs on multiple cells and / or uplink carriers, the terminal device transmits a CSI report on the PUSCHs of one, some, or all of the cells and / or uplink carriers; and when scheduling a PUSCH on one cell and / or uplink carrier, the terminal device transmits the CSI report using the same method as in the above embodiment. In this way, the network device can use the same DCI to trigger the terminal device to transmit a CSI report on one, some, or all of the cells and / or uplink carriers, and can also use the same DCI to schedule UL-SCH data transmissions for multiple cells while triggering the CSI report, thereby improving CSI feedback efficiency when the bandwidth of each carrier is relatively small, and also increasing scheduling flexibility and data transmission throughput.

[0224] In the above embodiment, the DCI format may include a field for indicating a cell and / or an uplink carrier, and the field indicates the above-mentioned multiple cells and / or uplink carriers.

[0225] 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 indicating that multiple cells and / or uplink carriers are scheduled, the terminal device transmits CSI reports on the PUSCHs of the multiple cells and / or uplink carriers.

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

[0227] In some implementations, the above-mentioned DCI format includes one field for triggering or activating a CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are respectively used to carry different CSI reports corresponding to the trigger states associated with the field, and / or different PUSCHs are respectively used to carry different parts of the CSI report.

[0228] For example, DCI format 0_X includes one field for triggering or activating CSI, e.g., a CSI request field, and CSI reports on different PUSCHs are identical (overlapping), and / or different PUSCHs are used to carry different CSI reports corresponding to the trigger states indicated by the field (wherein one trigger state can correspond to one or more CSI reports), and / or different PUSCHs are used to carry different parts of the CSI report (e.g., carrying Part 1 and Part 2, respectively).

[0229] In some implementations, the above-mentioned DCI format includes multiple CSI report trigger or activation fields, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different CSI report trigger or activation fields.

[0230] For example, DCI format 0_X includes multiple fields for triggering or activating CSI, e.g., CSI request fields, where different fields correspond to different cells and / or uplink carriers, respectively. In other words, different PUSCHs are used to carry CSI reports corresponding to trigger conditions indicated by different fields for triggering or activating CSI, respectively.

[0231] FIG. 22 is a diagram illustrating an example of semi-persistent CSI reporting.

[0232] As shown in Figure 22, in this example, the CRC of DCI format 0_X is scrambled with the SP-CSI-RNTI, one or more CSI request fields indicate triggered states, and the carrier indication field indicates a cell and / or an uplink carrier. For example, if the cells indicated on the left side of Figure 22 are a Pcell and an Scell, and the cells indicated on the right side of Figure 22 are two Scells, the terminal device can transmit CSI reports on two cells and / or uplink carriers, and the contents of the CSI reports on the two cells and / or uplink carriers may be the same or different. In this example, the PUSCH may or may not carry UL-SCH data. In this example, the DCI format 0_X schedules two PUSCHs.

[0233] Although Figures 15 to 22 illustrate an example in which the SP-CSI reporting periods on different cells and / or uplink carriers are the same, the present invention is not limited thereto, and the SP-CSI reporting periods on different cells and / or uplink carriers may be the same or different.

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

[0235] In an embodiment of the present invention, the terminal device further determines / validates the validity of the above-mentioned DCI format for semi-persistent CSI activation.

[0236] In some embodiments, the terminal device determines / validates the above validity based on a field for indicating a cell and / or an uplink carrier and / or a field for indicating a HARQ process ID and / or a field for indicating an RV in the above DCI format.

[0237] For example, the above-mentioned DCI format includes multiple fields for indicating HARQ process IDs, and the terminal device determines / validates the above-mentioned validity based on the fields for indicating some or all of the cells and / or uplink carriers in the DCI format.

[0238] Also, for example, the above-mentioned DCI format has multiple fields for indicating RV, and the terminal device determines / validates the above-mentioned validity based on some or all of the fields for indicating RV in the DCI format.

[0239] Furthermore, for example, the above-mentioned DCI format includes one or more fields for indicating cells and / or uplink carriers, and the terminal device determines / validates the above-mentioned validity based on some or all of the fields for indicating cells and / or uplink carriers in the DCI format.

[0240] In the above-mentioned embodiments, the above-mentioned embodiments for determining / validating the validity may be used alone or in combination, and are not limited by the present invention. In the above-mentioned embodiments, if the terminal device determines that the DCI format is invalid, the terminal device ignores or drops the DCI format. Alternatively, if the terminal device determines that the DCI format is invalid, the terminal device may determine that the CRC of the DCI format does not match or that the CRC check has failed.

[0241] In each of the above-mentioned embodiments, the above-mentioned fields in a valid DCI format should satisfy certain conditions.

[0242] For example, the field for indicating the cell and / or uplink carrier should indicate one cell and / or uplink carrier, and / or the cell and / or uplink carrier indicated by the field is a Pcell, a PScell, or a PUCCH Scell. Also, for example, the field should be a dedicated value, and the dedicated value does not correspond to any cell and / or uplink carrier.

[0243] Furthermore, when DCI format 0_X has multiple fields for indicating HARQ process IDs (e.g., HARQ process number fields) and / or multiple fields for indicating RVs (e.g., redundancy version fields), all of the multiple fields shall satisfy the following condition: Alternatively, the field for indicating HARQ process IDs and / or the field for indicating RVs corresponding to the cell and / or uplink carrier indicated by the field for indicating the cell and / or uplink carrier shall satisfy the following condition: Optionally, the terminal equipment ignores other fields for indicating HARQ process IDs and / or other fields for indicating RVs.

[0244] These conditions refer to the settings shown in the table below.

[0245] [Table 1] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0246] As can be seen from the above embodiments, semi-persistent CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

[0247] <Example of the fourth aspect> In an embodiment of the present invention, a method for receiving a CSI report is provided, which is applied to a network device side and is a process on the network device side corresponding to the method in the embodiment of the third aspect, and the description of the same content as in the embodiment of the third aspect will be omitted.

[0248] 23 is a diagram illustrating a method for receiving a CSI report in an embodiment of the present invention. As shown in FIG. 23, the method includes the following steps: 2301: A network device transmits a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and 2302: The network device receives a CSI report.

[0249] Note that, although the above-mentioned FIG. 23 is used to exemplify an embodiment of the present invention, the present invention is not limited thereto. For example, the execution order of each operation may be appropriately adjusted, or some operations may be added or removed. Those skilled in the art may make appropriate modifications based on the above content without being limited to the description of the above-mentioned FIG. 23.

[0250] According to an embodiment of the present invention, semi-persistent CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

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

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

[0253] In some embodiments, the above-mentioned DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates one cell and / or uplink carrier, and the network device receives the CSI report on the cell and / or uplink carrier indicated by the field.

[0254] In some embodiments, the network device receives the CSI report on a cell and / or uplink carrier for transmission of the CSI report that is configured by default or by signaling.

[0255] In the above-mentioned embodiment, in some implementations, the above-mentioned 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.

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

[0257] In the above-mentioned embodiments, in some implementation schemes, the above-mentioned DCI format includes a field for requesting or triggering a CSI report, and the field for requesting or triggering a CSI report is located before the field for indicating a cell and / or an uplink carrier.

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

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

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

[0261] In each of the above-mentioned embodiments, the above-mentioned DCI format may include a field for requesting or triggering a CSI report, and the value of the field corresponds to a CSI trigger state.

[0262] In the above-mentioned embodiment, the length of the field may be set by a higher layer parameter, and the higher layer parameter may be specific to the above-mentioned DCI format or common (shared) to the above-mentioned DCI format and other DCI formats.

[0263] In the above embodiment, the length of the field may also be determined by the terminal device based on the number of trigger conditions in the trigger condition list set.

[0264] In each of the above embodiments, the one cell and / or uplink carrier is a default cell and / or uplink carrier for transmitting a CSI report or is configured by signaling.

[0265] For example, the cell for transmission of the default CSI report may be at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located; and The cell having the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the semi-persistent CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0266] Also, for example, the cell for transmitting the default CSI report may be a Pcell, a PScell, or a PUCCH Scell.

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

[0268] For example, the default PUSCH may be at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0269] Also, for example, the cell in which the default PUSCH is located may be a Pcell, a PScell, or a PUCCH Scell.

[0270] In some embodiments, the DCI format described above includes fields for cell and / or uplink carrier indication.

[0271] In the above-mentioned embodiments, the cell and / or uplink carrier for transmitting the CSI report set by the default or signaling may be within the range of one or more cells and / or uplink carriers indicated by the above-mentioned fields, or may not be within the range of one or more cells and / or uplink carriers indicated by the above-mentioned fields.

[0272] In some embodiments, the above-mentioned DCI format schedules PUSCH on multiple cells and / or uplink carriers, and the network device receives CSI reports on one or more of the multiple cells and / or uplink carriers.

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

[0274] In the above embodiments, the content of the CSI reports on different PUSCHs may be the same or different.

[0275] In the above-mentioned embodiments, the above-mentioned DCI format may further include one field for triggering or activating a CSI report, and the CSI report on different PUSCHs may be the same, and / or different PUSCHs may be used to carry different CSI reports corresponding to trigger states associated with the field, and / or different PUSCHs may be used to carry different parts of the CSI report.

[0276] In the above-mentioned embodiment, the above-mentioned DCI format may further include fields for triggering or activating multiple CSI reports, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different CSI report request or trigger fields.

[0277] In each of the above-described embodiments, the CRC of the DCI format may be scrambled by the SP-CSI-RNTI.

[0278] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0279] As can be seen from the above embodiments, semi-persistent CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

[0280] <Example of the fifth aspect> In an embodiment of the present invention, a semi-persistent CSI reporting release or deactivation method is provided, which is applied on the terminal device side.

[0281] FIG. 24 illustrates a method for releasing or deactivating a semi-persistent CSI report in an embodiment of the present invention. As shown in FIG. 24 , the method includes the following steps: 2401: A terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format releasing or deactivating semi-persistent CSI reporting; and 2402: The terminal device deactivates semi-persistent CSI reporting.

[0282] Note that the above-mentioned Figure 24 is intended to exemplify an embodiment of the present invention, and uses a terminal device as an example, but the present invention is not limited to this. For example, it is possible to appropriately adjust the execution order between operations (steps), add or remove some operations, or adjust the target of each operation. Those skilled in the art will be able to make appropriate modifications based on the above content without being limited to the description of the above-mentioned Figure 24.

[0283] According to an embodiment of the present invention, it is possible to realize the release or deactivation of semi-persistent CSI reporting in a case where a DCI format can schedule PUSCHs of multiple cells.

[0284] In some embodiments, the above-mentioned DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates one cell or 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 dedicated value, where the dedicated value does not correspond to any cell and / or uplink carrier.

[0285] In the above embodiment, when validating, the terminal device also takes into account fields for indicating the scheduled cell and / or uplink carrier.

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

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

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

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

[0290] In the above example, the above DCI format may further include one or more fields for indicating cells and / or uplink carriers, and the terminal device can determine / validate the above validity based on some or all of the fields for indicating cells and / or uplink carriers in the DCI format.

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

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

[0293] In each of the above examples, if the DCI format is invalid, the terminal device can further ignore or drop the DCI format. Alternatively, if the terminal device determines that the DCI format is invalid, it can consider that the CRC of the DCI format does not match or the CRC check has failed.

[0294] In an embodiment of the present invention, when DCI format 0_X includes multiple fields for indicating HARQ process IDs (e.g., HARQ process number fields) and / or multiple fields for indicating RVs (e.g., redundancy version fields) and / or multiple fields for indicating MCSs and / or multiple fields for indicating frequency domain resource (RB) allocation, all of the multiple fields shall satisfy the following condition: Alternatively, the above-mentioned fields corresponding to the cell and / or uplink carrier indicated by the field for indicating the scheduled cell and / or uplink carrier shall satisfy the following condition: Optionally, the terminal device ignores other fields for indicating HARQ process IDs.

[0295] These conditions are the settings shown in the table below.

[0296] [Table 2] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0297] As can be seen from the above embodiments, it is possible to realize the release or deactivation of semi-persistent CSI reporting when the DCI format can schedule PUSCHs of multiple cells.

[0298] <Example of the sixth aspect> An embodiment of the present invention provides a method for releasing or deactivating semi-persistent CSI reporting, which is applied to a network device and is a process on the network device side corresponding to the method in the embodiment of the fifth aspect, and the description of the same content as in the embodiment of the fifth aspect will be omitted.

[0299] 25 is a diagram illustrating a method for releasing or deactivating a semi-persistent CSI report in an embodiment of the present invention. As shown in FIG. 25, the method includes the following steps: 2501: A network device transmits a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format releasing or deactivating semi-persistent CSI reporting.

[0300] Note that, although the above-mentioned Figure 25 is used to exemplify an embodiment of the present invention, the present invention is not limited thereto. For example, some other operations may be added. Those skilled in the art will be able to make appropriate modifications based on the above content without being limited to the description of the above-mentioned Figure 25.

[0301] According to an embodiment of the present invention, it is possible to realize the release or deactivation of semi-persistent CSI reporting in a case where a DCI format can schedule PUSCHs of multiple cells.

[0302] In some embodiments, the above-mentioned DCI format includes a field for indicating a cell and / or an uplink carrier, where the field indicates one cell or 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 dedicated value, where the dedicated value does not correspond to any cell and / or uplink carrier.

[0303] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0304] As can be seen from the above embodiments, it is possible to realize the release or deactivation of semi-persistent CSI reporting when the DCI format can schedule PUSCHs of multiple cells.

[0305] In the above-described embodiments of the first to sixth aspects, a DCI format (referred to as DCI format 0_X) that supports scheduling PUSCHs of one or more cells and / or uplink carriers using one DCI is described. The following table shows a specific example of fields of the DCI format 0_X.

[0306] The table below summarizes the ranges of DCI format 0_X.

[0307] [Table 3] In the above example, the "type-1 field" is a single field indicating common information for all co-scheduled cells, or a single field indicating separate information for each co-scheduled cell through joint indication, or a single field indicating information for only one of the co-scheduled cells. DCI format 0_X includes only one such field.

[0308] In the above example, the "type-2 field" is a single field for each co-scheduled cell, or a single field for each subgroup containing one or more co-scheduled cells, where a single field usually applies to co-scheduled cells that belong to the same subgroup. DCI format 0_X includes multiple such fields.

[0309] In the above example, the "type-3 field" may be common (shared) for each cell or subgroup to be jointly scheduled, or may be independent. DCI format 0_X includes one or more such fields, which may be explicitly configured or implicitly determined, for example, intra-band or inter-band CA, FR1, or FR2.

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

[0311] In the above example, the area refers to a field, which may also be called an information area.

[0312] <Example of the seventh aspect> An embodiment of the present invention provides an aperiodic CSI reporting device, which may be, for example, a terminal device or one or more components or assemblies installed in the terminal device. Here, descriptions of the same content as in the embodiments of the first and second aspects will be omitted.

[0313] 26 is a diagram illustrating an aperiodic CSI reporting device in an embodiment of the present invention. As shown in FIG. 26, an aperiodic CSI reporting device 2600 in an embodiment of the present invention includes: A receiving unit 2601: receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and Transmitting unit 2602: Transmits the CSI report.

[0314] In some embodiments, the DCI format schedules a PUSCH on one cell and / or uplink carrier, and the transmitting unit 2602 transmits the CSI report on the one cell and / or uplink carrier.

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

[0316] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the transmitting unit 2602 transmits the CSI report on the cell and / or uplink carrier indicated by the field.

[0317] In some embodiments, the transmitting unit 2602 transmits the CSI report on a cell and / or uplink carrier for transmission of the CSI report that is configured by default or by signaling.

[0318] 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.

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

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

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

[0322] In some embodiments, the cell for transmission of the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

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

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

[0325] In some embodiments, the length of the field is set by a higher layer parameter, and the higher layer parameter is either specific to the DCI format or common (shared) to the DCI format and other DCI formats.

[0326] In some embodiments, the length of the field is determined by the terminal device based on the number of trigger conditions in a configured trigger condition list.

[0327] In some embodiments, the one cell and / or uplink carrier is a default or signaling-configured cell and / or uplink carrier for transmitting a CSI report.

[0328] In some embodiments, the cell for transmission of the default CSI report is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain is located; and The cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0329] In some embodiments, the cell for transmission of the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0330] In some embodiments, the transmitting unit 2602 transmits the CSI report on a default PUSCH.

[0331] In some embodiments, the default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0332] In some embodiments, the default PUSCH cell is a Pcell, a PScell, or a PUCCH Scell.

[0333] In some embodiments, the DCI format includes fields for cell and / or uplink carrier indication.

[0334] In some embodiments, the cell and / or uplink carrier for transmission of the default or signaling-configured CSI report 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.

[0335] In some embodiments, the DCI format schedules a PUSCH on multiple cells and / or uplink carriers, and the transmitting unit 2602 transmits the CSI report on one or more cells and / or uplink carriers among the multiple cells and / or uplink carriers.

[0336] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating the plurality of cells and / or uplink carriers.

[0337] In some embodiments, the content of the CSI reports on different PUSCHs may be the same or different.

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

[0339] In some embodiments, the DCI format includes multiple CSI report request or trigger fields, and different PUSCHs are used to carry CSI reports corresponding to trigger conditions associated with different CSI report request or trigger fields, respectively.

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

[0341] In some embodiments, the receiving unit 2601 further receives configuration information for configuring the terminal device to monitor the DCI format in a search space dedicated to the UE.

[0342] In some embodiments, the receiving unit 2601 further receives configuration information for configuring whether the DCI format supports triggering of a CSI report or whether the DCI format is for triggering of a CSI report.

[0343] In some embodiments, the receiving unit 2601 further receives configuration information for configuring a cell and / or an uplink carrier on which the DCI format can be scheduled.

[0344] In some embodiments, each of the plurality of uplink carriers is for a different cell, or at least two of the plurality of uplink carriers are for a different cell.

[0345] An embodiment of the present invention further provides a device for receiving a CSI report, which may be, for example, a network device or one or more components or assemblies installed in the network device, and the description of the same content as the embodiments of the first and second aspects will be omitted here.

[0346] 27 is a diagram illustrating a receiving apparatus for CSI report in an embodiment of the present invention. As shown in FIG. 27, the receiving apparatus for CSI report 2700 in an embodiment of the present invention includes: A transmitting unit 2701: transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and Receiving unit 2702: Receives the CSI report.

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

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

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

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

[0351] 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.

[0352] 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.

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

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

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

[0356] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers, and 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.

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

[0358] In some embodiments, the length of the field is set by a higher layer parameter, and the higher layer parameter is either specific to the DCI format or common (shared) to the DCI format and other DCI formats.

[0359] In some embodiments, the length of the field is determined by the terminal device based on the number of trigger conditions in a configured trigger condition list.

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

[0361] In some embodiments, the default cell for receiving CSI reports is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain is located; and The cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

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

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

[0364] In some embodiments, the default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0365] In some embodiments, the default PUSCH cell is a Pcell, a PScell, or a PUCCH Scell.

[0366] In some embodiments, the DCI format includes fields for cell and / or uplink carrier indication.

[0367] In some embodiments, the default or signaling-configured cell and / or uplink carrier for receiving the CSI report 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.

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

[0369] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating the plurality of cells and / or uplink carriers.

[0370] In some embodiments, the content of the CSI reports on different PUSCHs may be the same or different.

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

[0372] In some embodiments, the DCI format includes multiple CSI report request or trigger fields, and different PUSCHs are used to carry CSI reports corresponding to trigger conditions associated with different CSI report request or trigger fields, respectively.

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

[0374] In some embodiments, the sending unit 2701 further sends configuration information for configuring the terminal device to monitor the DCI format in a search space dedicated to the UE.

[0375] In some embodiments, the sending unit 2701 further sends configuration information for configuring whether the DCI format supports triggering of a CSI report or whether the DCI format is for triggering of a CSI report.

[0376] In some embodiments, the transmitting unit 2701 further transmits configuration information for configuring a cell and / or an uplink carrier on which the DCI format can be scheduled.

[0377] In some embodiments, each of the plurality of uplink carriers is for a different cell, or at least two of the plurality of uplink carriers are for a different cell.

[0378] An embodiment of the present invention further provides a semi-persistent CSI reporting device, which may be, for example, a terminal device or one or more components or assemblies installed in the terminal device, and in this section, descriptions of the same content as in the embodiments of the third and fourth aspects will be omitted.

[0379] 28 is a diagram illustrating a semi-persistent CSI reporting device in an embodiment of the present invention. As shown in FIG. 28, a semi-persistent CSI reporting device 2800 in an embodiment of the present invention includes: A receiving unit 2801: receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and A transmitting unit 2802: transmits the CSI report.

[0380] In some embodiments, the DCI format schedules a PUSCH on one cell and / or uplink carrier, and the transmitting unit 2802 transmits the CSI report on the one cell and / or uplink carrier.

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

[0382] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the transmitting unit 2802 transmits the CSI report on the cell and / or uplink carrier indicated by the field.

[0383] In some embodiments, the transmitting unit 2802 transmits the CSI report on a cell and / or uplink carrier for transmission of the CSI report that is configured by default or by signaling.

[0384] 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.

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

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

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

[0388] In some embodiments, the cell for transmission of the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0389] In some embodiments, the DCI format schedules a PUSCH on one or more cells and / or uplink carriers, and the transmitting unit 2802 transmits the CSI report on one cell and / or uplink carrier of the one or more cells and / or uplink carriers.

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

[0391] In some embodiments, the length of the field is set by a higher layer parameter, and the higher layer parameter is either specific to the DCI format or common (shared) to the DCI format and other DCI formats.

[0392] In some embodiments, the length of the field is determined by the terminal device based on the number of trigger conditions in a configured trigger condition list.

[0393] In some embodiments, the one cell and / or uplink carrier is a default or signaling-configured cell and / or uplink carrier for transmitting a CSI report.

[0394] In some embodiments, the cell for transmission of the default CSI report is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located; and The cell having the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the semi-persistent CSI reporting timing requirement in the time domain among the scheduled PUSCHs is located.

[0395] In some embodiments, the cell for transmission of the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0396] In some embodiments, the transmitting unit 2802 transmits the CSI report on a default PUSCH.

[0397] In some embodiments, the default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0398] In some embodiments, the default PUSCH cell is a Pcell, a PScell, or a PUCCH Scell.

[0399] In some embodiments, the DCI format includes fields for cell and / or uplink carrier indication.

[0400] In some embodiments, the cell and / or uplink carrier for transmission of the default or signaling-configured CSI report 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.

[0401] In some embodiments, the DCI format schedules a PUSCH on multiple cells and / or uplink carriers, and the transmitting unit 2802 transmits the CSI report on one or more cells and / or uplink carriers among the multiple cells and / or uplink carriers.

[0402] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating the plurality of cells and / or uplink carriers.

[0403] In some embodiments, the content of the CSI reports on different PUSCHs may be the same or different.

[0404] In some embodiments, the DCI format includes one field for triggering or activating a CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are each used to carry a different CSI report corresponding to a trigger state associated with the field, and / or different PUSCHs are each used to carry a different part of the CSI report.

[0405] In some embodiments, the DCI format includes multiple CSI report trigger or activation fields, and different PUSCHs are used to carry CSI reports corresponding to trigger conditions associated with different CSI report request or trigger fields, respectively.

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

[0407] In some embodiments, as shown in FIG. 28, the apparatus 2800 further includes: A determination / validation unit 2803: determines / validates the validity of the DCI format for semi-persistent CSI activation.

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

[0409] In some embodiments, the DCI format includes multiple fields for indicating HARQ process IDs, and the determination / confirmation unit 2803 determines / validates the validity based on the fields for indicating some or all of the cells and / or uplink carriers in the DCI format.

[0410] In some embodiments, the DCI format includes multiple fields for indicating RV, and the determination / confirmation unit 2803 determines / validates the validity based on some or all of the fields for indicating RV in the DCI format.

[0411] In some embodiments, the DCI format includes one or more fields for indicating cells and / or uplink carriers, and the determination / confirmation unit 2803 determines / validates the validity based on some or all of the fields for indicating cells and / or uplink carriers in the DCI format.

[0412] In some embodiments, if the DCI format is invalid, the receiving unit 2801 ignores or drops the DCI format.

[0413] An embodiment of the present invention further provides a device for receiving a CSI report, which may be, for example, a network device or one or more components or assemblies installed in the network device, and the description of the same content as in the third and fourth embodiments will be omitted here.

[0414] 29 is a diagram illustrating a receiving apparatus for CSI report in an embodiment of the present invention. As shown in FIG. 29, the receiving apparatus for CSI report 2900 in an embodiment of the present invention includes: A transmitting unit 2901: transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and Receiving unit 2902: Receives the CSI report.

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

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

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

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

[0419] 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.

[0420] 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.

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

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

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

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

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

[0426] In some embodiments, the length of the field is set by a higher layer parameter, and the higher layer parameter is either specific to the DCI format or common (shared) to the DCI format and other DCI formats.

[0427] In some embodiments, the length of the field is determined by the terminal device based on the number of trigger conditions in a configured trigger condition list.

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

[0429] In some embodiments, the default cell for receiving CSI reports is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located; and The device is a cell with the smallest serving cell indicator number among cells in which a first PUSCH that satisfies a semi-persistent CSI reporting timing requirement in the time domain among scheduled PUSCHs is located.

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

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

[0432] In some embodiments, the default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0433] In some embodiments, the default PUSCH cell is a Pcell, a PScell, or a PUCCH Scell.

[0434] In some embodiments, the DCI format includes fields for cell and / or uplink carrier indication.

[0435] In some embodiments, the default or signaling-configured cell and / or uplink carrier for receiving the CSI report 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.

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

[0437] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating the plurality of cells and / or uplink carriers.

[0438] In some embodiments, the content of the CSI reports on different PUSCHs may be the same or different.

[0439] In some embodiments, the DCI format includes one field for triggering or activating a CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are each used to carry a different CSI report corresponding to a trigger state associated with the field, and / or different PUSCHs are each used to carry a different part of the CSI report.

[0440] In some embodiments, the DCI format includes multiple CSI report trigger or activation fields, and different PUSCHs are used to carry CSI reports corresponding to trigger conditions associated with different CSI report request or trigger fields, respectively.

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

[0442] An embodiment of the present invention further provides a device for releasing or deactivating semi-persistent CSI reports, which may be, for example, a terminal device or one or more components or assemblies installed in the terminal device, and the description of the same content as in the embodiments of the fifth and sixth aspects will be omitted here.

[0443] 30 is a diagram illustrating a semi-persistent CSI report release or deactivation device 3000 according to an embodiment of the present invention. As shown in FIG. 30, the semi-persistent CSI report release or deactivation device 3000 according to an embodiment of the present invention includes: A receiving unit 3001: receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format releasing or deactivating semi-persistent CSI reporting; and Processing unit 3002: Deactivate semi-persistent CSI reporting.

[0444] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, wherein the field indicates one cell or 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 dedicated value, wherein the dedicated value does not correspond to any cell and / or uplink carrier.

[0445] In some embodiments, as shown in FIG. 30, the apparatus 3000 further includes: A determination / validation unit 3003: determines / validates the validity of the DCI format for semi-persistent CSI release / deactivation.

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

[0447] In some embodiments, the DCI format includes multiple fields for indicating HARQ process IDs, and the determination / confirmation unit 3003 determines / validates the validity based on some or all of the fields for indicating HARQ process IDs in the DCI format.

[0448] In some embodiments, the DCI format includes multiple fields for indicating RV, and the determination / confirmation unit 3003 determines / validates the validity based on some or all of the fields for indicating RV in the DCI format.

[0449] In some embodiments, the DCI format includes one or more fields for indicating cells and / or uplink carriers, and the determination / confirmation unit 3003 determines / validates the validity based on some or all of the fields for indicating cells and / or uplink carriers in the DCI format.

[0450] In some embodiments, the DCI format includes multiple fields for indicating MCS (Modulation and coding scheme), and the determination / confirmation unit 3003 determines / validates the validity based on some or all of the MCS indication fields in the DCI format.

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

[0452] In some embodiments, if the DCI format is invalid, the determination / confirmation unit 3003 ignores or drops the DCI format.

[0453] An embodiment of the present invention further provides a device for releasing or deactivating semi-persistent CSI reports, which may be, for example, a network device or one or more components or assemblies installed in the network device, and in this description, descriptions of the same content as in the fifth and sixth embodiments are omitted.

[0454] 31 is a diagram illustrating a device 3100 for releasing or deactivating a semi-persistent CSI report in an embodiment of the present invention. As shown in FIG. 31, the device 3100 for releasing or deactivating a semi-persistent CSI report in an embodiment of the present invention includes: A transmitting unit 3101: transmits a DCI format for scheduling PUSCH on one or more cells and / or uplink carriers, where the DCI format releases or deactivates semi-persistent CSI reporting.

[0455] In some embodiments, the DCI format includes a field for indicating a cell and / or an uplink carrier, wherein the field indicates one cell or 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 dedicated value, wherein the dedicated value does not correspond to any cell and / or uplink carrier.

[0456] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0457] Although only the components or modules related to the present invention have been described above, the present invention is not limited thereto. The devices 2600, 2700, 2800, 2900, 3000, and 3100 may further include other components or modules, and reference can be made to the related art for details of these components or modules.

[0458] 26 to 31 show only the connection relationships or signal directions between each component or module, but as will be understood by those skilled in the art, various related technologies such as bus connections may be adopted. Each of the above-described components or modules may be realized by hardware such as a processor, memory, transmitter (device), or receiver (device), but the implementation of the present invention is not limited to this.

[0459] As can be seen from the above embodiments, aperiodic CSI reporting and PUSCH-based semi-persistent CSI reporting can be realized when the DCI format can schedule PUSCHs of multiple cells.

[0460] <Example of the eighth aspect> An embodiment of the present invention further provides a communication system, which can be seen from FIG. 1, and the description of the same contents as those of the embodiments of the first to sixth aspects will be omitted here.

[0461] In some embodiments, the communication system 100 includes at least a network device and a terminal device, wherein the network device is configured to perform a method according to an embodiment of the second, fourth or sixth aspect, and the terminal device is configured to perform a method according to an embodiment of the first, third or fifth aspect.

[0462] The network devices and terminal devices have already been described in detail in the first to sixth aspects, and therefore the details thereof are incorporated herein and will not be described in detail here.

[0463] Although the embodiment of the present invention further provides a terminal device, the present invention is not limited thereto and may further include other devices.

[0464] Figure 32 is a diagram illustrating a terminal device according to an embodiment of the present invention. As shown in Figure 32, the terminal device 3200 may include a processor 3210 and a memory 3220, where the memory 3220 stores data and programs and is connected to the processor 3210. Note that this diagram is merely an example, and other types of components may be used to supplement or replace the components to achieve telecommunications or other functions.

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

[0466] As shown in Figure 32, the terminal device 3200 may further include the following: a communication module 3230, an input unit 3240, a display 3250, a power supply 3260, etc. The functions of the above-mentioned components are the same as those of the prior art, and detailed descriptions thereof will be omitted here. Note that the terminal device 3200 does not need to include all the components shown in Figure 32, and these components are not essential. Furthermore, the terminal device 3200 may further include components not shown in Figure 32, and reference can be made to the prior art for such components.

[0467] In the embodiment of the present invention, a network device is further provided, which may be, for example, a base station, but the present invention is not limited thereto and may also be other network devices.

[0468] Figure 33 is a configuration diagram of a network device in an embodiment of the present invention. As shown in Figure 33, a network device 3300 may include the following: a processor 3310 (e.g., a central processing unit (CPU)) and a memory 3320, which is connected to the processor 3310. The memory 3320 can store various data and can also store a program 3330 for information processing, and can execute the program 3330 under the control of the processor 3310.

[0469] For example, the processor 3310 may be configured to execute a program to implement the method described in the embodiments of the second, fourth or sixth aspects.

[0470] 33, the network device 3300 may further include the following: a transceiver 3340, an antenna 3350, etc., of which the functions of the above-mentioned components are the same as those of the prior art, and detailed description thereof will be omitted here. Note that the network device 3300 does not need to include all the components shown in Fig. 33, and the network device 3300 may further include components not shown in Fig. 33, for which reference can be made to the prior art.

[0471] An embodiment of the present invention further provides a computer program, which, when executed on a terminal device, causes the terminal device to perform a method according to an embodiment of the first, third or fifth aspect.

[0472] An embodiment of the present invention further provides a storage medium storing a computer program, wherein the computer program causes a terminal device to perform the method described in the embodiment of the first, third or fifth aspect.

[0473] In an embodiment of the present invention, a computer program is further provided, which, when executed by a network device, causes the network device to perform a method described in an embodiment of the second, fourth or sixth aspect.

[0474] An embodiment of the present invention further provides a storage medium storing a computer program, wherein the computer program causes a network device to perform a method according to an embodiment of the second, fourth or sixth aspect.

[0475] The above-described devices and methods may be realized by software or hardware, or by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, which, when executed by a logic component, causes the logic component to realize the above-described devices or components, or to perform each of the above-described methods or steps. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, or a processing unit used in a computer. The present invention also relates to a storage medium, such as a hard disk, magnetic disk, optical hard disk, DVD, or flash memory, that stores the above-described program.

[0476] Furthermore, one or more combinations of the functional blocks illustrated in the figures and / or one or more combinations of the functional blocks 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 component, a discrete gate or transistor logic component, a discrete hardware assembly, or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks illustrated in the figures and / or one or more combinations of the functional blocks may be further configured 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 configuration.

[0477] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and any modifications to the present invention that do not depart from the spirit of the present invention fall within the technical scope of the present invention.

[0478] Furthermore, the following additional notes are disclosed regarding the above-described embodiments.

[0479] (Appendix 1) 1. An aperiodic CSI reporting method, comprising: A terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and The terminal device transmitting a CSI report.

[0480] (Appendix 2) 2. The method of claim 1, comprising: The DCI format schedules a PUSCH on one cell and / or uplink carrier, and the terminal device transmits the CSI report on the one cell and / or uplink carrier.

[0481] (Appendix 3) 10. The method according to claim 1 or 2, When the DCI format requests or triggers aperiodic CSI reporting, the DCI format schedules a PUSCH on only one cell and / or uplink carrier.

[0482] (Appendix 4) 10. The method of claim 2, The DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the terminal device transmits the CSI report on the cell and / or uplink carrier indicated by the field.

[0483] (Appendix 5) 10. The method of claim 2, The terminal device transmits the CSI report on a cell and / or uplink carrier for transmitting the CSI report by default or configured by signaling.

[0484] (Appendix 6) 6. The method of claim 5, 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.

[0485] (Appendix 7) 6. The method of claim 5, The DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores the field.

[0486] (Appendix 8) 2. The method of claim 1, comprising: The DCI format includes a field for requesting or triggering a CSI report, and the field for requesting or triggering a CSI report is located before a field for indicating a cell and / or an uplink carrier.

[0487] (Appendix 9) 10. The method according to claim 5 or 8, The DCI format does not include a field for indicating a cell and / or an uplink carrier when requesting or triggering aperiodic CSI reporting.

[0488] (Appendix 10) 10. The method according to any one of appendices 5-9, comprising: The cell for transmitting the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0489] (Appendix 11) 2. The method of claim 1, comprising: The DCI format schedules a PUSCH on one or more cells and / or uplink carriers, and the terminal device transmits the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0490] (Appendix 12) 12. The method of claim 1, 2 or 11, The DCI format includes a field for requesting or triggering a CSI report, and the value of the field corresponds to a CSI aperiodic trigger state.

[0491] (Appendix 13) 13. The method of claim 12, The length of the field is set by a higher layer parameter, and the higher layer parameter is either dedicated to the DCI format or common (shared) to the DCI format and other DCI formats.

[0492] (Appendix 14) 13. The method of claim 12, The length of the field is determined by the terminal device based on the number of trigger conditions in the trigger condition list that is set.

[0493] (Appendix 15) 12. The method of claim 11, The one cell and / or uplink carrier is a default cell and / or uplink carrier for transmitting a CSI report configured by signaling.

[0494] (Appendix 16) 16. The method of claim 15, The cell for transmission of the default CSI report is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain is located; and The cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0495] (Appendix 17) 17. The method according to claim 15 or 16, The cell for transmitting the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0496] (Appendix 18) 2. The method of claim 1, comprising: The terminal device transmits the CSI report on a default PUSCH.

[0497] (Appendix 19) 19. The method of claim 18, The default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0498] (Appendix 20) 20. The method according to claim 18 or 19, The cell where the default PUSCH is located is a Pcell, a PScell, or a PUCCH Scell.

[0499] (Appendix 21) 16. The method of claim 15, The DCI format includes a field for indicating a cell and / or an uplink carrier.

[0500] (Appendix 22) 22. The method of claim 21, The cell and / or uplink carrier for transmitting the default or signaled CSI report 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.

[0501] (Appendix 23) 2. The method of claim 1, comprising: The DCI format schedules PUSCH on multiple cells and / or uplink carriers, and the terminal device transmits the CSI report on one or more cells and / or uplink carriers among the multiple cells and / or uplink carriers.

[0502] (Appendix 24) 24. The method of claim 23, The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the multiple cells and / or uplink carriers.

[0503] (Appendix 25) 24. The method of claim 23, The content of the CSI reports on different PUSCHs may be the same or different.

[0504] (Appendix 26) 26. The method according to claim 23 or 25, The DCI format includes a field for requesting or triggering one CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are respectively used to carry different CSI reports corresponding to trigger states associated with the field, and / or different PUSCHs are respectively used to carry different parts of the CSI report.

[0505] (Appendix 27) 26. The method according to claim 23 or 25, The DCI format includes fields for requesting or triggering multiple CSI reports, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different CSI report request or trigger fields, respectively.

[0506] (Appendix 28) 28. The method of any one of claims 1 to 27, comprising: The CRC of the DCI format is scrambled by the C-RNTI or by the MCS-C-RNTI.

[0507] (Appendix 29) 29. The method of any one of claims 1 to 28, comprising: The terminal device receives configuration information for configuring the terminal device to monitor the DCI format in a search space dedicated to the UE.

[0508] (Appendix 30) 30. The method of any one of claims 1 to 29, comprising: The terminal device receives configuration information for setting whether the DCI format supports triggering of a CSI report or whether the DCI format is for triggering a CSI report.

[0509] (Appendix 31) 31. The method of any one of claims 1 to 30, comprising: The terminal device receives configuration information for configuring a cell and / or an uplink carrier on which the DCI format can be scheduled.

[0510] (Appendix 32) 2. The method of claim 1, comprising: The plurality of uplink carriers are each for a different cell, or at least two of the plurality of uplink carriers are for a different cell.

[0511] (Appendix 33) 1. A method for receiving a CSI report, comprising: A network device transmits a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering an aperiodic CSI report; and The network device receiving a CSI report.

[0512] (Appendix 34) 34. The method of claim 33, The DCI format schedules a PUSCH on one cell and / or uplink carrier, and the network device receives the CSI report on the one cell and / or uplink carrier.

[0513] (Appendix 35) 35. The method according to claim 33 or 34, When the DCI format requests or triggers aperiodic CSI reporting, the DCI format schedules a PUSCH on only one cell and / or uplink carrier.

[0514] (Appendix 36) 35. The method of claim 34, The DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the network device receives the CSI report on the cell and / or uplink carrier indicated by the field.

[0515] (Appendix 37) 35. The method of claim 34, The network device receives the CSI report on a cell and / or uplink carrier for receiving the CSI report by default or configured by signaling.

[0516] (Appendix 38) 38. The method of claim 37, 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.

[0517] (Appendix 39) 38. The method of claim 37, The DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores the field.

[0518] (Appendix 40) 2. The method of claim 1, comprising: The DCI format includes a field for requesting or triggering a CSI report, and the field for requesting or triggering a CSI report is located before a field for indicating a cell and / or an uplink carrier.

[0519] (Appendix 41) 41. The method of claim 37 or 40, The DCI format does not include a field for indicating a cell and / or an uplink carrier when requesting or triggering aperiodic CSI reporting.

[0520] (Appendix 42) 37-41. The method according to any one of claims 37-41, comprising: The default cell for receiving a CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0521] (Appendix 43) 34. The method of claim 33, 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.

[0522] (Appendix 44) 34. The method of claim 33, 34 or 43, The DCI format includes a field for requesting or triggering a CSI report, and the value of the field corresponds to a CSI aperiodic trigger state.

[0523] (Appendix 45) 45. The method of claim 44, The length of the field is set by a higher layer parameter, and the higher layer parameter is either dedicated to the DCI format or common (shared) to the DCI format and other DCI formats.

[0524] (Appendix 46) 45. The method of claim 44, The length of the field is determined by the terminal device based on the number of trigger conditions in the trigger condition list that is set.

[0525] (Appendix 47) 44. The method of claim 43, The one cell and / or uplink carrier is a default cell and / or uplink carrier for receiving a CSI report or is configured by signaling.

[0526] (Appendix 48) 48. The method of claim 47, The default cell for receiving CSI reports is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain is located; and The cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0527] (Appendix 49) 49. The method according to claim 47 or 48, The default cell for receiving a CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0528] (Appendix 50) 2. The method of claim 1, comprising: The network device receives the CSI report on a default PUSCH.

[0529] (Appendix 51) 51. The method of claim 50, The default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0530] (Appendix 52) 52. The method of claim 50 or 51, The cell where the default PUSCH is located is a Pcell, a PScell, or a PUCCH Scell.

[0531] (Appendix 53) 48. The method of claim 47, The DCI format includes a field for indicating a cell and / or an uplink carrier.

[0532] (Appendix 54) 54. The method of claim 53, The cell and / or uplink carrier for receiving the default or signaled CSI report 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.

[0533] (Appendix 55) 2. The method of claim 1, comprising: The DCI format schedules PUSCH on multiple cells and / or uplink carriers, and the network device receives the CSI report on one or more cells and / or uplink carriers among the multiple cells and / or uplink carriers.

[0534] (Appendix 56) 56. The method of claim 55, The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the multiple cells and / or uplink carriers.

[0535] (Appendix 57) 56. The method of claim 55, The content of the CSI reports on different PUSCHs may be the same or different.

[0536] (Appendix 58) 58. The method of claim 55 or 57, The DCI format includes a field for requesting or triggering one CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are respectively used to carry different CSI reports corresponding to trigger states associated with the field, and / or different PUSCHs are respectively used to carry different parts of the CSI report.

[0537] (Appendix 59) 58. The method of claim 56 or 57, The DCI format includes fields for requesting or triggering multiple CSI reports, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different CSI report request or trigger fields, respectively.

[0538] (Appendix 60) 59. The method of any one of claims 33 to 59, comprising: The CRC of the DCI format is scrambled by the C-RNTI or by the MCS-C-RNTI.

[0539] (Appendix 61) 61. The method of any one of claims 33 to 60, comprising: The network device transmits configuration information for configuring the terminal device to monitor the DCI format in a search space dedicated to the UE.

[0540] (Appendix 62) 62. The method of any one of claims 33 to 61, comprising: The network device transmits configuration information for configuring whether the DCI format supports triggering of a CSI report or whether the DCI format is for triggering a CSI report.

[0541] (Appendix 63) 63. The method of any one of claims 33 to 62, comprising: The network device transmits configuration information for configuring a cell and / or an uplink carrier on which the DCI format can be scheduled.

[0542] (Appendix 64) 2. The method of claim 1, comprising: The plurality of uplink carriers are each for a different cell, or at least two of the plurality of uplink carriers are for a different cell.

[0543] (Appendix 1') 1. A semi-persistent CSI reporting method, comprising: The terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and The terminal device transmitting a CSI report.

[0544] (Appendix 2') 10. The method of claim 1 , further comprising: The DCI format schedules a PUSCH on one cell and / or uplink carrier, and the terminal device transmits the CSI report on the one cell and / or uplink carrier.

[0545] (Appendix 3') The method according to claim 1' or 2', When the DCI format triggers or activates semi-persistent CSI reporting, the DCI format schedules a PUSCH on only one cell and / or uplink carrier.

[0546] (Appendix 4') 2'. The method according to claim 2', The DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the terminal device transmits the CSI report on the cell and / or uplink carrier indicated by the field.

[0547] (Appendix 5') 2'. The method according to claim 2', The terminal device transmits the CSI report on a cell and / or uplink carrier for transmitting the CSI report by default or configured by signaling.

[0548] (Appendix 6') The method according to claim 5', 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.

[0549] (Appendix 7') The method according to Appendix 5', The DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores the field.

[0550] (Appendix 8') 10. The method of claim 1 , further comprising: The DCI format includes a field for requesting or triggering a CSI report, and the field for requesting or triggering a CSI report is located before a field for indicating a cell and / or an uplink carrier.

[0551] (Appendix 9') The method according to appendix 5' or 8', 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.

[0552] (Appendix 10') 10. The method of any one of appendices 5'-8', comprising: The cell for transmitting the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0553] (Appendix 11') 10. The method of claim 1 , further comprising: The DCI format schedules a PUSCH on one or more cells and / or uplink carriers, and the terminal device transmits the CSI report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

[0554] (Appendix 12') 11. The method according to claim 1', 2' or 11', The DCI format includes a field for requesting or triggering a CSI report, and the value of the field corresponds to a CSI trigger state.

[0555] (Appendix 13') 12'. The method of claim 12', The length of the field is set by a higher layer parameter, and the higher layer parameter is either dedicated to the DCI format or common (shared) to the DCI format and other DCI formats.

[0556] (Appendix 14') 12'. The method of claim 12', The length of the field is determined by the terminal device based on the number of trigger conditions in the trigger condition list that is set.

[0557] (Appendix 15') 11'. The method of claim 11', The one cell and / or uplink carrier is a default cell and / or uplink carrier for transmitting a CSI report configured by signaling.

[0558] (Appendix 16') 15'. The method of claim 15', The cell for transmission of the default CSI report is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located; and The cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0559] (Appendix 17') The method according to claim 15' or 16', The cell for transmitting the default CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0560] (Appendix 18') 10. The method of claim 1 , further comprising: The terminal device transmits the CSI report on a default PUSCH.

[0561] (Appendix 19') 18'. The method of claim 18', The default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0562] (Appendix 20') The method according to claim 18' or 19', The cell where the default PUSCH is located is a Pcell, a PScell, or a PUCCH Scell.

[0563] (Appendix 21') 15'. The method of claim 15', The DCI format includes a field for indicating a cell and / or an uplink carrier.

[0564] (Appendix 22') 21'. The method of claim 21', The cell and / or uplink carrier for transmitting the default or signaled CSI report 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.

[0565] (Appendix 23') 10. The method of claim 1 , further comprising: The DCI format schedules PUSCH on multiple cells and / or uplink carriers, and the terminal device transmits the CSI report on one or more cells and / or uplink carriers among the multiple cells and / or uplink carriers.

[0566] (Appendix 24') 23'. The method of claim 23', The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the multiple cells and / or uplink carriers.

[0567] (Appendix 25') 23'. The method of claim 23', The content of the CSI reports on different PUSCHs may be the same or different.

[0568] (Appendix 26') 23' or 25', comprising: The DCI format includes one field for triggering or activating a CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are respectively used to carry different CSI reports corresponding to trigger states associated with the field, and / or different PUSCHs are respectively used to carry different parts of the CSI report.

[0569] (Appendix 27') The method according to claim 23' or 25', The DCI format includes fields for triggering or activating multiple CSI reports, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different CSI report request or trigger fields, respectively.

[0570] (Appendix 28') 10. The method of any one of appendices 1′-27′, comprising: The CRC of the DCI format is scrambled by the SP-CSI-RNTI.

[0571] (Appendix 29') 28. The method of any one of claims 1' to 28', comprising: The terminal device validates the validity of the DCI format for semi-persistent CSI activation.

[0572] (Appendix 30’) The method described in Appendix 29’, where the terminal device validates the validity based on a field for indicating a cell and / or an uplink carrier, and / or a field for indicating a HARQ process ID, and / or a field for indicating an RV, in the DCI format.

[0573] (Appendix 31’) The method described in Appendix 30’, where the DCI format includes a plurality of fields for indicating a HARQ process ID, and the terminal device validates the validity based on some or all of the fields for indicating a HARQ process ID in the DCI format.

[0574] (Appendix 32’) The method described in Appendix 30’ or 31’, where the DCI format includes a plurality of fields for indicating an RV, and the terminal device validates the validity based on some or all of the fields for indicating an RV in the DCI format.

[0575] (Appendix 33’) The method described in any one of Appendices 30’ - 32’, where the DCI format includes one or more fields for indicating a cell and / or an uplink carrier, and the terminal device validates the validity based on some or all of the fields for indicating a cell and / or an uplink carrier in the DCI format.

[0576] (Appendix 34’) 10. The method of any one of clauses 30'-33', comprising: If the DCI format is invalid, the terminal device ignores or drops the DCI format.

[0577] (Appendix 35') 1. A method for receiving a CSI report, comprising: A network device transmits a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and The network device receiving a CSI report.

[0578] (Appendix 36') 35'. The method of claim 35', The DCI format schedules a PUSCH on one cell and / or uplink carrier, and the network device receives the CSI report on the one cell and / or uplink carrier.

[0579] (Appendix 37') 35' or 36', comprising: When the DCI format triggers or activates semi-persistent CSI reporting, the DCI format schedules a PUSCH on only one cell and / or uplink carrier.

[0580] (Appendix 38') 36'. The method of claim 36', The DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the network device receives the CSI report on the cell and / or uplink carrier indicated by the field.

[0581] (Appendix 39') 36'. The method of claim 36', The network device receives the CSI report on a cell and / or uplink carrier for receiving the CSI report by default or configured by signaling.

[0582] (Appendix 40') 39'. The method of claim 39', 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.

[0583] (Appendix 41') 39'. The method of claim 39', The DCI format includes a field for indicating a cell and / or an uplink carrier, and the terminal device ignores the field.

[0584] (Appendix 42') 35'. The method of claim 35', The DCI format includes a field for requesting or triggering a CSI report, and the field for requesting or triggering a CSI report is located before a field for indicating a cell and / or an uplink carrier.

[0585] (Appendix 43') 39' or 42', comprising: 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.

[0586] (Appendix 44') 10. The method of any one of clauses 39'-42', comprising: The default cell for receiving a CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0587] (Appendix 45') 35'. The method of claim 35', 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.

[0588] (Appendix 46') 35', 36', or 45', comprising: The DCI format includes a field for requesting or triggering a CSI report, and the value of the field corresponds to a CSI trigger state.

[0589] (Appendix 47') 46'. The method of claim 46', The length of the field is set by a higher layer parameter, and the higher layer parameter is either dedicated to the DCI format or common (shared) to the DCI format and other DCI formats.

[0590] (Appendix 48') 46'. The method of claim 46', The length of the field is determined by the terminal device based on the number of trigger conditions in the trigger condition list that is set.

[0591] (Appendix 49') 45'. The method of claim 45', The one cell and / or uplink carrier is a default cell and / or uplink carrier for receiving a CSI report or is configured by signaling.

[0592] (Appendix 50') 49'. The method of claim 49', The default cell for receiving CSI reports is at least one of the following: The cell to be scheduled that has the smallest serving cell indicator number; A cell in which the first PUSCH among scheduled PUSCHs that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located; and The cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the semi-persistent CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0593] (Appendix 51') The method according to claim 49' or 50', The default cell for receiving a CSI report is a Pcell, a PScell, or a PUCCH Scell.

[0594] (Appendix 52') 35'. The method of claim 35', The network device receives the CSI report on a default PUSCH.

[0595] (Appendix 53') 52'. The method of claim 52', The default PUSCH is at least one of the following: PUSCH of the cell with the smallest serving cell indicator number among the scheduled cells; The first PUSCH among the scheduled PUSCHs that satisfies the aperiodic CSI reporting timing requirement in the time domain; and The PUSCH is the PUSCH of the cell with the smallest serving cell indicator number among the cells in which the first PUSCH that satisfies the aperiodic CSI reporting timing requirement in the time domain is located among the scheduled PUSCHs.

[0596] (Appendix 54') 52' or 53', comprising: The cell where the default PUSCH is located is a Pcell, a PScell, or a PUCCH Scell.

[0597] (Appendix 55') 49'. The method of claim 49', The DCI format includes a field for indicating a cell and / or an uplink carrier.

[0598] (Appendix 56') 55'. The method of claim 55', The cell and / or uplink carrier for receiving the default or signaled CSI report 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.

[0599] (Appendix 57') 35'. The method of claim 35', The DCI format schedules PUSCH on multiple cells and / or uplink carriers, and the network device receives the CSI report on one or more cells and / or uplink carriers among the multiple cells and / or uplink carriers.

[0600] (Appendix 58') 57'. The method of claim 57', The DCI format includes a field for indicating a cell and / or an uplink carrier, and the field indicates the multiple cells and / or uplink carriers.

[0601] (Appendix 59') 57'. The method of claim 57', The content of the CSI reports on different PUSCHs may be the same or different.

[0602] (Appendix 60') 57' or 59', comprising: The DCI format includes one field for triggering or activating a CSI report, and the CSI report on different PUSCHs is the same, and / or different PUSCHs are respectively used to carry different CSI reports corresponding to trigger states associated with the field, and / or different PUSCHs are respectively used to carry different parts of the CSI report.

[0603] (Appendix 61') 57' or 59', comprising: The DCI format includes fields for triggering or activating multiple CSI reports, and different PUSCHs are used to carry CSI reports corresponding to trigger states associated with different CSI report request or trigger fields, respectively.

[0604] (Appendix 62') 10. The method of any one of clauses 35'-61', comprising: The CRC of the DCI format is scrambled by the SP-CSI-RNTI.

[0605] (Appendix 1'') 1. A method for releasing or deactivating semi-persistent CSI reports, comprising: The terminal device receives a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format releasing or deactivating semi-persistent CSI reporting; and The method includes the terminal device deactivating semi-persistent CSI reporting.

[0606] (Appendix 2'') 12. The method of claim 1 , The DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicates one 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 dedicated value, and the dedicated value does not correspond to any cell and / or uplink carrier.

[0607] (Appendix 3'') The method according to Appendix 1'' or 2'', The terminal device validates the validity of the DCI forma for the semi-persistent CSI release / deactivation.

[0608] (Appendix 4'') The method according to Appendix 3'', The terminal device validates the validity based on a field for indicating a cell and / or an uplink carrier and / or a field for indicating a HARQ process ID and / or a field for indicating an RV and / or a plurality of fields for indicating an MCS and / or a plurality of fields for indicating frequency domain resource (RB) allocation in the DCI format.

[0609] (Appendix 5'') The method according to Appendix 4'', The DCI format includes a plurality of fields for indicating a HARQ process ID, and the terminal device validates the validity based on some or all of the fields for indicating a HARQ process ID in the DCI format.

[0610] (Appendix 6'') The method according to Appendix 4'' or 5'', The DCI format includes multiple fields for indicating RV, and the terminal device determines / validates the validity based on some or all of the fields for indicating RV in the DCI format.

[0611] (Appendix 7'') 1. The method according to any one of claims 4″-6″, comprising: 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 indicating a cell and / or an uplink carrier in the DCI format.

[0612] (Appendix 8'') 1. The method according to any one of claims 4″-7″, comprising: 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 for indicating MCS in the DCI format.

[0613] (Appendix 9'') 1. The method of any one of claims 4″-8″, comprising: The DCI format includes a plurality of fields for indicating frequency domain resource (RB) allocation, and the terminal device determines / validates the validity based on some or all of the fields for indicating frequency domain resource (RB) allocation in the DCI format.

[0614] (Appendix 10'') 10. The method of any one of claims 4″-9″, comprising: If the DCI format is invalid, the terminal device ignores or drops the DCI format.

[0615] (Appendix 11’’) A method for releasing or deactivating semi-persistent CSI reports, wherein a network device transmits DCI format for scheduling PUSCH on one or more cells and / or uplink carriers, and the DCI format includes releasing or deactivating semi-persistent CSI reports.

[0616] (Appendix 12’’) The method according to Appendix 11’’, where the DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicates one 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 has a dedicated value that does not correspond to any cell and / or uplink carrier.

[0617] (Appendix 1a) A terminal device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to execute the computer program to implement the method according to any one of Appendices 1 to 32, 1' to 34', and 1'' to 10''.

[0618] (Appendix 2a) A network device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to execute the computer program to implement the method according to any one of Appendices 33 to 64, 35' to 62', and 11'' to 12''.

[0619] (Appendix 3a) A communication system, including a network device and a terminal device, The network device includes: Transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic CSI reporting; and configured to receive a CSI report; The terminal device is receiving the DCI format; and configured to transmit the CSI report.

[0620] (Appendix 4a) 1. A communication system comprising: Including network equipment and terminal equipment, The network device includes: Transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent CSI reporting; and configured to receive a CSI report; The terminal device is receiving the DCI format; and configured to transmit the CSI report.

[0621] (Appendix 5a) 1. A communication system comprising: Including network equipment and terminal equipment, The network device includes: transmitting a DCI format for scheduling a PUSCH on one or more cells and / or uplink carriers, the DCI format being configured to release or deactivate semi-persistent CSI reporting; The terminal device is receiving the DCI format; and configured to deactivate semi-persistent CSI reporting.

Claims

1. 1. An apparatus for reporting aperiodic channel state information, comprising: A receiving unit for receiving a DCI format for scheduling a physical uplink shared channel on one or more cells and / or uplink carriers, the DCI format requesting or triggering aperiodic channel state information reporting; and An apparatus including a transmitting unit for transmitting a channel state information report.

2. 10. The apparatus of claim 1, The DCI format schedules a physical uplink shared channel on one cell and / or uplink carrier, and the transmitting unit transmits the channel state information report on the one cell and / or uplink carrier.

3. 3. The device according to claim 1 or 2, 10. The apparatus, wherein, when the DCI format requests or triggers aperiodic channel state information reporting, the DCI format schedules a physical uplink shared channel on only one cell and / or uplink carrier.

4. 3. The apparatus of claim 2, The DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the transmitting unit transmits the channel state information report on the cell and / or uplink carrier indicated by the field.

5. 3. The apparatus of claim 2, The transmitting unit transmits the channel state information report on a cell and / or an uplink carrier for transmitting the channel state information report, the cell and / or an uplink carrier being configured by default or by signaling.

6. 6. The apparatus of claim 5, The apparatus, wherein the default cell for transmitting a channel state information report is a Pcell, a PScell, or a PUCCH Scell.

7. 10. The apparatus of claim 1, the DCI format schedules a physical uplink shared channel on one or more cells and / or uplink carriers, and the transmitting unit transmits the channel state information report on one cell and / or uplink carrier among the one or more cells and / or uplink carriers.

8. 8. The apparatus of claim 7, The apparatus, wherein the one cell and / or uplink carrier is a default or signaling-configured cell and / or uplink carrier for transmitting a channel state information report.

9. 9. The apparatus of claim 8, The default cell for transmitting channel state information reports is at least one of the following: The cell with the smallest serving cell indicator number among the cells to be scheduled; a cell in which a first physical uplink shared channel that satisfies a timing requirement for aperiodic channel state information reporting in the time domain is located among the scheduled physical uplink shared channels; and The device is a cell having the smallest serving cell indicator number among cells in which a first physical uplink shared channel that satisfies a non-periodic channel state information reporting timing requirement in the time domain is located among scheduled physical uplink shared channels.

10. 9. The apparatus of claim 8, The apparatus, wherein the default cell for transmitting a channel state information report is a Pcell, a PScell, or a PUCCH Scell.

11. 10. The apparatus of claim 1, the DCI format schedules a physical uplink shared channel on multiple cells and / or uplink carriers, and the transmitting unit transmits the channel state information report on one or more cells and / or uplink carriers among the multiple cells and / or uplink carriers.

12. 1. An apparatus for reporting semi-persistent channel state information, comprising: a receiving unit for receiving a DCI format for scheduling a physical uplink shared channel on one or more cells and / or uplink carriers, the DCI format triggering or activating semi-persistent channel state information reporting; An apparatus including a transmitting unit for transmitting a channel state information report.

13. 13. The apparatus of claim 12, The DCI format schedules a physical uplink shared channel on one cell and / or uplink carrier, and the transmitting unit transmits the channel state information report on the one cell and / or uplink carrier.

14. 13. The apparatus of claim 12, 10. The apparatus, wherein the DCI format schedules a physical uplink shared channel on only one cell and / or uplink carrier when the DCI format triggers or activates semi-persistent channel state information reporting.

15. 14. The apparatus of claim 13, The DCI format includes a field for indicating a cell and / or an uplink carrier, the field indicating one cell and / or uplink carrier, and the transmitting unit transmits the channel state information report on the cell and / or uplink carrier indicated by the field.

16. 14. The apparatus of claim 13, The transmitting unit transmits the channel state information report on a cell and / or an uplink carrier for transmitting the channel state information report by default or configured by signaling.

17. 13. The apparatus of claim 12, The cyclic redundancy check of the DCI format is scrambled by the SP-CSI-RNTI.

18. 13. The apparatus of claim 12, further comprising: An apparatus comprising: a determining / confirming unit for determining / confirming the validity of the DCI format for semi-persistent channel state information activation.

19. 19. The apparatus of claim 18, The determination / confirmation unit determines / confirms the validity based on 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. 20. The apparatus of claim 19, The DCI format includes multiple fields for indicating redundancy versions, and the determination / confirmation unit determines / confirms the validity based on some or all of the fields for indicating redundancy versions in the DCI format.

Images