Channel state information reporting method and apparatus, and channel state information configuration method and apparatus

Abstract

A channel state information (CSI) reporting method and apparatus, and a CSI configuration method and apparatus. The channel state information reporting method comprises: a terminal device receives first configuration information; and the terminal device sends a report on the basis of the first configuration information, the first configuration information comprising at least one of the following configuration information: an event-triggered CSI resource configuration, an event-triggered CSI report configuration, an event-triggered LTM CSI resource configuration, and an event trigger LTM CSI report configuration, and the number (ID) of the event-triggered CSI report configuration being determined on the basis of at least one of the following modes: the event-triggered CSI report configuration and a CSI report configuration are numbered independently; the event-triggered CSI report configuration and the CSI report configuration are numbered uniformly; the event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently; the event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered uniformly; the event-triggered CSI report configuration and an LTM CSI report configuration are numbered independently.

Description

Channel state information reporting method, configuration method and device Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] 5G NR supports Channel State Information (CSI) reporting. For example, a CSI report may include at least one of a CSI-RS Resource Indicator (CRI), an SSB Resource Indicator (SSBRI), L1-RSRP, and L1-SINR, that is, a beam-related report. The terminal device sends a beam report to the network device, and the network device can perform beam management based on it, for example, indicating a better beam for the terminal device. When the terminal device sends the CSI report is determined by the network device. The network device can configure periodic CSI reporting so that the terminal device sends CSI reports periodically; the network device can configure semi-persistent CSI reporting. After the semi-persistent CSI reporting is activated by the network device, the terminal device sends the CSI report periodically; the network device can configure aperiodic CSI reporting. After the aperiodic CSI reporting is triggered by the network device, the terminal device sends a CSI report once. The CSI report includes measurement results for the serving cell. Rel-17 adds support for ICBM (Inter Cell Beam Management). In ICBM, the CSI report can include measurement results for non-serving cells, so that the network equipment can instruct the terminal device to use the beam of the non-serving cell, but the terminal device does not switch to the non-serving cell.

[0003] Rel-18 adds support for LTM CSI reports. Rel-18 supports LTM (L1 / L2 Triggered Mobility). In LTM, terminal devices can send LTM CSI reports. Rel-18's LTM CSI reports include SSBRI and L1-RSRP. Unlike the traditional CSI reports mentioned above, LTM CSI reports include measurement results for candidate cells. The network equipment can determine the beam to be used in the candidate cell for the terminal device based on this, and indicate the beam to the terminal device before switching to the candidate cell, so that the terminal device can quickly apply the appropriate beam for data transmission after switching. In other words, in LTM, the terminal device switches to the candidate cell and uses the beam of the candidate cell after switching. Similarly, the terminal device can send LTM CSI reports in a periodic, semi-continuous, or non-periodic manner.

[0004] It should be noted that the above introduction to the technical background is merely for convenience, to provide a clear and complete description of the technical solutions of this application and to facilitate understanding by those skilled in the art. It should not be assumed that the above technical solutions are well known to those skilled in the art simply because they are described in the background technology section of this application.

[0005] Summary of the Invention

[0006] In the upcoming Rel-19, further enhancements to CSI reporting and LTM CSI reporting will be introduced, namely, support for event-triggered CSI reporting and event-triggered LTM CSI reporting. Event-triggered CSI reporting and event-triggered LTM CSI reporting correspond to traditional CSI reporting and LTM CSI reporting, respectively. Unlike the traditional reporting mentioned above, for event-triggered reporting, when the terminal device sends the report is determined by the terminal device, that is, through event triggering. In other words, the terminal device only sends the report when necessary, so that the report can be sent more promptly. In addition, since unnecessary reports are avoided, the reporting overhead can also be reduced. How to support event-triggered CSI reporting and event-triggered LTM CSI reporting is a problem that needs to be solved. At present, 3GPP has just approved the establishment of Rel-19 and has not yet started to discuss the relevant technical details of event-triggered CSI reporting and event-triggered LTM CSI reporting.

[0007] The inventors discovered that to support event-triggered reporting, terminal devices need to be configured with event-triggered reporting configuration and event-triggered resources. Currently, there are challenges in configuring event-triggered reporting and event-triggered resources, including the relationship between event-triggered reporting configuration and traditional reporting configuration, and between event-triggered resource configuration and traditional resource configuration.

[0008] In order to solve one or more of the above problems, embodiments of the present application provide a channel state information reporting method, configuration method, and apparatus.

[0009] According to a first aspect of an embodiment of the present application, a channel state information (CSI) reporting device is provided, the device being configured in a terminal device, the device comprising:

[0010] A first receiving unit, configured to receive first configuration information; and

[0011] a first sending unit configured to send a report according to the first configuration information;

[0012] The first configuration information includes at least one of the following configuration information:

[0013] Event triggers CSI resource configuration;

[0014] Event-triggered CSI reporting configuration;

[0015] Event triggers LTM CSI resource configuration;

[0016] Event-triggered LTM CSI report configuration,

[0017] The ID of the event-triggered CSI report configuration is determined according to at least one of the following methods:

[0018] The event triggering CSI report configuration is numbered independently from the CSI report configuration;

[0019] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly;

[0020] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently;

[0021] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered uniformly;

[0022] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0023] According to a second aspect of an embodiment of the present application, a configuration apparatus is provided, the apparatus being arranged in a network device, the apparatus comprising:

[0024] A second sending unit, configured to send first configuration information to a terminal device; and

[0025] a second receiving unit configured to receive a report sent according to the first configuration information from the terminal device;

[0026] The first configuration information includes at least one of the following configuration information:

[0027] Event triggers CSI resource configuration;

[0028] Event-triggered CSI reporting configuration;

[0029] Event triggers LTM CSI resource configuration;

[0030] Event-triggered LTM CSI report configuration,

[0031] The ID of the event-triggered CSI report configuration is determined according to at least one of the following methods:

[0032] The event triggering CSI report configuration is numbered independently from the CSI report configuration;

[0033] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly;

[0034] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently;

[0035] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered uniformly;

[0036] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0037] According to the third aspect of the embodiment of the present application, a communication system is provided, which includes a terminal device and / or a network device, the terminal device includes the apparatus according to the first aspect of the embodiment of the present application, and the network device includes the apparatus according to the second aspect of the embodiment of the present application.

[0038] According to a fourth aspect of an embodiment of the present application, a channel state information (CSI) reporting method is provided, the method comprising:

[0039] The terminal device receives the first configuration information; and

[0040] The terminal device sends a report according to the first configuration information,

[0041] The first configuration information includes at least one of the following configuration information:

[0042] Event triggers CSI resource configuration;

[0043] Event-triggered CSI reporting configuration;

[0044] Event triggers LTM CSI resource configuration;

[0045] Event-triggered LTM CSI report configuration,

[0046] The ID of the event-triggered CSI report configuration is determined according to at least one of the following methods:

[0047] The event triggering CSI report configuration is numbered independently from the CSI report configuration;

[0048] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly;

[0049] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently;

[0050] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered uniformly;

[0051] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0052] According to a fifth aspect of an embodiment of the present application, a configuration method is provided, the method comprising:

[0053] The network device sends first configuration information to the terminal device; and

[0054] The network device receives a report sent according to the first configuration information from the terminal device,

[0055] The first configuration information includes at least one of the following configuration information:

[0056] Event triggers CSI resource configuration;

[0057] Event-triggered CSI reporting configuration;

[0058] Event triggers LTM CSI resource configuration;

[0059] Event-triggered LTM CSI report configuration,

[0060] The ID of the event-triggered CSI report configuration is determined according to at least one of the following methods:

[0061] The event triggering CSI report configuration is numbered independently from the CSI report configuration;

[0062] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly;

[0063] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently;

[0064] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered uniformly;

[0065] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0066] According to the sixth aspect of the embodiment of the present application, a computer-readable program is provided, wherein when the program is executed in a channel state information reporting device or a terminal device, the program enables the channel state information reporting device or the terminal device to execute the channel state information reporting method described in the fourth aspect of the embodiment of the present application.

[0067] According to the seventh aspect of the embodiment of the present application, a computer-readable program is provided, wherein when the program is executed in a channel state information reporting device or a network device, the program enables the configuration device or the network device to execute the configuration method described in the fifth aspect of the embodiment of the present application.

[0068] According to the eighth aspect of the embodiments of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables a channel state information reporting device or a terminal device to execute the channel state information reporting method described in the fourth aspect of the embodiments of the present application.

[0069] According to the ninth aspect of the embodiment of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables a configuration device or a network device to execute the configuration method described in the fifth aspect of the embodiment of the present application.

[0070] One of the benefits of the embodiments of the present application is that a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

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

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

[0073] It should be emphasized that the terms “include / comprising / having” when used herein refer to the presence of features, integers, steps or components, but do not preclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0075] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

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

[0077] FIG2 is a schematic diagram of a channel state information reporting method according to an embodiment of the present application;

[0078] FIG3 is a schematic diagram of a first implementation of report configuration and resource configuration according to an embodiment of the present application;

[0079] FIG4 is a schematic diagram of a second implementation of report configuration and resource configuration according to an embodiment of the present application;

[0080] FIG5 is a schematic diagram of a third implementation of report configuration and resource configuration according to an embodiment of the present application;

[0081] FIG6 is a schematic diagram of a fourth implementation of report configuration and resource configuration according to an embodiment of the present application;

[0082] FIG7 is a schematic diagram of a fifth implementation of report configuration and resource configuration according to an embodiment of the present application;

[0083] FIG8 is a schematic diagram of a sixth implementation of report configuration and resource configuration according to an embodiment of the present application;

[0084] FIG9 is a schematic diagram of a seventh implementation of report configuration and resource configuration according to an embodiment of the present application;

[0085] FIG10 is a schematic diagram of an eighth implementation of report configuration and resource configuration according to an embodiment of the present application;

[0086] FIG11 is a schematic diagram of a ninth implementation of report configuration and resource configuration according to an embodiment of the present application;

[0087] FIG12 is a schematic diagram of a tenth implementation of report configuration and resource configuration according to an embodiment of the present application;

[0088] FIG13 is a schematic diagram of a configuration method according to an embodiment of the present application;

