Information reporting method and apparatus, and information receiving method and apparatus

Abstract

Embodiments of the present application provide an information reporting method and apparatus, and an information receiving method and apparatus. The information receiving method comprises: a terminal device receiving configuration information used for configuring one or more event-triggered reports, the one or more event-triggered reports being associated with a scheduling request configuration or a RACH configuration; when an event-triggered report meets a triggering condition, sending a scheduling request or a PRACH; receiving downlink control information (DCI); and sending the event-triggered report on a PUSCH or PUCCH indicated by the DCI, wherein the event-triggered report comprises at least one of a report index, a measurement resource index, and a measurement result.

Description

Information reporting and receiving method and device Technical Field

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

[0002] 5G NR supports Channel State Information (CSI) reporting. For example, a CSI report can include at least one of the following: CSI-RS Resource Indicator (CRI), SSB Resource Indicator (SSBRI), L1-RSRP, and L1-SINR, i.e., it can include beam-related reporting. The terminal device sends a beam report to the network device, which can perform beam management based on the report, for example, indicating a better beam for the terminal device.

[0003] The network device determines when a terminal device sends a CSI report. The network device can configure periodic CSI reporting, which causes the terminal device to send CSI reports periodically. It can also configure semi-persistent CSI reporting, which causes the terminal device to send CSI reports periodically after being activated by the network device. It can also configure aperiodic CSI reporting, which causes the terminal device to send a single CSI report after being triggered by the network device. CSI reports include measurement results for the serving cell.

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

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

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

[0007] Summary of the Invention

[0008] The inventors have discovered that event-triggered reporting will be introduced in the upcoming Rel-19 release. More specifically, further enhancements will be introduced to CSI and LTM CSI reporting, namely, support for event-triggered CSI and LTM CSI reporting. Event-triggered CSI and LTM CSI reporting correspond to traditional CSI and LTM CSI reporting, respectively.

[0009] Unlike the traditional reporting described above, event-triggered reporting determines when the terminal device sends the report, i.e., it is triggered by an event. In other words, the terminal device only sends reports when necessary, resulting in more timely reporting. Furthermore, by avoiding unnecessary reports, reporting overhead is reduced. Supporting event-triggered CSI reporting and event-triggered LTM CSI reporting is an issue that needs to be addressed. Currently, 3GPP has just approved the Rel-19 project and has not yet begun discussing technical details.

[0010] To address at least one of the above problems, an embodiment of the present application provides an information reporting method and apparatus.

[0011] According to one aspect of an embodiment of the present application, there is provided an information reporting method, including:

[0012] The terminal device receives configuration information for configuring one or more event-triggered reports, wherein the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; and

[0013] The terminal device sends a scheduling request or PRACH when an event trigger report meets the triggering condition;

[0014] The terminal device receives downlink control information (DCI); and

[0015] The terminal device sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0016] According to another aspect of an embodiment of the present application, there is provided an information reporting device, including:

[0017] a receiving unit configured to receive configuration information for configuring one or more event-triggered reports, wherein the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; and

[0018] a sending unit, which sends a scheduling request or PRACH when an event triggered report meets a triggering condition;

[0019] The receiving unit further receives downlink control information (DCI); and

[0020] The sending unit further sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0021] According to another aspect of an embodiment of the present application, there is provided an information reporting method, including:

[0022] The terminal device receives configuration information for configuring one or more event-triggered reports and / or one or more trigger states; wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration;

[0023] The terminal device sends a scheduling request or PRACH according to the scheduling request configuration or RACH configuration associated with the event triggered report when an event triggered report meets the triggering condition;

[0024] The terminal device receives downlink control information (DCI); and

[0025] The terminal device sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

[0026] According to another aspect of an embodiment of the present application, there is provided an information reporting device, including:

[0027] a receiving unit configured to receive configuration information for configuring one or more event-triggered reports and / or one or more trigger states, wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration;

[0028] a sending unit configured to send a scheduling request or a PRACH according to a scheduling request configuration or a RACH configuration associated with an event triggered report when an event triggered report satisfies a triggering condition;

[0029] The receiving unit further receives downlink control information (DCI); and

[0030] The sending unit further sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

[0031] According to another aspect of an embodiment of the present application, there is provided an information reporting method, including:

[0032] The terminal device receives configuration information for configuring one or more event-triggered reports; wherein the first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and the second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration;

[0033] The terminal device sends a scheduling request or PRACH according to the scheduling request configuration or RACH configuration associated with the event triggered report when an event triggered report meets the triggering condition;

[0034] The terminal device receives downlink control information (DCI); and

[0035] The terminal device sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0036] According to another aspect of an embodiment of the present application, there is provided an information reporting device, including:

[0037] a receiving unit configured to receive configuration information for configuring one or more event-triggered reports, wherein a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration;

[0038] a sending unit configured to send a scheduling request or a PRACH according to a scheduling request configuration or a RACH configuration associated with an event triggered report when an event triggered report satisfies a triggering condition;

[0039] The receiving unit further receives downlink control information (DCI); and

[0040] The sending unit further sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0041] One of the beneficial effects of the embodiments of the present application is that it enables the terminal device to quickly send an event trigger report after an event occurs, thereby improving the timeliness of the report and reducing the reporting overhead.

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

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

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

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

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

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

[0048] FIG3 is an example diagram of the relationship between scheduling request configuration, events, and reports according to an embodiment of the present application;

[0049] FIG4 is a timing diagram illustrating an example of information reporting according to an embodiment of the present application;

[0050] FIG5 is an example diagram of an event-triggered report according to an embodiment of the present application;

[0051] FIG6 is an example diagram of the relationship between a CSI request and a trigger state according to an embodiment of the present application;

[0052] FIG7 is another example diagram of an event-triggered report according to an embodiment of the present application;

[0053] FIG8 is another example diagram of an event-triggered report according to an embodiment of the present application;

[0054] FIG9 is another example diagram of an event-triggered report according to an embodiment of the present application;

[0055] FIG10 is a schematic diagram of an information reporting method according to an embodiment of the present application;

[0056] FIG11 is an example diagram of the relationship between scheduling request configuration, events, and reports according to an embodiment of the present application;

[0057] FIG12 is an example diagram of the relationship between a CSI request and a trigger state according to an embodiment of the present application;

[0058] FIG13 is an example diagram of an event-triggered report according to an embodiment of the present application;

[0059] FIG14 is another example diagram of an event-triggered report according to an embodiment of the present application;

[0060] FIG15 is a schematic diagram of an information reporting method according to an embodiment of the present application;

[0061] FIG16 is an example diagram of the relationship between scheduling request configuration, events, and reports according to an embodiment of the present application;

[0062] FIG17 is a schematic diagram of an information receiving method according to an embodiment of the present application;

[0063] FIG18 is a schematic diagram of an information reporting device according to an embodiment of the present application;

[0064] FIG19 is a schematic diagram of an information receiving device according to an embodiment of the present application;

[0065] FIG20 is a schematic diagram of a terminal device according to an embodiment of the present application;

[0066] Figure 21 is a schematic diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

[0071] 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 5G, New Radio (NR), future 6G, etc., and / or other currently known or future developed communication protocols.

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

[0073] Among them, base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB) and 5G base station (gNB), IAB host, etc., and may also include remote radio head (RRH, Remote Radio Head), remote radio unit (RRU, Remote Radio Unit), relay (relay) or low-power node (such as femeto, pico, etc.). The term "base station" can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

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

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

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

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

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

[0079] 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 terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0080] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. 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.

[0081] It is worth noting that FIG1 shows that both terminal devices 102 and 103 are within the coverage range of network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 may not be within the coverage range of network device 101, or one terminal device 102 may be within the coverage range of network device 101 while the other terminal device 103 is outside the coverage range of network device 101.

[0082] In the embodiments of the present application, the 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 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.