[0089] FIG14 is an interaction diagram of a channel state information reporting method according to an embodiment of the present application;

[0090] FIG15 is a schematic diagram of a channel state information reporting device according to an embodiment of the present application;

[0091] FIG16 is a schematic diagram of a configuration device according to an embodiment of the present application;

[0092] 17 is a schematic block diagram of a system structure of a terminal device according to an embodiment of the present invention;

[0093] FIG18 is a schematic block diagram of the system structure of the network device according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

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

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

[0100] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs). They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may encompass some or all of their functions. Each base station can provide communication coverage for a specific geographic area. For example, a 5G gNB may include a gNB CU and one or more gNB DUs, where a CU / DU is a logical node within the gNB that also performs some of the gNB's functions. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used. A gNB-DU supports one or more cells, and a cell is supported by only one gNB-DU.

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

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

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

[0104] In the embodiments of the present application, "when...", "under the circumstances of...", "for the circumstances of..." and "if..." all mean based on one or certain conditions or states, etc. In addition, these expressions can be replaced with each other.

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

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

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

[0108] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, an MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0109] The following describes various implementations of the present application in conjunction with the accompanying drawings. These implementations are merely illustrative and are not intended to limit the present application.

[0110] Embodiments of the first aspect

[0111] An embodiment of the present application provides a channel state information reporting method, which is applied to a terminal device, such as the terminal device 102 in Figure 1.

[0112] In the embodiment of the present application, the reports used to report CSI may include different types of reports, which may be collectively referred to as reports. For example, the reports include at least one of: CSI reports, LTM CSI reports, event-triggered CSI reports, and event-triggered LTM CSI reports.

[0113] Similarly, different types of report configurations may be collectively referred to as report configurations, different types of resource configurations may be collectively referred to as resource configurations, and different types of resources may be collectively referred to as resources.

[0114] For example, the reporting configuration includes at least one of a CSI reporting configuration, an LTM CSI reporting configuration, an event-triggered CSI reporting configuration, and an event-triggered LTM CSI reporting configuration.

[0115] For example, the resource configuration includes at least one of CSI resource configuration, LTM CSI resource configuration, event-triggered CSI resource configuration, and event-triggered LTM CSI resource configuration.

[0116] For example, the resource includes at least one of a CSI resource, an LTM CSI resource, an event-triggered CSI resource, and an event-triggered LTM CSI resource.

[0117] In the embodiment of the present application, "event-triggered report" is also referred to as "event-triggered report".

[0118] In the embodiment of the present application, “event triggered” may be replaced by “UE initiated” or “event driven”.

[0119] In an embodiment of the present application, the terminal device sends a report according to a report configuration, the report configuration is associated with a resource configuration, the terminal device measures the resource according to the resource configuration, and includes the measurement result of the resource in the sent report.

[0120] FIG2 is a schematic diagram of a channel state information reporting method according to an embodiment of the present application. As shown in FIG2 , the method includes:

[0121] 201: The terminal device receives first configuration information; and

[0122] 202: The terminal device sends a report according to the first configuration information.

[0123] In some embodiments, the first configuration information is configuration information about CSI reporting.

[0124] In some embodiments, the first configuration information includes at least one of the following configuration information:

[0125] Event triggers CSI resource configuration;

[0126] Event-triggered CSI reporting configuration;

[0127] Event triggers LTM CSI resource configuration;

[0128] Event-triggered LTM CSI reporting configuration.

[0129] That is, the first configuration information includes event-triggered report configuration and / or resource configuration.

[0130] In some embodiments, the first configuration information further includes at least one of the following configuration information:

[0131] CSI resource allocation;

[0132] CSI report configuration;

[0133] LTM CSI resource configuration;

[0134] LTM CSI reporting configuration.

[0135] That is, the first configuration information may also include traditional report configuration and / or resource configuration.

[0136] In an embodiment of the present application, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or can be configured separately from a set of traditional reporting configurations. For example, whether the event-triggered reporting configurations are configured as a subset of the traditional reporting configurations or as separate configurations can be distinguished by whether the event-triggered reporting configurations and the traditional reporting configurations are numbered uniformly or numbered independently.

[0137] In some embodiments, the ID of the report configuration is also called the identification of the report configuration.

[0138] In some embodiments, the ID of the event-triggered CSI reporting configuration is determined according to at least one of the following methods:

[0139] This event triggers the CSI report configuration and the CSI report configuration is numbered independently;

[0140] The event triggers the CSI report configuration and the CSI report configuration has the same number;

[0141] The CSI report configuration triggered by this event and the LTM CSI report configuration triggered by this event are numbered independently;

[0142] The CSI report configuration triggered by this event is numbered the same as the LTM CSI report configuration triggered by this event.

[0143] The CSI report configuration triggered by this event is numbered independently from the LTM CSI report configuration.

[0144] In some embodiments, the ID of the event-triggered LTM CSI reporting configuration is determined according to at least one of the following methods:

[0145] The event triggering the LTM CSI report configuration is numbered independently from the LTM CSI report configuration;

[0146] The event triggering LTM CSI report configuration has the same number as the LTM CSI report configuration;

[0147] The LTM CSI report configuration triggered by this event is numbered independently from the CSI report configuration triggered by this event;

[0148] The LTM CSI report configuration triggered by this event is numbered the same as the CSI report configuration triggered by this event;

[0149] The event triggering the LTM CSI report configuration is numbered independently from the CSI report configuration.

[0150] In an embodiment of the present application, a set of event-triggered resource configurations can be configured as a subset of a set of traditional resource configurations, or can be configured separately from a set of traditional resource configurations. For example, whether the event-triggered resource configurations are configured as a subset of the traditional resource configurations or as separate configurations can be distinguished by whether the event-triggered resource configurations and the traditional resource configurations are numbered uniformly or numbered independently.

[0151] In some embodiments, the ID of a resource configuration is also called an identifier of the resource configuration.

[0152] In some embodiments, the number of the event-triggered CSI resource configuration is determined according to at least one of the following methods:

[0153] The event triggering the CSI resource configuration is numbered independently of the CSI resource configuration;

[0154] The event triggering the CSI resource configuration has the same number as the CSI resource configuration;

[0155] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event are numbered independently;

[0156] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event have the same number;

[0157] The event triggering CSI resource configuration is numbered independently from the LTM CSI resource configuration.

[0158] In some embodiments, the number of the event-triggered LTM CSI resource configuration is determined according to at least one of the following methods:

[0159] The event triggering the LTM CSI resource configuration is numbered independently from the LTM CSI resource configuration;

[0160] The event triggering the LTM CSI resource configuration has the same number as the LTM CSI resource configuration;

[0161] The LTM CSI resource configuration triggered by this event is numbered independently from the CSI resource configuration triggered by this event;

[0162] The LTM CSI resource configuration triggered by this event is numbered the same as the CSI resource configuration triggered by this event;

[0163] The event triggering the LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0164] In addition, it should be noted that the numbering determination method (numbering rule) of the event-triggered report configuration and / or event-triggered resource configuration does not depend on whether the first configuration information contains the traditional report configuration and / or resource configuration, that is, the numbering determination method of the event-triggered report configuration and / or event-triggered resource configuration does not depend on the actual configuration of the terminal device. For example, the RRC IE itself complies with the above-mentioned numbering determination method.

[0165] The numbering rules for event-triggered report configuration and / or event-triggered resource configuration are described in detail below through some examples. However, these examples do not limit the present application.

[0166] FIG3 is a schematic diagram of a first implementation of report configuration and resource configuration according to an embodiment of the present application.

[0167] For example, as shown in FIG3 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0168] The event-triggered CSI report configuration and the CSI report configuration are numbered independently.

[0169] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently.

[0170] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0171] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently.

[0172] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0173] Event trigger CSI resource configuration and CSI resource configuration are numbered independently.

[0174] Event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are numbered independently.

[0175] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0176] Event trigger LTM CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0177] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0178] For example, as shown in FIG3 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0179] S0 CSI resource configurations (IDs from 0 to S0-1),

[0180] R0 CSI report configurations (IDs from 0 to R0-1),

[0181] S1 LTM CSI resource configuration (ID from 0 to S1-1),

[0182] R1 LTM CSI report configuration (ID from 0 to R1-1),

[0183] S2 events trigger CSI resource configuration (ID from 0 to S2-1),

[0184] R2 events trigger CSI report configuration (ID from 0 to R2-1),

[0185] S3 events trigger LTM CSI resource configuration (ID from 0 to S3-1),

[0186] R3 events trigger LTM CSI reporting configuration (IDs from 0 to R3-1).

[0187] In this embodiment, different types of report configurations and resource configurations are configured independently, which can provide maximum configuration flexibility.

[0188] FIG4 is a schematic diagram of a second implementation of report configuration and resource configuration according to an embodiment of the present application.

[0189] For example, as shown in FIG4 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0190] The event-triggered CSI report configuration and the CSI report configuration are numbered independently.

[0191] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently.

[0192] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0193] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently.

[0194] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0195] The event triggering CSI resource configuration and the CSI resource configuration are numbered uniformly.

[0196] Event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are numbered independently.

[0197] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0198] The event triggering LTM CSI resource configuration is numbered with the LTM CSI resource configuration.

[0199] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0200] As shown in FIG4 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0201] S0 resource configurations including CSI resource configurations and / or event-triggered CSI resource configurations,

[0202] R0 CSI reporting configuration,

[0203] S1 resource configurations including LTM CSI resource configurations and / or event-triggered LTM CSI resource configurations,

[0204] R1 LTM CSI reporting configuration,

[0205] R2 events trigger CSI report configuration,

[0206] R3 events trigger LTM CSI reporting configuration.

[0207] In this implementation, by unifying the numbering of event-triggered resource configurations and traditional resource configurations, the maximum number of existing resource configurations can be maintained. In other words, some resource configurations originally reserved for traditional resources are now used as event-triggered resources, thereby reducing device implementation complexity. In other words, a set of event-triggered resource configurations can be configured as a subset of a set of traditional resource configurations.

[0208] FIG5 is a schematic diagram of a third implementation of report configuration and resource configuration according to an embodiment of the present application.

[0209] For example, as shown in FIG5 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0210] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly.