[0083] In the following description, to avoid confusion, the terms "PDCCH" and "Physical Downlink Control Channel" or "downlink control information" are interchangeable, and the terms "PDSCH" and "Physical Downlink Data Channel" or "downlink data" are also interchangeable. Furthermore, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH; transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH.

[0084] The terms "PUCCH" and "Physical Uplink Control Channel" or "uplink control information" are interchangeable, and the terms "PUSCH" and "Physical Uplink Data Channel" or "uplink data" are also interchangeable. Furthermore, transmitting or receiving PUCCH can be understood as transmitting or receiving downlink control information carried by the PUCCH; transmitting or receiving PUSCH can be understood as transmitting or receiving downlink data carried by the PUSCH.

[0085] The terms "PRACH" and "physical random access channel" or "random access information" are interchangeable. Furthermore, transmitting or receiving PRACH can be understood as transmitting or receiving random access information carried by the PRACH. In the embodiments of this application, the terms "indication," "activation," and "trigger" are interchangeable, or any combination of the two or more.

[0086] In the embodiments of this application, one of the issues that needs to be addressed is how to support event-triggered CSI reporting and event-triggered LTM CSI reporting. More specifically, after an event occurs, the terminal device must send an event-triggered report. This involves addressing the procedures for sending the event-triggered report, the container that carries the event-triggered report, and the content included in the event-triggered report.

[0087] Embodiments of the first aspect

[0088] The embodiment of the present application provides an information reporting method. FIG2 is a schematic diagram of the information reporting method of the embodiment of the present application. As shown in FIG2, the method includes:

[0089] 201. A terminal device receives configuration information for configuring one or more event-triggered reports, where the one or more event-triggered reports are associated with a scheduling request (SR) configuration or a random access channel (RACH) configuration.

[0090] 202. When an event trigger report satisfies a trigger condition, the terminal device sends a scheduling request or a physical random access channel (PRACH);

[0091] 203, the terminal device receives downlink control information (DCI); and

[0092] 204. The terminal device sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

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

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

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

[0096] In some embodiments, the event trigger report further includes at least one of an event index, a number of measurement resource indexes, a number of measurement results, and a measurement resource set index. The present application is not limited thereto, and for example, other information may also be included.

[0097] FIG3 is an example diagram of the relationship between a scheduling request configuration, an event, and a report according to an embodiment of the present application. The “report” in the figure refers to an “event-triggered report.” As shown in FIG3 , for example, a terminal device may be configured with multiple event-triggered reports (e.g., by being configured with multiple event-triggered report configurations), each event-triggered report may be associated with a measurement resource set (e.g., by associating a measurement resource configuration for each event-triggered report configuration), multiple event-triggered reports may be associated with one or more events, and all event-triggered reports may share a scheduling request (SR) configuration.

[0098] When the triggering condition of any event-triggered report (such as report #n1 in Figure 3) is met, the terminal device sends the SR according to the SR configuration (for example, selects a resource from multiple candidate resources that can be used for SR sending to send the SR). Simply put, a dedicated SR is used for event-triggered reporting, and any event-triggered report can trigger the SR.

[0099] For example, all event-triggered reports are associated with the same SR ID (for example, the corresponding RRC IE is represented as Scheduling RequestId), thereby associating the SR configuration corresponding to SchedulingRequestId. The SR configuration includes the necessary information of the SR. The SR configuration may include multiple RRC IEs, such as SchedulingRequestResourceConfig and SchedulingRequestToAddMod (for the detailed definition of the above RRC IE, please refer to the relevant technology of TS 38.331).

[0100] Table 1 shows an example of event-triggered report association. For example, as shown in Table 1, all SRs used in event-triggered reports are configured through schedulingRequestID-Event-Triggered, and schedulingRequestID-Event-Triggered is associated with a SchedulingRequestId.

[0101] Table 1

[0102] Table 2 shows another example of event-triggered report association. For example, as shown in Table 2, each event-triggered report configuration (Event-Triggered-CSI-ReportConfig) is associated with the same SchedulingRequestId.

[0103] Table 2

[0104] Figure 4 is a timing diagram of an example of information reporting in an embodiment of the present application. As shown in Figure 4, after receiving the SR, the network device is able to know that the terminal device has an event trigger report to send, so it sends DCI to schedule PUSCH, so that the terminal device can send the event trigger report via PUSCH. From the perspective of the terminal device, the terminal device receives DCI after sending the SR and sends the event trigger report on the PUSCH scheduled by DCI.

[0105] For example, an event-triggered report may include a measurement resource index, where the measurement resource index is an index defined within the measurement resource set associated with the event-triggered report. In other words, the measurement resource index is an index of a measurement resource within the measurement resource set, for example, the measurement resource index is an SSBRI (SSB Resource Indicator) or a CSI-RS Resource Indicator (CRI).

[0106] For example, the event triggered report may include a measurement result, where the measurement result is at least one of L1-RSRP, L1-SINR, filtered RSRP, and filtered SINR.

[0107] For example, an event-triggered report may include a report index (e.g., report #n1 in FIG3 ). Since multiple event-triggered reports share the same SR configuration, the network device cannot know which event-triggered report the terminal device wants to send after receiving the SR, so the terminal device can notify the network device of this information by reporting the report index. In addition, since the measurement resource index can be an index defined within a certain measurement resource set (for example, the measurement resource index is SSBRI or CRI), by reporting the report index, the network device can know which event-triggered report the terminal device sent, and then know the measurement resource set associated with the event-triggered report, so as to correctly interpret the measurement resource index.

[0108] For example, the event-triggered report may include a measurement resource set index (e.g., measurement resource set #s1 in FIG3 ). Since the measurement resource index may be an index defined within a certain measurement resource set (e.g., the measurement resource index is an SSBRI or CRI), by reporting the measurement resource set index, the network device may correctly interpret the measurement resource index.

[0109] For example, the number of measurement results is equal to the number of measurement resource indices, both being equal to M (with a one-to-one mapping relationship between them), and the event-triggered report may include M. For example, when M is determined by the terminal device itself, the event-triggered report includes M. Since M is determined by the terminal device and the network device does not know the value of M, it is impossible to correctly decode the encoded information including M measurement results and M measurement resource indices. Therefore, the terminal device is made to report M. The network device can first obtain the value of M through one demodulation and decoding, and on the basis of knowing M, then obtain the specific information of M measurement results and M measurement resource indices through another demodulation and decoding.

[0110] For example, multiple types of events are defined for the event-triggered report. The event-triggered report may include an event index (such as event #e0 in Figure 3), and the event type is notified to the network device. For example, in Figure 3, event #e0 includes that the terminal device discovers a new beam whose RSRP is higher than that of the currently used beam by a certain value, and event #e1 includes that the terminal device discovers a new beam whose RSRP is higher than that of the currently used beam by a certain value, and the RSRP of the currently used beam is less than a certain threshold.

[0111] Figure 5 is an example diagram of the event-triggered report in an embodiment of the present application. For example, as shown in Figure 5, the event-triggered report includes a report index (report ID in the figure), M measurement resource indices, and M measurement results, and the mapping order may be as shown in Figure 5. Differential reporting may be used for the measurement results. For example, measurement result #1 (absolute value) is quantized using N1 bits, and other measurement results (differential values) are quantized in a differential manner using N2 (N2 < N1) bits. More details of differential reporting can be found in the related art.

[0112] In some embodiments, the event-triggered report is sent on the PUSCH or the PUCCH through uplink control information (UCI), or the event-triggered report is sent on the PUSCH through MAC-CE.

[0113] For example, the event-triggered report is sent on the PUSCH as UCI. The terminal device can use existing UCI multiplexing methods to send the UCI through the PUSCH. The PUSCH may carry the UL-SCH (for example, in the case where the UL-SCH indicator field in the corresponding DCI indicates "1"), or may not carry the UL-SCH (for example, in the case where the UL-SCH indicator field in the corresponding DCI indicates "0"). More details of UCI multiplexing can be found in the related art.

[0114] In some embodiments, the report index is an event-triggered report configuration number, or the report index is a number corresponding to one or more event-triggered reports of the configuration.

[0115] For example, the report index is an event-triggered report configuration number (ID). The terminal device is configured with multiple event-triggered report configurations, and thus is configured with multiple event-triggered reports. The event-triggered report configuration number can uniquely identify an event-triggered report. Therefore, the report index can be the event-triggered report configuration number. For example, the event-triggered report configuration number can reuse an existing report configuration number (CSI-ReportConfigId), or can be a newly defined report configuration number (such as Event-Triggered-CSI-ReportConfigId). For example, if the value range of the event-triggered report configuration number is [0, X-1], the number of bits (bit width) required for the report index is

[0116] For example, the report index is a number within one or more configured event-triggered reports. Although the value range of the event-triggered report configuration number is [0, X-1] (that is, at most X event-triggered reports are configured), if the terminal device is only configured with Y (Y < X) event-triggered reports (that is, only Y event-triggered report configuration numbers are actually configured for the terminal device), the number of bits required for the report index is rather than the report index is a number within the Y event-triggered reports.

[0117] Similarly, the measurement resource set index is a measurement resource set configuration number, or the measurement resource set index is a number corresponding to one or more configured measurement resource sets.

[0118] In some embodiments, the terminal device determines to send the event-triggered report according to at least one of the fields included in the downlink control information (DCI), the format of the downlink control information (DCI), and the information indicated by the downlink control information (DCI).

[0119] For example, the DCI in the existing standard can schedule PUSCH transmission, or can trigger an aperiodic CSI report, or can trigger an aperiodic LTM CSI report. The DCI in the embodiments of the present application can trigger or schedule an event-triggered report. The terminal device needs to distinguish in some way which of the above purposes the DCI is used for.

[0120] For example, when the value of one or more fields of the DCI is a predefined special value, it indicates that the DCI is used for scheduling event triggering reporting; otherwise, the DCI is not used for scheduling event triggering reporting. At this time, the terminal device determines that the DCI is used for scheduling PUSCH transmission, or triggering non-periodic CSI reporting, or triggering non-periodic LTM CSI reporting according to the existing standard method; one or more fields may be existing fields and / or newly defined fields. For example, DCI format Z1 indicates that the DCI is used for scheduling event triggering reporting, and DCI format Z2 indicates that the DCI is not used for scheduling event triggering reporting. For example, DCI indicates one piece of information among multiple pieces of information configured in RRC signaling. When the DCI indicates the first information, it indicates that the DCI is used for scheduling event triggering reporting. When the DCI indicates the second information, it indicates that the DCI is not used for scheduling event triggering reporting.

[0121] In some embodiments, the CSI request (CSI request) field of the downlink control information (DCI) indicates a trigger status dedicated to an event-triggered report, and the terminal device determines to send the event-triggered report according to the trigger status.

[0122] Figure 6 is an example diagram of the relationship between the CSI request and the trigger state in an embodiment of the present application. For example, as shown in Figure 6, the terminal device is configured with one or more trigger states (CSI-AperiodicTriggerState), one of which (trigger state #i4) is used to trigger an event-triggered report (trigger state #i4 is marked as "event triggered"). When the CSI request field of the DCI indicates this trigger state, the terminal device sends an event-triggered report on the PUSCH scheduled by the DCI.

[0123] Optionally, the terminal device may also be configured with a trigger state for triggering a non-periodic CSI report (trigger state #i0, trigger state #i1), and / or a trigger state for triggering a non-periodic LTM CSI report (trigger state #i2, trigger state #i3). Different codepoints of the CSI request field correspond to different trigger states. Therefore, the CSI request field can trigger a non-periodic CSI report, a non-periodic LTM CSI report, or an event-triggered report. The terminal device may determine which type of report is triggered by the CSI request field based on the RRC IE associated with the trigger state.

[0124] Table 3 shows an example of RRC IE, showing the triggering status for triggering aperiodic CSI reporting.

[0125] Table 3

[0126] Table 4 shows another example of RRC IE, showing the triggering status for triggering aperiodic LTM CSI reporting.

[0127] Table 4

[0128] Table 5 shows another example of RRC IE, showing the triggering status for triggering event triggering reporting.

[0129] Table 5

[0130] For example, Table 5 shows the trigger state dedicated to event-triggered reporting, and the sub-RRC IE Event-triggered marks it as dedicated to event-triggered reporting. The CSI request field indicates a CSI-AperiodicTriggerState. Since the sub-RRC IEs of different types of CSI-AperiodicTriggerState are different, the terminal device can determine whether the CSI request field triggers an aperiodic CSI report, an aperiodic LTM CSI report, or an event-triggered report based on the sub-RRC IE of CSI-AperiodicTriggerState.

[0131] Therefore, DCI can flexibly indicate which type of report to trigger. Since the CSI request field of DCI is reused, DCI can trigger both traditional reports and event-triggered reports without increasing any DCI overhead.

[0132] In some embodiments, different event-triggered reports include the same number of measurement resource indexes or measurement results.

[0133] For example, each event-triggered report includes M measurement resource indexes and M measurement results. The same M value facilitates demodulation and decoding by network devices. For example, when an event-triggered report is used as an UCI, the UCI sizes of different event-triggered reports are the same, and network devices can demodulate and decode the UCI in a unified manner. When an event-triggered report is used as an UCI, the event-triggered report can use the report format shown in Figure 5. For example, the "number of measurement resource indexes or the number of measurement results" can be replaced with the "bit width of the measurement resource index."

[0134] In some embodiments, the number of measurement resource indexes or the number of measurement results is configured in units of terminal devices, or the number of measurement resource indexes or the number of measurement results is predefined.

[0135] For example, each event-triggered report includes M measurement resource indexes and M measurement results, where M is configured per UE or predefined. Therefore, when an event-triggered report is used as UCI, the network device knows the size of the UCI in advance and can therefore demodulate and decode the UCI. For example, the "number of measurement resource indexes or number of measurement results" can be replaced with the "bit width of the measurement resource index."

[0136] In some embodiments, the number of measurement resource indexes or the number of measurement results included in reports triggered by different events are independent.

[0137] For example, an event-triggered report includes M measurement resource indices and M measurement results, and the M values ​​for different event-triggered reports are independent. In other words, the M values ​​for different event-triggered reports may be the same or different. Independent M values ​​facilitate more flexible event-triggered reporting. For example, the number of preferred measurement results included in different event-triggered reports may not necessarily be the same. For example, "the number of measurement resource indices or the number of measurement results" can be replaced with "the bit width of the measurement resource index."

[0138] In some embodiments, the number of measurement resource indexes or the number of measurement results is configured in units of event-triggered reports or is determined by the terminal device.

[0139] For example, an event-triggered report includes M measurement resource indexes and M measurement results, where M is configured per event-triggered report. For example, M is configured in the event-triggered report configuration. For example, "the number of measurement resource indexes or the number of measurement results" can be replaced with "the bit width of the measurement resource index."

[0140] In some embodiments, the event-triggered report includes a first CSI part (CSI part 1) and a second CSI part (CSI part 2); the first CSI part (CSI part 1) includes at least one of a report index, a first group of measurement resource indexes, and a first group of measurement results, and the second CSI part (CSI part 2) includes at least one of a second group of measurement resource indexes and a second group of measurement results.

[0141] In some embodiments, the event-triggered report includes a first CSI part (CSI part 1) and a second CSI part (CSI part 2); the first CSI part (CSI part 1) includes a report index, and the second CSI part (CSI part 2) includes at least one of a measurement resource index and a measurement result.

[0142] FIG7 is another example diagram of an event-triggered report according to an embodiment of the present application. For example, as shown in FIG7 , an event-triggered report is used as UCI. The event-triggered report includes a report index, M measurement resource indexes, and M measurement results. The report index is included in CSI part 1, and the M measurement resource indexes and M measurement results are included in CSI part 2. M is configured in the event-triggered report configuration or is configured per terminal device.

[0143] The UCI size (the number of bits included in the UCI) depends on the number of fields included in the UCI and the number of bits in each field. The UCI size of different event-triggered reports may be different. Although the quantization method and the number of quantization bits of the measurement results may be the same for different event-triggered reports, the value of M and / or the bit width of the resource index may be different for different event-triggered reports. M affects the number of fields included in the UCI, and the bit width of the resource index affects the number of bits of the field, so both will affect the size of the UCI. Since M, which affects the size of the UCI, is independently configured for each event-triggered report, and the network device cannot know which event-triggered report is sent based on the SR, the network device cannot know the size of the UCI in advance, and thus cannot demodulate and decode the UCI as a whole. In addition, the bit width of the measurement resource index will also affect the size of the UCI. The bit width of the measurement resource index in different event-triggered reports may be different (for example, the bit width of the measurement resource index is K is the number of measurement resources included in the measurement resource set. The K value of the measurement resource set associated with different event-triggered reports may be different. Therefore, the bit width of the measurement resource index in different event-triggered reports is different), resulting in different UCI sizes for different event-triggered reports. Since the network device cannot know which event trigger report is sent based on the SR, the network device cannot know the bit width of the measurement resource index in advance, and therefore cannot know the size of the UCI.

[0144] The above problem can be solved by dividing the UCI into two parts, CSI Part 1 and CSI Part 2. As CSI Part 1 and CSI Part 2 that constitute the UCI, the size of CSI Part 1 is fixed (known in advance by the network device), and the size of CSI Part 2 is variable (unknown in advance by the network device). For example, the number of bits used to indicate the report index is fixed (e.g., configured or predefined by the network device, such as the one mentioned above). or The network device can first demodulate and decode CSI part 1 to obtain the report index, and then obtain the corresponding event-triggered report configuration through the report index. All configuration information can be obtained through the event-triggered report configuration, so the M value (obtained from the configuration information) and the measurement resource index bit width (the K value can be obtained from the configuration information, and then the bit width can be obtained) can be known. Based on the M value and the measurement resource index bit width, the network device can determine the size of CSI Part 2 and thus demodulate and decode CSI Part 2. Based on the event-triggered report configuration, the network device can correctly interpret the measurement resource index. At this point, the network device has completed demodulation and decoding of the event-triggered report.

[0145] FIG8 is another example diagram of an event-triggered report according to an embodiment of the present application. For example, FIG8 differs from FIG7 in that the report index, M1 (M1 ≤ M) measurement resource indices, and M1 measurement results are included in CSI part 1, while M-M1 measurement resource indices and M–M1 measurement results are included in CSI part 2. M1 is a fixed value; FIG8 assumes that M1 = 1.

[0146] CSI Part 2 has a lower priority or importance than CSI Part 1. Considering that CSI Part 2 may be discarded (i.e., not transmitted) in some cases due to its lower priority, a fixed number of measurement resource indices and measurement results are included in CSI Part 1. For example, the best measurement results and their corresponding measurement resource indices are included in CSI Part 1. This allows network devices to obtain relatively important measurement results and measurement resource indices through CSI Part 1 even if CSI Part 2 is discarded.

[0147] In some embodiments, the number of the first group of measurement resource indexes or the number of the first group of measurement results is configured in units of terminal devices, or the number of the first group of measurement resource indexes or the number of the first group of measurement results is predefined.

[0148] For example, as shown in Figure 8, M1 measurement resource indexes and M1 measurement results are included in CSI Part 1. M1 is the same for reports triggered by different events. For example, the value of M1 is configured or predefined by the network device. Thus, the network device knows the size of CSI Part 1 in advance and is able to demodulate and decode it. For example, M1 is configured per terminal device, or M1 is predefined as 1. For example, the terminal device includes the M1 best measurement results and their corresponding measurement resource indexes in CSI Part 1.

[0149] In some embodiments, the CSI part 1 further includes the number of measurement resource indexes and / or the number of measurement results.

[0150] Figure 9 is another example diagram of an event-triggered report according to an embodiment of the present application. For example, as shown in Figure 9, unlike Figure 7, M is included in CSI Part 1 and determined independently by the terminal device. Because the terminal device determines M independently and M affects the size of the UCI, the network device cannot know the UCI size in advance, nor can it obtain M from the report index. This problem can be resolved by including M in CSI Part 1.

[0151] For example, the number of bits used to indicate M is fixed (configured or predefined by the network device). The network device first demodulates and decodes CSI part 1 to obtain M. Based on the value of M, the network device can obtain the size of CSI part 2 and thus demodulate and decode CSI part 2.

[0152] In some embodiments, when the event-triggered report is sent and / or the event-triggered report is cancelled, the scheduling request is cancelled and / or a timer (sr-ProhibitTimer) associated with the scheduling request is stopped.

[0153] For example, if an SR is triggered by an event-triggered report, the terminal device cancels the SR if certain conditions are met. In addition, if the sr-ProhibitTimer associated with the SR is running, the terminal device stops the sr-ProhibitTimer. During the sr-ProhibitTimer running, the terminal device does not send the associated SR.

[0154] For example, the satisfied conditions may include that the event-triggered report is sent, and / or that the event-triggered report is cancelled. After the event-triggered report is sent, the terminal device no longer sends the SR; or, if the sending of the event-triggered report is cancelled, the terminal device no longer sends the SR.

[0155] In some embodiments, the event-triggered report is an event-triggered CSI report, or the event-triggered report is an event-triggered LTM CSI report.

[0156] For example, the event-triggered report may be an event-triggered CSI report for non-cell handover purposes; or, the event-triggered report may be an event-triggered LTM CSI report for cell handover purposes.

[0157] As can be seen from the above embodiment, after an event occurs, the terminal device sends an SR (or PRACH), then receives DCI, and sends an event trigger report on the PUSCH or PUCCH scheduled by the DCI. Multiple event trigger reports are associated with one SR (or RACH) configuration, and the DCI instructs the terminal device to send an event trigger report. The event trigger report includes at least one of a report index, a measurement resource index, a measurement result, the number of measurement resource indexes, the number of measurement results, and a measurement resource set index.

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

[0159] Through the embodiments of the present application, the terminal device can quickly send an event trigger report after an event occurs, thereby improving the timeliness of the report and reducing the reporting overhead.

[0160] Embodiments of the second aspect

[0161] The embodiment of the present application provides an information reporting method, and the contents identical to those in the embodiment of the first aspect are omitted for description. FIG10 is a schematic diagram of the information reporting method of the embodiment of the present application, as shown in FIG10 , the method includes:

[0162] 1001. A terminal device receives configuration information for configuring one or more event-triggered reports and / or one or more trigger states, wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration.

[0163] 1002. When an event-triggered report satisfies a triggering condition, the terminal device sends a scheduling request or a PRACH according to a scheduling request configuration or a RACH configuration associated with the event-triggered report.

[0164] 1003, the terminal device receives downlink control information (DCI); and

[0165] 1004. The terminal device sends the event triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event triggered report includes at least one of a measurement resource index and a measurement result.

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

[0167] In some embodiments, the event trigger report further includes at least one of an event index, a number of measurement resource indexes, a number of measurement results, and a measurement resource set index. The present application is not limited thereto, and for example, other information may also be included.

[0168] Figure 11 is an example diagram of the relationship between the scheduling request configuration, events and reports of an embodiment of the present application. As shown in Figure 11, for example, the terminal device is configured with multiple event-triggered reports, and each event-triggered report is associated with an SR configuration. When the triggering condition of an event-triggered report (such as report #n1 in Figure 11) is met, the terminal device sends an SR according to the SR configuration associated with the event-triggered report (SR configuration #d1 in Figure 11). Since there is a one-to-one mapping relationship between SR and event-triggered report, the network device can know which event-triggered report the terminal device wants to send based on the received SR. For example, by configuring the SR configuration in units of event-triggered reports, the above-mentioned association relationship can be achieved, for example, different event-triggered report configurations (Event-Triggered-CSI-ReportConfig) in Table 2 are associated with different SchedulingRequestId. For example, "SR configuration" can be replaced with "SR resource", so that each event-triggered report is associated with an SR resource, and the SR resource can include at least one of time domain resources, frequency domain resources, sequence, and cyclic prefix.

[0169] Figure 12 illustrates an example of the relationship between CSI requests and trigger states in an embodiment of the present application. For example, as shown in Figure 12 , a terminal device is configured with one or more trigger states, each of which is associated with a report. The report can be an aperiodic CSI report, an aperiodic LTM CSI report, or an event-triggered report. Each event-triggered report associated with a trigger state is associated with an SR configuration.

[0170] For example, if the terminal device is configured to trigger P reports for events, but only P1 (P1 < P) of these event-triggered reports are associated with the trigger status, then only P1 event-triggered reports are associated with the SR configuration. This is because only the event-triggered reports associated with the trigger status can be triggered by DCI for transmission. Therefore, only P1 SR configurations are required instead of P SR configurations. Since one SR configuration corresponds to a set of reserved SR resources, the SR resource overhead can be reduced. For example, "SR configuration" can be replaced with "SR resource", so that each event-triggered report is associated with one SR resource, and the SR resource can include at least one of time-domain resources, frequency-domain resources, sequences, and cyclic prefixes.

[0171] Table 6 shows an example of an RRC IE, showing the trigger status associated with the aperiodic CSI report. The trigger status can be associated with the event-triggered report in the manner shown in Table 6, that is, the event-triggered report configuration number uses a newly defined report configuration number.

[0172] Table 6

[0173] Table 7 shows another example of an RRC IE, showing the trigger status associated with the aperiodic LTM CSI report. The trigger status can be associated with the event-triggered report in the manner of Table 7, that is, the event-triggered report configuration number reuses the existing report configuration number.

[0174] Table 7

[0175] FIG. 13 is an example diagram of an event-triggered report according to an embodiment of the present application. For example, since the network device can determine which event-triggered report the terminal device wants to send based on the received SR, the report index may not be included in the event-triggered report. As shown in FIG. 13, the event-triggered report includes a measurement resource index and a measurement result, and does not include a report index. For the event-triggered report format (i.e., the content included in the event-triggered report), except for the report index, other contents can refer to the aforementioned event-triggered report format.

[0176] In some embodiments, the event-triggered report is sent on the PUSCH or the PUCCH through uplink control information (UCI), or the event-triggered report is sent on the PUSCH through a MAC-CE.

[0177] For example, the event-triggered report is sent as UCI on PUSCH, and the terminal device can use the existing UCI multiplexing method to send UCI through PUSCH. PUSCH can carry UL-SCH (for example, corresponding to the case where the UL-SCH indicator field in DCI indicates "1"), or not carry UL-SCH (for example, corresponding to the case where the UL-SCH indicator field in DCI indicates "0").

[0178] In some embodiments, the terminal device determines to send the event trigger report based on at least one of the fields included in the downlink control information (DCI), the format of the downlink control information (DCI), and the information indicated by the downlink control information (DCI).

[0179] For example, after receiving DCI, the terminal device needs to determine whether the DCI triggers an event trigger report and which event trigger report is triggered. The terminal device can make this judgment based on at least one of the fields included in the DCI, the DCI format, and the information indicated by the DCI. For example, a field in the DCI indicates that a specific event trigger report is triggered. For example, the DCI indicates one piece of information among multiple pieces of information configured in the RRC signaling, and the information indicates that a specific event trigger report is triggered.

[0180] In some embodiments, the CSI request (CSI request) field of the downlink control information (DCI) indicates a trigger state associated with an event triggered report, and the terminal device determines to send the event triggered report associated with the trigger state according to the trigger state.

[0181] For example, as shown in Figure 12, the CSI request field of the DCI indicates a trigger state (CSI-Aperiodic TriggerState), and a trigger state can be associated with an aperiodic CSI report, an aperiodic LTM CSI report, or an event-triggered report. Since the trigger state is associated with the report configuration number, the terminal device can determine whether the DCI triggers an event-triggered report and which event-triggered report is triggered based on the trigger state indicated by the CSI request field. Since the CSI request field of the DCI is reused, the DCI can trigger both traditional reports and event-triggered reports.

[0182] For example, a terminal device is configured with one or more event-triggered event-specific trigger states (Event-CSI-TriggerState, referred to as event trigger states). An event trigger state can only be associated with an event trigger report. If a DCI field indicates an event trigger state, the terminal device sends an event trigger report associated with the event trigger state. In this case, the DCI field triggers one of the multiple event trigger reports.

[0183] In some embodiments, different event-triggered reports include the same number of measurement resource indexes or measurement results.

[0184] For example, each event-triggered report includes M measurement resource indexes and M measurement results. A consistent M value facilitates demodulation and decoding by network devices. For example, when event-triggered reports are used as UCI, the UCI size of different event-triggered reports is the same, allowing network devices to demodulate and decode the UCI in a unified manner. When event-triggered reports are used as UCI, the report format shown in Figure 13 can be used.

[0185] In some embodiments, the number of measurement resource indexes or the number of measurement results is configured in units of terminal devices, or the number of measurement resource indexes or the number of measurement results is predefined.

[0186] For example, each event-triggered report includes M measurement resource indices and M measurement results, where M is configured per UE or predefined. Therefore, when an event-triggered report is used as UCI, the network device knows the size of the UCI in advance and can therefore demodulate and decode the UCI.

[0187] In some embodiments, the number of measurement resource indexes or the number of measurement results included in reports triggered by different events are independent.

[0188] For example, an event-triggered report includes M measurement resource indices and M measurement results. The M values ​​for different event-triggered reports are independent. In other words, the M values ​​for different event-triggered reports may be the same or different. Independent M values ​​facilitate more flexible event-triggered reporting. For example, different event-triggered reports may not necessarily include the same number of preferred measurement results.

[0189] In some embodiments, the number of measurement resource indexes or the number of measurement results is configured in units of event-triggered reports or is determined by the terminal device.

[0190] For example, an event-triggered report includes M measurement resource indexes and M measurement results, where M is configured per event-triggered report. For example, M is configured in the event-triggered report configuration.

[0191] In some embodiments, the event-triggered report includes a first CSI part (CSI part 1) and a second CSI part (CSI part 2); the first CSI part (CSI part 1) includes the number of measurement resource indexes or the number of measurement results, and the second CSI part (CSI part 2) includes at least one of the measurement resource index and the measurement result.

[0192] Figure 14 is another example diagram of an event-triggered report according to an embodiment of the present application. For example, as shown in Figure 14 , the event-triggered report is used as UCI, with the M value included in CSI part 1, M measurement resource indexes, and M measurement results included in CSI part 2, where M is determined by the terminal device. The event-triggered report does not include a report index.

[0193] In some embodiments, when the event-triggered report is sent and / or the event-triggered report is cancelled, the scheduling request is cancelled and / or a timer (sr-ProhibitTimer) associated with the scheduling request is stopped.

[0194] For example, if an SR is triggered by an event-triggered report, the terminal device cancels the SR if certain conditions are met. In addition, if the sr-ProhibitTimer associated with the SR is running, the terminal device stops the sr-ProhibitTimer. During the sr-ProhibitTimer running, the terminal device does not send the associated SR.

[0195] For example, the satisfied conditions may include that the event-triggered report is sent, and / or that the event-triggered report is cancelled. After the event-triggered report is sent, the terminal device no longer sends the SR; or, if the sending of the event-triggered report is cancelled, the terminal device no longer sends the SR.

[0196] In some embodiments, the event-triggered report is an event-triggered CSI report, or the event-triggered report is an event-triggered LTM CSI report.

[0197] For example, the event-triggered report may be an event-triggered CSI report for non-cell handover purposes; or, the event-triggered report may be an event-triggered LTM CSI report for cell handover purposes.

[0198] As can be seen from the above embodiment, after an event occurs, the terminal device sends an SR (or PRACH), then receives DCI, and sends an event trigger report on the PUSCH or PUCCH scheduled by the DCI. Multiple event trigger reports are associated with multiple SR (or RACH) configurations, and the DCI instructs the terminal device which event trigger report to send. The event trigger report includes at least one of a measurement resource index, a measurement result, the number of measurement resource indices, the number of measurement results, and a measurement resource set index.

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

[0200] Through the embodiments of the present application, the terminal device can quickly send an event trigger report after an event occurs, thereby improving the timeliness of the report and reducing the reporting overhead.

[0201] Embodiments of the third aspect

[0202] The embodiment of the present application provides an information reporting method, and the contents identical to those of the first and second aspects are omitted for explanation. FIG15 is a schematic diagram of the information reporting method of the embodiment of the present application, as shown in FIG15 , the method includes:

[0203] 1501. A terminal device receives configuration information for configuring one or more event-triggered reports, wherein a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration.

[0204] 1502. When an event-triggered report satisfies a triggering condition, the terminal device sends a scheduling request or a PRACH according to a scheduling request configuration or a RACH configuration associated with the event-triggered report.

[0205] 1503, the terminal device receives downlink control information (DCI); and

[0206] 1504. The terminal device sends the event triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

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

[0208] In some embodiments, the event trigger report further includes at least one of an event index, a number of measurement resource indexes, a number of measurement results, and a measurement resource set index. The present application is not limited thereto, and for example, other information may also be included.

[0209] Figure 16 illustrates an example of the relationship between scheduling request configurations, events, and reports in an embodiment of the present application. As shown in Figure 16 , for example, event-triggered reports #n0 and #n1 are associated with SR configuration #f0, while event-triggered reports #n2 and #n3 are associated with SR configuration #f1. This reduces SR resource overhead. Because multiple event-triggered reports share a single SR configuration, a network device cannot determine which event-triggered report should be triggered based on a received SR. Therefore, event-triggered reports must include a report index.

[0210] For example, within the scope of multiple event-triggered reports associated with SR configuration #f0 in Figure 16, the terminal device can reuse the embodiment of the first aspect. This is because the upper half of Figure 16 also shows a situation where multiple event-triggered reports share the same SR configuration, so the embodiment of the first aspect can be reused, which will not be further described.

[0211] In some embodiments, the report index is an index within the first number of event-triggered reports, or the report index is an index within the second number of event-triggered reports.

[0212] For example, as shown in Figure 16, after receiving an SR, the network device only needs to further distinguish each event-triggered report within the multiple event-triggered report ranges associated with the SR. Therefore, the report index can be an index within the multiple event-triggered report ranges associated with the SR. The number of bits (bit width) used to indicate the report index is fixed. If the bit widths of the report indexes determined based on different SRs are different, the maximum bit width can be used as the bit width of the report index.

[0213] In some embodiments, the first number of event-triggered reports are associated with a first event, and the second number of event-triggered reports are associated with a second event.

[0214] For example, as shown in Figure 16, event-triggered reports #n0 and #n1 are associated with event #e0 and SR configuration #f0, while event-triggered reports #n2 and #n3 are associated with event #e1 and SR configuration #f1. Therefore, SR configuration #f0 is associated with event #e0, and SR configuration #f1 is associated with event #e0. This association can be achieved by configuring SR configurations on an event-by-event basis.

[0215] As can be seen from the above embodiment, after an event occurs, the terminal device sends an SR (or PRACH), then receives DCI, and sends an event trigger report on the PUSCH or PUCCH scheduled by the DCI. Multiple event trigger reports are associated with one or more SR (or RACH) configurations, and the DCI instructs the terminal device to send an event trigger report. The event trigger report includes at least one of a report index, a measurement resource index, a measurement result, the number of measurement resource indexes, the number of measurement results, and a measurement resource set index.

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

[0217] Through the embodiments of the present application, the terminal device can quickly send an event trigger report after an event occurs, thereby improving the timeliness of the report and reducing the reporting overhead.

[0218] Embodiments of the fourth aspect

[0219] The embodiment of the present application provides an information receiving method, which is described from the perspective of a network device. The embodiment of the fourth aspect can be combined with the embodiments of the first to third aspects, and the same contents as the embodiments of the first to third aspects will not be repeated.

[0220] FIG17 is a schematic diagram of an information receiving method according to an embodiment of the present application. As shown in FIG17 , the method includes:

[0221] 1701, the network device sends configuration information for configuring one or more event trigger reports;

[0222] 1702, the network device receives a scheduling request or a PRACH;

[0223] 1703, the network device sends downlink control information (DCI); and

[0224] 1704. The network device receives an event triggered report sent on the PUSCH or PUCCH indicated by the downlink control information (DCI).

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

[0226] In some embodiments, the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; the terminal device sends a scheduling request or PRACH when an event-triggered report meets the triggering condition; wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0227] In some embodiments, each event triggered report is associated with a scheduling request configuration or a RACH configuration, and / or, each event triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration; when an event triggered report meets the triggering condition, the terminal device sends a scheduling request or PRACH according to the scheduling request configuration or RACH configuration associated with the event triggered report; wherein the event triggered report includes at least one of a measurement resource index and a measurement result.

[0228] In some embodiments, a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration; when an event-triggered report meets a triggering condition, the terminal device sends a scheduling request or PRACH according to the scheduling request configuration or the RACH configuration associated with the event-triggered report; wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

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

[0230] Through the embodiments of the present application, the terminal device can quickly send an event trigger report after an event occurs, thereby improving the timeliness of the report and reducing the reporting overhead.

[0231] Embodiments of the fifth aspect

[0232] The embodiment of the present application provides an information reporting device, which may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device, and the same contents as those in the first to third aspects of the embodiment will not be repeated.

[0233] FIG18 is a schematic diagram of an information reporting device according to an embodiment of the present application. As shown in FIG18 , the information reporting device 1800 includes: a receiving unit 1801 and a sending unit 1802

[0234] In some embodiments, the receiving unit 1801 receives configuration information for configuring one or more event-triggered reports, and the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; and the sending unit 1802 sends a scheduling request or PRACH when an event-triggered report meets a triggering condition; the receiving unit 1802 also receives downlink control information (DCI); and the sending unit 1802 also sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0235] In some embodiments, the event-triggered report further includes at least one of an event index, a number of measurement resource indexes, a number of measurement results, and a measurement resource set index.

[0236] In some embodiments, the event-triggered report is sent on the PUSCH or the PUCCH via uplink control information (UCI), or the event-triggered report is sent on the PUSCH via MAC-CE.

[0237] In some embodiments, the report index is an event-triggered report configuration number, or the report index is a number corresponding to one or more configured event-triggered reports.

[0238] In some embodiments, as shown in FIG18 , the apparatus further comprises:

[0239] The processing unit 1803 determines to send the event trigger report according to at least one of the fields included in the downlink control information (DCI), the format of the downlink control information (DCI), and the information indicated by the downlink control information (DCI).

[0240] In some embodiments, a CSI request (CSI request) field of the downlink control information (DCI) indicates a triggering status dedicated to an event-triggered report, and the processing unit determines to send the event-triggered report according to the triggering status.

[0241] In some embodiments, different event-triggered reports include the same number of measurement resource indexes or measurement results.

[0242] In some embodiments, the number of measurement resource indexes or the number of measurement results is configured in units of terminal devices, or the number of measurement resource indexes or the number of measurement results is predefined.

[0243] In some embodiments, the number of measurement resource indexes or the number of measurement results included in reports triggered by different events are independent.

[0244] In some embodiments, the number of measurement resource indexes or the number of measurement results is configured in units of event-triggered reports or is determined by the terminal device.

[0245] In some embodiments, the event-triggered report includes a CSI part 1 and a CSI part 2;

[0246] The CSI first part (CSI part 1) includes at least one of a report index, a first set of measurement resource indexes, and a first set of measurement results, and the CSI second part (CSI part 2) includes at least one of a second set of measurement resource indexes and a second set of measurement results.

[0247] In some embodiments, the number of the first group of measurement resource indexes or the number of the first group of measurement results is configured in units of terminal devices, or the number of the first group of measurement resource indexes or the number of the first group of measurement results is predefined.

[0248] In some embodiments, the CSI part 1 further includes the number of measurement resource indexes and / or the number of measurement results.

[0249] In some embodiments, when the event-triggered report is sent and / or the event-triggered report is cancelled, the scheduling request is cancelled and / or a timer (sr-ProhibitTimer) associated with the scheduling request is stopped.

[0250] In some embodiments, the event-triggered report is an event-triggered CSI report, or the event-triggered report is an event-triggered LTM CSI report.

[0251] In some embodiments, the receiving unit 1801 receives configuration information for configuring one or more event-triggered reports and / or one or more trigger states; wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or, each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration; the sending unit 1802 sends a scheduling request or a PRACH according to the scheduling request configuration or the RACH configuration associated with the event-triggered report when an event-triggered report meets a trigger condition; the receiving unit 1801 also receives downlink control information (DCI); and the sending unit 1802 also sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

[0252] In some embodiments, the receiving unit 1801 receives configuration information for configuring one or more event-triggered reports; wherein, a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration; the sending unit 1802 sends a scheduling request or a PRACH according to the scheduling request configuration or the RACH configuration associated with the event-triggered report when an event-triggered report meets a triggering condition; the receiving unit 1801 also receives downlink control information (DCI); and the sending unit 1802 also sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0253] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The information reporting device 1800 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

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

[0255] Through the embodiments of the present application, the terminal device can quickly send an event trigger report after an event occurs, thereby improving the timeliness of the report and reducing the reporting overhead.

[0256] Embodiments of the sixth aspect

[0257] The embodiment of the present application provides an information receiving device, which may be, for example, a network device, or one or more components or assemblies configured in the network device, and the contents that are the same as those in the first to fourth aspects of the embodiment are not repeated here.

[0258] FIG19 is a schematic diagram of an information receiving device according to an embodiment of the present application. As shown in FIG19 , the information receiving device 1900 includes a sending unit 1901 and a receiving unit 1902 .

[0259] In some embodiments, the sending unit 1901 sends configuration information for configuring one or more event-triggered reports, and the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; and the receiving unit 1902 receives a scheduling request or a PRACH; the sending unit 1901 also sends downlink control information (DCI); and the receiving unit 1902 also receives the event-triggered report sent on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0260] In some embodiments, the sending unit 1901 sends configuration information for configuring one or more event-triggered reports and / or one or more trigger states; wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or, each trigger state-associated event-triggered report is associated with a scheduling request configuration or a RACH configuration; the receiving unit 1902 receives a scheduling request or a PRACH; the sending unit 1901 also sends downlink control information (DCI); and the receiving unit 1902 also receives the event-triggered report sent on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

[0261] In some embodiments, the sending unit 1901 sends configuration information for configuring one or more event-triggered reports; wherein, a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration; the receiving unit 1902 receives a scheduling request or a PRACH; the sending unit 1901 also sends downlink control information (DCI); and the receiving unit 1902 also receives the event-triggered report sent on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0262] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The information receiving device 1900 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

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

[0264] Through the embodiments of the present application, the terminal device can quickly send an event trigger report after an event occurs, thereby improving the timeliness of the report and reducing the reporting overhead.

[0265] Embodiments of the seventh aspect

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

[0267] In some embodiments, the communication system 100 may include at least:

[0268] A terminal device, receiving configuration information for configuring one or more event-triggered reports, the one or more event-triggered reports being associated with a scheduling request configuration or a RACH configuration; and sending a scheduling request or a PRACH when an event-triggered report meets a triggering condition; receiving downlink control information (DCI); and sending the event-triggered report on a PUSCH or a PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result;

[0269] A network device sends configuration information for configuring one or more event-triggered reports; receives a scheduling request or a PRACH; sends downlink control information (DCI); and receives the event-triggered report.

[0270] In some embodiments, the communication system 100 may include at least:

[0271] A terminal device, comprising: receiving configuration information for configuring one or more event-triggered reports and / or one or more trigger states; wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration; sending a scheduling request or a PRACH according to the scheduling request configuration or the RACH configuration associated with the event-triggered report when an event-triggered report meets a triggering condition; receiving downlink control information (DCI); and sending the event-triggered report on a PUSCH or a PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result;

[0272] A network device sends configuration information for configuring one or more event-triggered reports; receives a scheduling request or a PRACH; sends downlink control information (DCI); and receives the event-triggered report.

[0273] In some embodiments, the communication system 100 may include at least:

[0274] A terminal device, comprising: receiving configuration information for configuring one or more event-triggered reports; wherein a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration; sending a scheduling request or a PRACH according to the scheduling request configuration or the RACH configuration associated with the event-triggered report when an event-triggered report meets a triggering condition; receiving downlink control information (DCI); and sending the event-triggered report on a PUSCH or a PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result;

[0275] A network device sends configuration information for configuring one or more event-triggered reports; receives a scheduling request or a PRACH; sends downlink control information (DCI); and receives the event-triggered report.

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

[0277] Figure 20 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 20 , terminal device 2000 may include a processor 2010 and a memory 2020. Memory 2020 stores data and programs and is coupled to processor 2010. 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.

[0278] For example, the processor 2010 may be configured to execute a program to implement the information reporting method as described in the embodiment of the first aspect. For example, the processor 2010 may be configured to perform the following control: receiving configuration information for configuring one or more event-triggered reports, wherein the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; and sending a scheduling request or a PRACH when an event-triggered report meets a triggering condition; receiving downlink control information (DCI); and sending the event-triggered report on a PUSCH or a PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0279] For example, the processor 2010 can be configured to execute a program to implement the information reporting method as described in the embodiment of the second aspect. For example, the processor 2010 can be configured to perform the following control: receiving configuration information for configuring one or more event-triggered reports and / or one or more trigger states; wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or, each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration; when an event-triggered report meets a trigger condition, sending a scheduling request or a PRACH according to the scheduling request configuration or the RACH configuration associated with the event-triggered report; receiving downlink control information (DCI); and sending the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

[0280] For example, the processor 2010 may be configured to execute a program to implement the information reporting method as described in the embodiment of the third aspect. For example, the processor 2010 may be configured to perform the following control: receiving configuration information for configuring one or more event-triggered reports; wherein a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration; when an event-triggered report meets a triggering condition, sending a scheduling request or a PRACH according to the scheduling request configuration or the RACH configuration associated with the event-triggered report; receiving downlink control information (DCI); and sending the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

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

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

[0283] Figure 21 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 21 , network device 2100 may include a processor 2110 (e.g., a central processing unit (CPU)) and a memory 2120. Memory 2120 is coupled to processor 2110. Memory 2120 can store various data and also store an information processing program 2130, which is executed under the control of processor 2110.

[0284] For example, the processor 2110 may be configured to execute a program to implement the information receiving method as described in the embodiments of the first to third aspects. For example, the processor 2110 may be configured to perform the following control: sending configuration information for configuring one or more event-triggered reports; receiving a scheduling request or a PRACH; sending downlink control information (DCI); and receiving the event-triggered report.

[0285] In addition, as shown in Figure 21, network device 2100 may further include: a transceiver 2140 and an antenna 2150; wherein, the functions of the above components are similar to those in the prior art and are not described here in detail. It is worth noting that network device 2100 does not necessarily include all the components shown in Figure 21; in addition, network device 2100 may also include components not shown in Figure 21, and reference may be made to the prior art for details.

[0286] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the information reporting method described in the embodiments of the first to third aspects.

[0287] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the information reporting method described in the embodiments of the first to third aspects.

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

[0289] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the information receiving method described in the embodiment of the fourth aspect.

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

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

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

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

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

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

[0296] 1. An information reporting method, comprising:

[0297] The terminal device receives configuration information for configuring one or more event-triggered reports, wherein the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; and

[0298] The terminal device sends a scheduling request or PRACH when an event trigger report meets the triggering condition;

[0299] The terminal device receives downlink control information (DCI); and

[0300] The terminal device sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0301] 2. An information reporting method, comprising:

[0302] The terminal device receives configuration information for configuring one or more event-triggered reports and / or one or more trigger states; wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration;

[0303] The terminal device sends a scheduling request or PRACH according to the scheduling request configuration or RACH configuration associated with the event triggered report when an event triggered report meets the triggering condition;

[0304] The terminal device receives downlink control information (DCI); and

[0305] The terminal device sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

[0306] 3. An information reporting method, comprising:

[0307] The terminal device receives configuration information for configuring one or more event-triggered reports; wherein the first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and the second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration;

[0308] The terminal device sends a scheduling request or PRACH according to the scheduling request configuration or RACH configuration associated with the event triggered report when an event triggered report meets the triggering condition;

[0309] The terminal device receives downlink control information (DCI); and

[0310] The terminal device sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0311] 4. A method for receiving information, comprising:

[0312] The network device sends configuration information for configuring one or more event-triggered reports, wherein the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; and

[0313] The network device receives a scheduling request or a PRACH;

[0314] The network device sends downlink control information (DCI); and

[0315] The network device receives the event-triggered report sent on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0316] 5. A method for receiving information, comprising:

[0317] The network device sends configuration information for configuring one or more event-triggered reports and / or one or more trigger states; wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration;

[0318] The network device receives a scheduling request or a PRACH;