[0211] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently.

[0212] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0213] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered uniformly.

[0214] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0215] The event triggering CSI resource configuration and the CSI resource configuration are numbered uniformly.

[0216] Event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are numbered independently.

[0217] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0218] The event triggering LTM CSI resource configuration is numbered with the LTM CSI resource configuration.

[0219] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0220] For example, as shown in FIG5 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0221] S0 resource configurations including CSI resource configurations and / or event-triggered CSI resource configurations,

[0222] R0 reporting configurations including CSI reporting configurations and / or event-triggered CSI reporting configurations,

[0223] S1 resource configurations including LTM CSI resource configurations and / or event-triggered LTM CSI resource configurations,

[0224] R1 reporting configurations including LTM CSI reporting configurations and / or event-triggered LTM CSI reporting configurations.

[0225] In this embodiment, by unifying the numbering of event-triggered reporting configurations and traditional reporting configurations, the maximum number of existing reporting configurations can be maintained. In other words, some reporting configurations originally reserved for traditional reporting are now used for event-triggered reporting, thereby reducing device implementation complexity. In other words, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations.

[0226] FIG6 is a schematic diagram of a fourth implementation of report configuration and resource configuration according to an embodiment of the present application.

[0227] For example, as shown in FIG6 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0228] The event-triggered CSI report configuration and the CSI report configuration are numbered independently.

[0229] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration have the same number.

[0230] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0231] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently.

[0232] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0233] Event trigger CSI resource configuration and CSI resource configuration are numbered independently.

[0234] Event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are numbered independently.

[0235] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0236] Event trigger LTM CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0237] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0238] For example, as shown in FIG6 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0239] S0 CSI resource configuration,

[0240] R0 CSI reporting configuration,

[0241] S1 LTM CSI resource configuration,

[0242] R1 LTM CSI reporting configuration,

[0243] S2 events trigger CSI resource configuration,

[0244] S3 events trigger LTM CSI resource configuration,

[0245] R2 reporting configurations including event-triggered CSI reporting configurations and / or event-triggered LTM CSI reporting configurations.

[0246] In this implementation, by unifying the numbering of event-triggered CSI report configurations and event-triggered LTM CSI report configurations, the maximum total number of the two can be limited, thereby facilitating reduction of device implementation complexity.

[0247] FIG7 is a schematic diagram of a fifth implementation of report configuration and resource configuration according to an embodiment of the present application.

[0248] For example, as shown in FIG7 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0249] The event-triggered CSI report configuration and the CSI report configuration are numbered independently.

[0250] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration have the same number.

[0251] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0252] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently.

[0253] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0254] Event trigger CSI resource configuration and CSI resource configuration are numbered independently.

[0255] The event-triggered CSI resource configuration and the event-triggered LTM CSI resource configuration have the same number.

[0256] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0257] Event trigger LTM CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0258] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0259] For example, as shown in FIG7 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0260] S0 CSI resource configuration,

[0261] R0 CSI reporting configuration,

[0262] S1 LTM CSI resource configuration,

[0263] R1 LTM CSI reporting configuration,

[0264] S2 resource configurations including event-triggered CSI resource configurations and / or event-triggered LTM CSI resource configurations,

[0265] R2 reporting configurations including event-triggered CSI reporting configurations and / or event-triggered LTM CSI reporting configurations.

[0266] In this implementation, by unifying the numbering of event-triggered CSI resource configurations and event-triggered LTM CSI resource configurations, the maximum total number of the two can be limited, thereby facilitating reduction of device implementation complexity.

[0267] FIG8 is a schematic diagram of a sixth implementation of report configuration and resource configuration according to an embodiment of the present application.

[0268] For example, as shown in FIG8 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0269] The event-triggered CSI report configuration and the CSI report configuration are numbered independently.

[0270] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration have the same number.

[0271] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0272] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently.

[0273] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0274] The event triggering CSI resource configuration and the CSI resource configuration are numbered uniformly.

[0275] Event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are numbered independently.

[0276] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0277] The event triggering LTM CSI resource configuration is numbered with the LTM CSI resource configuration.

[0278] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0279] For example, as shown in FIG8 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0280] S0 resource configurations including CSI resource configurations and / or event-triggered CSI resource configurations,

[0281] S1 resource configurations including LTM CSI resource configurations and / or event-triggered LTM CSI resource configurations,

[0282] R0 CSI reporting configuration,

[0283] R1 LTM CSI reporting configuration,

[0284] R2 reporting configurations including event-triggered CSI reporting configurations and / or event-triggered LTM CSI reporting configurations.

[0285] FIG9 is a schematic diagram of a seventh implementation of report configuration and resource configuration according to an embodiment of the present application.

[0286] For example, as shown in FIG9 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0287] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly.

[0288] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently.

[0289] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0290] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered uniformly.

[0291] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0292] Event trigger CSI resource configuration and CSI resource configuration are numbered independently.

[0293] Event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are numbered independently.

[0294] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0295] Event trigger LTM CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0296] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0297] For example, as shown in FIG9 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0298] S0 CSI resource configuration,

[0299] S1 LTM CSI resource configuration,

[0300] S2 events trigger CSI resource configuration,

[0301] S3 events trigger LTM CSI resource configuration,

[0302] R0 reporting configurations including CSI reporting configurations and / or event-triggered CSI reporting configurations,

[0303] R1 reporting configurations including LTM CSI reporting configurations and / or event-triggered LTM CSI reporting configurations.

[0304] FIG10 is a schematic diagram of an eighth implementation of report configuration and resource configuration according to an embodiment of the present application.

[0305] For example, as shown in FIG10 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0306] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly.

[0307] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently.

[0308] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0309] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered uniformly.

[0310] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0311] Event trigger CSI resource configuration and CSI resource configuration are numbered independently.

[0312] The event-triggered CSI resource configuration and the event-triggered LTM CSI resource configuration have the same number.

[0313] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0314] Event trigger LTM CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0315] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0316] For example, as shown in FIG10 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0317] S0 CSI resource configuration,

[0318] S1 LTM CSI resource configuration,

[0319] S2 resource configurations including event-triggered CSI resource configurations and / or event-triggered LTM CSI resource configurations,

[0320] R0 reporting configurations including CSI reporting configurations and / or event-triggered CSI reporting configurations,

[0321] R1 reporting configurations including LTM CSI reporting configurations and / or event-triggered LTM CSI reporting configurations.

[0322] FIG11 is a schematic diagram of a ninth implementation of report configuration and resource configuration according to an embodiment of the present application.

[0323] For example, as shown in FIG11 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0324] The event-triggered CSI report configuration and the CSI report configuration are numbered independently.

[0325] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently.

[0326] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0327] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently.

[0328] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0329] Event trigger CSI resource configuration and CSI resource configuration are numbered independently.

[0330] The event-triggered CSI resource configuration and the event-triggered LTM CSI resource configuration have the same number.

[0331] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0332] Event trigger LTM CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0333] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0334] For example, as shown in FIG11 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0335] S0 CSI resource configuration,

[0336] S1 LTM CSI resource configuration,

[0337] R0 CSI reporting configuration,

[0338] R1 LTM CSI reporting configuration,

[0339] S2 resource configurations including event-triggered CSI resource configurations and / or event-triggered LTM CSI resource configurations,

[0340] R2 events trigger CSI report configuration,

[0341] R3 events trigger LTM CSI reporting configuration.

[0342] FIG12 is a schematic diagram of a tenth implementation of report configuration and resource configuration according to an embodiment of the present application.

[0343] For example, as shown in FIG12 , the ID of the report configuration and the ID of the resource configuration are determined as follows:

[0344] The event-triggered CSI report configuration and the CSI report configuration are numbered uniformly.

[0345] The event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered independently.

[0346] The event-triggered CSI report configuration and the LTM CSI report configuration are numbered independently.

[0347] The event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently.

[0348] The event-triggered LTM CSI report configuration and CSI report configuration are numbered independently.

[0349] The event triggering CSI resource configuration and the CSI resource configuration are numbered uniformly.

[0350] Event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are numbered independently.

[0351] Event-triggered CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0352] Event trigger LTM CSI resource configuration and LTM CSI resource configuration are numbered independently.

[0353] The event-triggered LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0354] For example, as shown in FIG12 , the terminal device is configured with at least one of the following, that is, the first configuration information may include at least one of the following:

[0355] S0 resource configurations including CSI resource configurations and / or event-triggered CSI resource configurations,

[0356] R0 reporting configurations including CSI reporting configurations and / or event-triggered CSI reporting configurations,

[0357] S1 LTM CSI resource configuration,

[0358] R1 LTM CSI reporting configuration,

[0359] S2 events trigger LTM CSI resource configuration,

[0360] R2 events trigger LTM CSI reporting configuration.

[0361] The above describes whether event-triggered report configuration and traditional report configuration are numbered uniformly or independently, and / or whether event-triggered resource configuration and traditional resource configuration are numbered uniformly or independently.

[0362] In some embodiments, the unified numbering includes: configured through the same RRC IE; and the independent numbering includes: configured through different RRC IEs.

[0363] For example, “event-triggered CSI resource configuration and CSI resource configuration are numbered uniformly” also means “event-triggered CSI resource configuration and CSI resource configuration are configured through the same RRC IE”.

[0364] The following is an example of RRC IE csi-ResourceConfigToAddModList (Example 1). csi-ResourceConfigToAddModList SEQUENCE(SIZE(1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig,

[0365] For example, as shown in Example 1 above, one or more CSI-ResourceConfigs configured by the same RRC IE csi-ResourceConfigToAddModList are numbered uniformly, where some CSI-ResourceConfigs belong to event-triggered CSI resource configurations and some CSI-ResourceConfigs belong to CSI resource configurations. In other words, both event-triggered CSI resource configurations and CSI resource configurations are configured through CSI-ResourceConfig, or both are configured through csi-ResourceConfigToAddModList. Therefore, event-triggered CSI resource configurations and CSI resource configurations are configured through the same RRC IE, and the same RRC IE refers to CSI-ResourceConfig or csi-ResourceConfigToAddModList.

[0366] For example, "event-triggered CSI resource configuration and CSI resource configuration are numbered uniformly" can be replaced with "event-triggered CSI resource configuration and CSI resource configuration are configured through the same RRC IE." For example, "event-triggered CSI resource configuration and CSI resource configuration are numbered uniformly" can be replaced with "event-triggered CSI resource configuration and CSI resource configuration are numbered uniformly, and event-triggered CSI resource configuration and CSI resource configuration are configured through the same RRC IE." For example, "event-triggered CSI resource configuration and CSI resource configuration are numbered independently" also means "event-triggered CSI resource configuration and CSI resource configuration are configured through different RRC IEs."

[0367] The following is another example of RRC IE csi-ResourceConfigToAddModList (Example 2).

[0368] For example, as shown in Example 2 above, one or more CSI-ResourceConfigs configured by the RRC IE csi-ResourceConfigToAddModList are uniformly numbered and belong to CSI resource configurations, and one or more EventTriggered-CSI-ResourceConfigs configured by the RRC IE eventTriggered-csi-ResourceConfigToAddModList are uniformly numbered and belong to event-triggered CSI resource configurations. Therefore, the event-triggered CSI resource configuration and the CSI resource configuration are configured through different RRC IEs, which refer to CSI-ResourceConfig and EventTriggered-CSI-ResourceConfig, or, csi-ResourceConfigToAddModList and eventTriggered-csi-ResourceConfigToAddModList.

[0369] For example, “event-triggered CSI resource configuration and CSI resource configuration are numbered independently” can be replaced with “event-triggered CSI resource configuration and CSI resource configuration are configured through different RRC IEs”.

[0370] For example, “event-triggered CSI resource configuration and CSI resource configuration are numbered independently” can be replaced with “event-triggered CSI resource configuration and CSI resource configuration are numbered independently, and the event-triggered CSI resource configuration and CSI resource configuration are configured through different RRC IEs”.

[0371] The above description uses event-triggered CSI resource configuration and CSI resource configuration as examples. Both event-triggered CSI resource configuration and CSI resource configuration are logical concepts and can be configured using the same RRC IE or different RRC IEs. The generalizations for other resource configurations and reporting configurations are similar and are not detailed here.

[0372] In some embodiments, the event-triggered CSI reporting configuration is associated with the event-triggered CSI resource configuration, and / or the event-triggered LTM CSI reporting configuration is associated with the event-triggered LTM CSI resource configuration.

[0373] For example, the arrows in Figures 3 to 12 schematically illustrate the association between reporting configurations and resource configurations. A reporting configuration of a certain type is associated with one or more resource configurations of the same type. For example, a resource configuration associated with an event-triggered CSI reporting configuration is called an event-triggered CSI resource configuration, a reporting configuration associated with an event-triggered CSI resource configuration is called an event-triggered CSI reporting configuration, and so on.

[0374] In some embodiments, an event-triggered CSI reporting configuration is associated with a number of an event-triggered CSI reporting configuration and a number of one or more event-triggered CSI resource configurations, and / or an event-triggered LTM CSI reporting configuration is associated with a number of an event-triggered LTM CSI reporting configuration and a number of one or more event-triggered LTM CSI resource configurations.

[0375] For example, the following is an example of the association relationship between report configuration and resource configuration (Example 3).

[0376] For example, as shown in Example 3 above, an event-triggered CSI report configuration (EventTriggered-CSI-ResourceConfig) is associated with a report configuration ID (ReportConfigId) and is associated with one or more resource configuration IDs (ResourceConfigId). In other words, an event-triggered CSI report configuration has a report configuration ID, which is associated with one or more event-triggered CSI resource configurations through one or more resource configuration IDs. The one or more event-triggered CSI resource configurations include at least one of eventTriggered-ResourcesForChannelMeasurement (configuration of resources for channel measurement), eventTriggered-csi-IM-ResourcesForInterference (configuration of IM resources for interference measurement), or eventTriggered-nzp-CSI-RS-ResourcesForInterference (configuration of NZP CSI-RS resources for interference measurement). The generalization of other resource configurations and report configurations can be obtained in the same way, and will not be repeated here.

[0377] In some embodiments, the type of resource configuration is determined based on the type of report configuration associated with the resource configuration, and / or the type of report configuration is determined based on the type of resource configuration associated with the report configuration, the type of report configuration including at least one of an event-triggered CSI report configuration, an event-triggered LTM CSI report configuration, a CSI report configuration, and an LTM CSI report configuration, and the type of resource configuration including at least one of an event-triggered CSI resource configuration, an event-triggered LTM CSI resource configuration, a CSI resource configuration, and an LTM CSI resource configuration.

[0378] For example, as shown in the left part of Figure 4, the event-triggered CSI report configuration and the CSI report configuration are numbered independently, while the event-triggered CSI resource configuration and the CSI resource configuration are numbered uniformly. The following is an example of the corresponding RRC signaling (RRC IE) structure (Example 4).

[0379] For example, as shown in Example 4 above, the event-triggered CSI report configuration (EventTriggered-CSI-ReportConfig) and the CSI report configuration (CSI-ReportConfig) are provided through different RRC IEs, and both the event-triggered CSI report configuration and the CSI report configuration are associated with the resource configuration CSI-ResourceConfig through CSI-ResourceConfigId. The type of resource configuration is determined according to the type of the report configuration with which it is associated. More specifically, the CSI-ResourceConfig associated with the event-triggered CSI report configuration is an event-triggered CSI resource configuration, and the CSI-ResourceConfig associated with the CSI report configuration is a CSI resource configuration. Although the resource configurations are both provided through CSI-ResourceConfig (i.e., configured through the same RRC IE), since the types of the report configurations with which they are associated are distinguishable, it is possible to distinguish which CSI-ResourceConfig belongs to the event-triggered CSI resource configuration and which CSI-ResourceConfig belongs to the CSI resource configuration (i.e., distinguish the types of resource configurations). Event-triggered CSI resource configuration and CSI resource configuration are both logical concepts. The resource configuration associated with event-triggered CSI reporting configuration is called event-triggered CSI resource configuration, and the resource configuration associated with CSI reporting configuration is called CSI resource configuration.

[0380] Similarly, as shown in the right part of FIG4 , the event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered independently, and the event-triggered LTM CSI resource configuration and the LTM CSI resource configuration are numbered uniformly.

[0381] The following is an example of the corresponding RRC signaling (RRC IE) structure (Example 5).

[0382] For example, as shown in FIG8 , the event-triggered CSI report configuration and the event-triggered LTM CSI report configuration are numbered uniformly, the event-triggered CSI resource configuration and the CSI resource configuration are numbered uniformly, and the event-triggered LTM CSI resource configuration and the LTM CSI resource configuration are numbered uniformly.

[0383] The following is an example of the corresponding RRC signaling (RRC IE) structure (Example 6).

[0384] As shown in Example 6, both event-triggered CSI report configuration and event-triggered LTM CSI report configuration are configured through EventTriggered-CSI-ReportConfig.

[0385] In some embodiments, event-triggered CSI resource configuration and event-triggered LTM CSI resource configuration are not configured simultaneously. For example, in EventTriggered-CSI-ReportConfig, eventTriggered-resourcesForChannelMeasurement is configured, or eventTriggered-ltm-ResourcesForChannelMeasurement is configured.

[0386] Here is another example of EventTriggered-CSI-ReportConfig (Example 7)

[0387] As shown in Example 7, eventTriggered-resourcesForChannelMeasurement is configured in EventTriggered-CSI-ReportConfig. EventTriggered-CSI-ReportConfig is associated with CSI-ResourceConfig through CSI-ResourceConfigId.

[0388] The following is another example of EventTriggered-CSI-ReportConfig (Example 8)

[0389] As shown in Example 8, eventTriggered-ltm-ResourcesForChannelMeasurement is configured in EventTriggered-CSI-ReportConfig. EventTriggered-CSI-ReportConfig is associated with LTM-CSI-ResourceConfig-r18 through LTM-CSI-ResourceConfigId-r18.

[0390] According to Examples 7 and 8 above, depending on the type of associated resource configuration, the EventTriggered-CSI-ReportConfig associated with CSI-ResourceConfig is an event-triggered CSI report configuration, and the EventTriggered-CSI-ReportConfig associated with LTM-CSI-ResourceConfig-r18 is an event-triggered LTM CSI report configuration. Depending on the type of associated resource report, the CSI-ResourceConfig associated with EventTriggered-CSI-ReportConfig is an event-triggered CSI resource configuration, and the CSI-ResourceConfig associated with CSI-ReportConfig is a CSI resource configuration. Similarly, the LTM-CSI-ResourceConfig-r18 associated with EventTriggered-CSI-ReportConfig is an event-triggered LTM CSI resource configuration, and the LTM-CSI-ResourceConfig-r18 associated with LTM-CSI-ReportConfig-r18 is an LTM CSI resource configuration.

[0391] The same principle can be extended to other combinations of resource configuration and report configuration, which will not be elaborated one by one.

[0392] According to the above example, for the case where the type of resource configuration is determined according to the type of report configuration associated with the resource configuration, the resource configuration associated with the event-triggered CSI report configuration is the event-triggered CSI resource configuration, and / or, the resource configuration associated with the event-triggered LTM CSI report configuration is the event-triggered LTM CSI resource configuration, and / or, the resource configuration associated with the CSI report configuration is the CSI resource configuration, and / or, the resource configuration associated with the LTM CSI report configuration is the LTM CSI resource configuration.

[0393] Similarly, for the case where the type of report configuration is determined according to the type of resource configuration associated with the report configuration, the report configuration associated with the event-triggered CSI resource configuration is an event-triggered CSI report configuration, and / or, the report configuration associated with the event-triggered LTM CSI resource configuration is an event-triggered LTM CSI report configuration, and / or, the report configuration associated with the CSI resource configuration is a CSI report configuration, and / or, the report configuration associated with the LTM CSI resource configuration is an LTM CSI report configuration.

[0394] In some embodiments, the type of report configuration is determined according to a child RRC IE of the report configuration, and / or the type of resource configuration is determined according to the child RRC IE of the resource configuration, the type of report configuration includes at least one of the event-triggered CSI report configuration, the event-triggered LTM CSI report configuration, the CSI report configuration, and the LTM CSI report configuration, and the type of resource configuration includes at least one of the event-triggered CSI resource configuration, the event-triggered LTM CSI resource configuration, the CSI resource configuration, and the LTM CSI resource configuration.

[0395] For example, the type of report configuration is determined according to the sub-RRC IE in the RRC IE providing the report configuration, and the sub-RRC IE indicates the type of report configuration; the generalization of resource configuration can be obtained in the same way.

[0396] In some embodiments, the type of the report configuration is determined according to the sub-RRC IE of the report configuration, including: the sub-RRC IE is reportConfigType, the reportConfigType of the event-triggered CSI report configuration is configured as eventTriggered, and the reportConfigType of the CSI report configuration is configured as periodic, semiPersistentOnPUCCH, semiPersistentOnPUCCH or aperiodic; and / or, the reportConfigType of the event-triggered LTM CSI report configuration is configured as eventTriggered, and the reportConfigType of the LTM CSI report configuration is configured as periodic, semiPersistentOnPUCCH, semiPersistentOnPUCCH or aperiodic.

[0397] For example, as shown in the left part of FIG5 , the event-triggered CSI report configuration and the CSI report configuration are numbered uniformly.

[0398] The following is an example of the corresponding RRC signaling (RRC IE) structure (Example 9).

[0399] As shown in Example 9, both event-triggered CSI reporting configuration and CSI reporting configuration are configured through CSI-ReportConfig. When reportConfigType is configured as eventTriggered, CSI-ReportConfig is an event-triggered CSI reporting configuration. When reportConfigType is configured as periodic, semiPersistentOnPUCCH, semiPersistentOnPUCCH, or aperiodic, CSI-ReportConfig is a CSI reporting configuration. That is, reportConfigType is used to distinguish whether CSI-ReportConfig is an event-triggered CSI reporting configuration or a CSI reporting configuration. EventTriggerConfig can include specific configurations for event-triggered CSI reporting.

[0400] Similarly, as shown in the right part of FIG5 , the event-triggered LTM CSI report configuration and the LTM CSI report configuration are numbered uniformly.

[0401] The following is an example of the corresponding RRC signaling (RRC IE) structure (Example 10).

[0402] As shown in Example 10, ltm-ReportConfigType is the event-triggered LTM CSI report configuration or the reportConfigType of the LTM CSI report configuration.

[0403] In some embodiments, the event-triggered CSI resource configuration is configured in CSI-MeasConfig, and / or,

[0404] Event triggering LTM CSI resource configuration configured in LTM-Config-r18, and / or,

[0405] Event-triggered CSI reporting configuration is configured in CSI-MeasConfig, and / or,

[0406] Event-triggered LTM CSI reporting is configured in CSI-MeasConfig.

[0407] For example, as shown in FIG3 , different types of resource configurations and different types of report configurations are numbered independently.

[0408] The following is an example of the corresponding RRC signaling (RRC IE) structure (Example 11).

[0409] As shown in Example 11, the event-triggered CSI resource configuration (EventTriggered-CSI-ResourceConfig) is configured in CSI-MeasConfig, the event-triggered LTM CSI resource configuration (EventTriggered-LTM-CSI-ResourceConfig) is configured in LTM-Config-r18, the event-triggered CSI report configuration (EventTriggered-CSI-ReportConfig) is configured in CSI-MeasConfig, and the event-triggered LTM CSI report configuration (EventTriggered-LTM-CSI-ReportConfig) is configured in CSI-MeasConfig.

[0410] In some embodiments, a DCI-triggered aperiodic report is an event-triggered CSI report or an event-triggered LTM CSI report.

[0411] For example, a DCI triggers a non-periodic report, and the non-periodic report is one of an event-triggered CSI report, a CSI report, an LTM CSI report, and an event-triggered LTM CSI report. In other words, the terminal device does not expect a DCI to trigger multiple types of reports. For example, the terminal device does not expect a DCI to trigger both an event-triggered CSI report and a CSI report. As a result, the triggering of different types of reports is independent of each other, which can improve the flexibility of configuration and / or triggering. For example, an event-triggered CSI report or an event-triggered LTM CSI report is sent in a PUSCH scheduled by the DCI. For example, after an event occurs, the terminal device notifies the network device, and the network device schedules the terminal device to send a PUSCH or PUCCH through the DCI. The PUSCH or PUCCH can carry an event-triggered CSI report or an event-triggered LTM CSI report, that is, the event-triggered CSI report or the event-triggered LTM CSI report is included in the PUSCH or PUCCH for transmission. For example, an aperiodic trigger state is associated with an event-triggered CSI report, a CSI report, an LTM CSI report, or an event-triggered LTM CSI report.

[0412] In some embodiments, in a non-periodic trigger state IE,

[0413] The first sub-IE is associated with the CSI report, and / or,

[0414] The second sub-IE associated event triggers a CSI report, and / or

[0415] The third sub-IE is associated with LTM CSI reporting, and / or,

[0416] The fourth sub-IE association event triggers LTM CSI reporting.

[0417] The following is an example of the aperiodic trigger state CSI-AperiodicTriggerState (Example 12).

[0418] For example, as shown in Example 12, in CSI-AperiodicTriggerState, CSI report, event-triggered CSI report, and LTM CSI report correspond to independent RRC IEs, namely, associatedReportConfigInfoList, eventTriggered-associatedReportConfigInfo, and ltm-AssociatedReportConfigInfo-r18, respectively. One DCI indicates one CSI-AperiodicTriggerState, and one CSI-AperiodicTriggerState is associated with one of the event-triggered CSI report (EventTriggered-CSI-ReportConfigId), CSI report (CSI-ReportConfigId), and LTM CSI report (LTM-CSI-ReportConfigId-r18). For example, if ltm-AssociatedReportConfigInfo-r18 is configured, the terminal device ignores associatedReportConfigInfoList and eventTriggered-associatedReportConfigInfo; if ltm-AssociatedReportConfigInfo-r18 is not configured and eventTriggered-associatedReportConfigInfo is configured, the terminal device ignores associatedReportConfigInfoList. Therefore, a CSI-AperiodicTriggerState can only be associated with one of the event-triggered CSI report, CSI report, and LTM CSI report, and a DCI can only trigger one of the event-triggered CSI report, CSI report, and LTM CSI report. For example, when the event-triggered CSI report and the CSI report are numbered independently, the CSI report, the event-triggered CSI report, and the LTM CSI report correspond to associatedReportConfigInfoList, eventTriggered-associatedReportConfigInfo, and ltm-AssociatedReportConfigInfo-r18, respectively.

[0419] In some embodiments, eventTriggered-associatedReportConfigInfo may be replaced with eventTriggered-associatedReportConfigInfoList to associate with multiple event-triggered CSI reports.

[0420] The following is an example of eventTriggered-associatedReportConfigInfoList (Example 13). eventTriggered-associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofEventTriggered ReportConfigPerAperiodicTrigger))OF EventTriggered-CSI-AssociatedReportConfigInfo