[0319] The network device sends downlink control information (DCI); and

[0320] The network device receives the event-triggered report sent on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

[0321] 6. A method for receiving information, comprising:

[0322] The network device sends configuration information for configuring one or more event-triggered reports; wherein a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration;

[0323] The network device receives a scheduling request or a PRACH;

[0324] The network device sends downlink control information (DCI); and

[0325] The network device receives the event-triggered report sent on the PUSCH or PUCCH indicated by the downlink control information (DCI); wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

[0326] 7. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the information reporting method as described in any one of Notes 1 to 3.

[0327] 8. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the information receiving method as described in any one of Notes 4 to 6.

[0328] 9. A computer program product, comprising at least a computer program, wherein when the computer program is executed by a processor, the terminal device executes the information reporting method as described in any one of Notes 1 to 3.

[0329] 10. A computer program product, comprising at least a computer program, wherein when the computer program is executed by a processor, the network device executes the information receiving method as described in any one of Notes 4 to 6.

Claims

1. An information reporting device, comprising: a receiving unit configured to receive configuration information for configuring one or more event-triggered reports, wherein the one or more event-triggered reports are associated with a scheduling request configuration or a RACH configuration; as well as a sending unit, which sends a scheduling request or PRACH when an event triggered report meets a triggering condition; The receiving unit further receives downlink control information; and The sending unit further sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information; wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