[0421] Here is another example of eventTriggered-associatedReportConfigInfoList (Example 14). eventTriggered-associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofEventTriggeredReportConfigPerAperiodicTrigger))OF EventTriggered-CSI-ReportConfigId

[0422] For example, eventTriggered-associatedReportConfigInfo may be replaced with eventTriggered-associatedReportConfigInfoList in Example 13 or Example 14, thereby associating with multiple event-triggered CSI reports.

[0423] In some embodiments, in an aperiodic triggered status IE, the fifth sub-IE is associated with CSI reporting or event-triggered CSI reporting, and / or the sixth sub-IE is associated with LTM CSI reporting or event-triggered LTM CSI reporting.

[0424] The following is an example of CSI-AperiodicTriggerState (Example 15).

[0425] For example, as shown in Example 15, no new RRC IE is defined for event-triggered CSI reporting, but certain restrictions are placed on the RRC configuration, limiting the reports in the associatedReportConfigInfoList in CSI-AperiodicTriggerState to event-triggered CSI reports, or to CSI reports. In other words, the terminal device does not expect to be configured with an associatedReportConfigInfoList that includes both event-triggered CSI reports and CSI reports. How to determine whether the report in the associatedReportConfigInfoList is an event-triggered CSI report or a CSI report can use any of the methods described above.

[0426] For example, if ltm-AssociatedReportConfigInfo-r18 is configured, the terminal device ignores associatedReportConfigInfoList. For example, when event-triggered CSI reports and CSI reports are numbered uniformly, the reports in associatedReportConfigInfoList are all event-triggered CSI reports, or all CSI reports.

[0427] As can be seen from the above embodiments, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

[0428] Embodiments of the second aspect

[0429] An embodiment of the present application provides a configuration method, which is applied to a network device, corresponding to the channel state information reporting method applied to a terminal device described in the embodiment of the first aspect. The same or corresponding content can refer to the records in the embodiment of the first aspect.

[0430] The method is applied to a network device, for example, the network device 101 in FIG1 .

[0431] FIG13 is a schematic diagram of a configuration method according to an embodiment of the present application. As shown in FIG13 , the method includes:

[0432] 1301: The network device sends first configuration information to the terminal device; and

[0433] 1302: The network device receives a report sent according to the first configuration information from the terminal device.

[0434] The first configuration information includes at least one of the following configuration information:

[0435] Event triggers CSI resource configuration;

[0436] Event-triggered CSI reporting configuration;

[0437] Event triggers LTM CSI resource configuration;

[0438] Event-triggered LTM CSI report configuration,

[0439] The ID of the CSI reporting configuration triggered by the event is determined according to at least one of the following methods:

[0440] This event triggers the CSI report configuration and the CSI report configuration is numbered independently;

[0441] The event triggers the CSI report configuration and the CSI report configuration has the same number;

[0442] The CSI report configuration triggered by this event and the LTM CSI report configuration triggered by this event are numbered independently;

[0443] The CSI report configuration triggered by this event is numbered the same as the LTM CSI report configuration triggered by this event.

[0444] The CSI report configuration triggered by this event is numbered independently from the LTM CSI report configuration.

[0445] In some embodiments, the number of the LTM CSI report configuration triggered by the event is determined according to at least one of the following methods:

[0446] The event triggering the LTM CSI report configuration is numbered independently from the LTM CSI report configuration;