2. The device according to claim 1, wherein The event trigger report further includes at least one of an event index, a number of measurement resource indexes, a number of measurement results, and a measurement resource set index.

3. The device according to claim 1, wherein The event-triggered report is sent on the PUSCH or the PUCCH through uplink control information, or the event-triggered report is sent on the PUSCH through MAC-CE.

4. The device according to claim 1, wherein The report index is an event-triggered report configuration number, or the report index is a number corresponding to one or more configured event-triggered reports.

5. The device according to claim 1, wherein The device further comprises: A processing unit determines to send the event trigger report according to at least one of the fields included in the downlink control information, the format of the downlink control information, and information indicated by the downlink control information.

6. The device according to claim 5, wherein The CSI request field of the downlink control information indicates a triggering status dedicated to an event-triggered report, and the processing unit determines to send the event-triggered report according to the triggering status.

7. The device according to claim 1, wherein The number of measurement resource indexes or measurement results included in reports triggered by different events is the same.

8. The device according to claim 7, wherein The number of measurement resource indexes or the number of measurement results is configured in units of terminal devices, or the number of measurement resource indexes or the number of measurement results is predefined.

9. The device according to claim 1, wherein The number of measurement resource indexes or measurement results included in reports triggered by different events are independent.

10. The device according to claim 9, wherein The number of measurement resource indexes or the number of measurement results is configured in units of event-triggered reports or is determined by the terminal device.