[0447] The event triggering LTM CSI report configuration has the same number as the LTM CSI report configuration;

[0448] The LTM CSI report configuration triggered by this event is numbered independently from the CSI report configuration triggered by this event;

[0449] The LTM CSI report configuration triggered by this event is numbered the same as the CSI report configuration triggered by this event;

[0450] The event triggering the LTM CSI report configuration is numbered independently from the CSI report configuration.

[0451] In some embodiments, the number of the CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0452] The event triggering the CSI resource configuration is numbered independently of the CSI resource configuration;

[0453] The event triggering the CSI resource configuration has the same number as the CSI resource configuration;

[0454] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event are numbered independently;

[0455] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event have the same number;

[0456] The event triggering CSI resource configuration is numbered independently from the LTM CSI resource configuration.

[0457] In some embodiments, the number of the LTM CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0458] The event triggering the LTM CSI resource configuration is numbered independently from the LTM CSI resource configuration;

[0459] The event triggering the LTM CSI resource configuration has the same number as the LTM CSI resource configuration;

[0460] The LTM CSI resource configuration triggered by this event is numbered independently from the CSI resource configuration triggered by this event;

[0461] The LTM CSI resource configuration triggered by this event is numbered the same as the CSI resource configuration triggered by this event;

[0462] The event triggering the LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0463] In some embodiments, the first configuration information further includes at least one of the following configuration information:

[0464] CSI resource allocation;

[0465] CSI report configuration;

[0466] LTM CSI resource configuration;

[0467] LTM CSI reporting configuration.

[0468] In the embodiment of the present application, the specific implementation of the above operations 1301 and 1302 can refer to the relevant records in the embodiment of the first aspect, and will not be repeated here.

[0469] As can be seen from the above embodiments, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

[0470] Embodiments of the third aspect

[0471] The present application provides a method for reporting channel state information, which is applied to a terminal device and a network device, such as the terminal device 102 and the network device 101 in Figures 1 and 2. This method corresponds to the channel state information reporting method described in the embodiment of the first aspect and the configuration method described in the embodiment of the second aspect, and the same content will not be repeated here.

[0472] FIG14 is an interactive diagram of a channel state information reporting method according to an embodiment of the present application, which is applied to a terminal device and a network device. As shown in FIG14 , the method includes:

[0473] 1401: The network device sends first configuration information to the terminal device;

[0474] 1402: The terminal device sends a report to the network device according to the first configuration information.

[0475] The first configuration information includes at least one of the following configuration information:

[0476] Event triggers CSI resource configuration;

[0477] Event-triggered CSI reporting configuration;

[0478] Event triggers LTM CSI resource configuration;

[0479] Event-triggered LTM CSI report configuration,

[0480] The ID of the CSI reporting configuration triggered by the event is determined according to at least one of the following methods:

[0481] This event triggers the CSI report configuration and the CSI report configuration is numbered independently;

[0482] The event triggers the CSI report configuration and the CSI report configuration has the same number;

[0483] The CSI report configuration triggered by this event and the LTM CSI report configuration triggered by this event are numbered independently;

[0484] The CSI report configuration triggered by this event is numbered the same as the LTM CSI report configuration triggered by this event.

[0485] The CSI report configuration triggered by this event is numbered independently from the LTM CSI report configuration.

[0486] In some embodiments, the number of the LTM CSI report configuration triggered by the event is determined according to at least one of the following methods:

[0487] The event triggering the LTM CSI report configuration is numbered independently from the LTM CSI report configuration;

[0488] The event triggering LTM CSI report configuration has the same number as the LTM CSI report configuration;

[0489] The LTM CSI report configuration triggered by this event is numbered independently from the CSI report configuration triggered by this event;

[0490] The LTM CSI report configuration triggered by this event is numbered the same as the CSI report configuration triggered by this event;

[0491] The event triggering the LTM CSI report configuration is numbered independently from the CSI report configuration.

[0492] In some embodiments, the number of the CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0493] The event triggering the CSI resource configuration is numbered independently of the CSI resource configuration;

[0494] The event triggering the CSI resource configuration has the same number as the CSI resource configuration;

[0495] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event are numbered independently;

[0496] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event have the same number;

[0497] The event triggering CSI resource configuration is numbered independently from the LTM CSI resource configuration.

[0498] In some embodiments, the number of the LTM CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0499] The event triggering the LTM CSI resource configuration is numbered independently from the LTM CSI resource configuration;

[0500] The event triggering the LTM CSI resource configuration has the same number as the LTM CSI resource configuration;

[0501] The LTM CSI resource configuration triggered by this event is numbered independently from the CSI resource configuration triggered by this event;

[0502] The LTM CSI resource configuration triggered by this event is numbered the same as the CSI resource configuration triggered by this event;

[0503] The event triggering the LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0504] In some embodiments, the first configuration information further includes at least one of the following configuration information:

[0505] CSI resource allocation;

[0506] CSI report configuration;

[0507] LTM CSI resource configuration;

[0508] LTM CSI reporting configuration.

[0509] In the embodiment of the present application, the specific implementation of the above operations 1401-1402 can refer to the records in the embodiment of the first aspect and will not be repeated here.

[0510] As can be seen from the above embodiments, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

[0511] Embodiments of the fourth aspect

[0512] The present application provides a channel state information reporting device, which is provided in a terminal device. Since the principle of solving the problem of this device is similar to that of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method described in the embodiment of the first aspect, and the same or related content will not be repeated here.

[0513] FIG15 is a schematic diagram of a channel state information reporting device according to an embodiment of the present application. As shown in FIG15 , the device 1500 includes:

[0514] A first receiving unit 1501 receives first configuration information; and

[0515] The first sending unit 1502 sends a report according to the first configuration information.

[0516] The first configuration information includes at least one of the following configuration information:

[0517] Event triggers CSI resource configuration;

[0518] Event-triggered CSI reporting configuration;

[0519] Event triggers LTM CSI resource configuration;

[0520] Event-triggered LTM CSI report configuration,

[0521] The ID of the CSI reporting configuration triggered by the event is determined according to at least one of the following methods:

[0522] This event triggers the CSI report configuration and the CSI report configuration is numbered independently;

[0523] The event triggers the CSI report configuration and the CSI report configuration has the same number;

[0524] The CSI report configuration triggered by this event and the LTM CSI report configuration triggered by this event are numbered independently;

[0525] The CSI report configuration triggered by this event is numbered the same as the LTM CSI report configuration triggered by this event.

[0526] The CSI report configuration triggered by this event is numbered independently from the LTM CSI report configuration.

[0527] In some embodiments, the first configuration information further includes at least one of the following configuration information:

[0528] CSI resource allocation;

[0529] CSI report configuration;

[0530] LTM CSI resource configuration;

[0531] LTM CSI reporting configuration.

[0532] In some embodiments, the number of the LTM CSI report configuration triggered by the event is determined according to at least one of the following methods:

[0533] The event triggering the LTM CSI report configuration is numbered independently from the LTM CSI report configuration;

[0534] The event triggering LTM CSI report configuration has the same number as the LTM CSI report configuration;

[0535] The LTM CSI report configuration triggered by this event is numbered independently from the CSI report configuration triggered by this event;

[0536] The LTM CSI report configuration triggered by this event is numbered the same as the CSI report configuration triggered by this event;

[0537] The event triggering the LTM CSI report configuration is numbered independently from the CSI report configuration.

[0538] In some embodiments, the number of the CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0539] The event triggering the CSI resource configuration is numbered independently of the CSI resource configuration;

[0540] The event triggering the CSI resource configuration has the same number as the CSI resource configuration;

[0541] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event are numbered independently;

[0542] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event have the same number;

[0543] The event triggering CSI resource configuration is numbered independently from the LTM CSI resource configuration.

[0544] In some embodiments, the number of the LTM CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0545] The event triggering the LTM CSI resource configuration is numbered independently from the LTM CSI resource configuration;

[0546] The event triggering the LTM CSI resource configuration has the same number as the LTM CSI resource configuration;

[0547] The LTM CSI resource configuration triggered by this event is numbered independently from the CSI resource configuration triggered by this event;

[0548] The LTM CSI resource configuration triggered by this event is numbered the same as the CSI resource configuration triggered by this event;

[0549] The event triggering the LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0550] In some embodiments, the unified numbering includes: configuring through the same RRC IE,

[0551] The independent numbering includes: configuring through different RRC IEs.

[0552] In some embodiments, the event-triggered CSI reporting configuration is associated with the event-triggered CSI resource configuration, and / or,

[0553] The event-triggered LTM CSI report configuration is associated with the event-triggered LTM CSI resource configuration.

[0554] In some embodiments, an event-triggered CSI reporting configuration is associated with an event-triggered CSI reporting configuration number and one or more event-triggered CSI resource configuration numbers, and / or,

[0555] An event-triggered LTM CSI report configuration is associated with an event-triggered LTM CSI report configuration number and one or more event-triggered LTM CSI resource configuration numbers.

[0556] In some embodiments, the type of resource configuration is determined based on the type of report configuration associated with the resource configuration, and / or the type of report configuration is determined based on the type of resource configuration associated with the report configuration.

[0557] The type of the reporting configuration includes at least one of the event-triggered CSI reporting configuration, the event-triggered LTM CSI reporting configuration, the CSI reporting configuration, and the LTM CSI reporting configuration.

[0558] The type of the resource configuration includes at least one of the event-triggered CSI resource configuration, the event-triggered LTM CSI resource configuration, the CSI resource configuration, and the LTM CSI resource configuration.

[0559] In some embodiments, the resource configuration associated with the event-triggered CSI reporting configuration is the event-triggered CSI resource configuration, and / or,

[0560] The resource configuration associated with the event-triggered LTM CSI report configuration is the event-triggered LTM CSI resource configuration, and / or,

[0561] The resource configuration associated with the CSI report configuration is the CSI resource configuration, and / or,

[0562] The resource configuration associated with the LTM CSI report configuration is the LTM CSI resource configuration.

[0563] In some embodiments, the reporting configuration associated with the event-triggered CSI resource configuration is the event-triggered CSI reporting configuration, and / or,

[0564] The report configuration associated with the event-triggered LTM CSI resource configuration is the event-triggered LTM CSI report configuration, and / or,

[0565] The report configuration associated with the CSI resource configuration is the CSI report configuration, and / or,

[0566] The report configuration associated with the LTM CSI resource configuration is the LTM CSI report configuration.

[0567] In some embodiments, the type of report configuration is determined according to a child RRC IE of the report configuration, and / or the type of resource configuration is determined according to the child RRC IE of the resource configuration.

[0568] The type of the reporting configuration includes at least one of the event-triggered CSI reporting configuration, the event-triggered LTM CSI reporting configuration, the CSI reporting configuration, and the LTM CSI reporting configuration.

[0569] The type of the resource configuration includes at least one of the event-triggered CSI resource configuration, the event-triggered LTM CSI resource configuration, the CSI resource configuration, and the LTM CSI resource configuration.

[0570] In some embodiments, the type of the report configuration is determined according to the sub-RRC IE of the report configuration, including:

[0571] The sub-RRC IE is reportConfigType,

[0572] The reportConfigType of the event-triggered CSI report configuration is configured as eventTriggered, and the reportConfigType of the CSI report configuration is configured as periodic, semiPersistentOnPUCCH, semiPersistentOnPUCCH, or aperiodic;

[0573] and / or,

[0574] The reportConfigType of the event-triggered LTM CSI report configuration is configured as eventTriggered, and the reportConfigType of the LTM CSI report configuration is configured as periodic, semiPersistentOnPUCCH, semiPersistentOnPUCCH, or aperiodic.

[0575] In some embodiments, the event triggers the CSI resource configuration to be configured in CSI-MeasConfig, and / or,

[0576] This event triggers the LTM CSI resource configuration configured in LTM-Config-r18, and / or,

[0577] This event triggers the CSI report configuration configured in CSI-MeasConfig, and / or,

[0578] This event triggers the LTM CSI report configuration configured in CSI-MeasConfig.

[0579] In some embodiments, a DCI-triggered aperiodic report is an event-triggered CSI report or an event-triggered LTM CSI report.

[0580] In some embodiments, in a non-periodic trigger state IE,

[0581] The first sub-IE is associated with the CSI report, and / or,

[0582] The second sub-IE associated event triggers a CSI report, and / or

[0583] The third sub-IE is associated with LTM CSI reporting, and / or,

[0584] The fourth sub-IE association event triggers LTM CSI reporting.

[0585] In some embodiments, in an aperiodic triggered status IE, the fifth sub-IE is associated with CSI reporting or event-triggered CSI reporting, and / or the sixth sub-IE is associated with LTM CSI reporting or event-triggered LTM CSI reporting.

[0586] As can be seen from the above embodiments, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

[0587] Embodiments of the fifth aspect

[0588] The present application provides a configuration device for use with a network device. Since the principle of solving the problem is similar to that of the second aspect of the embodiment, its specific implementation can refer to the implementation of the method described in the second aspect of the embodiment, and the same or related parts will not be repeated here.

[0589] FIG16 is a schematic diagram of a configuration device according to an embodiment of the present application. As shown in FIG16 , the device 1600 includes:

[0590] A second sending unit 1601 is configured to send first configuration information to a terminal device; and

[0591] The second receiving unit 1602 receives a report sent according to the first configuration information from the terminal device,

[0592] The first configuration information includes at least one of the following configuration information:

[0593] Event triggers CSI resource configuration;

[0594] Event-triggered CSI reporting configuration;

[0595] Event triggers LTM CSI resource configuration;

[0596] Event-triggered LTM CSI report configuration,

[0597] The ID of the CSI reporting configuration triggered by the event is determined according to at least one of the following methods:

[0598] This event triggers the CSI report configuration and the CSI report configuration is numbered independently;

[0599] The event triggers the CSI report configuration and the CSI report configuration has the same number;

[0600] The CSI report configuration triggered by this event and the LTM CSI report configuration triggered by this event are numbered independently;

[0601] The CSI report configuration triggered by this event is numbered the same as the LTM CSI report configuration triggered by this event.

[0602] The CSI report configuration triggered by this event is numbered independently from the LTM CSI report configuration.

[0603] In some embodiments, the number of the LTM CSI report configuration triggered by the event is determined according to at least one of the following methods:

[0604] The event triggering the LTM CSI report configuration is numbered independently from the LTM CSI report configuration;

[0605] The event triggering LTM CSI report configuration has the same number as the LTM CSI report configuration;

[0606] The LTM CSI report configuration triggered by this event is numbered independently from the CSI report configuration triggered by this event;

[0607] The LTM CSI report configuration triggered by this event is numbered the same as the CSI report configuration triggered by this event;

[0608] The event triggering the LTM CSI report configuration is numbered independently from the CSI report configuration.

[0609] In some embodiments, the number of the CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0610] The event triggering the CSI resource configuration is numbered independently of the CSI resource configuration;

[0611] The event triggering the CSI resource configuration has the same number as the CSI resource configuration;

[0612] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event are numbered independently;

[0613] The CSI resource configuration triggered by this event and the LTM CSI resource configuration triggered by this event have the same number;

[0614] The event triggering CSI resource configuration is numbered independently from the LTM CSI resource configuration.

[0615] In some embodiments, the number of the LTM CSI resource configuration triggered by the event is determined according to at least one of the following methods:

[0616] The event triggering the LTM CSI resource configuration is numbered independently from the LTM CSI resource configuration;

[0617] The event triggering the LTM CSI resource configuration has the same number as the LTM CSI resource configuration;

[0618] The LTM CSI resource configuration triggered by this event is numbered independently from the CSI resource configuration triggered by this event;

[0619] The LTM CSI resource configuration triggered by this event is numbered the same as the CSI resource configuration triggered by this event;

[0620] The event triggering the LTM CSI resource configuration is numbered independently from the CSI resource configuration.

[0621] In some embodiments, the first configuration information further includes at least one of the following configuration information:

[0622] CSI resource allocation;

[0623] CSI report configuration;

[0624] LTM CSI resource configuration;

[0625] LTM CSI reporting configuration.

[0626] As can be seen from the above embodiments, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

[0627] Embodiments of the sixth aspect

[0628] An embodiment of the present application provides a terminal device, which includes the channel state information reporting device according to the embodiment of the fourth aspect.

[0629] Figure 17 is a schematic block diagram of the system architecture of a terminal device according to an embodiment of the present invention. As shown in Figure 17 , terminal device 1700 may include a processor 1710 and a memory 1720; memory 1720 is coupled to processor 1710. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0630] In one embodiment, the function of the channel state information reporting apparatus may be integrated into the processor 1710 .

[0631] The processor 1710 is configured to: receive first configuration information at a terminal device; and send a report according to the first configuration information by the terminal device.

[0632] The first configuration information includes at least one of the following configuration information:

[0633] Event triggers CSI resource configuration;

[0634] Event-triggered CSI reporting configuration;

[0635] Event triggers LTM CSI resource configuration;

[0636] Event-triggered LTM CSI report configuration,

[0637] The ID of the CSI reporting configuration triggered by the event is determined according to at least one of the following methods:

[0638] This event triggers the CSI report configuration and the CSI report configuration is numbered independently;

[0639] The event triggers the CSI report configuration and the CSI report configuration has the same number;

[0640] The CSI report configuration triggered by this event and the LTM CSI report configuration triggered by this event are numbered independently;

[0641] The CSI report configuration triggered by this event is numbered the same as the LTM CSI report configuration triggered by this event.

[0642] The CSI report configuration triggered by this event is numbered independently from the LTM CSI report configuration.

[0643] In another embodiment, the channel state information reporting device can be configured separately from the processor 1710. For example, the channel state information reporting device can be configured as a chip connected to the processor 1710, and the functions of the channel state information reporting device are realized through the control of the processor 1710.

[0644] As shown in FIG17 , the terminal device 1700 may further include: a communication module 1730, an input unit 1740, a display 1750, and a power supply 1760. It is worth noting that the terminal device 1700 does not necessarily include all the components shown in FIG17 ; in addition, the terminal device 1700 may also include components not shown in FIG17 , and reference may be made to related art for details.

[0645] As shown in FIG. 17 , the processor 1710 is sometimes also referred to as a controller or an operation control, and may include a microprocessor or other processor device and / or logic device. The processor 1710 receives inputs and controls the operations of various components of the terminal device 1700 .

[0646] Memory 1720 may be, for example, one or more of a cache, flash memory, a hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store various data and programs for executing related information. Processor 1710 may execute the programs stored in memory 1720 to implement information storage or processing. The functions of other components are similar to those of existing devices and are not further described here. Each component of terminal device 1700 may be implemented using dedicated hardware, firmware, software, or a combination thereof without departing from the scope of the present invention.

[0647] As can be seen from the above embodiments, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

[0648] Embodiments of the seventh aspect

[0649] An embodiment of the present application provides a network device, which includes the configuration device according to the embodiment of the fifth aspect.

[0650] Figure 18 is a schematic block diagram of the system configuration of a network device according to an embodiment of the present application. As shown in Figure 18 , network device 1800 may include a processor 1810 and a memory 1820; the memory 1820 is coupled to the processor 1810. The memory 1820 can store various data and also stores an information processing program 1830. This program 1830 is executed under the control of the processor 1810 to receive various information sent by terminal devices and to send various information to the terminal devices.

[0651] In one embodiment, the functionality of the configuration device may be integrated into the processor 1810 .

[0652] The processor 1810 may be configured to: the network device sends first configuration information to the terminal device; and the network device receives a report sent according to the first configuration information from the terminal device,

[0653] The first configuration information includes at least one of the following configuration information:

[0654] Event triggers CSI resource configuration;

[0655] Event-triggered CSI reporting configuration;

[0656] Event triggers LTM CSI resource configuration;

[0657] Event-triggered LTM CSI report configuration,

[0658] The ID of the CSI reporting configuration triggered by the event is determined according to at least one of the following methods:

[0659] This event triggers the CSI report configuration and the CSI report configuration is numbered independently;

[0660] The event triggers the CSI report configuration and the CSI report configuration has the same number;

[0661] The CSI report configuration triggered by this event and the LTM CSI report configuration triggered by this event are numbered independently;