11. The device according to claim 1, wherein The event-triggered report includes a first CSI part and a second CSI part; The first part of the CSI includes at least one of a report index, a first group of measurement resource indexes, and a first group of measurement results; the second part of the CSI includes at least one of a second group of measurement resource indexes and a second group of measurement results.

12. The device according to claim 11, wherein The number of the first group of measurement resource indexes or the number of the first group of measurement results is configured in units of terminal devices, or the number of the first group of measurement resource indexes or the number of the first group of measurement results is predefined.

13. The device according to claim 11, wherein The first part of the CSI also includes the number of the measurement resource indexes and / or the number of the measurement results.

14. The device according to claim 1, wherein In case that the event-triggered report is sent and / or the event-triggered report is cancelled, the scheduling request is cancelled and / or the timer associated with the scheduling request is stopped.

15. The device according to claim 1, wherein The event-triggered report is an event-triggered CSI report, or the event-triggered report is an event-triggered LTM CSI report.

16. An information reporting device, comprising: a receiving unit configured to receive configuration information for configuring one or more event-triggered reports and / or one or more trigger states, wherein each event-triggered report is associated with a scheduling request configuration or a RACH configuration, and / or each event-triggered report associated with a trigger state is associated with a scheduling request configuration or a RACH configuration; a sending unit configured to send a scheduling request or a PRACH according to a scheduling request configuration or a RACH configuration associated with an event triggered report when an event triggered report satisfies a triggering condition; The receiving unit further receives downlink control information; and The sending unit further sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information; wherein the event-triggered report includes at least one of a measurement resource index and a measurement result.