[0662] The CSI report configuration triggered by this event is numbered the same as the LTM CSI report configuration triggered by this event.

[0663] The CSI report configuration triggered by this event is numbered independently from the LTM CSI report configuration.

[0664] In another embodiment, the configuration device may be configured separately from the processor 1810 . For example, the random access device may be configured as a chip connected to the processor 1810 , and the functions of the configuration device may be implemented under the control of the processor 1810 .

[0665] In addition, as shown in FIG18 , network device 1800 may further include: a transceiver 1840 and an antenna 1850, etc.; wherein, the functions of the above components are similar to those in the prior art and are not further described here. It is worth noting that network device 1800 does not necessarily include all the components shown in FIG18 ; in addition, network device 1800 may also include components not shown in FIG18 , and reference may be made to the prior art for such components.

[0666] As can be seen from the above embodiments, a set of event-triggered reporting configurations can be configured as a subset of a set of traditional reporting configurations, or configured separately from a set of traditional reporting configurations. Furthermore, event-triggered resources can also be configured in a similar manner. This can reduce device complexity or increase configuration flexibility, thereby reducing reporting overhead and improving reporting timeliness through event-triggered reporting.

[0667] Embodiments of the eighth aspect

[0668] The embodiment of the present application provides a communication system, including the terminal device according to the embodiment of the sixth aspect and / or the network device according to the embodiment of the seventh aspect. For specific details, please refer to the description of the embodiment of the sixth aspect and the embodiment of the seventh aspect.

[0669] For example, the structure of the communication system can refer to Figure 1. As shown in Figure 1, the communication system 100 includes a network device 101 and a terminal device 102. The terminal device 102 can be the same as the terminal device recorded in the embodiment of the sixth aspect, and / or, the network device 101 can be the same as the network device recorded in the embodiment of the seventh aspect. The repeated content will not be repeated.

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

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

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

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

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

Claims

1. A channel state information (CSI) reporting device, which is disposed in a terminal device and includes: A first receiving unit, which receives first configuration information; And A first transmitting unit, which sends a report according to the first configuration information, The first configuration information includes at least one of the following configuration information: Event-triggered CSI resource configuration; Event-triggered CSI report configuration; Event-triggered LTM CSI resource configuration; Event-triggered LTM CSI report configuration, The number (ID) of the event-triggered CSI report configuration is determined according to at least one of the following methods: The event-triggered CSI report configuration is numbered independently of the CSI report configuration; The event-triggered CSI report configuration is numbered uniformly with the CSI report configuration; The event-triggered CSI report configuration is numbered independently of the event-triggered LTM CSI report configuration; The event-triggered CSI report configuration is numbered uniformly with the event-triggered LTM CSI report configuration; The event-triggered CSI report configuration is numbered independently of the LTM CSI report configuration.

2. The device according to claim 1, wherein The first configuration information further includes at least one of the following configuration information: CSI resource configuration; CSI report configuration; LTM CSI resource configuration; LTM CSI report configuration.

3. The device according to claim 1, wherein, The number of the event-triggered LTM CSI report configuration is determined according to at least one of the following methods: The event-triggered LTM CSI report configuration is numbered independently of the LTM CSI report configuration; The event-triggered LTM CSI report configuration is numbered uniformly with the LTM CSI report configuration; The event-triggered LTM CSI report configuration is numbered independently of the event-triggered CSI report configuration; The event-triggered LTM CSI report configuration is numbered uniformly with the event-triggered CSI report configuration; The event-triggered LTM CSI report configuration is numbered independently of the CSI report configuration.

4. The device according to claim 1, wherein The number of the event-triggered CSI resource configuration is determined according to at least one of the following methods: The event-triggered CSI resource configuration is numbered independently of the CSI resource configuration; The event-triggered CSI resource configuration is numbered uniformly with the CSI resource configuration; The event-triggered CSI resource configuration is numbered independently of the event-triggered LTM CSI resource configuration; The event-triggered CSI resource configuration is numbered uniformly with the event-triggered LTM CSI resource configuration; The event-triggered CSI resource configuration is numbered independently of the LTM CSI resource configuration.

5. The device according to claim 1, wherein The number of the event-triggered LTM CSI resource configuration is determined according to at least one of the following methods: The event-triggered LTM CSI resource configuration is numbered independently of the LTM CSI resource configuration; The event-triggered LTM CSI resource configuration is numbered uniformly with the LTM CSI resource configuration; The event-triggered LTM CSI resource configuration is numbered independently of the event-triggered CSI resource configuration; The event-triggered LTM CSI resource configuration and the event-triggered CSI resource configuration are numbered uniformly; The event-triggered LTM CSI resource configuration and the CSI resource configuration are numbered independently.

6. The apparatus according to any one of claims 1-5, wherein The uniform numbering includes: through the same RRC IE configuration, The independent numbering includes: through different RRC IE configurations.

7. The apparatus according to claim 1, wherein The event-triggered CSI report configuration is associated with the event-triggered CSI resource configuration, and / or The event-triggered LTM CSI report configuration is associated with the event-triggered LTM CSI resource configuration.

8. The apparatus according to claim 7, wherein One event-triggered CSI report configuration is associated with the number of one event-triggered CSI report configuration and the numbers of one or more event-triggered CSI resource configurations, and / or One event-triggered LTM CSI report configuration is associated with the number of one event-triggered LTM CSI report configuration and the numbers of one or more event-triggered LTM CSI resource configurations.

9. The apparatus according to claim 1, wherein The type of resource configuration is determined according to the type of report configuration associated with the resource configuration, and / or the type of report configuration is determined according to the type of resource configuration associated with the report configuration, The type of the report configuration includes at least one of the event-triggered CSI report configuration, the event-triggered LTM CSI report configuration, the CSI report configuration, and the LTM CSI report configuration, The type of the resource configuration includes at least one of the event-triggered CSI resource configuration, the event-triggered LTM CSI resource configuration, the CSI resource configuration, and the LTM CSI resource configuration.

10. The apparatus according to claim 9, wherein The resource configuration associated with the event-triggered CSI report configuration is the event-triggered CSI resource configuration, and / or The resource configuration associated with the event-triggered LTM CSI report configuration is the event-triggered LTM CSI resource configuration, and / or The resource configuration associated with the CSI report configuration is the CSI resource configuration, and / or The resource configuration associated with the LTM CSI report configuration is the LTM CSI resource configuration.

11. The apparatus according to claim 9, wherein The report configuration associated with the event-triggered CSI resource configuration is the event-triggered CSI report configuration, and / or The report configuration associated with the event-triggered LTM CSI resource configuration is the event-triggered LTM CSI report configuration, and / or The report configuration associated with the CSI resource configuration is the CSI report configuration, and / or The report configuration associated with the LTM CSI resource configuration is the LTM CSI report configuration.

12. The apparatus according to claim 1, wherein The type of the report configuration is determined according to the child RRC IE (radio resource control information element) of the report configuration, and / or, the type of the resource configuration is determined according to the child RRC IE of the resource configuration. The type of the report configuration includes at least one of the event-triggered CSI report configuration, the event-triggered LTM CSI report configuration, the CSI report configuration, and the LTM CSI report configuration. The type of the resource configuration includes at least one of the event-triggered CSI resource configuration, the event-triggered LTM CSI resource configuration, the CSI resource configuration, and the LTM CSI resource configuration.

13. The device according to claim 12, wherein, The type of the report configuration is determined according to the child RRC IE of the report configuration, including: The child RRC IE is reportConfigType. The reportConfigType of the event-triggered CSI report configuration is configured as eventTriggered, and the reportConfigType of the CSI report configuration is configured as periodic, semiPersistentOnPUCCH, semiPersistentOnPUCCH, or aperiodic. and / or, The reportConfigType of the event-triggered LTM CSI report configuration is configured as eventTriggered, and the reportConfigType of the LTM CSI report configuration is configured as periodic, semiPersistentOnPUCCH, semiPersistentOnPUCCH, or aperiodic.

14. The device according to claim 1, wherein, The event-triggered CSI resource configuration is configured in CSI-MeasConfig, and / or, The event-triggered LTM CSI resource configuration is configured in LTM-Config-r18, and / or, The event-triggered CSI report configuration is configured in CSI-MeasConfig, and / or, The event-triggered LTM CSI report configuration is configured in CSI-MeasConfig.

15. The device according to claim 1, wherein, Aperiodic reports triggered by a DCI are event-triggered CSI reports or event-triggered LTM CSI reports.

16. The device according to claim 15, wherein, In an aperiodic trigger status IE, The first sub-IE is associated with a CSI report, and / or, The second sub-IE is associated with an event-triggered CSI report, and / or, The third sub-IE is associated with an LTM CSI report, and / or, The fourth sub-IE is associated with an event-triggered LTM CSI report.

17. The device according to claim 15, wherein, In an aperiodic trigger status IE, The fifth sub-IE is associated with a CSI report or an event-triggered CSI report, and / or the sixth sub-IE is associated with an LTM CSI report or an event-triggered LTM CSI report.

18. A configuration device, which is arranged in a network device, and the device includes: A second sending unit, which sends first configuration information to a terminal device; And A second receiving unit, which receives a report sent by the terminal device according to the first configuration information, The first configuration information includes at least one of the following configuration information: Event-triggered CSI resource configuration; Event-triggered CSI report configuration; Event-triggered LTM CSI resource configuration; Event-triggered LTM CSI report configuration, The number (ID) of the event-triggered CSI report configuration is determined according to at least one of the following methods: The event-triggered CSI report configuration is numbered independently of the CSI report configuration; The event-triggered CSI report configuration is numbered uniformly with the CSI report configuration; The event-triggered CSI report configuration is numbered independently of the event-triggered LTM CSI report configuration; The event-triggered CSI report configuration is numbered uniformly with the event-triggered LTM CSI report configuration; The event-triggered CSI report configuration is numbered independently of the LTM CSI report configuration.

19. The device according to claim 18, wherein The first configuration information further includes at least one of the following configuration information: CSI resource configuration; CSI report configuration; LTM CSI resource configuration; LTM CSI report configuration.

20. A communication system, the communication system includes a network device and / or a terminal device, The terminal device includes the device according to claim 1, The network device includes the device according to claim 18.

Images