17. The device according to claim 16, wherein The device further comprises: A processing unit determines to send the event trigger report according to at least one of the fields included in the downlink control information, the format of the downlink control information, and information indicated by the downlink control information.

18. The device according to claim 17, wherein The CSI request field of the downlink control information indicates a trigger status associated with an event triggered report, and the processing unit determines to send the event triggered report associated with the trigger status according to the trigger status.

19. An information reporting device, comprising: a receiving unit configured to receive configuration information for configuring one or more event-triggered reports, wherein a first number of event-triggered reports are associated with a first scheduling request configuration or a RACH configuration, and a second number of event-triggered reports are associated with a second scheduling request configuration or a RACH configuration; a sending unit configured to send a scheduling request or a PRACH according to a scheduling request configuration or a RACH configuration associated with an event triggered report when an event triggered report satisfies a triggering condition; The receiving unit further receives downlink control information; and The sending unit further sends the event-triggered report on the PUSCH or PUCCH indicated by the downlink control information; wherein the event-triggered report includes at least one of a report index, a measurement resource index, and a measurement result.

20. The device according to claim 19, wherein The report index is an index within the first number of event-triggered reports, or the report index is an index within the second number of event-triggered reports; and / or, The first number of event-triggered reports are associated with a first event, and the second number of event-triggered reports are associated with a second event.

Images