Measurement result reporting method, device and system

Abstract

A method, device and system for reporting a measurement result, the method comprising: acquiring configuration information, the configuration information being used for indicating information of X events corresponding to M cells, sending a measurement report, the measurement report comprising a measurement result related to at least one event corresponding to M1 cells, the at least one event corresponding to the M1 cells is an event occurring in the X events, the load size of the measurement report is the load size required for reporting the first event and / or the measurement result related to the first cell, and the M1 cells belong to the M cells. According to the scheme, the terminal is supported to report the measurement result related to at least one event occurring on one or more cells, the overhead of uplink resources can be reduced, and reasonable allocation of the resources is realized.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method, apparatus, and system for reporting measurement results. Background Technology

[0002] In wireless communication, reference signals are transmitted between the transmitting and receiving ends to send and receive data, obtain system synchronization, and provide feedback channel information. For example, the transmitting end sends a reference signal to the receiving end, which receives the reference signal and can then perform corresponding operations based on it, such as performing channel measurements and reporting measurement reports. Currently, the timing of measurement report reporting is mainly determined by the network device. For instance, in periodic and semi-persistent measurement reporting, the terminal device reports the measurement results every period, but these results may be meaningless to the network device, leading to significant uplink resource overhead. Therefore, designing an effective method for reporting measurement results is a problem that needs to be considered. Summary of the Invention

[0003] This application provides a method, apparatus, and system for reporting measurement results, with the aim of supporting the reporting of measurement results related to events occurring on one or more cells.

[0004] Firstly, a method for reporting measurement results is provided. This method can be executed by a first device. Unless otherwise specified, the "first device" in this application can refer to the first device itself (e.g., a terminal device), a component in the first device (e.g., a communication module, processor, circuit, chip, or chip system), or a logic module or software that can implement all or part of the functions of the first device.

[0005] The method includes: obtaining configuration information, which indicates information about X events corresponding to (or associated with) M cells, where M and X are both integers greater than or equal to 1; sending a measurement report, which includes measurement results related to at least one event corresponding to M1 cells, where at least one event corresponding to M1 cells is an event that occurred among the X events, and the load size of the measurement report is the load size required to report the first event and / or report the measurement report results related to the first cell, where M1 cells belong to M cells, and M1 is a positive integer less than or equal to M.

[0006] Understandably, the payload size of a measurement report refers to the payload size included in the measurement report, or in other words, the number of bits / bit space / bit width included in the measurement report, or the space / payload size / number of bits / bit space / bit width reserved in the measurement report, etc. That is, the terms "space," "reporting space," "bit space," "reporting bit space," "payload size," "reporting payload size," "number of bits," "reporting bit number," "bit width," "reporting bit width," "reporting payload size," or "payloadsize" in this application can be used interchangeably.

[0007] Optionally, the load size of the measurement report is: the load size required to report the measurement report results related to the first event, or the load size required to report the measurement results related to the first cell, or the load size required to report the measurement results related to both the first event and the first cell. This can be understood as the load size required to report the measurement results related to the first event associated with the first cell, or the load size required to report the measurement results corresponding to the first event that occurred on the first cell.

[0008] Based on the above scheme, terminal devices can report events across cells, thereby avoiding the reporting of invalid measurement reports to network devices and enabling the reporting of meaningful measurement results (such as measurement results associated with at least one event in M1 cells where an event has occurred), reducing uplink resource overhead. Furthermore, terminal devices can define the load size of measurement reports, thus avoiding resource waste caused by allocating corresponding reporting resources for each event when the terminal device supports or is configured to handle at least one event occurring in one or more cells, achieving rational resource allocation.

[0009] In one possible design, M1 equals 1, and at least one event is an event.

[0010] In other words, this application does not limit the number of cells where an event occurs, and / or the size of the number of events. The terminal device can select or determine a cell where an event occurs to report, and / or select an event to report, which facilitates cell and event management and is easier to implement.

[0011] In one possible design, the first event is the event with the largest load among the X events whose related measurement results are reported, and the first cell is the cell with the largest load among the M cells whose related measurement results are reported.

[0012] In other words, the load size of the measurement report is the load size required for the measurement results associated with the event with the largest load size among X events, or the load size of the measurement report is the load size required for the measurement results associated with the cell with the largest load size among M cells.

[0013] In one possible design, the first cell consists of M cells, and the load of the measurement report is the sum of the loads required to report the relevant measurement results of the M cells.

[0014] In other words, the load size of the measurement report is the sum of the load sizes required for the measurement results related to M cells, which enables reasonable allocation of resources and ensures that the measurement results related to all events are reported to the network devices.

[0015] In one possible design, the portion of the measurement report excluding the measurement results related to at least one event corresponding to M1 cells contains predefined values, such as all zeros. In other words, the reporting positions for the measurement results corresponding to M-M1 cells, excluding the measurement results related to at least one event corresponding to M1 cells, can be filled with predefined values.

[0016] In one possible design, the method further includes: sending first information, which indicates information about each of the M1 cells, such as the cell identifier; and / or, the load size of the measurement report.

[0017] Optionally, the first information may be carried in a scheduling request (SR) signaling or a reporting instruction signaling.

[0018] Optionally, the first information may also include at least one event-related measurement result corresponding to the M1 cells.

[0019] In one possible design, the method further includes: sending second information, which indicates information about at least one event occurring in each of the M1 cells, or event information requiring the reporting of relevant measurement results; and / or, the number of reports for each reporting parameter corresponding to each occurring event.

[0020] For example, the second information includes information about at least one event corresponding to each of the M1 cells, such as the cell identifier and the index or identifier of at least one event; and / or, the number of reports for each report quantity (also referred to as a report parameter) in at least one report quantity (e.g., reportquantity) corresponding to each occurrence of the event. It is understood that each event may be associated with one or more report quantities.

[0021] Optionally, the terminal device may simultaneously send at least one of the following through a single message: information about each of the M1 cells, the load size required for measurement results related to at least one event corresponding to the M1 cells, information about at least one event corresponding to each of the M1 cells, or the number of reports corresponding to each of the at least one event, wherein each event may correspond to one or more reports.

[0022] Optionally, the first information and the second information can be different. Optionally, the first information and the second information can be sent simultaneously or separately, and the specific order of sending is not limited.

[0023] Optionally, the second information may be carried in a scheduling request (SR) message signaling or a reporting indication signaling.

[0024] Optionally, the second information may also include at least one event-related measurement result corresponding to the M1 cells.

[0025] In one possible design, the load required to report the relevant measurement results for each of the M cells is determined based on the event with the largest load required to report the relevant measurement results among one or more events corresponding to each cell.

[0026] In one possible design, the load required to report the measurement results related to each of the M cells is determined by the sum of the load required to report the measurement results related to all events corresponding to each cell.

[0027] In one possible design, the method further includes: determining the reporting quantity corresponding to each of the X events, and the number of reports corresponding to each of the X events, wherein each event may correspond to one or more reporting quantities.

[0028] In one possible design, the load required to report the measurement results related to each of the X events is determined based on the reporting amount for each event and the number of reports for each reporting amount.

[0029] In one possible design, when M is greater than 1, at least two of the M cells have different measurement report configurations; or, the M cells correspond to one measurement report configuration.

[0030] Optionally, the measurement report configuration can be the same as the above configuration information, in which case the configuration information and measurement report configuration in the application document can be used interchangeably. Optionally, the measurement report configuration can also be different from the above configuration information. For example, the measurement report configuration may include the configuration information, or the above configuration information may include the measurement report configuration, without limitation.

[0031] In other words, network devices can configure one or more measurement report configurations for M cells. That is, if the terminal device determines that an event has occurred on multiple cells, it can decide whether to report one measurement report or multiple measurement report configurations based on the measurement report configuration. This application does not limit this.

[0032] In one possible design, the measurement report configuration includes one or more of the following, or in other words, the measurement report configuration is associated with one or more of the following:

[0033] Information on one or more of the M cells;

[0034] One or more event information corresponding to one or more cells in M ​​cells;

[0035] Reference signal measurement resources corresponding to one or more events in one or more of the M cells;

[0036] Event trigger reporting resources for one or more of the M cells;

[0037] Scheduling requests or indication resources for one or more cells among M cells;

[0038] The number of events reported for one or more of the M cells; or...

[0039] The number of events reported for one or more of the M cells.

[0040] In one possible design, sending a measurement report includes: configuring one measurement report for each of M cells; sending one measurement report; and a measurement report including at least one event-related measurement result for each of the M1 cells. The order of the at least one event-related measurement result for each of the M1 cells in the measurement report is determined according to the cell priority sorting information of the M1 cells. That is, the measurement report carries at least one event-related measurement result for each of the M1 cells, wherein the order of the at least one event-related measurement result for each of the M1 cells is determined according to the cell priority sorting information of the M1 cells (used to indicate the reporting priority of the cells).

[0041] In one possible design, sending a measurement report includes: multiple measurement report configurations corresponding to M cells; sending one or more measurement reports according to the priority ordering information of the multiple measurement report configurations; the one or more measurement reports include measurement results related to at least one event corresponding to M1 cells; and the multiple measurement report configurations correspond one-to-one with the multiple measurement reports.

[0042] Optionally, there can be Z measurement report configurations, where Z is less than or equal to M. When Z equals M, it means that each of the M cells corresponds to one measurement report configuration, i.e., each cell corresponds to one measurement report. In this case, the terminal device reports M1 measurement reports, and each of the M1 measurement reports includes one cell from the M1 cells. When Z is greater than 1 and less than M, it means that there are multiple cells among the M cells corresponding to one measurement report configuration. That is, the terminal device can report the measurement results related to events occurring on multiple cells corresponding to that one measurement report configuration through one measurement report.

[0043] In one possible design, sending measurement reports includes: configuring *a* measurement reports for M cells; sending *b* measurement reports according to the priority ordering information of the *a* measurement report configurations; and sending *b* measurement reports, each of which includes measurement results related to at least one event for M1 cells. The *a* measurement report configurations correspond one-to-one with the *a* measurement reports, and the *b* measurement reports belong to the *a* measurement reports. Here, *a* is an integer greater than 1, and *b* is a positive integer less than or equal to *a*. It is understood that the priority of the measurement report configurations corresponding to the *b* measurement reports is higher than the priority of the measurement report configurations corresponding to the other *ab* measurement reports.

[0044] In other words, M cells can correspond to one or more measurement configurations. That is, the measurement results related to at least one event of M1 cells reported by the terminal device can be carried in one measurement report or multiple measurement reports without restriction.

[0045] In one possible design, a measurement report is sent, comprising: a configuration of one measurement report corresponding to M cells; a first part of the measurement report including a first portion of measurement results related to at least one event corresponding to M1 cells; and a second part of the measurement report including a second portion of measurement results related to at least one event corresponding to M1 cells. In this case, the order of the first portion of the measurement results related to at least one event corresponding to M1 cells in the first part of the measurement report is determined according to the cell priority ordering information of the M1 cells, and the order of the second portion of the measurement results related to at least one event corresponding to M1 cells in the second part of the measurement report is determined according to the cell priority ordering information of the M1 cells.

[0046] In other words, the first part of the measurement report carries the first part of the measurement results related to at least one event corresponding to the M1 cells, wherein the order of the first part of the measurement results related to at least one event corresponding to the M1 cells is determined according to the cell priority sorting information of the M1 cells (used to indicate the reporting priority of the cells), and the second part of the measurement report carries the second part of the measurement results related to at least one event corresponding to the M1 cells, wherein the order of the second part of the measurement results related to at least one event corresponding to the M1 cells is determined according to the cell priority sorting information of the M1 cells (used to indicate the reporting priority of the cells).

[0047] In one possible design, sending a measurement report includes: multiple measurement report configurations corresponding to M cells; sending one or more measurement reports according to priority sorting information of the multiple measurement report configurations; a first part of the one or more measurement reports includes a first part of measurement results related to at least one event corresponding to M1 cells; a second part of the one or more measurement reports includes a second part of measurement results related to at least one event corresponding to M1 cells; and the multiple measurement report configurations correspond one-to-one with the multiple measurement reports.

[0048] Optionally, there can be Z measurement report configurations, where Z is less than or equal to M. When Z equals M, it means that each of the M cells corresponds to one measurement report configuration, i.e., each cell corresponds to one measurement report. In this case, the terminal device reports M1 measurement reports, and each of the M1 measurement reports includes one cell from the M1 cells. When Z is greater than 1 and less than M, it means that there are multiple cells among the M cells corresponding to one measurement report configuration. That is, the terminal device can report the measurement results related to events occurring on multiple cells corresponding to that one measurement report configuration through one measurement report.

[0049] In one possible design, sending measurement reports includes: M cells corresponding to *a* measurement report configurations; sending *b* measurement reports according to the priority ordering information of the *a* measurement report configurations; the first part of the *b* measurement reports includes the first part of the measurement results related to at least one event corresponding to M1 cells; the second part of the *b* measurement reports includes the second part of the measurement results related to at least one event corresponding to M1 cells. The *a* measurement report configurations correspond one-to-one with the *a* measurement reports, and the *b* measurement reports belong to the *a* measurement reports, where *a* is an integer greater than 1 and *b* is a positive integer less than or equal to *a*. It is understood that the priority of the measurement report configurations corresponding to the *b* measurement reports is higher than the priority of the measurement report configurations corresponding to the other *ab* measurement reports.

[0050] In other words, the measurement results related to at least one event corresponding to M1 cells reported by the terminal device can be carried in one measurement report or multiple measurement reports without restriction. Each measurement report includes a first part and a second part. The first part of the measurement report carries the first portion of the measurement results related to at least one event corresponding to M1 cells, such as event information, or the number of reported parameters corresponding to the event. The second part of the measurement report carries the second portion of the measurement results related to at least one event corresponding to M1 cells, such as the relevant measurement results corresponding to the event, or the measurement quantity corresponding to each reported parameter corresponding to the event.

[0051] In one possible design, the first part includes one or more of the following: whether an event has occurred in the cell corresponding to the first part; information about the event that occurred in the cell corresponding to the first part; or, the number of reports corresponding to each of the at least one event; the load size corresponding to the second part is determined according to the first part.

[0052] In one possible design, M cells correspond to multiple measurement report configurations, and the multiple measurement report configurations correspond one-to-one with the multiple measurement reports carried on the same reporting resource. This method can save reporting resources.

[0053] Secondly, a method for reporting measurement results is provided. This method can be executed by a second device. Unless otherwise specified, the "second device" in this application can refer to the second device itself (e.g., a network device), a component in the second device (e.g., a communication module, processor, circuit, chip, or chip system), or a logic module or software that can implement all or part of the functions of the second device.

[0054] The method includes: sending configuration information, which indicates information about X events corresponding to M cells, where M and X are both integers greater than or equal to 1; receiving a measurement report, which includes measurement results related to at least one event corresponding to M1 cells, where at least one event corresponding to M1 cells is an event that occurred among X events, and the load size of the measurement report is the load size required to report the first event and / or report the measurement results related to the first cell, where M1 cells belong to M cells, and M1 is a positive integer less than or equal to M.

[0055] In one possible design, M1 equals 1, and at least one event is an event.

[0056] In one possible design, the first event is the event with the largest load among the X events that require reporting the relevant measurement results, and the first cell is the cell with the largest load among the M cells that require reporting the relevant measurement results.

[0057] In one possible design, the first cell consists of M cells, and the load of the measurement report is the sum of the loads required to report the relevant measurement results of the M cells.

[0058] In one possible design, the portion of the measurement report other than the measurement results related to at least one event corresponding to M1 cells consists of predefined values.

[0059] In one possible design, the method further includes: receiving first information, which indicates information about each of the M1 cells, and / or, the load size of the measurement report.

[0060] In one possible design, the method further includes: receiving second information, the second information being used to indicate information about at least one event corresponding to each of the M1 cells; and / or, the number of reports corresponding to each of the at least one event, wherein each event may correspond to one or more reports.

[0061] In one possible design, the load required to report the relevant measurement results for each of the M cells is determined based on the event with the largest load required to report the relevant measurement results among one or more events corresponding to each cell.

[0062] In one possible design, the load required to report the measurement results related to each of the M cells is determined by the sum of the load required to report the measurement results related to all events corresponding to each cell.

[0063] In one possible design, the load required to report the measurement results related to each of the X events is determined based on the reporting amount for each event and the number of reports for each reporting amount.

[0064] In one possible design, when M is greater than 1, at least two of the M cells have different measurement report configurations; or, the M cells correspond to one measurement report configuration.

[0065] In one possible design, the measurement report configuration includes one or more of the following, or in other words, the measurement report configuration is associated with one or more of the following:

[0066] Information on one or more of the M cells;

[0067] One or more event information corresponding to one or more cells in M ​​cells;

[0068] Reference signal measurement resources corresponding to one or more events in one or more of the M cells;

[0069] Event trigger reporting resources for one or more of the M cells;

[0070] Scheduling requests or indication resources for one or more cells among M cells;

[0071] The number of events reported for one or more of the M cells; or...

[0072] The number of events reported for one or more of the M cells.

[0073] In one possible design, receiving a measurement report includes: receiving one measurement report configuration corresponding to M cells, wherein the measurement report includes at least one event-related measurement result corresponding to M1 cells; or, receiving multiple measurement report configurations corresponding to M cells, wherein multiple measurement reports are received according to priority sorting information of the multiple measurement report configurations, wherein the multiple measurement reports include at least one event-related measurement result corresponding to M1 cells, wherein the multiple measurement report configurations correspond one-to-one with the multiple measurement reports, and the sorting of at least one event-related measurement result corresponding to M1 cells in the single measurement report is determined according to the cell priority sorting information corresponding to the M1 cells.

[0074] In one possible design, receiving a measurement report includes: configuring one measurement report for each of M cells, receiving a measurement report, a first part of the measurement report including a first part of measurement results related to at least one event for each of the M1 cells, and a second part of the measurement report including a second part of measurement results related to at least one event for each of the M1 cells.

[0075] In one possible design, receiving measurement reports includes: multiple measurement report configurations corresponding to M cells; receiving multiple measurement reports according to priority sorting information of the multiple measurement report configurations; a first part of the multiple measurement reports includes a first part of measurement results related to at least one event corresponding to M1 cells; a second part of the multiple measurement reports includes a second part of measurement results related to at least one event corresponding to M1 cells; and the multiple measurement report configurations correspond one-to-one with the multiple measurement reports.

[0076] In one possible design, M cells correspond to multiple measurement report configurations, and the multiple measurement report configurations correspond one-to-one with the multiple measurement reports carried on the same reporting resource.

[0077] In one possible design, the first part includes one or more of the following: whether an event has occurred in the cell corresponding to the first part; information about the event that occurred in the cell corresponding to the first part; or, the number of reports corresponding to each of the at least one event; the load size corresponding to the second part is determined according to the first part.

[0078] The second aspect and some of its implementations, as well as their corresponding beneficial effects, can be found in the description of the first aspect, and will not be elaborated upon here.

[0079] Thirdly, a communication device is provided, which has the functions of the first aspect above. For example, the communication device includes modules, units or means corresponding to the operations involved in the first aspect above. The modules, units or means can be implemented by software, or by hardware, or by a combination of software and hardware.

[0080] For example, the communication device may be the first device, or a module or unit (e.g., a chip, a chip system, or a circuit) in the first device that corresponds to each of the methods, operations, steps, or actions described in the first aspect above, or a device that can be used in conjunction with the first device.

[0081] In one possible implementation, the communication device includes a transceiver unit (or communication module) and a processing unit (or processing module) connected to the transceiver unit.

[0082] For example, the processing unit is used to obtain configuration information, which indicates information about X events corresponding to M cells, where M and X are both integers greater than or equal to 1; the transceiver unit is used to send a measurement report, which includes measurement results related to at least one event corresponding to M1 cells, where at least one event corresponding to M1 cells is an event that occurred among X events, and the load size of the measurement report is the load size required to report the first event and / or report the measurement results related to the first cell, where M1 cells belong to M cells, and M1 is a positive integer less than or equal to M.

[0083] In one possible design, M1 equals 1, and at least one event is an event.

[0084] In one possible design, the first event is the event with the largest load among the X events whose related measurement results are reported, and the first cell is the cell with the largest load among the M cells whose related measurement results are reported.

[0085] In one possible design, the first cell consists of M cells, and the load of the measurement report is the sum of the loads required to report the relevant measurement results of the M cells.

[0086] In one possible design, the portion of the measurement report other than the measurement results related to at least one event corresponding to M1 cells consists of predefined values.

[0087] In one possible design, the transceiver unit is also used to transmit first information, which indicates information about each of the M1 cells, and / or the load size of the measurement report.

[0088] In one possible design, the transceiver unit is also used for second information, which indicates information about at least one event corresponding to each of the M1 cells; and / or, the number of reported quantities corresponding to each of the at least M1 events.

[0089] In one possible design, the load required to report the relevant measurement results for each of the M cells is determined based on the event with the largest load required to report the relevant measurement results among one or more events corresponding to each cell.

[0090] In one possible design, the load required to report the measurement results related to each of the M cells is determined by the sum of the load required to report the measurement results related to all events corresponding to each cell.

[0091] In one possible design, the processing unit is also used to determine the reporting amount corresponding to each of the X events, and the number of reports corresponding to each of the X events.

[0092] In one possible design, the payload required for the measurement results associated with each of the X events is determined based on the reporting volume for each event and the number of reports for each reporting volume.

[0093] In one possible design, when M is greater than 1, at least two of the M cells have different measurement report configurations; or, the M cells correspond to one measurement report configuration.

[0094] In one possible design, the measurement report configuration includes one or more of the following, or in other words, the measurement report configuration is associated with one or more of the following:

[0095] Information on one or more of the M cells;

[0096] One or more event information corresponding to one or more cells in M ​​cells;

[0097] Reference signal measurement resources corresponding to one or more events in one or more of the M cells;

[0098] Event trigger reporting resources for one or more of the M cells;

[0099] Scheduling requests or indication resources for one or more cells among M cells;

[0100] The number of events reported for one or more of the M cells; or...

[0101] The number of events reported for one or more of the M cells.

[0102] In one possible design, M cells correspond to one measurement report configuration, and the transceiver unit is also used to send a measurement report according to the cell priority sorting information. The measurement report includes at least one event-related measurement result corresponding to M1 cells. Alternatively, M cells correspond to multiple measurement report configurations, and the transceiver unit is also used to send multiple measurement reports according to the priority sorting information of the multiple measurement report configurations. The multiple measurement reports include at least one event-related measurement result corresponding to M1 cells.

[0103] In one possible design, M cells correspond to one measurement report configuration. The transceiver unit is also used to send a measurement report according to the cell priority sorting information. The first part of a measurement report includes the first part of the measurement results related to at least one event corresponding to M1 cells, and the second part of a measurement report includes the second part of the measurement results related to at least one event corresponding to M1 cells.

[0104] In one possible design, M cells correspond to multiple measurement report configurations. The transceiver unit is also used to send multiple measurement reports according to the priority sorting information of the multiple measurement report configurations. The first part of the multiple measurement reports includes the first part of the measurement results related to at least one event corresponding to M1 cells. The second part of the multiple measurement reports includes the second part of the measurement results related to at least one event corresponding to M1 cells.

[0105] In one possible design, M cells correspond to multiple measurement report configurations, and the multiple measurement report configurations correspond one-to-one with the multiple measurement reports carried on the same reporting resource.

[0106] In one possible design, the first part includes one or more of the following: whether an event has occurred in the cell corresponding to the first part; information about the event that occurred in the cell corresponding to the first part; or, the number of reports corresponding to each of the at least one event; the load size corresponding to the second part is determined according to the first part.

[0107] Fourthly, a communication device is provided, which has the functions of the second aspect above. For example, the communication device includes modules, units or means corresponding to the operations involved in the second aspect above. The modules, units or means can be implemented by software, or by hardware, or by a combination of software and hardware.

[0108] For example, the communication device may be a second device, or a module or unit (e.g., a chip, a chip system, or a circuit) in the first device that corresponds one-to-one with the method, operation, step, or action described in the second aspect above, or a device that can be used in conjunction with the second device.

[0109] In one possible implementation, the communication device includes a transceiver unit (or communication module) and a processing unit (or processing module) connected to the transceiver unit.

[0110] For example, the transceiver unit is configured to send configuration information, which indicates information about X events corresponding to M cells, where M and X are both integers greater than or equal to 1; the transceiver unit is also configured to receive a measurement report, which includes measurement results related to at least one event corresponding to M1 cells, where at least one event corresponding to M1 cells is an event that occurred among X events, and the load size of the measurement report is the load size required to report the first event and / or report the measurement results related to the first cell, where M1 cells belong to M cells, and M1 is a positive integer less than or equal to M.

[0111] In one possible design, M1 equals 1, and at least one event is an event.

[0112] In one possible design, the first event is the event with the largest load among the X events whose related measurement results are reported, and the first cell is the cell with the largest load among the M cells whose related measurement results are reported.

[0113] In one possible design, the first cell consists of M cells, and the load of the measurement report is the sum of the loads required to report the relevant measurement results of the M cells.

[0114] In one possible design, the portion of the measurement report other than the measurement results related to at least one event corresponding to M1 cells consists of predefined values.

[0115] In one possible design, the transceiver unit is also used to receive first information, which indicates information about each of the M1 cells, and / or the load size of the measurement report.

[0116] In one possible design, the transceiver unit is also configured to receive second information, which indicates information about at least one event corresponding to each of the M1 cells; and / or, the number of reports corresponding to each of the at least M1 events.

[0117] In one possible design, the load required to report the relevant measurement results for each of the M cells is determined based on the event with the largest load required to report the relevant measurement results among one or more events corresponding to each cell.

[0118] In one possible design, the load required to report the measurement results related to each of the M cells is determined by the sum of the load required to report the measurement results related to all events corresponding to each cell.

[0119] In one possible design, the load required to report the measurement results related to each of the X events is determined based on the reporting amount for each event and the number of reports for each reporting amount.

[0120] In one possible design, when M is greater than 1, at least two of the M cells have different measurement report configurations; or, the M cells correspond to one measurement report configuration.

[0121] In one possible design, the measurement report configuration includes one or more of the following, or in other words, the measurement report configuration is associated with one or more of the following:

[0122] Information on one or more of the M cells;

[0123] One or more event information corresponding to one or more cells in M ​​cells;

[0124] Reference signal measurement resources corresponding to one or more events in one or more of the M cells;

[0125] Event trigger reporting resources for one or more of the M cells;

[0126] Scheduling requests or indication resources for one or more cells among M cells;

[0127] The number of events reported for one or more of the M cells; or...

[0128] The number of events reported for one or more of the M cells.

[0129] In one possible design, M cells correspond to one measurement report configuration, and the transceiver unit is further configured to receive a measurement report according to cell priority sorting information. A measurement report includes at least one event-related measurement result corresponding to M1 cells. Alternatively, M cells correspond to multiple measurement report configurations, and the transceiver unit is further configured to receive multiple measurement reports according to priority sorting information of multiple measurement report configurations. Multiple measurement reports include at least one event-related measurement result corresponding to M1 cells.

[0130] In one possible design, M cells correspond to one measurement report configuration. The transceiver unit is also used to receive a measurement report according to cell priority sorting information. The first part of a measurement report includes the first part of the measurement results related to at least one event corresponding to M1 cells, and the second part of a measurement report includes the second part of the measurement results related to at least one event corresponding to M1 cells.

[0131] In one possible design, M cells correspond to multiple measurement report configurations. The transceiver unit is also used to receive multiple measurement reports according to the priority ordering information of the multiple measurement report configurations. The first part of the multiple measurement reports includes the first part of the measurement results related to at least one event corresponding to M1 cells, and the second part of the multiple measurement reports includes the second part of the measurement results related to at least one event corresponding to M1 cells.

[0132] In one possible design, M cells correspond to multiple measurement report configurations, and the multiple measurement report configurations correspond one-to-one with the multiple measurement reports carried on the same reporting resource.

[0133] In one possible design, the first part includes one or more of the following: whether an event has occurred in the cell corresponding to the first part; information about the event that occurred in the cell corresponding to the first part; or, the number of reports corresponding to each of the at least one event; the load size corresponding to the second part is determined according to the first part.

[0134] Fifthly, a communication device is provided. This communication device may be either the first or second device described above. The communication device includes a transceiver and a processor, the processor controlling the transceiver to transmit and receive signals, a memory storing a computer program, and the processor retrieving and running the computer program from the memory, causing the communication device to execute any possible implementation of either the first or second aspect described above.

[0135] Optionally, there may be one or more processors and one or more memories.

[0136] Optionally, the communication device may also include a memory, which may be integrated with the processor or disposed separately from the processor.

[0137] Optionally, the communication device may also include a transmitter and a receiver.

[0138] In a sixth aspect, a communication device is provided, the communication device comprising one or more processors. The one or more processors are capable of executing the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first or second aspect described above.

[0139] In one possible design, the communication device may further include an interface circuit, through which the processor communicates with other devices or components.

[0140] In one possible design, the communication device may further include a memory for storing part or all of the computer programs or instructions necessary to implement the functions involved in the first or second aspect described above.

[0141] The aforementioned communication device may be a terminal, or a communication module in a terminal, or a chip in a terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip), or a system-on-chip (SoC) chip or system-in-a-package (SIP) chip that includes a modem module.

[0142] The aforementioned communication device may be a network device, or a communication module in a network device, or a circuit or chip in a network device responsible for communication functions, or a functional module in a network device capable of calling and executing programs.

[0143] In a seventh aspect, a communication system is provided. The communication system includes a first device and / or a second device, wherein the first device is configured to perform the method in any possible implementation of the first aspect, and the second device is configured to perform the method in any possible implementation of the second aspect.

[0144] For example, the first device may be a terminal device, or a chip or circuit in the terminal device, or a functional module in the terminal device capable of calling and executing a program; or, the second device may be a network device, or a chip or circuit in the network device, or a central unit (CU) or distributed unit (DU) in the network device, or a functional module in the network device capable of calling and executing a program.

[0145] Eighthly, a computer-readable storage medium is provided. This computer-readable storage medium stores computer program code or instructions to cause the method in any possible implementation of the first or second aspect to be executed, for example, when a computer reads and executes the computer program code or instructions, causing the method in any possible implementation of the first or second aspect to be implemented.

[0146] A ninth aspect provides a computer program product. The computer program product includes computer program code or instructions to cause the method in any possible implementation of the first or second aspect to be implemented. For example, when a computer reads and executes the computer program product, the method in any possible implementation of the first or second aspect is implemented.

[0147] In a tenth aspect, a computer program is provided. When the computer program is run, it causes the method in any of the possible implementations of the first or second aspect to be implemented.

[0148] It should be understood that the beneficial effects of the third to tenth aspects mentioned above can be referred to the first or second aspects mentioned above and any possible implementation thereof, which will not be elaborated here. Attached Figure Description

[0149] Figure 1 This is a schematic diagram of a wireless communication system applicable to embodiments of this application;

[0150] Figure 2 This is another schematic diagram of a wireless communication system applicable to embodiments of this application;

[0151] Figure 3 This is a schematic diagram of beam management applicable to embodiments of this application;

[0152] Figure 4 This is a schematic diagram of a component carrier (CC) structure;

[0153] Figure 5 This is a schematic diagram of a method for reporting measurement results provided in an embodiment of this application;

[0154] Figure 6 This is a schematic diagram of the structure of the measurement quantity of the reporting parameter of the terminal device reporting event q provided in the embodiments of this application;

[0155] Figure 7 This diagram illustrates the measurement results reported by a satisfaction event carried in a measurement report.

[0156] Figure 8 This is a schematic block diagram of a communication device provided in an embodiment of this application;

[0157] Figure 9 This is a schematic block diagram of another communication device provided in the embodiments of this application;

[0158] Figure 10 This is a schematic block diagram of a chip system provided in an embodiment of this application;

[0159] Figure 11 This is a schematic block diagram of another chip system provided in the embodiments of this application. Detailed Implementation

[0160] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0161] To facilitate understanding of the embodiments of this application, the following points are made:

[0162] (1) In this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0163] (2) In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple.

[0164] (3) In this application, the terms "first," "second," and various numerical designations are used for convenience of description and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, rather than to describe a specific order or sequence. It should be understood that such descriptions can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0165] (4) In this application, the descriptions such as “when…”, “under the circumstances of…” and “if” all refer to the device making corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device to make a judgment action when it is implemented, nor do they mean that there are other limitations.

[0166] (5) In this application, “instruction” or “for instruction” can include both direct instruction and indirect instruction. When describing an instruction as being used to instruct A, it can include whether the instruction directly instructs A or indirectly instructs A, but does not necessarily mean that the instruction carries A.

[0167] The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the sending method, for example.

[0168] The "instruction information" in the embodiments of this application can be an explicit instruction, that is, a direct instruction through signaling, or an instruction obtained by combining other rules or parameters with the parameters indicated by the signaling, or by deduction. It can also be an implicit instruction, that is, an instruction obtained based on rules or relationships, or based on other parameters, or by deduction. This application does not specifically limit it in this regard.

[0169] (6) In this application, "protocol" can refer to a standard protocol in the field of communications, such as the 5th generation (5G) protocol, the new radio (NR) protocol, and related protocols applied to future communication systems. This application does not limit the term "protocol". "Predefined" can include predefined terms, such as protocol definitions. "Preconfiguration" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device. This application does not limit the implementation method of this feature.

[0170] (7) In this application, “communication” can also be described as “communication”, “information transmission”, “data processing”, etc. “Transmission” includes “sending” and “receiving”. “Transmission” can be described as “output”.

[0171] (8) In this application, “message”, “information”, “signal” or “information element (IE)” can be used interchangeably. There are no restrictions on the name of the message or information, as long as it can achieve the corresponding function.

[0172] "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information directly or indirectly to that device. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information directly or indirectly from that device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way, and will not be repeated here. Furthermore, "sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, "sending" or "receiving" can occur between devices, for example, between network devices and terminal devices via an air interface. "Sending" or "receiving" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0173] (9) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” “corresponding,” and “associate” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.

[0174] (10) In this application, when comparing A and B, the description "when A is greater than or equal to B, execute method A; when A is less than or equal to B, execute method B" can be implemented as "when A is greater than or equal to B, execute method A; or when A is less than B, execute method B" or "when A is greater than B, execute method A; or when A is less than or equal to B, execute method B". This application does not limit this. For ease of description, the implementation methods provided in this application are all illustrated using "when A is greater than or equal to B, execute method A; or when A is less than B, execute method B" as an example.

[0175] (11) In this application, the configuration can be signaling configuration, such as radio resource control (RRC) messages, downlink control information (DCI), or system information block (SIB). Optionally, the signaling configuration can be pre-configured signaling configuration given to the terminal device, or configured to the terminal device through pre-configuration. Here, pre-configuration means defining or configuring the values ​​of corresponding parameters in advance in the form of a protocol, and storing them in the terminal device when communicating with it. The pre-configured messages can be modified or updated when the terminal device is connected to the network.

[0176] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0177] The technical solutions in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication systems. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to low-frequency scenarios, high-frequency scenarios, and terahertz frequencies.

[0178] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.

[0179] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The term "device" can also be replaced by an entity, network entity, network element, communication equipment, communication module, node, communication node, etc. This application uses "device" as an example for description. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device.

[0180] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3GPP standard. The terminal device (RSU) can be a unit or a device built into the aforementioned equipment (e.g., a communication module, modem, or chip in the aforementioned equipment), or other processing devices connected to a wireless modem. For ease of description, the terminal device will be described below as a terminal or UE.

[0181] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or P2P.

[0182] In this embodiment, the device for implementing the functions of a terminal device, i.e., the terminal device, can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can also be configured with program instructions for performing corresponding communication functions.

[0183] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), gNB (gNB) in future communication networks, relay station, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in D2D, V2X, and M2M communications, network-side devices in future networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0184] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0185] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0186] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be set up separately or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as RRUs, AAUs, or RRHs.

[0187] In some deployments, the CU (Core Unit) is a logical node that carries the RRC (Resource Control Code) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be E2 interfaces, etc. Optionally, the CU possesses some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports the control plane (F1 controlplane, F1-C) and the user plane (F1 user plane, F1-U).

[0188] In some deployments, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements. CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet such latency requirements can be placed in the CU.

[0189] In some deployments, the DU (Distributed Unit) is a logical node carrying the RLC (Real-Time Control) layer, the Medium Access Control (MAC) layer, the Higher Physical Layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0190] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Low-PHY includes portions of the PHY processing, such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0191] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include interfaces providing control and user plane information respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0192] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0193] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0194] In different systems, CU (including open CU-CP (O-CU-CP) and open CU-UP (O-CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open access network (open RAN, O-RAN, or ORAN) system, CU can also be called an open central unit (O-CU), DU can also be called an open distributed unit (O-DU), CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called an open radio unit (O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0195] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0196] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0197] Figure 1 This is a schematic diagram of a wireless communication system applicable to embodiments of this application. For example... Figure 1As shown, the wireless communication system includes a wireless access network 100. The wireless access network 100 can be a future (e.g., a higher version) wireless access network, or a traditional (e.g., 5G or 4G) wireless access network. One or more terminal devices (120a-120j, collectively referred to as 12) can be interconnected or connected to one or more network devices (110a, 110b, collectively referred to as 110) within the wireless access network 100. Network elements in the wireless communication system are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces.

[0198] The above Figure 1 This diagram is provided for ease of understanding only. The wireless communication system may also include other devices, such as core network (CN) equipment, wireless relay equipment, and / or wireless backhaul equipment. Figure 1 It is not shown in the middle.

[0199] Figure 2 This is another schematic diagram of a wireless communication system applicable to embodiments of this application. For example... Figure 2 As shown, this wireless communication system may include core network equipment, access network equipment (such as RAN), and terminal equipment. Access network equipment communicates with the core network equipment via a backhaul link and with the terminal equipment via an air interface. For example, a BBU in the access network equipment communicates with the core network via a backhaul link, while an RU in the access network equipment communicates with the terminal equipment via an air interface. The BBU can communicate with the RU via a fronthaul link. The BBU and RU may or may not be co-located. In some deployments, the BBU includes at least one CU and at least one DU, and the CU and DU communicate with each other via a midhaul link.

[0200] The above Figure 2 This is a schematic diagram provided for ease of understanding. Other devices may also be included in this wireless communication system. Figure 2 It is not shown in the middle.

[0201] To facilitate understanding of the technical solution of this application, some related technologies involved in the technical solution of this application are introduced.

[0202] 1. Beam: A communication resource. Different beams can be considered different resources. The same information or different information can be transmitted through different beams.

[0203] In the NR protocol, beamforming can be represented as a spatial domain filter, spatial parameter, spatial domain parameter, spatial domain setting, spatial setting, quasi-co-location (QCL) information, QCL assumption, QCL indication, etc. Beamforming can be indicated by transmission configuration indicator (TCI) state parameters (TCI-state or TCIstate) or by spatial relation parameters. Therefore, in this application, beamforming can be replaced by spatial domain filter, spatial filter, spatial parameter, spatial parameter, spatial domain setting, spatial setting, QCL information, QCL assumption, QCL indication, TCI-state, spatial relation, etc. These terms are also equivalent to each other. Beamforming can also be replaced with other beamforming terms, which are not limited in this application.

[0204] The beam used to transmit signals can be called a transmission beam (Tx beam), a spatial domain transmission filter, a spatial transmission filter, a spatial domain transmission parameter, a spatial transmission setting, or a spatial transmission setting. The downlink transmission beam can be indicated by the TCI-state. The transmission beam can also be called the downlink beam. In this application, the transmission beam, downlink beam, channel status information reference signal (CSI-RS), TCI State, downlink / joint TCI state, synchronization signal and PBCH block (SSB), and tracking reference signal (PT-RS) can be interchanged.

[0205] The beam used to receive signals can be called a reception beam (Rx beam), a spatial domain reception filter, a spatial reception filter, a spatial domain reception parameter, a spatial reception setting, or a spatial reception setting. The uplink transmit beam can be indicated by a spatial relation, an uplink TCI-state, or a sounding reference signal (SRS) resource (indicating the transmit beam using that SRS). Therefore, uplink beam, SRS resource, and uplink TCI-state are interchangeable. The receive beam can also be called the uplink beam. In this application, the receive beam, uplink beam, uplink transmission configuration indication state (UL TCI state), DLorjointTCI state, sounding reference signal (SRS), CSI-RS, SSB, and tracking reference signal (TRS) can be interchanged.

[0206] The transmitting beam can refer to the distribution of signal strength in different directions in space after a signal is transmitted through an antenna, while the receiving beam can refer to the distribution of signal strength in different directions in space of a wireless signal received from an antenna.

[0207] Furthermore, the beam can be a wide beam, a narrow beam, or other types of beam. The beamforming technology can be beamforming technology or other technologies. Specifically, beamforming technology can be digital beamforming technology, analog beamforming technology, or hybrid digital / analog beamforming technology, etc.

[0208] As an example, multiple beams with the same or similar communication characteristics can be considered as a single beam.

[0209] Beams are generally associated with resources. For example, when performing beam measurement, network devices measure different beams through different resources. The terminal devices provide feedback on the measured resource quality, and the network devices then know the quality of the corresponding beam.

[0210] Optionally, multiple beams with the same or similar communication characteristics can be considered as a single beam. A beam may include one or more antenna ports for transmitting data channels, control channels, and detection signals, etc. One or more antenna ports forming a beam can also be considered as a set of antenna ports.

[0211] 2. Reference signal (RS): Also known as pilot, reference sequence, reference signal, etc. For consistency, it will be described as reference signal below. The reference signal can be used for channel measurement or channel estimation, etc.

[0212] The channel measurements involved in this application also include beam measurements, i.e., obtaining beam quality information by measuring a reference signal. As an example, parameters used to measure beam quality include at least one of the following: reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), signal-to-noise ratio (SNR), and signal-to-interference plus noise ratio (SINR) (or simply signal-to-dryness ratio). In the embodiments of this application, for ease of explanation, unless otherwise specified, the channel measurements involved can be regarded as beam measurements.

[0213] The reference signals mentioned in this application, by way of example, may be any of the following: CSI-RS, synchronization signal block (SSB), sounding reference signal (SRS), user equipment specific reference signal (US-RS), demodulation reference signal (DMRS), phase track reference signal (PT-RS), cell reference signal (CRS), etc. It should be understood that the reference signals listed above are merely examples and should not constitute any limitation on this application. This application does not preclude the possibility of defining other reference signals in future protocols to achieve the same or similar functions.

[0214] Furthermore, the reference signal can be understood as a reference signal associated with the handover candidate cell configuration. The handover candidate cell can also be called a candidate cell or a neighboring cell. This candidate cell can be the current serving cell or a non-serving cell, and its physical cell identifier (PCI) is different from the current primary cell (PCell). Additionally, the reference signal can also be a reference signal associated with an additional PCI, i.e., the reference signal of a neighboring cell.

[0215] The terminal device can be configured with one or more candidate cells, and the configuration of each candidate cell may include the configuration of reference signal resources.

[0216] 3. Reference signal resources: can be used to configure the transmission attributes of reference signals.

[0217] Generally, reference signals are configured in the form of resources. Network devices can configure various reference signals to terminal devices in the form of resources. Each resource is a configuration information unit, which typically includes parameters related to a reference signal, such as the time-frequency resource location, number of ports, time domain type (periodic / semi-static / aperiodic), etc. Transmitting devices can send reference signals based on reference signal resources, and receiving devices can receive reference signals based on reference signal resources.

[0218] To distinguish different reference signal resources, each reference signal resource can correspond to a reference signal resource identifier, such as CSI-RS resource indicator (CRI), SSB resource indicator (SSBRI), or SRS resource index (SRI).

[0219] 4. TCI-state: Network devices can generate different beams pointing in different transmission directions. During downlink data transmission, when a network device uses a specific beam to send data to a terminal device, it needs to inform the terminal device of the transmitted beam information. This allows the terminal device to use the corresponding received beam to receive the data sent by the network device. One possible approach is for the network device to indicate the transmitted beam information to the terminal device through the Transmission Configuration Index (TCI) field in the downlink control information (DCI).

[0220] For example, the TCI field is 3 bits in size and can represent 8 different field values ​​(codepoints). Each value in the TCI field corresponds to a TCI-state index (tci-StateId), which uniquely identifies a TCI-state. A TCI-state includes several parameters that determine information related to the transmitted beam. As an example, each TCI-state includes its own index (tci-StateId) and two QCL information entries (QCL-Info). Each QCL-Info includes a cell field and a bandwidth part (BWP) identifier (ID), indicating which BWP in which cell the TCI-state applies to; that is, different cells or different BWPs in the same cell can be configured with different QCL-Infos. The QCL-Info may also include a reference signal (RS) to indicate which reference signal resource constitutes the QCL relationship. In data transmission and channel measurements, beams can be mapped to reference signal resources, such as one beam corresponding to one reference signal resource. Therefore, which reference signal resource constitutes the QCL relationship can also refer to which beam it forms the QCL relationship with.

[0221] QCL relationship refers to two reference signal resources (or two antenna ports, with a one-to-one correspondence between antenna ports and reference signal resources) having certain identical spatial parameters. Which specific spatial parameters are identical depends on the type of the QCL-Info, specifically another field of the QCL-Info: QCL type (qcl-Type). qcl-Type can have four values: {type A, type B, type C, type D}. For example, type D indicates that the two reference signal resources have the same spatial reception parameter information, meaning the two beams have the same receiving beam. One of the two QCL-Info entries included in the TCI-state may be type D.

[0222] The following example illustrates how a network device uses TCI-state to indicate the receive beam information of the data transmission beam to a terminal device, including the configuration, activation, and indication of TCI-state.

[0223] TCI-state configuration: Network devices configure multiple TCI-states to terminal devices via RRC signaling. Each of these TCI-states includes a QCL-Info of type type D. Network devices can also configure TCI-states that do not include a QCL-Info of type type D; this is not a limitation.

[0224] TCI-state activation: After configuring multiple TCI-states on a network device, eight of them need to be activated via the Media Access Control (MAC) control element (CE) (MACCE). These eight TCI-states correspond one-to-one with the eight values ​​of the TCI field in the DCI. That is, which eight TCI-states correspond to the eight values ​​of the DCI's TCI field is determined by MAC CE signaling. The specific format of the MACCE signaling can be found in the protocol; it is not limited here.

[0225] TCI-state indication: Network devices indicate a specific TCI-state through the TCI field in the DCI. For example, if the TCI field value in the DCI sent by the network device to the terminal device is 000, it indicates that the data transmission beam uses the TCI-state corresponding to 000. The reference signal contained in the QCL-Info of type D within this TCI-state is the reference signal with index #1 (such as CSI-RS), indicating that the beam used for data transmission is the same as the receiving beam corresponding to CSI-RS with index #1. The receiving beam corresponding to CSI-RS with index #1 can be determined through beam measurement procedures and is known to the terminal device. Therefore, through the specific value of the TCI field, the terminal device can determine the receiving beam corresponding to the data transmission beam and thus use the corresponding receiving beam to receive data.

[0226] 5. Unified TCI: This is a unified beam indication framework. Network devices can indicate a beam for terminal devices, which can be used simultaneously for multiple channels and / or reference signals. The common beam can be an uplink common beam, a downlink common beam, or an uplink-downlink common beam, which the terminal device can use in subsequent transmissions. That is, the network device can indicate an uplink common beam for the transmission of multiple uplink channels and / or uplink reference signals. It can also indicate a downlink common beam for the transmission of multiple downlink channels and / or downlink reference signals. Alternatively, it can indicate an uplink-downlink common beam for the transmission of multiple uplink channels and / or uplink reference signals, as well as multiple downlink channels and / or downlink reference signals. In other words, the uplink-downlink common beam can be used for both uplink and downlink transmissions.

[0227] As an example, the terminal device can be configured with two TCI states, referred to as downlink (DL) or joint TCI (DLorjointTCI) and uplink (UL) TCI (ULTCI).

[0228] For example, the terminal device can be configured with both joint / DL TCI-state (up to 128) and uplink TCI-state (ULTCI-state) (up to 64).

[0229] For example, in the serving cell configuration of RRC signaling, the network device can configure the TCI mode currently used by the UE as joint mode or separate mode. In joint mode, it indicates that a joint TCI-state can be used for uplink and downlink transmission simultaneously; in separate mode, the network device indicates that the DL TCI-state and ULTCI-state are used for uplink and downlink transmission respectively.

[0230] When the terminal device receives the TCI-state activation signaling indicated by MACCE, which includes the TCI-state ID, the terminal device determines which TCI is activated by MACCE according to the RRC configuration.

[0231] 6. Physical uplink control channel (PUCCH): This channel is used to transmit uplink control information (UCI) to support uplink and downlink data transmission. UCI can also be transmitted on the physical uplink shared channel (PUSCH).

[0232] As an example, the UCI carried by PUCCH includes at least one of the following: scheduling request (SR), hybrid automatic repeat request (HARQ)-acknowledgement (ACK) (HARQ-ACK) information, and channel status information (CSI) signal.

[0233] The scheduling request can be used for uplink resource requests.

[0234] HARQ-ACK information, also known as HARQ information, represents feedback information on data (such as data on the physical downlink shared channel, PDSCH), such as acknowledgment (ACK) or negative acknowledgment (NACK).

[0235] CSI can include at least one of the following: channel quality indication (CQI), precoding matrix indicator (PMI), rank indicator (RI), CSI-RS resource indicator (CRI), layer indicator (LI), RSRP, or SINR, etc. The signal-to-interference-plus-noise ratio (SNR) can also be called the signal-to-interference-plus-noise ratio (SINR).

[0236] As examples, PUCCH formats include the following: PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, and PUCCH format 4. PUCCH format 0 and PUCCH format 1 can also be called short PUCCHs, occupying 1-2 time domain units (e.g., symbols); PUCCH format 2, PUCCH format 3, and PUCCH format 4 can also be called long PUCCHs, occupying 4-14 time domain units (e.g., symbols).

[0237] 7. Beam management: This includes, for example, beam measurement, such as measurements based on reference signals, to determine the best quality beam.

[0238] 5G can utilize high-frequency communication, specifically ultra-high-frequency (UHF) signals for data transmission. A major problem with high-frequency communication is the sharp decrease in signal energy with increasing transmission distance, resulting in short transmission ranges. To overcome this, high-frequency communication employs analog beamforming technology. By weighting the antenna array, the signal energy is concentrated within a small angular range, forming a beam-like signal (called an analog beam, or simply a beam), thereby increasing the transmission distance. Both network devices and terminal devices use beamforming for transmission. Specifically, network devices and terminal devices use specific beams for uplink and downlink data transmission. Currently, beam management first performs coarse beam alignment based on the SSB (Special Signal Stratos), and then performs fine beam adjustment based on the CSI-RS (Combined Signal Stratosing System). The following section combines... Figure 3 This section introduces the possible processes of beam management.

[0239] Figure 3 This is a schematic diagram of beam management applicable to embodiments of this application.

[0240] As an example, the overall process of beam management can be divided into the following three stages.

[0241] Phase 1: Coarse beam alignment of network equipment and terminal equipment, such as... Figure 3 As shown in (a).

[0242] Specifically, network devices perform beam scanning based on SSB (Service Signal Broadcast) signals, meaning that network devices transmit beams in different directions at different times to achieve broadcast beam coverage of the cell. Simultaneously, terminal devices scan and receive beams, meaning that terminal devices also receive signals using different beams at different times. The terminal devices determine the network device beam and terminal device beam with the best quality (e.g., the superior network device beam and terminal device beam) based on the received signal strength.

[0243] Phase 2: Fine-tuning of network equipment beams, such as... Figure 3 As shown in (b).

[0244] Specifically, the network device determines candidate beams based on the high-quality network device beams obtained in Phase 1, scans them using CSI-RS, and the terminal device receives the signals using the receiving beams selected in Phase 1, thereby fine-tuning the network device beams and determining the network device beams (such as the superior network device beams).

[0245] Phase 3: Fine-tuning of terminal equipment beams, such as... Figure 3 As shown in (c).

[0246] Specifically, the network device uses the beam obtained in Phase 2 to transmit CSI-RS, while the terminal device scans the beam to determine the terminal device beam (such as the preferred terminal device beam) and completes beam alignment. The process is similar to Phase 2.

[0247] The stages 1, 2, and 3 described herein are merely illustrative examples, and the embodiments of this application are not limited thereto. In implementation, a system does not necessarily need to implement all of the above processes; for example, it may only implement stages 1 and 2, leaving the determination of the received beam on the terminal device side to the terminal device itself.

[0248] 8. Measurement Result Reporting: Currently, based on the time-domain configuration behavior, network devices can be configured to perform three types of measurement result reporting processes (also known as beam reporting, beam measurement result reporting, or CSI reporting): periodic reporting, semi-persistent reporting, and aperiodic reporting. A brief introduction follows.

[0249] 1) Periodic Reporting: First, the network device is configured to perform periodic reference signal measurements. This means the network device periodically sends measurement reference signals to the terminal device, which then measures these reference signals and periodically reports the measurement results. After the configuration signaling takes effect, the terminal device periodically reports measurement reports. To terminate the measurement reporting process, an RRC signaling message can be sent to release the relevant configuration parameters for that process.

[0250] 2) Semi-persistent reporting: One type involves periodic reference signal measurement and semi-persistent reporting of measurement results. First, the network device can be configured with periodic reference signals, meaning it periodically sends measurement reference signals to the terminal device. The terminal device measures these reference signals. When the terminal device receives an activation signaling message from the network device (such as MAC CE or DCI signaling), it will continuously and periodically report the measurement results. Of course, the network device can also send a deactivation signaling message to the terminal device to deactivate the semi-persistent reporting process. The other type involves semi-persistent reference signal measurement and result reporting. When the terminal device receives an activation signaling message from the network device (such as MAC CE or DCI signaling), it will continuously and periodically measure the reference signals and report the measurement results. When the terminal device receives a deactivation signaling message from the network device, it stops the continuous reporting.

[0251] 3) Non-periodic reporting: This reporting is only executed after the terminal device receives a trigger signaling from the network device. Furthermore, after completing the reporting, the terminal device will stop reporting, making it a one-time reporting process.

[0252] 9. Component carrier (CC);

[0253] Figure 4 This is a schematic diagram of a component carrier (CC) structure. In current communication systems, the transmittable frequency domain resources are defined on the CC. For example... Figure 4 As shown, the central part of the CC (Carrier Cross Section) represents available frequency domain resources, including, for example, 21 resource blocks (RBs). The shaded areas represent activated RBs, allowing transceivers to exchange information on the resources corresponding to these shaded areas. The CC is flanked by guard bands (GBs), used to separate carriers from other frequency bands and prevent interference between adjacent channels. Optionally, the bandwidth of the GBs on both sides can be the same or different. Furthermore, the RBs containing the GBs at the CC's edges are unusable.

[0254] 10. Reference Signals Associated with TCI State: Reference signals associated with a TCI state can be QCL type D reference signals of the TCI state, or reference signals associated with QCL type D reference signals of the TCI state. Specifically, a QCL type D reference signal of the TCI state is the reference signal in the QCL-info where qcl-Type is type D. The reference signal associated with a QCL type D reference signal of the TCI state is the SSB that has a QCL relationship with that QCL type D reference signal. The SSB is the SSB corresponding to the source QCL resource in the QCL chain. That is, the source QCL resource is an SSB resource. The QCL chain is determined based on the QCL type D reference signal of the TCI state. For example, the network device indicates that the QCL resource of the TCI state for the terminal device is a CSI-RS resource. The QCL resource in the TCI state corresponding to this CSI-RS resource is a TRS resource. The TCI state corresponding to the CSI-RS resource can be understood as the TCI state used by the network device to send the CSI-RS resource, or the TCI state used by the network device to send the CSI-RS resource corresponding to the CSI-RS resource. The QCL resource in the TCI state corresponding to the TRS resource is an SSB resource. The TCI state corresponding to the TRS resource can be understood as the TCI state used by the network device to send the TRS resource, or the TCI state used by the network device to send the TRS resource corresponding to the TRS resource. Therefore, the QCL resources (such as CSI-RS resources) in the TCI state indicated by the network device to the terminal device, the QCL resources (such as TRS resources) in the TCI state corresponding to the CSI-RS resource, and the QCL resources (such as SSB resources) in the TCI state corresponding to the TRS resource constitute a QCL chain. The source QCL resource of this QCL chain is an SSB resource; therefore, the reference signal associated with the QCL type D reference signal of this TCI state is the SSB corresponding to this SSB resource.

[0255] It should be noted that the three descriptions of TCI state, TCI-state, and TCI state in this article can be used interchangeably.

[0256] In this application, "<" indicates less than, and "≤" indicates less than or equal to. The examples provided in this application are merely illustrative and do not constitute a limitation on this application. "<" and "≤" in the examples can be used interchangeably, and this application does not impose any specific limitations. ">" indicates greater than, and "≥" indicates greater than or equal to. ">" and "≥" in the examples can be used interchangeably, and this application does not impose any specific limitations. The examples provided in this application are merely illustrative and do not constitute a limitation on this application. In this application, "high" can specifically mean greater than or greater than or equal to, and "low" can specifically mean less than or less than or equal to.

[0257] In this application, the terms "cell," "serving cell," and "component carrier (CC)" are used interchangeably. A serving cell can be a primary cell (Pcell), a secondary cell (Scell), or a primary secondary cell (PScell). A cell with a primary component carrier (PCC) can be called a Pcell, and a cell with a secondary component carrier (SCC) can be called an Scell. Furthermore, a cell can also be a neighboring cell of the serving cell (the cell corresponding to an additional PCI), a candidate cell, etc.

[0258] The above description of the terminology is for ease of understanding only and does not limit the scope of protection of the embodiments of this application.

[0259] In the aforementioned measurement result reporting, it is either periodic or semi-persistent or aperiodic reporting triggered by instruction signaling from the network device; that is, the timing of reporting is determined by the network device. This approach results in significant uplink resource overhead. Specifically, in periodic and semi-persistent measurement reporting, the terminal device needs to report measurement results every cycle, and these results may be meaningless to the network device. For example, the current measurement result may be no different from the previously reported result (e.g., the optimal beam has not changed), making the reporting of such a result meaningless and wasting uplink resources.

[0260] In addition, since the terminal device determines whether the event triggering conditions are met, and then triggers the reporting of event-related measurement reports, the network device cannot know which cells have events or which events have occurred in the cells.

[0261] In view of this, this application provides a method and apparatus for reporting measurement results, aiming to enable terminal devices to report measurement results related to at least one event occurring in one or more cells, thereby reducing uplink resource overhead and achieving reasonable resource allocation.

[0262] The following will describe in detail, with reference to the accompanying drawings, the method for reporting measurement results provided in the embodiments of this application, which can be applied to the above. Figure 1 The communication system shown. It should be understood that the embodiments of this application can be applied to scenarios where the sending end and the receiving end communicate, for example, the embodiments of this application can be applied to uplink, downlink, or sidelink communication scenarios.

[0263] It should also be understood that the embodiments shown below do not specifically limit the structure of the execution subject of the method provided in the embodiments of this application, as long as it is possible to communicate according to the method provided in the embodiments of this application by running the code or program that records the method provided in the embodiments of this application. For example, the method provided in the embodiments of this application can be executed by a first device and a second device. Unless otherwise specified, the "first device" in this application can refer to the first device itself (e.g., a terminal device), or a component in the first device (e.g., a communication module, processor, circuit, chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core), or a chip system, or it can be a logic module or software that can implement all or part of the functions of the first device. The "second device" in this application can refer to the second device itself (e.g., a network device), or a component in the second device (e.g., a communication module, processor, circuit, chip), or it can be a logic module or software that can implement all or part of the functions of the second device.

[0264] Figure 5 This is a flowchart illustrating a method for reporting measurement results provided in an embodiment of this application. Figure 5 As shown, the method 500 includes the following steps.

[0265] S510, the first device (e.g., a terminal device) obtains configuration information.

[0266] This configuration information is used to indicate information about X events corresponding to M cells, where M and X are integers greater than or equal to 1.

[0267] It is understandable that "X events corresponding to M cells" means: M cells are associated with X events; M cells correspond to X events; M cells support X events; M cells are configured with X events; or the sum of the number of events supported (or configured) by each of the M cells is X. Optionally, each cell can be associated with one or more events, and the one or more events associated with each cell can be the same or different, for example, partially the same or completely different; this application does not limit this.

[0268] Optionally, the configuration information may include information about M cells and information about X events. Correspondingly, the first device learns about the M cells and X events based on the configuration information.

[0269] Optionally, the configuration information may further include the association between M cells and X events; in other words, the configuration information includes information about the X events corresponding to the M cells; or, the configuration information includes the association between each of the M cells and one or more of the X events. Correspondingly, the first device learns about the X events corresponding to the M cells based on the configuration information.

[0270] For example, the configuration information includes the index or identifier of each cell in M ​​cells, and the index or identifier of each event in X events. Optionally, the event index included in the configuration information indicates that the event has been activated, or the configuration information includes information on whether the event is activated.

[0271] For example, the configuration information may include one or more cell tables (or indexes of one or more cell tables) and one or more event tables (or indexes of one or more event tables). A cell table may include one or more cells, and an event table may include one or more events. Thus, based on the indexes of the cell tables and the event tables included in the configuration information, the first device can determine the cells contained in the cell tables and the events contained in the event tables.

[0272] For example, the configuration information includes the values ​​of M and X, such as M=2 and X=4.

[0273] For example, suppose there are M = 2 cells, such as cell A and cell B, where cell A is associated with events 1 and 2, and cell B is associated with events 3 and 4, then X = 4; or, cell A is associated with event 1, and cell B is associated with events 2, 3, and 4, then X = 4; or, cell A can be associated with events 1 and 3, and cell B can be associated with events 2, 3, and 4, then X = 5; or, cell A can be associated with events 1 and 4, and cell B can be associated with events 1, 2, 3, and 4, then X = 6; or, both cell A and cell B are associated with events 1, 2, 3, and 4, then X = 8.

[0274] Optionally, this application does not limit the number of configuration information items, which can be one or more. If it is a single configuration information item, then the configuration information is used to indicate information about X events corresponding to M cells. If it is multiple configuration information items, for example, x items, x = M, then each of the x configuration information items is used to indicate information about an event corresponding to one of the M cells. Alternatively, if x < M, then there is a configuration information item used to indicate information about events corresponding to multiple cells in the M cells. In short, the x configuration information items are used to jointly configure information about an event corresponding to one of the M cells. The specific configuration method is not limited.

[0275] Further optionally, method 500 further includes: the second device sending an activation signaling to the first device to activate some or all of the events in the configured or protocol-specified events (i.e., X events corresponding to M cells).

[0276] Further optionally, method 500 further includes: the second device sending a deactivation signaling to the first device to deactivate some or all of the configured or protocol-specified events (i.e., X events corresponding to M cells).

[0277] The aforementioned activation or deactivation signaling can be carried in RRC, MAC CE, or DCI. Optionally, the activation or deactivation signaling can be carried in the same signaling as the configuration information.

[0278] For example, suppose the second device configures M = 2 cells (e.g., cell #1 and cell #2) to the first device, and the protocol specifies that the second device configures events #1, #2, #3, and #4 to the first device. This configuration information includes the identifier of the event corresponding to cell #1. This identifier can be an event index or information indicating whether the event is active. Similarly, this configuration information also includes the identifier of the event corresponding to cell #2. This identifier can be an event index or information indicating whether the event is active. The activation information is indicated by a bitmap, with each bit corresponding to whether an event is active. For example, the bitmap size is 4 bits, where a bit value of 1 indicates that the corresponding event is active, a bit value of 0 indicates that the corresponding event is not active, and vice versa. When the bitmap corresponding to the activation information of cell #1 is 1010, it indicates that events 1 and 3 are active, and events 2 and 4 are not active. When event 1 and / or event 3 occurs in cell #1, the measurement results related to event #1 and / or event #3 can be reported.

[0279] The acquisition of configuration information for the first device includes, but is not limited to, the following two implementation methods.

[0280] In one implementation, this configuration information comes from the network side.

[0281] For example, the configuration information may be indicated or configured by the network device through signaling. Optionally, the signaling may be RRC signaling, MAC CE signaling, or DCI signaling. The specific implementation method is shown in step S501.

[0282] S501, the second device (e.g., a network device) sends (or instructs) configuration information to the first device;

[0283] Accordingly, the first device receives configuration information from the second device.

[0284] In another implementation, the configuration information can be predefined or preconfigured according to a protocol. Predefinition can include predefined features, such as protocol definitions, while preconfiguration can be achieved by pre-storing corresponding codes, tables, functions, text, strings, or other means that can be used to indicate relevant information (e.g., configuration information) in network devices and / or terminal devices. This application does not limit the specific implementation method.

[0285] The determination of X events corresponding to M cells includes, but is not limited to, the following scenarios.

[0286] In scenario one, the X events corresponding to the M cells are determined based on the indication information in step S502. In other words, the X events are events supported by the terminal device, or events indicated by the terminal device through the indication information. In this scenario, the network device does not need to configure the information of these X events to the terminal device.

[0287] Scenario 2: The X events corresponding to the M cells are configured by the network device, meaning the network device itself configures (or selects) X events. In this scenario, the terminal device can be assumed to support all events or only these X events. In this case, the terminal device does not need to indicate the events it supports to the network device.

[0288] Scenario 3: The X events corresponding to the M cells are determined based on the indication information in step S502 and the events configured by the network device. For example, the network device is configured with at least one event, and the terminal device supports at least one event. The X events are determined based on a combination of the at least one event configured by the network device and the at least one event supported by the terminal device.

[0289] Scenario 4: The X events corresponding to the M cells are predefined or preconfigured by the protocol.

[0290] Optionally, the X events may include at least one of the following: the first beam quality is lower than or equal to a first threshold; the second beam quality is higher than or equal to a second threshold; the second beam quality is higher than or equal to a third threshold of the first beam quality; the absolute difference between the second beam quality and the first beam quality is lower than or equal to a fourth threshold; the first beam quality is lower than or equal to a fifth threshold, and the second beam quality is higher than or equal to a sixth threshold; the first beam quality is lower than or equal to a preset beam quality seventh threshold; the first beam is not among the K best quality beams; the second beam quality is higher than or equal to an eighth threshold of the worst quality reference signal among the reference signals associated with the activated TCI state(s); the second beam quality is higher than or equal to a ninth threshold of the worst quality reference signal among the reference signals associated with the activated TCI state(s); there are S second beams whose beam quality is higher than or equal to a tenth threshold of the first beam quality, where S is an integer greater than or equal to 2; or, there is at least one second beam quality higher than or equal to an eleventh threshold of the beam quality of a configured reference signal.

[0291] The first beam represents the serving beam, i.e. the current serving beam. For example, the first beam can be at least one of the following: a reference signal in the currently indicated TCI-state whose QCL type is QCL type D; a reference signal associated with the reference signal in the currently indicated TCI-state whose QCL type is QCL type D (i.e., an SSB with a QCL relationship to the reference signal of QCL type D); a reference signal in the UL TCI-state where the QCL type is type D in the current uplink transmission (PUSCH / PUCCH / SRS / CSI-RS / physical random access channel (PRACH)); a reference signal in the downlink or joint TCI-state (DLorjoint TCI-state) where the QCL type is type D in the current downlink transmission (physical downlink control channel (PDCCH) / physical downlink shared channel (PDSCH) / SRS / CSI-RS); a reference signal in the UL TCI-state where the QCL type is type D in the current uplink transmission (PUSCH / PUCCH / SRS / CSI-RS / PRACH). In a TCI-state, a reference signal with QCL type D corresponds to an SSB that satisfies the QCL type D relationship; in the current downlink transmission (PDCCH / PDSCH / SRS / CSI-RS), a reference signal with QCL type D corresponds to an SSB that satisfies the QCL type D relationship; one or more reference signals configured or indicated by the network device for monitoring the first beam; the reference signal with the worst signal quality among the reference signals associated with the active TCI state(s); or, the reference signal with the best signal quality among the reference signals associated with the active TCI state(s). The aforementioned indicated TCI-state can be one or more of the indicated joint TCI state, DL TCI state, or UL TCI state.

[0292] The second beam refers to a beam different from the serving beam, also known as a new beam, such as a beam from the current serving cell or a beam from a candidate cell / neighboring cell. For example, the second beam can be at least one of the following: a reference signal associated with activated TCI states (excluding the indicated TCI state); one or more reference signals configured or indicated by the network device for monitoring the second beam; or, a reference signal associated with configured TCI states (excluding the indicated TCI state).

[0293] Optionally, the first beam may include one or more beams, and the second beam may also include one or more beams. This application does not specifically limit the number of the first beam and the second beam. The number of the first beam / second beam can be determined based on the number of UL / DL / joint TCI-states indicated by the network device, such as the UL / DL / joint TCI-states indicated by DCI signaling; or, the number of the first beam / second beam (or the maximum number of the first beam / second beam) can be predefined or preconfigured.

[0294] Optionally, the reference signal can be SSB, CSI-RS, SRS, or a path loss reference signal, etc.

[0295] Optionally, beam quality can be characterized by at least one of the following: reference signal received power (RSRP), signal to interference plus noise ratio (SINR), Layer 1 reference signal received power (L1-RSRP), Layer 1 signal to interference plus noise ratio (L1-SINR), synchronization signal based signal to interference plus noise ratio (SS-SINR), synchronization signal based reference signal received power (SS-RSRP), (CSI reference signal based signal to nise and interference ratio (CSI-RSRP), channel state information reference signal based signal to interference plus noise ratio (CSI-SINR), or channel quality indicator (CQI).

[0296] Optionally, the thresholds in this application, such as the first threshold, the second threshold, ..., or the eleventh threshold, can be predefined or preconfigured, configured, indicated by signaling, or determined by the UE, and there is no limitation on this. The thresholds can be the same or different. Two thresholds can be associated, that is, an associated threshold can be derived from one threshold, or they can be unassociated. The magnitude relationship between two thresholds is not limited. The unit of each threshold can be decibels (dB) or decibel-milliwatts (dBm), etc.

[0297] The following examples illustrate the X events listed above.

[0298] Example 1: The quality of the first beam is lower than or equal to the first threshold.

[0299] To distinguish it, this event is called event #A. In other words, event #A means that the current service beam quality is less than or equal to a certain threshold, such as the first threshold (e.g., threshold 1).

[0300] Example 2: The quality of the second beam is higher than or equal to the second threshold.

[0301] To distinguish it, this event is called event #B. In other words, event #B indicates that there exists at least one new beam (i.e., the second beam) whose beam quality is greater than or equal to a threshold, such as the second threshold (e.g., threshold 2).

[0302] As an example, the new beam can be a reference signal associated with the activation TCI-states (other than the indicated TCI-state), or it can be one of the reference signals configured by the network device (such as a reference signal configured by the network device for measurement, or a reference signal configured by the network device for the terminal device to monitor the occurrence of an event or event #B) (other than the reference signal corresponding to the currently serving beam).

[0303] Example 3: The quality of the second beam is higher than or equal to the quality of the first beam at the third threshold.

[0304] To distinguish it, this event is called event #C. In other words, event #C indicates that there exists at least one new beam with a beam quality greater than that of the currently serving beam, and the difference between the beam quality of the new beam and the beam quality of the currently serving beam is greater than or equal to a threshold, such as the third threshold (e.g., threshold 3).

[0305] Alternatively, event #C can also be described as: the quality of the first beam is lower than or equal to the quality of the second beam by a threshold, where the threshold can be a value less than 0 dB. Optionally, "the quality of the first beam is lower than or equal to the quality of the second beam by a threshold" can also be considered as an event different from event #C, and this is not limited.

[0306] Example 4: The (absolute) difference between the quality of the second beam and the quality of the first beam is less than or equal to the fourth threshold.

[0307] To distinguish them, this event is referred to as event #D. In other words, event #D indicates that the difference between the beam quality of at least one new beam and the beam quality of the currently serving beam is less than or equal to a threshold. Alternatively, event #D indicates that the absolute value of the difference between the beam quality of at least one new beam and the beam quality of the currently serving beam is less than or equal to a threshold, such as the fourth threshold (e.g., threshold 4).

[0308] The above are merely illustrative examples for ease of understanding, and the embodiments of this application are not limited thereto. The X events may also include other events. Several more examples are listed below.

[0309] Example 5: The quality of the first beam is lower than or equal to the fifth threshold, and the quality of the second beam is higher than or equal to the sixth threshold. Optionally, the sixth threshold is greater than or equal to the fifth threshold.

[0310] To distinguish them, this event is called event #E. In other words, event #E indicates that there is at least one new beam with a beam quality greater than a certain threshold, and the beam quality of the currently serving beam is less than or equal to a threshold.

[0311] Example 6: The quality of the first beam is lower than or equal to a preset beam quality seventh threshold. For example, the quality of the first beam is lower than or equal to the seventh threshold of the SSB quality of the first beam QCL type D. Optionally, the seventh threshold is less than 0 dB, or in other words, the SSB quality of the first beam QCL type D is higher than or equal to the seventh threshold of the first beam quality; optionally, the seventh threshold is greater than 0 dB. For example, the currently serving beam is a CSI-RS with QCL type D in the currently indicated TCI state, and the reference signal of the QCL type D CSI-RS is an SSB. The quality of the CSI-RS is lower than the quality of the SSB by a threshold 7, in which case the threshold 7 is less than 0 dB.

[0312] To distinguish it, this event is referred to as event #F. For example, the current serving beam is the CSI-RS with QCL type type D in the currently indicated TCI-state, and the preset beam is the reference signal (such as SSB) of the CSI-RS that satisfies QCL type type D. The quality of the CSI-RS is lower than or equal to the quality of the reference signal (such as SSB) by a threshold (i.e., the seventh threshold). At this time, the seventh threshold is a value less than 0dB.

[0313] The event #F can also be described as: the preset beam quality is higher than or equal to the seventh threshold of the first beam quality, at which time the seventh threshold is a value greater than 0dB.

[0314] Example 7: The first beam does not belong to the K best quality beams. The value of K can be an integer greater than or equal to 1. Optionally, the K best quality beams can exist in the form of a beam set / group / table.

[0315] To distinguish it, this event is called event #G. In other words, event #G indicates that the beam quality of the current serving beam is poor, for example, it is lower than or equal to a certain preset threshold. Therefore, when the beam quality of the first beam is lower than or equal to the preset threshold, the terminal device can trigger the reporting of event #G.

[0316] Example 8: The quality of the second beam is higher than or equal to the eighth threshold of the reference signal with the worst signal quality among the reference signals associated with the activated TCI state(s).

[0317] To distinguish it, this event is referred to as event #H. In other words, event #H indicates that there exists at least one new beam whose beam quality is greater than or equal to the worst-quality reference signal among the reference signals associated with the activated TCI state(s), and the difference between the beam quality of the new beam and the beam quality of the worst-quality reference signal is greater than or equal to a threshold, such as the eighth threshold (e.g., threshold 8).

[0318] Example 9: The quality of the second beam is higher than or equal to the ninth threshold of the reference signal with the worst signal quality among the reference signals associated with the activated TCI state(s).

[0319] To distinguish it, this event is called event #I. In other words, event #I indicates that there exists at least one new beam whose beam quality is greater than or equal to the best-quality reference signal among the reference signals associated with the activated TCI state(s), and the difference between the beam quality of the new beam and the beam quality of the best-quality reference signal is greater than a threshold, such as the ninth threshold (e.g., threshold 9).

[0320] Example 10: There exist S second beams whose beam quality is higher than or equal to the tenth threshold of the first beam quality. Optionally, the value of S can be predefined or preconfigured by the protocol, or it can be indicated or configured by the network device through signaling.

[0321] To distinguish them, this event is referred to as event #J. In other words, event #J indicates that there are multiple new beams whose beam quality is greater than or equal to the beam quality of the currently serving beam, and the difference between the beam quality of the new beam and the beam quality of the currently serving beam is greater than a threshold, such as the tenth threshold (e.g., threshold 10).

[0322] Example 11: There exists at least one second beam quality that is higher than or equal to the eleventh threshold of the beam quality of the configured reference signal.

[0323] To distinguish it, this event is referred to as event #K. In other words, event #K indicates that there exists at least one new beam whose beam quality is greater than or equal to the beam quality of the configured reference signal, and the difference between the beam quality of the new beam and the beam quality of the configured reference signal is greater than a threshold, such as the eleventh threshold (e.g., threshold 11).

[0324] Taking event #A as an example, if event #A occurs, it indicates that the following situation has occurred: the quality of the first beam is lower than the first threshold, or the quality of the first beam is equal to the first threshold. For example, if the terminal device determines through measurement that the quality of the first beam is lower than or equal to the first threshold, then event #A is determined to have occurred. Taking event #B as an example, if event #B occurs, it indicates that the following situation has occurred: the quality of the second beam is higher than the first threshold, or the quality of the second beam is equal to the second threshold. For example, if the terminal device determines through measurement that the quality of the second beam is higher than or equal to the second threshold, then event #B is determined to have occurred. In other words, the occurrence of an event triggers a reporting mechanism, specifically, it triggers the reporting of the measurement results corresponding to that event.

[0325] It is understandable that in the above examples, the situation regarding "equal to" can be either a situation where the event has occurred or a situation where the event has not occurred. That is, the events defined above may not include "equal to", or they may be used for other purposes, which are not limited.

[0326] The X events can be any one or more of the aforementioned events #A to #K, or they can be limited to the aforementioned events. This application does not limit the specific events.

[0327] The event triggering and reporting of X events corresponding to M cells can be associated with one or more measurement report configurations. Examples are given below using scenarios one, two, and three.

[0328] Scenario 1: Events occurring in X events corresponding to M cells are associated with a measurement report configuration. This measurement report configuration can be CSI-reportConfig, event-triggered reporting configuration, or event-triggered measurement report configuration, etc. Specifically, the CSI-reportConfig is configured with an indication (e.g., reportConfigType is configured as EventTriggered) to indicate that the report is configured for event-triggered reporting. Alternatively, the CSI-reportConfig may contain event-related information, such as the event index and the corresponding threshold, indicating that the report is configured for event-triggered reporting. Or, the event-triggered reporting configuration may be configured through a dedicated information element (IE), such as L1-EventTriggered-CSI-ReportConfig. In other words, in this method, a measurement report configuration can be associated with one or more cells or one or more CCs, and a measurement report configuration can be associated with one or more events corresponding to one or more cells or CCs. That is, one measurement report corresponds to one or more events of one or more cells or CCs.

[0329] Optionally, the measurement report configuration can be the same as the configuration information in step S510 above, in which case the configuration information and measurement report configuration in the application file can be used interchangeably. Optionally, the measurement report configuration can also be different from the above configuration information. For example, the measurement report configuration may include configuration information, or the above configuration information may include the measurement report configuration, or the measurement report configuration and the above configuration information may be two independent configuration information, without limitation.

[0330] Understandably, assuming a measurement report configuration associates M cells, then the network device can send a measurement report configuration for the M cells, and the terminal device can report a measurement report. That is, the measurement report includes the measurement results of at least one event associated with one of the M1 cells. In other words, the measurement report includes the measurement results of at least one event that occurred on one of the M1 cells.

[0331] For example, the measurement report configuration includes one or more of the following information, or in other words, the measurement report configuration is associated with one or more of the following: information about one or more cells in the M cells; information about one or more events corresponding to (or supported by) one or more cells in the M cells; reference signal measurement resources corresponding to one or more events in one or more cells in the M cells; event triggering reporting resources corresponding to one or more cells in the M cells; scheduling request or indication resources corresponding to one or more cells in the M cells; the reporting quantity of events corresponding to one or more cells in the M cells; or, the number of reporting parameters (or reporting quantity) of events corresponding to one or more cells in the M cells.

[0332] The following provides an example of the measurement report configurations listed above.

[0333] Example 1: Information about one or more cells out of M cells.

[0334] For example, the index or identifier of a serving cell can be a primary cell (Pcell), a secondary cell (Scell), or a primary secondary cell (PScell). A Pcell can also be called a cell on a primary component carrier (PCC), and an Scell ​​can be called a cell on a secondary component carrier (SCC). Another example is the cell corresponding to an additional physical cell identifier (additional PCI), which is a neighboring cell of the serving cell. The PCI can also be called the non-serving cell corresponding to the additional PCI, or the cell corresponding to the additional PCI associated with the active TCIstates; it can also be a candidate cell index; a CC index; or a PCI.

[0335] Example 2: One or more event information corresponding to one or more cells among M cells.

[0336] One or more event information corresponding to one or more cells in M ​​cells can refer to: one event information corresponding to one cell in M ​​cells, multiple event information corresponding to one cell in M ​​cells, one event information corresponding to multiple cells in M ​​cells, or multiple event information corresponding to multiple cells in M ​​cells.

[0337] For example, the event index corresponding to each cell, or one or more bits of one or more events supported by each cell, assuming the event information includes R bits. Used to indicate the event index This indicates rounding up. In this case, it can be understood as follows: a cell contains F events, and multiple cells may contain the same events, meaning X is greater than or equal to F, where F is an integer greater than 1. Alternatively, suppose the event information includes X bits, with each of the X bits corresponding to one of the X events. The x-th bit of the X bits indicates whether the corresponding cell supports the x-th event, where x = 1, 2, ..., X. For example, if the x-th bit is "0", it indicates that the corresponding cell does not support the x-th event; or if the x-th bit is "1", it indicates that the corresponding cell supports the x-th event, and vice versa. If the measurement report is configured to associate with only one cell, the one or more event information corresponds to that cell. If the measurement report is configured to associate with multiple cells, each cell can be configured with one or more event information independently, or multiple cells can be associated with the same one or more event information.

[0338] Example 3: Reference signal measurement resources corresponding to one or more events in one or more of the M cells.

[0339] The reference signal measurement resource can be configured individually for each event, or the same reference signal measurement resource can be configured for multiple events. The specific reference signal resource refers to the reference signals corresponding to the current beam and the new beam, as mentioned above, and can be explicitly configured or implicitly determined. For example, if the measurement report is configured to be associated with only one cell, the reference signal measurement resource corresponds to that cell; if the measurement report is configured to be associated with multiple cells, each cell independently configures one or more reference signal measurement resources corresponding to its events.

[0340] Example 4: Event-triggered reporting resources for one or more of the M cells are used to carry beam measurement results triggered by events, such as periodic PUCCH resources, aperiodic PUSCH resources, semi-persistent PUCCH resources, and semi-persistent PUSCH resources. Only one reporting resource can be configured, meaning each cell corresponds to the same reporting resource, or each cell can have its own reporting resource configured.

[0341] Optionally, the event-triggered reporting resource can be replaced with PUCCH resource, PUSCH resource, event-triggered reporting resource, UE-triggered reporting resource, event-triggered second channel resource, event-triggered second uplink resource, etc.

[0342] Example 5: One or more cells out of M cells correspond to scheduling request or indication resources, which are used to carry indication information about an event. This indication information is used to indicate to network devices that beam measurement results triggered by the event need to be reported and / or that an event has occurred, or to request reporting resources triggered by the event. Only one reporting indication resource can be configured, meaning each cell corresponds to the same scheduling request or indication resource, or each cell can have its own scheduling request or indication resource configured separately.

[0343] Optionally, the scheduling request or indication resource can be described in other ways as: reporting indication resource, PUCCH indication resource, PUSCH indication resource, scheduling request resource, pre-indication resource, pre-notification resource, event-triggered reporting scheduling request resource, event-triggered first channel resource, event-triggered first uplink resource, or UE-triggered reporting scheduling request resource.

[0344] Example 6: The reported amount (or reporting parameters) when one or more events occur in one or more cells out of M cells, and / or the number of reported events for one or more cells out of M cells. The reported amount for each event can be configured by the network or specified by the protocol. Similarly, if the report is configured to be associated with one cell, then the reported amount and / or the number of reported amounts for each event corresponds to one cell; if the report is configured to be associated with multiple cells, that is, each cell can correspond to the same reported amount and / or the same number of reported amounts for each event, or each cell can be configured with its own reported amount and / or the same number of reported amounts for each event.

[0345] The reported quantity (or reported parameters) may include one or more of the following:

[0346] (1) Report parameter #1, the current serving beam index or the first beam index, can also be understood as the reference signal index of type D in the currently indicated TCI-state; or, the reference signal (e.g., SSB) index corresponding to the reference signal of type D in the currently indicated TCI state that satisfies the QCL type D relationship; or, the reference signal (e.g., SSB) index of type D in the UL TCI-state applied by the current uplink transmission (PUSCH / PUCCH / SRS / PRACH); or, the reference signal (e.g., SSB) index of type D in the downlink or joint TCI-state (DLorjointTCI-state) applied by the current downlink transmission (PDCCH / PDSCH / CSI-RS).

[0347] (2) Report parameter #2, the beam quality of the current serving beam, or the first beam quality. For example, the first beam quality can be represented by the RSRP, or SINR, or L1-RSRP, or L1-SINR, or SS-RSRP, or CSI-RSRP, or SS-SINR, or CSI-SINR corresponding to the current serving beam.

[0348] (3) Report parameter #3, the index of the second beam, can also be understood as the index of the reference signal with QCL type type D in the activated TCI-states (excluding the indicated TCI-state), or it can be one or more reference signals (excluding the reference signal corresponding to the current service beam) in the reference signals configured by the network device (such as the reference signal configured by the network device for measurement, or the reference signal configured by the network device for the terminal device to monitor the occurrence of events).

[0349] (4) Report parameter #4, second beam quality. For example, the second beam quality can be represented by the RSRP, or SINR, or L1-RSRP, or L1-SINR, or SS-RSRP, or CSI-RSRP, or SS-SINR, or CSI-SINR corresponding to the second beam.

[0350] (5) Report parameter #5, one or more cell information, which can be understood as which cell the reported measurement report configuration corresponds to, or which cell's reference signal resource the reported measurement result is measuring (i.e., the cell corresponding to the reference signal resource associated with the reported measurement report configuration). For example, cell information can be the handover candidate cell ID, the non-serving cell ID (additional PCI), the component carrier (CC) index, or the PCI.

[0351] (6) Report parameter #6, the reason why the current service beam quality is below a threshold (e.g., the first threshold). For example, network equipment beam misalignment, terminal equipment receiving beam misalignment, transmitting and receiving beam misalignment, etc. The term "misalignment" can also be replaced with terms such as "expired" or "invalid". Alternatively, indicate whether to trigger a CSI-RS set measurement with "repetition" set to "on" to poll the receiving beam on the UE side.

[0352] (7) Report parameter #7, reference signal resource set index, such as CSI-RS resource set index, CSI-IM resource set index, channel status information synchronization signal and PBCH block (CSI-SSB) resource set index, or reference signal resource set index configured by the network device for the terminal device to monitor the occurrence of events, to indicate which reference signal resource set the reported current serving beam and / or second beam belongs to.

[0353] (8) Report parameter #8, report configuration index, such as CSI report configuration identifier (CSI-ReportConfigId), or event-triggered reporting configuration index.

[0354] (9) Report parameter #9, event information, such as the index of the event that occurred, or one or more bits indicating whether the event has occurred. For example, the event information includes R bits. An index used to indicate the events that have occurred. This indicates rounding up. In this case, it can be understood that a cell contains F events, and multiple cells may contain the same events, meaning X is greater than or equal to F, where F is an integer greater than 1. For example, event information may consist of X bits, each corresponding to one of the X events. The x-th bit in the X bits indicates whether the event corresponding to that x-th bit has occurred, where x = 1, 2, ..., X. For instance, if the x-th bit is "0", it indicates that the event corresponding to that x-th bit has occurred; or, if the x-th bit is "1", it indicates that the event corresponding to that x-th bit has occurred. Information about occurred events or event information requiring the reporting of relevant measurement results in this application can all adopt the aforementioned representation method.

[0355] In this application, the information of events occurring in the X events corresponding to the M cells can be simply referred to as event information or event details, representing information related to the events that occurred. As an example, the event information in the X events corresponding to the M cells includes at least one of the following: the index of the cell where the event occurred, the index of the event itself, the number of cells where the event occurred, the number of events, and the content of the event.

[0356] (10) Report parameter #10, capabilityindex, used to determine the maximum number of SRS ports.

[0357] (11) Report parameter #11, channel state information, which may include one or more of the following: precoding matrix indication (PMI), rank indication (RI), channel quality information (CQI), and layer indication (LI).

[0358] The above-mentioned reporting parameters are merely illustrative examples for ease of understanding. The embodiments of this application are not limited to these and may include other reporting parameters.

[0359] Scenario 2: Each of the M cells (e.g., M > 1) is associated with a measurement report configuration. In other words, all cells that report configuration event-related information or are triggered by a configuration event are associated with a single measurement report configuration. This configuration can be a CSI-reportConfig or an event-triggered reporting configuration, etc. In other words, in this approach, one measurement report configuration is associated with one cell or one CC (Cycles Targeting Component). That is, one measurement report corresponds to one cell or one CC, or one measurement report configuration is associated with the reference signal measurement resource corresponding to a cell or a CC event. In other words, M cells or M CCs correspond to one or more measurement report configurations, which in turn correspond to one or more measurement reports.

[0360] Understandably, assuming a measurement report configuration is associated with a cell, the network device can send M measurement report configurations for M cells, and the terminal device can report M1 measurement reports. That is, each measurement report includes the measurement result of at least one event associated with one of the M1 cells. In other words, each measurement report includes the measurement result of at least one event that occurred on one of the M1 cells.

[0361] For example, the measurement report configuration may include one or more of the following information, or in other words, the measurement report configuration may be associated with one or more of the following: cell information; one or more event information corresponding to a cell; reference signal measurement resources corresponding to one or more events corresponding to a cell; event triggering reporting resources corresponding to a cell; scheduling request or indication resources corresponding to a cell; the reporting quantity of events corresponding to a cell; or, the number of reporting quantities corresponding to each of the one or more events corresponding to a cell, wherein each event may correspond to one or more reporting quantities. For specific parameter interpretations, please refer to the relevant description in Case 1 above; for brevity, it will not be repeated here.

[0362] Scenario 3: Among M cells (e.g., M > 1), there may be multiple cells associated with a single measurement report configuration, one cell associated with a single measurement report configuration, or one cell associated with multiple measurement report configurations. This measurement report configuration can be a CSI-reportConfig, an event-triggered reporting configuration, etc. In other words, in this method, one measurement report configuration can be associated with one cell or one CC, or one measurement report configuration can be associated with multiple cells or multiple CCs. That is, M cells or M CCs correspond to T measurement report configurations, which in turn correspond to T measurement reports, where T is an integer greater than 1.

[0363] As an example, assuming M=3 and T=2, there are three cells (e.g., cell 1, cell 2, and cell 3) corresponding to two measurement report configurations (e.g., measurement report configuration #1 and measurement report configuration #2). For example, cell 1 and cell 2 correspond to measurement report configuration #1, and cell 3 corresponds to measurement report configuration #2. When an event occurs in cell 1 and / or cell 2, the terminal device can report the measurement results of the event that occurred in cell 1 and / or cell 2 as indicated by measurement report configuration #1. When an event occurs in cell 3, the terminal device can report the measurement results of the event that occurred in cell 3 as indicated by measurement report configuration #2.

[0364] As an example, assuming M=3 and T=4, there are three cells (e.g., cell 1, cell 2, and cell 3) corresponding to four measurement report configurations (e.g., measurement report configuration #1, measurement report configuration #2, measurement report configuration #3, and measurement report configuration #4). For instance, cell 1 corresponds to measurement report configuration #1, cell 2 corresponds to measurement report configuration #2 and measurement report configuration #3, and measurement report configuration #2 and measurement report configuration #3 are associated with different types of reference signal measurement resources in cell 2 (e.g., SSB and CSI-RS, respectively). Cell 4 corresponds to measurement report configuration #4. When an event occurs in cell 1, the terminal device can report the measurement result of the event in cell 1 indicated by measurement report #1 corresponding to measurement report configuration #1. When an event occurs in cell 2 and the event corresponding to the monitored SSB occurs, the terminal device can report the measurement result of the event in cell 2 indicated by measurement report #2 corresponding to measurement report configuration #2. When an event occurs in cell 3, the terminal device can report the measurement result of the event in cell 3 indicated by measurement report configuration #4 corresponding to measurement report configuration #4.

[0365] For example, the measurement report configuration includes one or more of the following information, or in other words, the measurement report configuration is associated with one or more of the following: information about one or more cells out of M cells; information about one or more events corresponding to one or more cells out of M cells; reference signal measurement resources corresponding to one or more events corresponding to one or more cells out of M cells; event triggering reporting resources corresponding to one or more cells out of M cells; scheduling request or indication resources corresponding to one or more cells out of M cells; the number of events reported by one or more cells out of M cells; or, the number of reporting parameters for events corresponding to one or more cells out of M cells. For specific parameter interpretations, please refer to the relevant description in Scenario 1 above; for brevity, it will not be repeated here.

[0366] Optionally, the above-mentioned one or more measurement report configurations can be associated with event-related reference signal measurement resources of one or more cells. Here, reference signal resources refer to the reference signal resources for measurements corresponding to the event, or the reference signal resources for measurements corresponding to the terminal device.

[0367] In one implementation, the network device is configured with reference signal resource information for measurements corresponding to different events.

[0368] Based on this method, the terminal device determines the reference signal resource, including: the terminal device receiving indication information, which indicates the reference signal resource. The information of the reference signal resource and the information of X events can be carried in the same signaling, such as the configuration information in step S510 including the information of X events and the information of the reference signal resource; or they can be carried in different signaling, which is not limited thereto.

[0369] As an example, a network device configures reference signal resources (one or more reference signals), reference signal resource sets (containing one or more reference signals), or reference signal resource settings (containing one or more reference signal resource sets) corresponding to different events, to monitor whether a certain event has occurred. If an event occurs, a report is triggered. Alternatively, the measurement result reported by a certain event corresponds to: the reference signal resource / reference signal resource set / reference signal resource configuration corresponding to that event.

[0370] Optionally, the network device may configure or associate different reference signal resources / sets of reference signal resources / configurations for different events; or, the network device may configure or associate the same reference signal resources / sets of reference signal resources / configurations for different events.

[0371] Another example is that the network device sends a measurement report configuration, also known as an event-triggered reporting configuration or event-triggered measurement report configuration, to the terminal device. This configuration is a dedicated event-triggered reporting configuration or event-triggered measurement report configuration.

[0372] For example, the measurement report configuration information may include information indicating that the report corresponds only to event-triggered measurement results, or it may include information indicating that the report can be event-triggered, or the measurement report configuration may be a dedicated RRC cell, and the terminal device may know that the configuration is an event-triggered reporting configuration. Furthermore, the measurement report configuration may also be associated with reference signal resources / reference signal resource sets / reference signal resource settings, allowing the terminal device to determine which reference signal resources' measurement results can be reported during event reporting.

[0373] Another example is the network device's configuration to send measurement reports triggered by different events to the terminal.

[0374] For example, the measurement report configuration information includes event information, such as an event index, which indicates that the measurement report configuration corresponds to a specific event. If the event occurs, it will be reported according to the corresponding configuration information.

[0375] In another implementation, different events trigger the reporting of corresponding measurement reference signal resource information.

[0376] As an example, the reference signal resources for measurements triggered by different events can be predefined as the reference signal resources corresponding to the currently serving beam. For instance, the reference signal resources for measurements triggered by different events could be reference signals with QCL type type D in the currently indicated TCI-state, or reference signals with QCL type type D in the UL TCI-state of the current uplink transmission (PUSCH / PUCCH / SRS / physical random access channel, PRACH) application, or reference signals with QCL type type D in the DLorjointTCI-state of the current downlink transmission (PDCCH / PDSCH / CSI-RS) application.

[0377] Another example is that the reference signal resources for the measurements triggered by different events can be predefined as reference signals of type D in the currently active TCI-states with QCL type.

[0378] The aforementioned predefined reference signal resources may correspond to different events or the same event, and there is no limitation on this. Furthermore, the aforementioned reference signals may be reference signals for the serving cell or reference signals for candidate cells / neighboring cells.

[0379] Optionally, before the terminal device obtains the configuration information, the terminal device may report the capability information to the network device. That is, before performing the above step S510, the method may also include the following step S502.

[0380] S502, the first device sends instruction information to the second device.

[0381] Accordingly, the second device receives instruction information from the first device.

[0382] The indication information indicates the information of the event corresponding to the first device, or in other words, the information of the event supported by the first device. This indication information can also be called terminal capability information.

[0383] As an example, specific implementation methods may include, but are not limited to: if the terminal device reports the terminal capability information, it indicates that the terminal device supports the capability; conversely, if the terminal device does not report the terminal capability information, it indicates that the terminal device does not support the capability; or, if the terminal device reports the terminal capability information, it indicates that the terminal device supports the capability; if the terminal device reports that it does not support the terminal capability, it indicates that the terminal device does not support the capability. Alternatively, if the terminal device supports capability #1, it also means that it supports capability #2. Therefore, when the terminal device reports capability information indicating support for capability #1, even if it does not report information about capability #2, it still indicates that the terminal device supports capability #2.

[0384] In this application, an event refers to an event related to a UE-initiated report, a measurement report initiated by the terminal device, a report (or measurement report) after the terminal device actively performs a measurement, or a specific condition related to a measurement report initiated by the terminal device. For example, the terminal device may actively perform measurements (such as beam measurements or channel measurements) to obtain a measurement report related to the event. Another example is that the terminal device may perform measurements based on reference signals according to the configuration of reference signal resources to obtain a measurement report related to the event. Yet another example is that the terminal device actively performs measurements and reports a measurement report related to the event when specific conditions are met. The event can also be interchanged with any of the following: trigger event, layer 1 (L1) trigger event, CSI measurement report trigger event, beam measurement report trigger event, L1 CSI report trigger event, L1 beam measurement report trigger event, etc. The naming of these events is not limited in this application.

[0385] In this application, the event-related report can be substituted with any of the following: an event-triggered or terminal device-initiated report, an event-triggered or terminal device-initiated beam report, an event-triggered or terminal device-initiated CSI report, an event-triggered or terminal device-initiated measurement report, an event-triggered or terminal device-initiated beam measurement result report, an event-triggered or terminal device-initiated interference measurement report, interference measurement report, CSI report, or beam measurement result report, etc.

[0386] Optionally, the indication information indicates at least one of the following: whether the terminal device supports the ability to trigger event reporting; one or more events corresponding to the event-triggered reporting supported by the terminal device; whether each CC (or cell) of the terminal device supports the ability to trigger event reporting; one or more events corresponding to the event-triggered reporting supported by each CC of the terminal device; the maximum number of event-triggered beam reporting configurations supported by the terminal device; the maximum number of event-triggered reporting configurations supported by each CC of the terminal device; the number of cells associated with the event-triggered beam reporting configuration; the number of events associated with each cell supported by the event-triggered beam reporting configuration; the maximum number of reporting beams supported by each event supported by the terminal device; or the maximum number of new beams (i.e., second beams) supported by each event supported by the terminal device.

[0387] In this application, event-triggered reporting can be interchanged with any of the following: event-triggered beam reporting, event-triggered channel state information (CSI) reporting, event-triggered beam measurement result reporting, or event-triggered interference measurement reporting, etc., without limitation. Optionally, event-triggered reporting can also be referred to as UE-initiated report.

[0388] In this application, the measurement report configuration can be interchanged with any of the following: event-triggered or terminal device-initiated report configuration, event-triggered or terminal device-initiated beam report configuration, event-triggered or terminal device-initiated CSIreportConfig, event-triggered or terminal device-initiated measurement report configuration, event-triggered or terminal device-initiated beam measurement result report configuration, event-triggered or terminal device-initiated interference measurement report configuration, interference measurement report configuration, CSIreportConfig, UE-initiated reportConfig, Event rigger-CSI-ReportConfig, or beam measurement result report configuration, etc. Specifically, the measurement report configuration can be CSI-reportConfig, which contains an indication (e.g., reportConfigType is configured as EventTriggered) to indicate that the report is configured for event-triggered reporting. Alternatively, the CSI-reportConfig may contain event-related information, such as the event index and the corresponding threshold, indicating that the report is configured for event-triggered reporting. Or, the measurement report configuration can be configured through a dedicated information element (IE), such as L1-EventTriggered-CSI-ReportConfig.

[0389] Below, examples are provided to illustrate the specific information indicated by the instruction messages.

[0390] Example 1: The indication information indicates whether the terminal device supports the ability to report events.

[0391] For example, whether a terminal device supports event-triggered reporting can be indicated by at least one bit. Let's assume 1 bit is used to indicate whether the terminal device supports event-triggered reporting. If this bit is set to "0", it means the terminal device supports event-triggered reporting; if this bit is set to "1", it means the terminal device does not support event-triggered reporting, and vice versa.

[0392] For example, by indicating whether or not the terminal device supports event-triggered reporting, it can be shown whether the terminal device supports this capability. If the terminal device does not report that it does not support event-triggered reporting, it can be assumed that the terminal device supports event-triggered reporting. Alternatively, if the terminal device does not report that it supports event-triggered reporting, it can be assumed that the terminal device does not support event-triggered reporting.

[0393] The above is an illustrative example, and the embodiments of this application are not limited thereto. For example, whether a terminal device supports the ability to trigger event reporting can also be indicated by a specific field. If the indication information includes the specific field, it means that the terminal device supports the ability to trigger event reporting; if the indication information does not include the specific field, it means that the terminal device does not support the ability to trigger event reporting.

[0394] Example 2: The indication information indicates that the terminal device supports events that trigger the reporting of one or more corresponding events. In short, the indication information indicates the events supported by the terminal device.

[0395] For example, the indication information may include the indexes of each event supported by the terminal device; or it may be represented in the form of a bitmap. Assuming there are events 1 to 4, if the events for which the terminal device supports event triggering reporting include events 1 and 4, the terminal device can send indication information. This indication information may include the indexes of events 1 and 4, or it may include bitmap = 1001, indicating that the terminal device supports event triggering reporting for events 1 and 4, but does not support event triggering reporting for events 2 and 3.

[0396] For example, the indication information includes indexes to various event tables supported by the terminal device, where an event table contains one or more events.

[0397] For example, the indication information includes the number of events supported by the terminal device.

[0398] For example, if a terminal does not report one or more events triggered by supported events, it means that it does not support reporting triggered by any events. Alternatively, if a terminal does not report one or more events triggered by supported events, it means that the terminal supports all events specified by the protocol.

[0399] Example 3 indicates whether each CC (or cell) of the terminal device supports the ability to trigger event reporting.

[0400] For example, whether each CC of the terminal device supports event-triggered reporting can be indicated by at least one bit. Let's assume 1 bit is used to indicate whether each CC of the terminal device supports event-triggered reporting. If this bit is set to "0", it means that each CC of the terminal device supports event-triggered reporting; if this bit is set to "1", it means that none of the CCs of the terminal device support event-triggered reporting. Assuming there are 4 CCs, 2 bits can be used to indicate whether each CC supports event-triggered reporting: if CC#0 and CC#1 of the terminal device support event-triggered reporting, and CC#2 and CC#3 do not, then the terminal device can report "00" and "01", indicating that CC#0 and CC#1 support event-triggered reporting.

[0401] For example, whether each CC of the terminal device supports event-triggered reporting can be implemented using a bitmap. Assuming there are 4 CCs, the bitmap size is 4 bits. If CC#0 and CC#1 of the terminal device support event-triggered reporting, while CC#2 and CC#3 do not, then bit "1" indicates that the terminal device's CCs support event-triggered reporting, and bit "0" indicates that the terminal device's CCs do not support event-triggered reporting. In this case, the terminal device can send bitmap="1100".

[0402] For example, by indicating whether or not to report support for event-triggered reporting, it can be instructed whether each CC of the terminal device supports event-triggered reporting. If the terminal device does not report support for event-triggered reporting, it can be assumed that each CC of the terminal device supports event-triggered reporting. Alternatively, for example, if the terminal device does not report support for event-triggered reporting, it can be assumed that each CC of the terminal device does not support event-triggered reporting.

[0403] The above is an illustrative example, and the embodiments of this application are not limited thereto. For example, whether each CC of the terminal device supports the ability to trigger event reporting can also be indicated by a specific field. If the indication information includes the specific field, it means that each CC of the terminal device supports the ability to trigger event reporting; if the indication information does not include the specific field, it means that each CC of the terminal device does not support the ability to trigger event reporting.

[0404] Example 4: The indication information indicates that each CC supported by the terminal device triggers the reporting of one or more corresponding events. In short, the indication information indicates the events supported by each CC of the terminal device.

[0405] For example, the indication information may include the index of each event supported by each CC of the terminal device; or it may be represented in the form of a bitmap. Assuming that CC#1 supports events 1, 2, and 3, if the terminal device triggers and reports events corresponding to events 1 and 3 for events supported by CC#1, the terminal device may send indication information. This indication information may include the indexes of events 1 and 3, or it may include bitmap=101, indicating that the terminal device supports event triggering and reporting for events 1 and 3, but does not support event triggering and reporting for event 2.

[0406] For example, the indication information includes an index to each event table supported by each CC of the terminal device, and an event table includes one or more events.

[0407] For example, the indication information includes the number of events supported by each CC of the terminal device.

[0408] Example 5 indicates the maximum number of event-triggered beam reporting configurations supported by the terminal device.

[0409] For example, if the maximum number of event-triggered beam reporting configurations supported by the terminal device is 4, it means that the number of measurement reports supported by the terminal device for event-triggered beam reporting can be 1, 2, 3, or 4.

[0410] Example 6 indicates the maximum number of event trigger reports configured for each CC of the terminal device.

[0411] For example, if the maximum number of event-triggered reports supported by each CC of the terminal device is 3, it means that the terminal device can support 1, 2 or 3 event-triggered measurement reports for each of the M cells.

[0412] Example 7 indicates the number of cells that the beam reporting configuration supports when the event triggers.

[0413] For example, if the event-triggered beam reporting configuration supports 4 associated cells, it means that the terminal device supports 1, 2, 3, or 4 associated cells for event-triggered beam reporting.

[0414] Example 8 indicates the number of events per cell that the event-triggered beam reporting configuration supports.

[0415] For example, if the event-triggered beam reporting configuration supports 2 events per cell, it means that the terminal device supports 1 or 2 events per cell for event-triggered beam reporting.

[0416] Example 9 indicates the maximum number of reporting beams supported for each event by the terminal device.

[0417] For example, the terminal device supports events #1 and #2, and the indication information includes that the maximum number of reporting beams supported for event #1 is 2, and the maximum number of reporting beams supported for event #2 is 3. When event #1 occurs, the number of reporting beams associated with event 1 can be 1 or 2; when event #2 occurs, the number of reporting beams associated with event 2 can be 1, 2, or 3.

[0418] For example, the terminal device supports events #1 and #2, and the indication information includes that the maximum number of reporting beams supported by the terminal device for both events #1 and #2 is 3. When event #1 occurs, the number of reporting beams associated with event 1 can be 1, 2, or 3; when event #2 occurs, the number of reporting beams associated with event 2 can be 1, 2, or 3.

[0419] Example 10 indicates the maximum number of new beams (i.e., second beams) that the terminal device supports for each event.

[0420] For example, the terminal device supports events #1 and #2, and the indication information includes that the maximum number of new beams that can be reported for event #1 is 2, and the maximum number of new beams that can be reported for event #2 is 3. When event #1 occurs, the number of new beams reported associated with event 1 can be 1 or 2; when event #2 occurs, the number of new beams reported associated with event 2 can be 1, 2, or 3.

[0421] For example, the terminal device supports events #1 and #2, and the indication information includes that the maximum number of new beams that can be reported for both events #1 and #2 supported by the terminal device is 3. When event #1 occurs, the number of new beams reported associated with event 1 can be 1, 2, or 3; when event #2 occurs, the number of new beams reported associated with event 2 can be 1, 2, or 3.

[0422] The above is an illustrative example, and the embodiments of this application are not limited thereto. The terminal device can indicate various information related to events supported by the terminal device to the network device.

[0423] Based on the above implementation, the first device can acquire configuration information and perform measurements (such as beam measurement or channel measurement) on M cells, thereby obtaining measurement results (or measurement reports) related to X events corresponding to the M cells. This application does not limit the specific implementation method of the terminal device's measurement; reference can be made to the relevant descriptions of current technical solutions.

[0424] S520, the first device sends a measurement report to the second device;

[0425] Accordingly, the second device receives a measurement report from the first device.

[0426] The measurement report includes measurement results related to at least one event for each of the M1 cells.

[0427] In this application, M1 cells are the cells where the event occurred, and at least one event is an event that has occurred, meaning that at least one event occurs in each of the M1 cells. In other words, at least one event corresponding to the M1 cells is an event that occurred on the M1 cells. For example, at least one event corresponding to the M1 cells can be at least one of the events #A to #K mentioned above. It is understood that the occurrence of an event triggers a reporting, that is, it triggers the reporting of the measurement report corresponding to that event.

[0428] Optionally, the measurement results may include, but are not limited to: whether an event has occurred on M1 cells, whether an event has occurred in any of the M1 cells, the cell index of the event, the event index, and the reporting parameters corresponding to the event, such as at least one or more of the aforementioned reporting parameters #1 to #11.

[0429] A measurement report, i.e. an event-related measurement report, can be understood as: including only at least one event-related measurement result for M1 cells, in which case the measurement report does not include measurement results related to cells where no event has occurred; or, it can also be understood as: including X event-related measurement results for M cells, in which case the measurement results related to cells where no event has occurred, or measurement results related to cells where events have occurred but not reported, can be filled with predefined values, such as 0.

[0430] In this application, the number of measurement reports can be one or more, depending on the number of measurement report configurations configured by the network device or predefined by the protocol. It should be understood that one measurement report configuration corresponds to one measurement report. Optionally, the reporting parameters for each event-triggered report supported on each cell can be predefined or preconfigured by the protocol, or can be indicated or configured by the network device through signaling; this application does not limit this. For example, when the measurement results related to at least one event corresponding to M1 cells correspond to multiple measurement reports, it means that one measurement report can include at least one event-related measurement result from one cell, or one measurement report can include one event-related measurement result from one cell, or one measurement report can include the same event-related measurement results from multiple cells, or one measurement report can include at least one event-related measurement result from multiple cells, etc. In this case, the terminal device reports the measurement results of at least one event corresponding to M1 cells through multiple measurement reports. As another example, when the measurement results related to at least one event corresponding to M1 cells correspond to one measurement report, the terminal device reports the measurement results of at least one event corresponding to M1 cells through one measurement report.

[0431] In one example, M cells correspond to one measurement report configuration. That is, when the measurement results related to at least one event corresponding to M1 cells correspond to one measurement report configuration, the terminal device can sort the measurement results related to at least one event corresponding to M1 cells in sequence according to the cell priority sorting information of M1 cells, and report them through a measurement report.

[0432] Another example is that M cells correspond to multiple measurement report configurations. That is, when the measurement results related to at least one event of M1 cells correspond to multiple measurement report configurations, the terminal device can sort the measurement results related to at least one event of M1 cells in sequence according to the priority sorting information of the multiple measurement report configurations, and report them through multiple measurement reports.

[0433] Another example is that M cells correspond to multiple measurement report configurations. That is, when the measurement results related to at least one event corresponding to M1 cells correspond to one measurement report configuration, the terminal device can sort the measurement results related to at least one event corresponding to M1 cells in sequence according to the cell priority sorting information of M1 cells, and report them through a single measurement report.

[0434] In other words, if a network device is configured to correspond to one measurement report for M cells or M1 cells, it means that the measurement results related to at least one event for each of the M1 cells are carried in a single measurement report. Specifically, these reports can be ordered sequentially according to the reporting priority of the M1 cells. For example, if M1 = 3, including cells A, B, and C, where cell A has a higher priority than cell B, and cell B has a higher priority than cell C, and the events occurring on cells A, B, and C are event 1, event 2, and event 3 respectively, then the measurement results corresponding to event 1, event 2, and event 3 will be placed sequentially in a single measurement report. If a network device is configured to correspond to multiple measurement reports for each of the M1 cells, it means that the measurement results related to at least one event for each of the M1 cells are carried in multiple measurement reports, and these reports can also be ordered sequentially according to the reporting priority of the M1 cells. For example, M1=3, including cell A, cell B and cell C, where cell A has a higher priority than cell B, cell B has a higher priority than cell C, and there are 2 measurement reports. Measurement report #1 corresponds to cell A and cell B, and measurement report 2 corresponds to cell C. If the events occurring in cell A, cell B and cell C are event 2, event 1, event 3 and event 4 respectively, then the measurement results corresponding to event 2 and event 1 are placed in measurement report 1 in sequence, and the measurement results corresponding to event 3 and event 4 are placed in measurement report 2 in sequence.

[0435] Optionally, the cell priority sorting information corresponding to M cells or M1 cells can be predefined or preconfigured by the protocol, or it can be indicated or configured by the network device through signaling. This application does not limit this.

[0436] Optionally, the configuration of one or more measurement reports associated with M cells or M1 cells can be indicated or configured by network devices through signaling, or it can be predefined by the protocol. This application does not limit this.

[0437] Optionally, the terminal device may also not send measurement results (i.e., event-related reports) related to events that have occurred in the M cell-associated X events. In other words, an event may occur, but the measurement results for that event do not need to be reported. For example, event A on cell #1 does not need to be reported. Assuming that the measurement results corresponding to event A are not in the measurement report, it is not necessary to send them; it is only necessary to inform the network device that event A has occurred on cell #1.

[0438] Optionally, this application does not limit the number of cells where an event occurred, and / or the size of the number of events. As an example, M1 equals 1, and at least one event constitutes one event, meaning that the terminal device can report a cell where an event occurred and / or the measurement results related to an event through a measurement report, facilitating cell and event management.

[0439] Optionally, M1 equals 1 and at least one event is an event, that is, the measurement result related to an event that occurred on a cell is reported by the terminal device. Specifically, it can be determined by one or more of the following methods: for example, it can be indicated or configured by the network device through signaling, or it can be predefined or preconfigured by the protocol, or it can be determined by the terminal device according to its own terminal capabilities. As long as the information of the reported cell and event is aligned between the network device and the terminal device, this application does not limit it in this regard.

[0440] Optionally, M1 equals 1 and at least one event is considered an event, which may also depend on the capabilities of the terminal device. For example, assuming there are Q = 6 events occurring on N = 4 cells, since the terminal device's capability only supports reporting measurement results related to one event occurring on one cell, the terminal device can report measurement results related to a specific event occurring on a specific cell.

[0441] Optionally, the terminal device may report one or more measurement reports via signaling or reporting resources (or uplink resources). The reporting resources may be the aforementioned event-triggered reporting resources. Optionally, this application does not limit the number of uplink resources carried by one or more measurement reports sent by the terminal device, wherein one or more measurement reports correspond to one or more measurement report configurations.

[0442] In one implementation, M cells are associated with multiple measurement report configurations. These multiple measurement report configurations can be M or T, where T is an integer greater than 1. The multiple measurement reports corresponding to these configurations can be hosted on the same uplink resource. Therefore, measurement results related to at least one event corresponding to M1 cells can be hosted on the same uplink resource, or in other words, measurement results related to at least one event corresponding to M1 cells can be reported through the same uplink resource.

[0443] In another implementation, M cells are associated with multiple measurement report configurations. These multiple measurement report configurations can be hosted on multiple uplink resources. Therefore, at least one event-related measurement result for each of the M1 cells is hosted on different uplink resources; or, in other words, the at least one event-related measurement result for each of the M1 cells is reported through different uplink resources. Alternatively, at least two of the M1 cells may have at least one event-related measurement result hosted on different uplink resources.

[0444] In another implementation, M cells are associated with multiple measurement report configurations, where M1 cells are associated with one measurement report configuration. Therefore, the measurement results related to at least one event corresponding to M1 cells can be carried on the same uplink resource, or in other words, the measurement results related to at least one event corresponding to M1 cells can be reported through the same uplink resource.

[0445] Optionally, the signaling can be MAC CE signaling or UCI signaling. The uplink resource can be periodic PUCCH resource, aperiodic PUSCH resource, semi-persistent PUCCH resource, or semi-persistent PUSCH resource, etc. The network device can be configured with only one reporting resource, meaning each of the M cells corresponds to the same reporting resource, or all event-triggered reports are configured with the same reporting resource; alternatively, the network device can be configured with multiple reporting resources, meaning the M cells correspond to different reporting resources, for example, each cell corresponds to a different reporting resource, or at least two cells correspond to different reporting resources. This application does not impose any limitations on this.

[0446] Optionally, for a scenario where N out of M cells may be the cells where events occurred, the total number of events occurring on the N cells can be Q. The N cells include M1 cells, meaning M1 is less than or equal to N, and N is less than or equal to M. This indicates that the terminal device can report all or some of the cells where events occurred. Q is greater than or equal to the number of at least one event, meaning the terminal device can report all events or some of the events that occurred. In other words, the number of at least one event occurring in the M1 cells can be less than or equal to Q, and the number of cells where events occurred, M1, can be less than or equal to N. This application does not impose any limitations on this.

[0447] Optionally, the terminal device may report measurement results related to at least one event corresponding to M1 cells in a predefined or preconfigured first order, or in a first order determined by the terminal. For example, when multiple events occur in the same cell, the predefined or preconfigured first order may be at least one of the following: in descending order of event index, or in ascending order of event index, or in descending order of event priority, or in descending order of priority configured in the measurement reports corresponding to the events. Specifically, assuming Q=2, M1=1, and the events occurring in the N cells include events #m and #r, with event #m having a higher priority than event #r, when the terminal device reports measurement results related to an event occurring in that cell, it may prioritize measurement reports related to event #m before prioritizing those related to event #r, or the terminal device may only report measurement reports related to event #m in that cell.

[0448] For example, when events occur in multiple cells, the predefined or preconfigured first order, or the first order determined by the terminal, can be at least one of the following: sorting between cells according to their priority from high to low; or sorting between cells according to the priority configured in the measurement reports corresponding to the cells from high to low; or sorting within a cell according to the event index from large to small; or sorting within a cell according to the event index from small to large; or sorting within a cell according to the event priority from high to low; or sorting within a cell according to the priority configured in the measurement reports corresponding to the events from high to low.

[0449] For example, suppose there are M = 4 cells, such as cell A, cell B, cell C, and cell D. Cell A supports event 1, cell B supports events 2 and 3, cell C supports events 1, 2, and 3, and cell D supports events 3, 4, and 5, i.e., X = 9. If N = 4 cells have events occurring, it means that an event has occurred in each cell. If event 1 occurs in cell A, event 2 occurs in cell B, events 1, 2, and 3 occur in cell C, and events 3 and 5 occur in cell D, then the terminal device can send measurement results related to at least one event (i.e., 7 events) corresponding to M1 = 4 cells, that is, report the results related to all cells where events occurred; or, if cell A and cell D... If the priority of cells A, B, and C is higher than that of cells B and C, the terminal device can send measurement results related to at least one event (e.g., event 1 on cell A and events 3, 4, and 5 on cell D) corresponding to M1 = 2 cells (e.g., cells A and D); or, if the priority of cells A, C, and D is higher than that of cell B, and the priority of events 1 and 3 in cell C is lower than that of event 2, and the priority of events 4 and 5 in cell D is lower than that of event 3, the terminal device can send measurement reports related to at least one event (e.g., event 1 on cell A, event 2 on cell C, and event 3 on cell D) corresponding to M1 = 3 cells (e.g., cells A, C, and D), that is, report the measurement results related to some of the cells where the events occurred and / or the events.

[0450] The payload size of the measurement report refers to the total payload included in the measurement report, or in other words, the number of bits / bit space / bit width included in the measurement report, or the reserved space / payload size / number of bits / bit space / bit width, etc. That is, the terms "space," "reporting space," "bit space," "reporting bit space," "payload size," "number of bits," "reporting bit number," "bit width," "reporting payload size," or "payload size" in this application can be used interchangeably.

[0451] The payload size of the measurement report can be: the payload size required to report measurement results related to the first event, or the payload size required to report measurement results related to the first cell, or the payload size required to report measurement results related to both the first event and the first cell. This can be understood as the payload size required to report measurement results related to the first event associated with the first cell, or the payload size required to report measurement results corresponding to the first event occurring on the first cell. M1 cells belong to M cells, where M1 is a positive integer less than or equal to M. Furthermore, the payload size required for measurement results related to the first event and / or the first cell refers to the payload size required to report measurement results of the first event and / or the first cell, or the number of bits / bit space / bit width, etc., required for measurement results of the first event and / or the first cell. Furthermore, the payload required to report event-related measurement results refers to the payload (or number of bits / bit space / bit width) required for all corresponding reporting parameters included in the event-related measurement results. In other words, the payload required to report event-related measurement results is determined by at least one of the following: all reporting parameters included in the event-related measurement results and the number of reports for each reporting parameter.

[0452] For example, suppose the measurement results related to event #m include reported parameters #a, #b, ..., #k, and the number of bits required to report each reported parameter in sequence are Pa, Pb, ..., Pk, respectively. Then the payload size required to report the measurement results related to event #m is (Pa + Pb + ... + Pk). As an example, if the measurement results related to event #m include k reported parameters #a, l reported parameters #b, ..., m reported parameters #k, and the number of bits required to report each reported parameter in sequence are Pa, Pb, ..., Pk, then the payload size required to report the measurement results related to event #m is (k*Pa + l*Pb + ... + m*Pk). Here, reported parameters #a, #b, ..., or #k can be one of the reported parameters #1 to #11 described above; or, one or more of reported parameters #a to #k may not be limited to the reported parameters described above. In this example, the reported parameters and the number of reports for each parameter in the measurement results related to event #m can be determined by at least one of the following: network device configuration, protocol specifications, and terminal capability reporting. Understandably, once the terminal device and network device determine the event-related measurement results, they can also determine the workload required to report those results.

[0453] Optionally, in at least two events corresponding to the M1 cells, the load sizes corresponding to the measurement results of at least two events are different. For example, M1 = 1, including cell A, and at least one event including event 1, event 2, and event 3, indicating that the terminal device reports the measurement results of events 1, 2, and 3 occurring in cell A by sending a measurement report. Here, the load size corresponding to the measurement result related to event 1 is 'a', the load size corresponding to the measurement result related to event 2 is 'b', and the load size corresponding to the measurement result related to event 3 is 'c', where a, b, and c are not equal; or, the load sizes corresponding to the measurement results related to events 1 and 2 are both 'a', and the load size corresponding to the measurement result related to event 3 is 'b', where a and b are not equal.

[0454] Optionally, if the measurement results related to one of the at least one events corresponding to M1 cells include multiple reporting parameters, the terminal device can report the multiple reporting parameters corresponding to that event in the order of reporting parameters. The reporting order of the multiple reporting parameters can be predefined or preconfigured, or it can be indicated or configured by the network device through signaling; this application does not limit this. For example, if at least one event corresponding to M1 cells includes event #1, and the measurement results related to event #1 include the aforementioned reporting parameter #1 and reporting parameter #2, then according to the predefined or preconfigured reporting order, the terminal device can report reporting parameter #1 first, and then report reporting parameter #2. That is, in the reported measurement report, the bit space occupied by reporting parameter #1 precedes the bit space occupied by reporting parameter #2.

[0455] Below, an example is provided illustrating the load size required for the aforementioned measurement report: the load size required to report the first event and / or report measurement results related to the first cell.

[0456] Optionally, the first event can be a predefined event, an event indicated by the network device to the terminal device, an event indicated by the terminal device to the network device, or an event in which the load size of the related measurement results among X events is greater than or equal to a threshold. For example, the first event is the event with the largest load size among the X events whose related measurement results are reported. For example, if the X events are event #1, event #2, ..., event #X, and the load sizes of the related measurement results of event #1, event #2, ..., event #X are P1, P2, ..., PX, respectively, and the load size Pn of the related measurement results of event #n is the largest among P1 to PX, then event #n is the first event.

[0457] That is to say, the payload size of the measurement report sent by the terminal device is the payload size of the event with the largest payload among the X events that report the measurement results related thereto. Then, the payload size required for the measurement results related to at least one event corresponding to the M1 cells reported by the terminal device can be less than or equal to the payload size of the measurement report. For example, assume X = 3, and the payload sizes corresponding to Event 1, Event 2, and Event 3 are A, B, and C, respectively, where A < B < C, indicating that the payload size corresponding to Event 3 is the largest. At this time, Event 3 is the first event. Additionally, if the terminal device reports at least one event on M1 = 2 cells, for example, Event 1 on Cell A and Event 2 on Cell B meet the event reporting conditions. If A + B ≤ C, the terminal device reports the measurement results corresponding to Event 1 on Cell A and Event 2 on Cell B; if A + B > C, A < C, and B < C, the terminal device can report the measurement results corresponding to Event 1 on Cell A, or report the measurement results corresponding to Event 1 on Cell B. Optionally, if the reporting priority of Cell A is higher than that of Cell B, the terminal device reports the measurement results corresponding to Event 1 on Cell A.

[0458] Optionally, the first cell can be a pre-defined cell, or a cell indicated by the network device to the terminal device, or a cell indicated by the terminal device to the network device, or the first cell is a cell with a payload greater than or equal to a threshold value among the payload sizes required for reporting the measurement results related to M cells. For example, the first cell is the cell with the largest payload size among the payload sizes required for reporting the measurement results related to M cells. For example, the M cells are Cell 1, Cell 2,..., Cell Y, Cell 2,..., Cell M, respectively, and the payload sizes required for the measurement results related thereto are Q1, Q2,..., QM, respectively. Among them, the payload size Qy required for the measurement results related to Cell Y is the largest among Q1 to QM, then Cell Y is the first cell.

[0459] In other words, if the load size of the measurement report sent by the terminal device is the load size of the cell with the largest load required to report the relevant measurement results among M cells, then the load size required for the measurement results related to at least one event corresponding to M1 cells reported by the terminal device can be less than or equal to the load size of the measurement report. For example, assuming M=3, the load sizes corresponding to cells A, B, and C are a, b, and c, respectively, where a < b < c, indicating that the load size corresponding to cell C is the largest. In this case, cell C is the first cell, and the load size of the measurement report reported by the terminal device is c. Then, if the terminal device reports at least one event on M1=2 cells, such as event 1 on cell A and event 1 and event 2 on cell B, where the load sizes corresponding to events 1 and 2 are A and B, then the load size corresponding to at least one event corresponding to M1 cells reported by the terminal device is 2A+B≤c. Optionally, if the load size required for the measurement results related to at least one event corresponding to M1 cells reported by the terminal device is greater than the load size of the measurement report, then the event-related measurement results of some cells can be discarded according to the reporting priority of the cells. For example, suppose events occur in cells A, B, and C: event 1 in cell A, events 1 and 2 in cell B, and events 3 and 4 in cell C. The load sizes corresponding to events 1 through 4 are A, B, C, and D, respectively, and the reporting priorities of cells A, B, and C increase sequentially. Since the load size required for the measurement results related to the cells where the events occurred is 2A+B+C+D, which is greater than c, and A+B+C+D < c, the terminal device can choose to prioritize reporting events occurring in M1 = 2 cells: events 1 and 2 in cell B, and events 3 and 4 in cell C.

[0460] Optionally, assuming the first cell consists of M cells, the load of the measurement report reported by the terminal device is the sum of the load required to report the measurement results related to the M cells.

[0461] In other words, the load size corresponding to the measurement report sent by the terminal device is the sum of the load sizes required to report the relevant measurement results in M ​​cells. Therefore, the load size required for the measurement results related to at least one event in M1 cells reported by the terminal device can be less than or equal to the load size of the measurement report. For example, assuming M=3, and the load sizes corresponding to cells A, B, and C are a, b, and c, respectively, the load size of the measurement report reported by the terminal device is a+b+c. Furthermore, if the terminal device reports at least one event in M1=2 cells, such as event 1 in cell A and event 2 in cell B, where the load sizes corresponding to events 1 and 2 are A and B, then the load size corresponding to at least one event in M1 cells reported by the terminal device is A+B≤a+b+c.

[0462] The following examples illustrate the relationship between the load size of measurement reports reported by terminal devices and the load size required for measurement results related to at least one event corresponding to M1 cells, using various scenarios as examples.

[0463] Scenario 1:

[0464] If the load required for measurement results related to at least one event corresponding to M1 cells is less than the load of the measurement report, then the portion of the measurement report other than the measurement results related to at least one event corresponding to M1 cells will be filled with predefined values.

[0465] As an example, the remaining bits in the measurement report, except for the bits required to carry the measurement results related to at least one event corresponding to M1 cells, are filled with 0. For instance, if the payload size of the measurement report is S bits, and the payload size required for the measurement results related to at least one event corresponding to M1 cells is L bits, if L < S, then the first L bits of the measurement report are used to carry the measurement results related to at least one event corresponding to M1 cells, and the remaining bits are filled with 0, where S and L are positive integers. Another example: if the payload size of the measurement report is S bits, and the measurement results related to at least one event corresponding to M1 cells include reporting parameter #a and reporting parameter #b, with the number of bits required for reporting parameter #a and reporting parameter #b being Pa and Pb respectively, if (Pa + Pb) < S, then the first (Pa + Pb) bits of the measurement report are used to carry the measurement results related to at least one event corresponding to M1 cells, and the remaining bits are filled with 0. Here, reporting parameter #a and reporting parameter #b can be one or more of the reporting parameters #1 to #11 described above.

[0466] Optionally, if the measurement results related to at least one event corresponding to M1 cells include one or more reporting parameters, and the number of reports corresponding to reporting parameter #f is less than the maximum number of reports corresponding to reporting parameter #f specified by the network device or protocol, then the portion of the measurement report sent by the terminal device corresponding to reporting parameter #f, excluding the reporting parameter #f included in the measurement results related to at least one event corresponding to M1 cells, is a predefined value. Here, reporting parameter #f can be one of the reporting parameters #1 to #11 described above. For example, the reported parameter #f is the reported parameter #3 described above, which is the index of the second beam. The network device or protocol specifies that the maximum number of beams included in the second beam is 4. In this case, the number of bits corresponding to the reported parameter #f in the measurement report is Pf. Pf bits can be used to carry the index of 4 beams. The reported parameter #f included in the measurement results related to at least one event corresponding to M1 cells includes the index of 2 beams. The number of bits required for the index of these 2 beams is Pf / 2. Therefore, in at least one event corresponding to M1 cells, Pf / 2 bits of the Pf bits corresponding to the reported parameter #f carry the reported parameter #f included in the measurement results related to at least one event corresponding to M1 cells, and the other Pf / 2 bits are filled with 0.

[0467] Scenario 2:

[0468] For example, among M cells, there may be N cells where the event occurred. The total number of events occurring on the N cells can be Q. There may be at least two cells where the same event occurs. The N cells include M1 cells.

[0469] If the load required for the measurement results of Q events corresponding to N cells is greater than the load of the measurement report, then the measurement report includes at least one event-related measurement result for some of the Q event-related measurement results for the N cells, for example, at least one event-related measurement result for M1 cells.

[0470] As an example, the payload size of the measurement report is S bits. The payload size required for the Q event-related measurement results corresponding to N cells is L bits. If L > S, then the measurement report can carry at least one event-related measurement result corresponding to M1 cells, and the payload size corresponding to this measurement result is S1, where S1 ≤ S. Optionally, the terminal device can report according to the cell priority sorting information corresponding to the M1 cells. For example, there are cells 1, 2, and 3. The payload size required for the event-related measurement results occurring on cell 1 is L1, the payload size required for the event-related measurement results occurring on cell 2 is L2, and the payload size required for the event-related measurement results occurring on cell 3 is L3. Cell 3 has a higher priority than cell 1, and cell 1 has a higher priority than cell 2. Since L1 + L2 + L3 > L and L1 + L3 < L, the terminal device can report the event-related measurement results occurring on cell 3 and cell 1 in sequence in the measurement report.

[0471] Scenario 3:

[0472] Assuming the load required for measurement results related to at least one event for M1 cells is equal to the load of the measurement report, the measurement report includes all measurement results related to at least one event for M1 cells, without needing to fill in predefined values. In other words, the terminal device can report measurement results related to at least one event for M1 cells according to a predefined or preconfigured reporting order.

[0473] As an example, suppose there are Q events corresponding to N cells. The load required for the measurement results of the Q events corresponding to N cells is greater than the load of the measurement report. Then the measurement report includes part of the measurement results related to the Q events corresponding to N cells. For example, the measurement report includes measurement results related to at least one event corresponding to M1 cells. In this case, the load of at least one event corresponding to M1 cells is equal to the load of the measurement report.

[0474] For example, the terminal device can discard a portion of the measurement results related to Q events corresponding to N cells according to a predefined or preconfigured reporting order. Assuming the payload size of the measurement report is S bits, and the payload size of the measurement results related to the Q events corresponding to N cells is L' bits, if L' > S, the terminal device discards the last (L'-S) bits of the measurement results related to the Q events corresponding to N cells, and reports the first S bits of the measurement results related to the Q events corresponding to N cells through the measurement report. For example, the first S bits are equal to the payload size required for the measurement results of at least one event corresponding to M1 cells, where L' is a positive integer.

[0475] For example, the payload size of the measurement report is S bits. The measurement results related to Q events corresponding to N cells include reported parameters #c, #d, and #e. The number of bits required for reported parameters #c, #d, and #e are Pc, Pd, and Pe, respectively. If (Pc+Pd+Pe)>S, the terminal device will report some of the parameters from reported parameters #c, #d, and #e through the measurement report according to the predefined or preconfigured reporting order. For example, if the reporting order of parameters #c and #d is first, and (Pc+Pd)≤S, (Pc+Pd+Pe)>S, then the terminal device drops the reporting parameter #e and reports parameters #c and #d through the measurement report. Alternatively, the terminal device discards the last (S-Pc-Pd) bits of the reporting parameter #e and reports the first (Pc+Pd+Pe-S) bits of the reporting parameters #c, #d, and #e through the measurement report. Here, the reporting parameters #c, #d, and #e can be one or more of the reporting parameters #1 to #11 described above.

[0476] The following example illustrates the workload required for a terminal device to determine the measurement results related to at least one event corresponding to M1 cells, and the method for reporting measurement reports.

[0477] Scenario 1: A measurement report is configured to be associated with M cells, meaning M cells are associated with one measurement report. In this case, the terminal device can report the measurement results of at least one event corresponding to M1 cells by sending a measurement report. This includes the following steps. Optionally, M and M1 are both integers greater than or equal to 1, and M1 is less than or equal to M.

[0478] Step 1: Determine the payload size required for the measurement results associated with one of the X events.

[0479] Method 1: Report using a fixed load size.

[0480] For example, the terminal device determines the reporting parameters corresponding to one of X events, and the number of times each reporting parameter can be reported. The one or more reporting parameters corresponding to one of the X events, and the maximum number of reports corresponding to each reporting parameter, can be predefined or preconfigured, indicated by the network device via signaling, or determined by the terminal device; there is no limitation on this. Correspondingly, the terminal device reserves reporting space for the event according to the maximum number of reports corresponding to each reporting parameter determined by at least one of the configured, predefined, or terminal capabilities. The reporting space is the sum of the products of the maximum number of reports corresponding to each reporting parameter for the event and the required load size for each reporting parameter.

[0481] For example, suppose an event (e.g., event #1) occurs in one of the M cells. Event #1 can be one of the events #A to #K in step S501 above. If the reporting parameters corresponding to event #1 include reporting parameter #x, reporting parameter #x can be any of the aforementioned reporting parameters #1 to #11. Suppose the load required to report one reporting parameter #x is a. If k reporting parameters #x need to be reported when event #1 occurs, then the load required for the terminal device to report the measurement results related to event #1 is a*k. As another example, suppose two events (e.g., events #2 and #3) occur in one of the M cells. Event #2 or event #3 can be one of the events #A to #K in step S501 above. If the reporting parameters corresponding to event #2 include reporting parameters #y and #z, reporting parameters #y and #z can be any of the aforementioned reporting parameters #1 to #11. When event #2 occurs, the number of reported parameters #y and #z that need to be reported are m and n, respectively. The reported parameters for event #3 include reported parameters #y and #f, which can be any of the aforementioned reported parameters #1 to #11. When event #3 occurs, the number of reported parameters #y and #f that need to be reported are f and g, respectively. The required load sizes for these reported parameters are a, b, and c, respectively. Therefore, the load size required to report the measurement results related to event #2 is a*m + b*n, and the load size required to report the measurement results related to event #3 is b*f + c*g. Here, k, m, n, f, and g are all positive integers.

[0482] Optionally, if the number of reports of a certain reporting parameter that meets the event occurrence conditions is less than the maximum number of reports of that reporting parameter configured on the network side, the terminal device may report the remaining space in any of the following ways.

[0483] (1) Fill in predefined values, such as 0;

[0484] (2) Report the measurement quantity corresponding to the reporting parameter that does not meet the event conditions;

[0485] (3) Repeatedly report the measurement quantity corresponding to the reporting parameter that meets the event conditions;

[0486] (4) Report the measurement quantities corresponding to other reported parameters.

[0487] For example, if the number of reported parameters #x that satisfy the conditions of event #1 (e.g., 3) is less than the maximum number of reported parameters #x configured on the network side (e.g., 4), then when event #1 occurs, the terminal device can report the measurements of the 3 reported parameters #x that satisfy the conditions of event #1, and can report the remaining space (i.e., the reporting space corresponding to the remaining 1 reported parameter #x) in any of the following ways:

[0488] (1) Fill in predefined values, such as 0;

[0489] (2) Report the measurement quantity corresponding to the reporting parameter #x that does not meet the event condition, that is, report one reporting parameter #x that does not meet the event #1 condition;

[0490] (3) Repeatedly report the measurement quantity corresponding to the reporting parameter #x that meets the event condition, that is, report any one of the three reporting parameters #x that meet the event #1 condition.

[0491] (4) Report the measurement quantity corresponding to other reporting parameters, such as the measurement quantity corresponding to reporting parameter #y.

[0492] For example, suppose the reported parameters corresponding to event q include reported parameter #3 (e.g., second beam index) and reported parameter #4 (e.g., second beam quality), and the maximum number of reported parameters #3 and #4 are N3 and N4 respectively, for example, N3 = 3 and N4 = 3; when the number of second beams satisfying the condition of event q is N1, for example, N1 = 2, then the terminal device can report N1 second beam indices and their corresponding N1 second beam qualities. For the positions corresponding to the remaining N3-N1 second beam indices and N4-N1 second beam qualities, the terminal device can fill in special values ​​(e.g., all 0s); or, the terminal device The terminal device can report N3 second beam indices and their corresponding N4 second beam qualities, where N1 second beam indices and their corresponding N1 second beam qualities satisfy event q, and the remaining N3-N1 second beam indices and their corresponding N4-N1 second beam qualities do not satisfy event q. Alternatively, the terminal device can repeatedly report N3-N1 second beam indices and their corresponding N4-N1 second beam qualities selected from the N1 second beam indices and their corresponding N1 second beam qualities that satisfy the event condition. Alternatively, the terminal device can report N3-N1 serving beam indices and their corresponding N4-N1 serving beam qualities. It is understood that event q in this application example can be one of events #A to #K in step S501 above.

[0493] In one implementation, the load required to report the measurement results related to each of the X events can be determined based on the corresponding reporting parameters and the number of reports for each reporting parameter.

[0494] Taking event q out of X events as an example, assuming that the reporting parameters corresponding to event q include reporting parameter #x and reporting parameter #y, and reporting parameter #x or reporting parameter #y can be any of the aforementioned reporting parameters #1 to #11, and the load required for the measurement of reporting parameter #x and reporting parameter #y are Pa and Pb respectively, if the network device configuration or protocol specifies that the number of reports corresponding to reporting parameter #x and reporting parameter #y are Na and Nb respectively, then when event q occurs, the load required for the terminal device to report the measurement results related to event q is: S = Pa * Na + Pb * Nb.

[0495] Optionally, the following is combined with Figure 6 The following example illustrates the situation where the number of reports n for reporting parameter #1 that satisfies event q is less than N1, and the number of reports m for reporting parameter #2 that satisfies event q is less than N2. Both n and m are integers greater than or equal to 1.

[0496] Figure 6 This is a schematic diagram of the structure of the measurement quantity of the reporting parameters that meet the event q condition provided in the embodiments of this application. For example... Figure 6 As shown, when an event q occurs in a cell, the reporting parameters corresponding to event q include reporting parameter #1 and reporting parameter #2. The load sizes required for the measurements of reporting parameter #1 and reporting parameter #2 are P1 and P2, respectively. If the number of reports of reporting parameter #1 configured by the network device is N1, and the number of reports of reporting parameter #2 configured is N2, if the number of measurements corresponding to reporting parameter #1 that satisfy the conditions of event q is n, and the number of measurements corresponding to reporting parameter #2 that satisfy the conditions of event q is m, where n < N1 and m < N2, then the load size required for the terminal device to report the measurement results related to event q is: S = P1 * N1 + P2 * N2. Figure 6 It can be seen that the terminal device reports the measurements of n reported parameters #1 that satisfy event q, and the measurements of m reported parameters #2 that satisfy event q. For the remaining space of size P1*(N1-n) corresponding to reported parameter #1, special values ​​can be filled in; alternatively, the measurement of reported parameter #1 that does not satisfy event q can be reported; or the measurement of reported parameter #1 that satisfies event q can be repeatedly reported. Similarly, for the remaining space of size P2*(N2-m) corresponding to reported parameter #2, special values ​​can be filled in; alternatively, the measurement of reported parameter #2 that does not satisfy event q can be reported; or the measurement of reported parameter #2 that satisfies event q can be repeatedly reported.

[0497] Optionally, for the number n of reported parameters #1 that satisfy the event q condition being greater than or equal to N1, and the number m of reported parameters #2 that satisfy the event q condition being greater than or equal to N2, where n and m are both integers greater than or equal to 1. If n equals N1 and m equals N2, then the terminal device reports the measurements of n reported parameters #1 that satisfy the event q condition, and the measurements of m reported parameters #2 that satisfy the event q condition. That is, the load required for the terminal device to report the measurement results related to event q is: S = P1*N1 + P2*N2. If n is greater than N1 and m is greater than N2, then the terminal device can report the measurements of N1 reported parameters #1 that satisfy the event q condition, and the measurements of N2 reported parameters #2 that satisfy the event q condition, in a predefined or preconfigured order. At this time, there are n-N1 reported parameters #1 that satisfy the event q condition, and m-N2 reported parameters #2 that satisfy the event q condition, which are not reported (or discarded). That is, the load required for the terminal device to report the measurement results related to event q is: S = P1*N1 + P2*N2.

[0498] Method 2: Use flexible load size reporting.

[0499] For example, the terminal device indicates to the network device the number of reports corresponding to each reporting parameter for a certain event, and reports the corresponding reporting parameters according to the reporting number. For instance, the workload required to report the measurement results related to each of X events can be determined based on the number of reports corresponding to each reporting parameter related to the event indicated by the terminal device to the network device.

[0500] Taking event q out of X events as an example, assume that the reporting parameters corresponding to event q include reporting parameters #a, #b, and #c, which can be any of the aforementioned reporting parameters #1 to #11. The required load sizes for reporting parameters #a, #b, and #c are Pa, Pb, and Pc, respectively. If the number of reporting parameters #a, #b, and #c that satisfy the conditions of event q are n, m, and h, respectively, then when event q occurs, the terminal device indicates to the network device the number of reporting parameters #a, #b, and #c that satisfy the conditions of event q, respectively. Therefore, the load size required for the terminal device to report the measurement results related to event q is: S = Pa*n + Pb*m + Pc*h. This event q can be one of the events #A to #K in step S501 above.

[0501] Optionally, the terminal device reports the number of reports corresponding to each reported parameter for the event through a first part (CSIPart 1) of a measurement report. Specifically, a measurement report can include a first part (CSIPart 1) and a second part (CSIPart 2). For example, the first part includes one or more of the following: the number of reports for one or more reported parameters corresponding to the event. The load size corresponding to the second part is determined based on the first part. Wherein, the load size corresponding to the second part is determined based on the first part, which can be understood as: the load size of the second part is determined based on the number of reports for one or more reported parameters corresponding to the event reported in the first part.

[0502] As shown in Table 1 below, taking event q as an example, the reporting parameters corresponding to event q include reporting parameter #a and reporting parameter #b. Reporting parameter #a or reporting parameter #b can be any of the aforementioned reporting parameters #1 to #11. The required load sizes for reporting parameters #a and #b are Pa and Pb, respectively. The number of reporting parameters #a and #b that satisfy the conditions of event q are x and y, respectively. Therefore, the load size required for the terminal device to report the measurement results related to event q is: S = Pa * x + Pb * y. Therefore, a measurement report reported by the terminal device includes CSI part 1 and CSI part 2. CSI part 1 carries the number of reported parameters #a (x) and #b (y) corresponding to event q. CSI part 2 carries the measurement quantities corresponding to x reported parameters #a and y reported parameters #b. The payload size of CSI part 2 is the sum of the payload size corresponding to the measurement quantities corresponding to x reported parameters #a and y reported parameters #b. That is, the payload size of CSI part 2 is: S = Pa*x + Pb*y. Or, the payload size required for the measurement results related to event q is: S = Pa*x + Pb*y.

[0503] Table 1

[0504]

[0505] Optionally, the terminal device reports the number of reports corresponding to each reporting parameter for the event through scheduling request signaling or reporting indication signaling. Specifically, this can be understood as follows: the terminal device determines that an event has occurred and initiates scheduling request signaling or reporting indication signaling to the network device. This is used to indicate whether reporting triggered by the event is required, to request uplink resources to carry the event-triggered report, or to indicate whether an event has occurred. The scheduling request signaling or reporting indication signaling may include at least one of the following information: the number of reports corresponding to one or more reporting parameters for each event. The terminal device can determine the reporting space for event-triggered reporting based on the scheduling request signaling or reporting indication signaling, that is, determine the reporting space based on the number of reports corresponding to one or more reporting parameters for the event carried by the scheduling request signaling or reporting indication signaling.

[0506] As shown in Tables 2 and 3 below, taking event q as an example, the reporting parameters corresponding to event q include reporting parameter #a and reporting parameter #b. Reporting parameter #a or reporting parameter #b can be any of the aforementioned reporting parameters #1 to #11. The number of reporting parameters #a and #b that satisfy the conditions of event q are x and y, respectively. Therefore, the terminal device can send scheduling request signaling or reporting indication signaling in the form of Table 2. The scheduling request signaling or reporting indication signaling includes the number of reported reporting parameters #a (x) and the number of reported reporting parameters #b (y) corresponding to event q. In addition, the terminal device can also report the measurement quantities corresponding to x reporting parameters #a and y reporting parameters #b in the form of Table 3. Since the required load sizes for reporting parameters #a and #b are Pa and Pb, respectively, the load size required for the terminal device to report the measurement results related to event q is: S = Pa * x + Pb * y.

[0507] Optionally, Tables 2 and 3 can be combined or implemented independently, without limitation.

[0508] Table 2

[0509]

[0510] Table 3

[0511]

[0512]

[0513] For example, the terminal device indicates to the network device the load required to report a measurement result related to an event. For instance, the load required to report the measurement result related to each of X events can be determined based on the load required for the corresponding event-related measurement result indicated by the terminal device to the network device.

[0514] Optionally, the required payload size for the event-related measurement result can be carried in a first part (CSIPart1) of a measurement report, and the event-related measurement result can be carried in a second part (CSIPart2) of the measurement report, with the payload size determined according to the payload size of the event-related measurement result indicated in the first part (CSIPart1) of the measurement report.

[0515] Optionally, the load size required for the measurement result related to an event can be carried in a scheduling request signaling or a reporting indication signaling. The load size carried in the measurement report regarding the measurement result related to the event is determined according to the load size of the measurement result related to the event indicated by the scheduling request signaling or the reporting indication signaling.

[0516] Step 2: Determine the load size required for an event to trigger the relevant measurement results in one of the M cells (or CC).

[0517] Method 1: Report using a fixed load size.

[0518] In one example, taking one of M cells as an example, the payload size required to report the measurement results related to the event triggered by that cell can be: the payload size corresponding to the event with the largest payload size among one or more events supported on that cell. The payload size required for an event can be understood as: the payload size required to report the measurement results related to that event when it occurs.

[0519] In other words, the load required to report a certain cell event that triggers related measurement results among M cells is determined based on the event with the largest load required to report related measurement results among one or more events supported by that cell.

[0520] For example, network device configuration, and / or terminal device determination, and / or protocol stipulation, may specify that a cell (e.g., cell #1) of a terminal device is associated with K events, namely event 1, event 2, ..., event K, and the payload size required to report the measurement results related to each event is P1, P2, ..., PK, respectively. Here, P1, P2, ..., PK can be determined according to step 1 above, and will not be elaborated here. Assuming that the maximum payload size required for the measurement results related to event n among the K events is Pn, then when at least one event occurs on cell #1, the payload size required for the terminal device to determine the reported measurement results triggered by the event related to cell #1 is: Z = Pn. In the example of this application, event 1, event 2, ..., event K can be any of the events #A to #K in step S501 above.

[0521] Optionally, if one or more events occur on cell #1, and the load size x required to report the measurement results related to the one or more events is less than Z, the remaining positions can be filled with special values, such as all 0s, with a corresponding load size of Zx; if the load size y required to report the measurement results related to the one or more events is greater than Z, the excess parts can be discarded according to a predefined priority order.

[0522] In another example, taking one of the M cells as an example, the load required to report the measurement results related to that cell can be the sum of the load required for that cell to report the measurement results related to each event, that is, the sum of the load required for all events of that cell.

[0523] In other words, the load required to report measurement results related to a particular cell out of M cells is determined by the sum of the load required to report measurement results related to all events supported by that cell.

[0524] For example, network device configuration, and / or terminal device determination, and / or protocol stipulation, the K events associated with a cell (e.g., cell #1) of the terminal device are event 1, event 2, ..., event K, and the payload size required to report the measurement results related to each event is P1, P2, ..., PK, where P1, P2, ..., PK can be determined according to the aforementioned step 1, which will not be elaborated here. Then the payload size required for the terminal device to determine the measurement results to be reported triggered by the event related to cell #1 is: Z = P1 + P2 + ... + PK.

[0525] Optionally, if all K events occur, the terminal device may report the measurement results related to the K events of cell #1 in sequence according to the reporting order of each event specified in the protocol (e.g., event index from smallest to largest or from largest to smallest, or other specified order) and the reporting order of the reporting parameters corresponding to each event.

[0526] Optionally, when one of the K events (e.g., event 1) occurs, the measurement results related to event 1 are reported; when one of the K events (e.g., event 2) does not occur, the reporting position corresponding to event 2 can be filled with a predefined value (e.g., 0), and the length of the predefined value is the load size required for the measurement results related to event 2. That is, the positions corresponding to the events that occurred are filled with the measurement results of the corresponding events, and the positions corresponding to the events that did not occur are filled with predefined values ​​(e.g., 0).

[0527] Optionally, when one of the K events (e.g., event 1) occurs, the measurement results related to event 1 are reported; when one of the K events (e.g., event 2) does not occur, the reporting position corresponding to event 2 can report the measurement results related to event 2, but none of the measurement results satisfy the conditions of event 2. That is, the position corresponding to the event that occurred among the K events is filled with the measurement results corresponding to at least one event that satisfies the conditions, and the position corresponding to the event that did not occur is filled with the measurement results that do not satisfy the conditions of the event.

[0528] As shown in Table 4 below, assuming that cell #1 of the terminal device is associated with K events, namely event 1, event 2, ..., event K, and the payload size required to report the measurement results related to each event is P1, P2, ..., PK respectively, then the payload size Z required to trigger the reporting of measurement results related to the events of cell #1 is Z = P1 + P2 + ... + PK. If event 2 does not occur, but all other events occur, then the reporting position corresponding to event 2 can be filled with 0, and the length of the 0 is the payload size required for the measurement results related to event 2. The other reporting positions are filled with the measurement results related to the events that occurred (e.g., event 1, event 3, ..., event K).

[0529] Table 4

[0530] Measurement results related to event 1 - P1 bit All 0s [Reporting position corresponding to event 2] - P2 bit … Measurement results related to event K - PK bit

[0531] In another example, taking one of the M cells as an example, the load required to report the measurement results related to that cell can be the load required for the union of all reported parameters corresponding to all events supported on that cell.

[0532] For example, network device configuration, and / or terminal device determination, and / or protocol stipulation, the K events associated with a cell (e.g., cell #1) of the terminal device are event 1, event 2, ..., event K, and the union of the reporting parameters corresponding to all events is reporting parameter #a, reporting parameter #b, ..., reporting parameter #j, that is, at least one event has reporting parameter #a, reporting parameter #b, ..., reporting parameter #j. In the example of this application, reporting parameter #a, reporting parameter #b, ..., reporting parameter #j can be any of the aforementioned reporting parameters #1 to reporting parameter #11, and the load size required to report each reporting parameter is Xa, Xb, ..., Xj, respectively. When at least one event has a reporting parameter #a, the maximum value of the maximum number of reports of the reporting parameter #a corresponding to all events in the at least one event is denoted as Na. This can be understood as follows: for example, if only events 1 and 2 among K events have reporting parameters containing the reporting parameter #a, and the maximum number of reports of the reporting parameter #a corresponding to event 1 is 2, and the maximum number of reports of the reporting parameter #a corresponding to event 1 is 3, then the maximum value of the maximum number of reports of the reporting parameter #a can be said to be Na = 3. Similarly, the maximum values ​​of the maximum number of reports corresponding to reporting parameters #a, #b, ..., #j are Na, Nb, ..., Nj, respectively. Therefore, the payload size required by the terminal device to determine the measurement results triggered by the event related to cell #1 is: S = Xa*Na + Xb*Nb + ... + Xj*Nj. That is, if events m and n among the K events correspond to the same reporting parameter, then one or more measurements corresponding to that reporting parameter can be reported only once, without needing to be reported repeatedly.

[0533] Optionally, if all K events occur, the terminal device can report the measurement of each reporting parameter in sequence according to the reporting order of each reporting parameter (i.e., reporting parameter #a, reporting parameter #b, ..., reporting parameter #j) specified in the protocol.

[0534] Optionally, if no event corresponding to a certain reporting parameter occurs, the reporting position corresponding to that reporting parameter can be filled with a predefined value (e.g., 0). The length of the predefined value is the load size required for the measurement of that reporting parameter. Alternatively, the measurement of that reporting parameter that does not meet the event conditions can also be filled. If at least one event corresponding to a certain reporting parameter occurs, the measurement of that reporting parameter is reported once. Furthermore, if the maximum number of reports corresponding to the event is less than the maximum value of the maximum reporting parameter, the predefined value (e.g., 0) can be used to fill the position, or the measurement of that reporting parameter that does not meet the event conditions can be filled.

[0535] As shown in Table 5 below, assuming the network device configuration and / or terminal device determination, and / or protocol stipulation, the K events associated with cell #1 of the terminal device are event 1, event 2, ..., event K, and the union of the reported parameters corresponding to all events is reported parameter #a, reported parameter #b, ..., reported parameter #j, and the corresponding payload sizes required to report each reported parameter are Xa, Xb, ..., Xj, respectively. The maximum number of reports for each reported parameter is Na, Nb, ..., Nj. Then, the payload size required for the terminal device to determine the measurement results triggered by the events related to cell #1 is: S = Na*Xa + Nb*Xb + ... + Nj*Xj. If none of the events corresponding to reported parameter #j occur, but at least one event corresponding to other reported parameters occurs, then the reporting position corresponding to reported parameter #j can be filled with 0s, and the length of the 0s is the payload size required for reported parameter #j, i.e., Xj. The other reporting positions are filled with the measurement quantities of the reporting parameters related to the event (e.g., reporting parameter #1, reporting parameter #2, ...), with corresponding payload sizes of Xa bits, Xb bits, ... . Furthermore, when the maximum number of reported parameters corresponding to an event is less than the maximum value of the reported parameter, a predefined value (e.g., 0) can be used to fill the measurement quantity corresponding to that reported parameter that does not meet the event conditions. For example, if only event 1 occurs, and the maximum number of reported parameters #a corresponding to event 1 is 2, while the maximum value of the maximum number of reported parameters #a is Na = 3, then Xa bits in the 3*Xa bits will be filled with 0 or filled with a measurement quantity corresponding to the reported parameter #a that does not meet the event conditions.

[0536] Table 5

[0537]

[0538]

[0539] Method 2: Use flexible load size reporting.

[0540] For example, taking one of the M1 cells as an example, the terminal device can send second information to the network device. This second information indicates event information of at least one event occurring in that cell, or event information requiring the reporting of relevant measurement results; and / or, the number of reports for each reporting parameter corresponding to each occurring event. That is, the terminal device indicates the information of the events occurring in that cell to the network device and reports the measurement results related to the events. Then, the load required to trigger the relevant measurement results on that cell is determined by the information of the events occurring in that cell and / or the number of reports for each reporting parameter corresponding to each occurring event. In this application, an event can be understood as an event that occurs and reports relevant measurement results, or it can be understood as an event that meets the event conditions.

[0541] Optionally, this application does not limit the order in which the second information and the measurement report are sent. The second information may be sent first, followed by the measurement report, or the measurement report may be sent first, followed by the second information; or the second information and the measurement report may be sent simultaneously.

[0542] For example, network device configuration, and / or terminal device determination, and / or protocol stipulation, may specify that a terminal device's cell (e.g., cell #1) is associated with K events, namely event 1, event 2, ..., event K, and the payload size required to report the measurement results related to each event is P1, P2, ..., PK, respectively. Here, P1, P2, ..., PK can be determined according to the aforementioned step one, which will not be elaborated here. When events p and q occur among the K events, the terminal device reports the index information of events p and q, and / or the number of reports for each reported parameter corresponding to event p and the number of reports for each reported parameter corresponding to event q. The payload sizes required to report the measurement results related to events p and q are Pp and Pq, respectively. Therefore, the payload size required for the terminal device to determine the reported measurement results triggered by the events related to cell #1 is: Z = Pp + Pq.

[0543] Optionally, the information of the events that have occurred, or the event information that needs to be reported for related measurement results (e.g., index information of events p and q), and / or the number of reports for each reporting parameter corresponding to each event that has occurred, can be carried in the scheduling request signaling or the reporting indication signaling. The payload size required for the terminal device to report the measurement results triggered by the event related to cell #1 is: S = Pp + Pq.

[0544] As shown in Tables 6 and 7 below, taking the occurrence of events p and q among K events associated with a cell (e.g., cell #1) of a terminal device as an example, the reporting parameters corresponding to event p include reporting parameter #a and reporting parameter #b, and the number of reporting parameters #a and #b that satisfy the conditions of event p are x and y, respectively. The reporting parameters corresponding to event q include reporting parameter #c and reporting parameter #d, and the number of reporting parameters #c and #d that satisfy the conditions of event q are m and n, respectively. Reporting parameter #a or reporting parameter #b or reporting parameter #d... Parameter #c or reporting parameter #d can be any of the aforementioned reporting parameters #1 to #11. x, y, m, and n are all positive integers. Therefore, the terminal device can send scheduling request signaling or reporting indication signaling in the form of Table 6. The scheduling request signaling or reporting indication signaling includes the index information of event p, the number of reports x of reporting parameter #a and the number of reports y of reporting parameter #b corresponding to event p, and the index information of event q, the number of reports m of reporting parameter #c and the number of reports n of reporting parameter #d corresponding to event q. In addition, the terminal device can also report the measurement quantities corresponding to x reporting parameters #a and y reporting parameters #b for event p in the form of Table 7, as well as the measurement quantities corresponding to m reporting parameters #c and n reporting parameters #d for event q. Since the required load sizes for reporting parameters #a, #b, #c, and #d are Pa, Pb, Pc, and Pd respectively, the load size required for the terminal device to report the measurement results related to events p and q is: S = Pa*x + Pb*y + Pc*m + Pd*n.

[0545] Optionally, the scheduling request signaling or reporting indication signaling in Table 5 may contain only the index information of events p and q, without reporting the number of reporting parameters corresponding to the events that occurred, such as the number of reports for each reporting parameter corresponding to events p and q.

[0546] Optionally, Tables 6 and 7 can be combined or implemented independently, without limitation.

[0547] Table 6

[0548]

[0549] Table 7

[0550]

[0551]

[0552] Optionally, the information of the events that occurred, or the event information that needs to report relevant measurement results (e.g., index information of events p and q), and / or the number of reports for each reporting parameter corresponding to each event, can be carried in CSI part 1 of a measurement report. The measurement quantity corresponding to each reporting parameter corresponding to events p and q can be carried in CSI Part 2 of the measurement report. Then, the payload size required for the terminal device to report the measurement results triggered by the event related to cell #1 is: S = Pp + Pq + N, where N is the number of bits required to report the information of the events that occurred and / or the number of reports for each reporting parameter corresponding to each event. The payload size in CSI part 1 is N, and the payload size of the measurement results triggered by the event related to cell #1 in CSI part 2 is Pp + Pq.

[0553] As shown in Table 8 below, taking the occurrence of events p and q among K events associated with a cell (e.g., cell #1) of a terminal device as an example, the reporting parameters corresponding to event p include reporting parameter #a and reporting parameter #b. The number of reporting parameters #a and #b that satisfy the conditions of event p are x and y, respectively. The reporting parameters corresponding to event q include reporting parameter #c and reporting parameter #d. The number of reporting parameters #c and #d that satisfy the conditions of event q are m and n, respectively. Reporting parameter #a, #b, #c, or #d can be any of the aforementioned reporting parameters #1 to #11. x, y, m, and n are all positive integers. Therefore, a measurement report reported by the terminal device includes CSI part 1 and CSI part 2, where CSI part 1... Part 1 carries the index information of events p and q, the number of reported parameters #a (x) and #b (y) corresponding to event p, and the number of reported parameters #c (m) and #d (n) corresponding to event q. Part 2 carries the reported measurement results corresponding to events p and q, namely the measurement quantities corresponding to x reported parameters #a and y reported parameters #b corresponding to event p, and the measurement quantities corresponding to m reported parameters #c and n reported parameters #d corresponding to event q. If the required payload sizes for reported parameters #a, #b, #c, and #d are Pa, Pb, Pc, and Pd, respectively, then the payload size for CSI part 2 is the sum of the payload sizes for x reported parameters #a, y reported parameters #b, m reported parameters #c, and n reported parameters #d. In other words, the payload size for CSI part 2 is: S = Pa*x + Pb*y + Pc*m + Pd*n.

[0554] Optionally, the aforementioned measurement report may contain only the measurement results reported by an event related to a single cell.

[0555] Table 8

[0556]

[0557]

[0558] As shown in Table 9 below, the terminal reports the measurement results related to events p and q among K events associated with a cell of the terminal device through a measurement report. The difference from Table 8 above is that CSI part 1 only contains the index information of events p and q, without reporting the number of reports for each reporting parameter corresponding to the events, such as the number of reports for each reporting parameter corresponding to events p and q. Specifically, this measurement report includes CSI part 1 and CSI part 2. CSI part 1 carries the indexes of events p and q, and CSI part 2 carries the relevant measurement results corresponding to events p and q. The relevant measurement results for events p and q are Yp and Yq, respectively. The payload size corresponding to Yp and Yq can be determined by the aforementioned step 1, that is, the payload size corresponding to CSI part 2 is: S = Yp + Yq.

[0559] Table 9

[0560]

[0561] For example, the terminal device indicates to the network device the load required to report the event-related measurement results for a cell. For instance, the load required to report the event-related measurement results for each of M events can be determined based on the load required for the event-related measurement results for the corresponding cell, as indicated by the terminal device to the network device.

[0562] Optionally, the required load size for the event-related measurement results corresponding to a cell can be carried in a first part (CSI Part 1) of a measurement report, and the event-related measurement results corresponding to the cell can be carried in a second part (CSI Part 2) of the measurement report. The load size is determined according to the load size of the event-related measurement results corresponding to the cell indicated in the first part (CSI Part 1) of the measurement report.

[0563] Optionally, the load required for the event-related measurement results corresponding to a cell can be carried in the scheduling request signaling or the reporting indication signaling. The load required for the event-related measurement results corresponding to the cell carried in the measurement report is determined according to the load required for the event-related measurement results corresponding to the cell indicated by the scheduling request signaling or the reporting indication signaling.

[0564] Step 3: Determine the load size of the measurement report, which includes measurement results related to at least one event for M1 cells.

[0565] Method 1: Report using a fixed load size.

[0566] In one example, the terminal device determines the payload size of the measurement report as: the payload size corresponding to the cell with the largest required payload size for the relevant measurement results among the M cells.

[0567] For example, network device configuration, and / or terminal device determination, and / or protocol stipulation, may associate a terminal device with K Control Centers (CCs), such as CC#1, CC#2, ..., CC#n, ..., CC#K. The K CCs are associated with events triggering reporting. The payload sizes required for the event-related measurement results of the K CCs are Z1, Z2, ..., Zn, ..., ZK, respectively. Z1, Z2, ..., Zn, ..., ZK can be determined by step 2 above. Among these, the maximum payload size required for the event-related measurement results of CC#n among the K CCs is Zn. Therefore, the terminal device determines the payload size of this measurement report as: F = Zn.

[0568] Optionally, if an event occurs in CC#1 out of the K CCs, and the load size 'a' required for the measurement results related to this event is less than F, then the remaining positions are filled with a special value, such as all 0s, and the corresponding load size is Fa. For the specific implementation of event triggering and reporting related to a CC, please refer to the relevant description in step 2 above.

[0569] Optionally, if an event occurs in one or more of the K CCs, and the load size b required to report the event-related measurement results on the one or more CCs is less than F, then the remaining positions are filled with special values, such as all 0s, and the corresponding load size is Fb; if the load size c required to report the event-related measurement results on the one or more CCs is greater than F, then the excess parts can be discarded according to a predefined priority, such as discarding the measurement results related to scell or neighboring cell events.

[0570] As shown in Table 10 below, assuming the network device configures multiple cells for the terminal device, such as the reporting triggered by events associated with CC#1, CC#2 and CC#3, the payload sizes required for the measurement results related to the events of the three CCs are Z1, Z2 and Z3 respectively. Z1, Z2 and Z3 can be determined by the aforementioned step 2, where Z3 is the largest. Then the payload size of the measurement report to be reported by the terminal device is determined to be: F = Z3.

[0571] Table 10

[0572] CC#1 --- Event 1, Event 2, ... CC#2 --- Event a, Event b, ... CC#3 --- Event i, Event ii, ...

[0573] In another example, the terminal device determines the load size of the measurement report as the sum of the load sizes required for the measurement results associated with each of the M cells.

[0574] In other words, according to the method in step 2 above, the terminal device can determine the load size required for the measurement results of each of the M cells, and use the sum of the load sizes required for the measurement results of all cells as the load size of the measurement report.

[0575] For example, network device configuration, and / or terminal device determination, and / or protocol stipulation, the terminal device is associated with K CCs, such as CC#1, CC#2, ..., CC#n, ..., CC#K, the K CCs are associated with event-triggered reporting, and the required payload sizes for the measurement results related to the events of the K CCs are Z1, Z2, ..., Zn, ..., ZK respectively. Z1, Z2, ..., Zn, ..., ZK can be determined by the aforementioned step 2. Then the terminal device determines the payload size of the measurement report as: F = Z1 + Z2 + ... + ZK.

[0576] Optionally, if events occur in all M cells, the terminal device may report the measurement results related to each of the M cells in sequence according to the reporting order of each cell specified in the protocol (e.g., cell index from smallest to largest or from largest to smallest, or other specified order), and the reporting order of the reporting parameters corresponding to each cell.

[0577] For example, when one or more of the K CCs have an event, the required load size for the event-related measurement results of one or more CCs can be reported according to step 2 above; when one or more of the K CCs have no event, the reporting position corresponding to the one or more CCs is filled with a predefined value, such as 0, and the length of the predefined value is the required load size for the event-related measurement results of the one or more CCs.

[0578] In another example, the terminal device determines the payload size of the measurement report as: the payload size of the event with the largest required payload size for the related measurement results among the X events corresponding to M cells.

[0579] For example, network device configuration, and / or terminal device determination, and / or protocol stipulation, may associate the terminal device with K Control Centers (CCs), such as CC#1, CC#2, ..., CC#K. These K CCs are associated with event-triggered reporting. CC#1 supports event-triggered reporting for events 1 and 2, CC#2 supports event-triggered reporting for events a and b, ..., CC#K supports event-triggered reporting for events i and ii. The payload size required for the measurement results associated with each event in each of these K CCs can be determined according to step 1. If the event with the largest payload size among all events in the K CCs is event i in CC#K, with a corresponding payload size of Xi, then the payload size of the measurement report to be reported by the terminal device is determined to be: F = Xi.

[0580] Optionally, if one or more events of a CC occur, or one or more events of multiple CCs occur, and the load required to report the measurement results related to one or more events of one or more CCs is less than Xi, then the remaining positions are filled with a special value; if the load required to report the measurement results related to one or more events of the one or more CCs is greater than Xi, then the excess parts are discarded according to a predefined priority.

[0581] For example, if only one event occurs in a single CC, such as event 1 of CC#1, and the required size X1 for event 1 on CC#1 is less than Xi, then the remaining space is filled with a special value, such as all zeros, and the corresponding load size is Xi-X1. If events 1 and 2 of CC#1 and event b of CC#2 occur, and the required load size X1+X2+Xa for the measurement results related to events 1, 2, and b is greater than Xi, then the excess portion is discarded according to a predefined priority. For example, if the reporting priority of CC#1 is higher than that of CC#2, and X1+X2 is less than Xi, then the terminal device can report the measurement results related to events 1 and 2 of CC#1, and discard the measurement results related to event b of CC#2.

[0582] Method 2: Use flexible load size reporting.

[0583] For example, the terminal device may send first information to the network device, the first information being used to indicate information about each of the M1 cells, and / or, the load size of the measurement report, and / or, information about events occurring in each of the M1 cells or event information about each of the M1 cells that needs to report relevant measurement results, and / or, the number of reports for each reporting parameter corresponding to each event occurring in each of the M1 cells, or the number of reports for each reporting parameter corresponding to each event that needs to report relevant measurement results in each of the M1 cells, and / or, the load size required for each of the M1 cells, and the load size required for each event occurring in each of the M1 cells.

[0584] Optionally, this application does not limit the order in which the first information and the measurement report are sent. The first information may be sent first, followed by the measurement report, or the measurement report may be sent first, followed by the first information; or the first information and the measurement report may be sent simultaneously.

[0585] Optionally, this application does not limit the order in which the first information and the second information are sent. The first information may be sent first and then the second information may be sent, or the second information may be sent first and then the first information may be sent; or the first information and the second information may be sent simultaneously.

[0586] Optionally, the first information can be carried in CSI part 1 of the measurement report, or in the dispatch request signaling, or in the reporting instruction signaling, or of course in other signaling, which is not limited in this application.

[0587] Below, examples are provided to illustrate the specific content contained in the first piece of information.

[0588] The first possible approach is that the first information includes information about M1 cells.

[0589] For example, the network device configures K CCs (CCs) for the terminal device, such as CC#1, CC#2, ..., CC#K, to report event triggers. When an event occurs in M1 cells, the terminal device can send information about the M1 cells to the network device, such as cell indexes, or the status of whether an event has occurred in each of the K configured cells. The payload size of the measurement report is the sum of the payload sizes required for the measurement results related to the event triggers of the M1 cells. The payload size required for the measurement results related to the event triggers of each of the M1 cells can be determined according to step 2 above. For example, when events occur in CC#1 and CC#2 of the terminal device, the terminal device can report the cell information of CC#1 and CC#2 (such as cell indexes, or bitmaps indicating that events have occurred in CC#1 and CC#2). If the payload sizes required for the measurement results related to the event triggers of CC#1 and CC#2 are Z1 and Z2 respectively, then the payload size of the measurement report reported by the terminal device is: F = Z1 + Z2. In this application, the required load size of the cell can be understood as the load size required to report the measurement results related to the cell (or CC) event trigger.

[0590] Optionally, if the first information is carried in CSI part 1 of the measurement report, the payload size of the measurement report reported by the terminal device is: the sum of the payload sizes required for the M1 cells corresponding to the information of the M1 cells sent by the terminal device to the network device, plus the number of bits required to report the information of the M1 cells. Wherein, the payload size of CSI part 1 of the measurement report is the number of bits required to report the information of the M1 cells, and the payload size of CSI part 2 of the measurement report is the sum of the payload sizes required for the measurement results related to the M1 cell events triggered by the information of the M1 cells sent by the terminal device to the network device. For example, when events CC#1 and CC#2 occur on a terminal device, the terminal device can report the cell information of CC#1 and CC#2 (e.g., cell index, or bitmap indicating the occurrence of events CC#1 and CC#2) through a measurement report CSIPart1. If the payload sizes required for the measurement results related to CC#1 and CC#2 are Z1 and Z2 respectively, then the payload size corresponding to CSIPart2 of the measurement report reported by the terminal device is Z1 + Z2, and the payload size corresponding to CSIPart1 of the measurement report reported by the terminal device is L, where L is the number of bits required to report the cell information of the event. Therefore, the payload size of the measurement report reported by the terminal device is: F = Z1 + Z2 + L.

[0591] The second possible approach is that the first information includes information about M1 cells, as well as information about events occurring in each of the M1 cells.

[0592] For example, the network device configures K CCs for the terminal device, such as CC#1, CC#2, ..., CC#K, to report events triggered by them. When an event occurs in M1 cells, such as event 1 occurring in cell 1 to cell M1, event 1 occurring in cell 1, event 1 and event 2 occurring in cell 2, ..., event m1 occurring in cell M1, where event 1, event 2, ..., or event m1 in this example is any of the events #A to #K mentioned above, the terminal device can send information about the M1 cells to the network device, such as the cell index or the status of whether an event has occurred in each of the K configured cells, and information about the events that have occurred in each of the M1 cells, such as the event index. The load size of the measurement report is the sum of the load sizes required for the measurement results related to the event triggering of the M1 cells corresponding to the information of the M1 cells. The load size required for the measurement results related to the event triggering of each of the M1 cells can be determined according to step 2 above, and the load size required for the measurement results related to the events that have occurred in each of the M1 cells can be determined according to step 1 above. For example, when events occur on CC#1 and CC#2 of the terminal device, with event 1 occurring on CC#1 and event 2 occurring on CC#2, the terminal device can report the cell information of CC#1 and CC#2 (e.g., cell index, or a bitmap indicating that events have occurred on CC#1 and CC#2), as well as the event information of event 1 occurring on CC#1 and event 2 occurring on CC#2 (e.g., event index). If the payload sizes required for the measurement results triggered by events CC#1 and CC#2 are Z1 and Z2 respectively, then the payload size of the measurement report reported by the terminal device is: F = Z1 + Z2.

[0593] Optionally, if the first information is carried in CSI part 1 of the measurement report, the payload size of the measurement report reported by the terminal device is: the sum of the payload sizes required for the M1 cells corresponding to the information of the M1 cells sent by the terminal device to the network device, plus the number of bits required for reporting the information of the M1 cells, plus the number of bits required for the information of the events occurring in each of the M1 cells. Wherein, the payload size of CSI part 1 of the measurement report is the sum of the number of bits required for reporting the information of the M1 cells and the number of bits required for reporting the information of the events occurring in each of the M1 cells, and the payload size of CSI part 2 of the measurement report is the sum of the payload sizes required for the measurement results related to the M1 cell events triggered by the information of the M1 cells sent by the terminal device to the network device. For example, when events occur on CC#1 and CC#2 of a terminal device, with event 1 occurring on CC#1 and event 2 occurring on CC#2, the terminal device can report the cell information of CC#1 and CC#2 (e.g., cell index, or bitmap indicating the occurrence of events on CC#1 and CC#2) and the information of the events occurring on CC#1 and CC#2 (e.g., event index) through a measurement report CSIPart1. If the payload sizes required for the measurement results related to CC#1 and CC#2 are Z1 and Z2 respectively, then the payload size corresponding to CSI Part2 of the measurement report reported by the terminal device is Z1+Z2, and the payload size corresponding to CSIPart1 of the measurement report reported by the terminal device is L1+L2, where L1 is the number of bits required to report the cell information of the event, and L2 is the number of bits required to report the information of the event. Therefore, the payload size of the measurement report reported by the terminal device is: F = Z1+Z2+L1+L2.

[0594] The third possible approach is that the first information includes information about M1 cells, information about events occurring in each of the M1 cells, and the number of reports corresponding to each reporting parameter for each event occurring in each of the M1 cells.

[0595] For example, the network device configures K CCs for the terminal device, such as CC#1, CC#2, ..., CC#K, to report events triggered by associated events. When an event occurs in M1 cells, such as events 1 to M1 in cells 1, events 1 and 2 in cell 2, ..., and event m1 in cell M1, where events 1, 2, ..., or m1 in this example are any of the events #A to #K mentioned above, the terminal device can send information about the M1 cells to the network device, such as the cell index or the status of whether an event has occurred in each of the K configured cells, information about the events that have occurred in each of the M1 cells, such as the event index, and the number of reports for each reporting parameter corresponding to each event that has occurred in each of the M1 cells. The load size of the measurement report is the sum of the load sizes required for the measurement results related to the events triggered by the M1 cells. The load size required for the measurement results related to the events triggered by each of the M1 cells can be determined according to step 2 above. The load size required for the measurement results related to the events occurring in each of the M1 cells can be determined according to step 1 above. For example, when events occur on CC#1 and CC#2 of the terminal device, event 1 occurs on CC#1 and event 2 occurs on CC#2. The reporting parameters corresponding to event 1 include reporting parameter #a and reporting parameter #b. The number of reporting parameters #a and #b that satisfy the conditions of event 1 are x and y, respectively. The reporting parameters corresponding to event 2 include reporting parameter #c and reporting parameter #d. The number of reporting parameters #c and #d that satisfy the conditions of event 2 are m and n, respectively. Reporting parameter #a, reporting parameter #b, reporting parameter #c, or reporting parameter #d can be the aforementioned... If any one of the reporting parameters #1 to #11 is reported, the terminal device can report cell information for CC#1 and CC#2 (e.g., cell index, or a bitmap indicating the occurrence of events in CC#1 and CC#2), event information for event 1 occurring on CC#1 and event 2 occurring on CC#2 (e.g., event index), and the number of reports x for reporting parameter #a corresponding to event 1, the number of reports y for reporting parameter #b corresponding to event 1, the number of reports m for reporting parameter #c corresponding to event 2, and the number of reports m for reporting parameter #d corresponding to event 2. If the payload sizes required for the measurement results triggered by CC#1 and CC#2 events are Z1 and Z2 respectively, then the payload size of the measurement report reported by the terminal device is: F = Z1 + Z2.

[0596] Optionally, if the first information is carried in CSI part 1 of the measurement report, the payload size of the measurement report reported by the terminal device is: the sum of the payload sizes required for the M1 cells corresponding to the information of the M1 cells sent by the terminal device to the network device, plus the number of bits required for reporting the information of the M1 cells, plus the number of bits required for the information of the events occurring in each of the M1 cells, plus the sum of the number of bits required for the reporting of the reporting parameter #a corresponding to event 1 (x), the reporting parameter #b corresponding to event 1 (y), the reporting parameter #c corresponding to event 2 (m), and the reporting parameter #d corresponding to event 2 (n). The CSI part 1 of the measurement report has a load of the number of bits required to report information about M1 cells, plus the number of bits required to report information about events occurring in each of the M1 cells, plus the sum of the number of bits required to report the number of reports for reporting parameter #a corresponding to event 1 (x), the number of reports for reporting parameter #b corresponding to event 1 (y), the number of reports for reporting parameter #c corresponding to event 2 (m), and the number of reports for reporting parameter #d corresponding to event 2. The CSI part 2 of the measurement report has a load of the sum of the loads required to trigger the measurement results related to the M1 cell events corresponding to the information about the M1 cells sent by the terminal device to the network device.For example, when events occur on CC#1 and CC#2 of a terminal device, with event 1 occurring on CC#1 and event 2 occurring on CC#2, and the number of reported parameters for event 1 (#a, y, m) and event 2 (#c, m) corresponding to the reported parameters #a and #b, respectively, and the terminal device can report the cell information of CC#1 and CC#2 (e.g., cell index, or a bitmap indicating the occurrence of events on CC#1 and CC#2) through a measurement report's CSIPart1, the information of the events occurring on CC#1 and CC#2 (e.g., event index), and the number of reported parameters for event 1 (#a, y, m, m) and event 2 (#c, m, m) corresponding to the reported parameters #d, respectively. If the payload required for the measurement results related to CC#1 and CC#2 is... The sizes are Z1 and Z2 respectively. Therefore, the payload size corresponding to CSI Part 2 of the measurement report reported by the terminal device is Z1+Z2, and the payload size corresponding to CSI Part 1 of the measurement report reported by the terminal device is Z3+Z4+Z5. Z3 is the number of bits required to report the cell information of the event, Z4 is the number of bits required to report the information of the event, and Z5 is the number of bits required to report the number of reported parameters corresponding to the event. Therefore, the payload size of the measurement report reported by the terminal device is F=Z1+Z2+Z3+Z4+Z5.

[0597] The fourth possible approach is that the first information includes information about M1 cells and / or the required load size for each of the M1 cells.

[0598] For example, the network device configures K control cells (CCs) for the terminal device, such as CC#1, CC#2, ..., CC#K, to report events. When an event occurs in M1 cells, the terminal device can send information about the M1 cells to the network device, such as the cell index or the status of whether an event has occurred in each of the K configured cells, and / or the load required for each of the M1 cells. The load of the measurement report is the sum of the load required for each of the M1 cells reported by the terminal.

[0599] Optionally, if the first information is carried in CSI part 1 of the measurement report, the payload size of the measurement report reported by the terminal device is: the sum of the payload sizes required for the M1 cells corresponding to the information of the M1 cells sent by the terminal device to the network device, plus the number of bits required to send the first information.

[0600] The fifth possible approach is that the first information includes M1 cell information and / or the load size required for each event occurring in each of the M1 cells.

[0601] For example, the network device configures K control cells (CCs) for the terminal device, such as CC#1, CC#2, ..., CC#K, to report events. When an event occurs in M1 cells, the terminal device can send information about the M1 cells to the network device, such as the cell index or the status of whether an event has occurred in each of the K configured cells, and / or the load required for each event corresponding to each of the M1 cells. The load of the measurement report is the sum of the load required for each event corresponding to each of the M1 cells reported by the terminal.

[0602] Optionally, if the first information is carried in CSI part 1 of the measurement report, the payload size of the measurement report reported by the terminal device is: the sum of the payload sizes required for the M1 cells corresponding to the information of the M1 cells sent by the terminal device to the network device, plus the number of bits sent for the first information.

[0603] It is understandable that the above implementation is only an example for ease of understanding, and other solutions are not excluded.

[0604] Optionally, the terminal device can also report the payload size required for the measurement results related to the cell where the event occurred. For example, the terminal device can report the required payload size in a scheduling request, resource indication, or CSI part 1 of a measurement report; or, the network configures one or more payload sizes, and the terminal device indicates one of the payload sizes based on the payload size required for the measurement results related to the cell where the event occurred to be reported.

[0605] Optionally, each of the M cells can correspond to the same reporting resource, or each of the M cells can correspond to different reporting resources, for example, the M cells and the M reporting resources are in one-to-one correspondence; or, at least two of the M cells correspond to different reporting resources, for example, the M cells and the N reporting resources are in correspondence, where M < N, and there is no restriction on this.

[0606] Figure 7 This diagram illustrates the measurement results of a reported event carried by a measurement report associated with multiple cell types (CCs). Assuming an event, such as event 1, occurs on a cell (CC1), a measurement report reported by the terminal device can be one of the following three examples: Figure 7As shown in (a), the CSI Part 1 of the measurement report includes a CC index (e.g., CC1), and CSI Part 2 includes a predefined value for Event 1, beam index #1, a predefined value, beam quality #1, and a predefined value; as Figure 7 As shown in (b), the CSI Part 1 of the measurement report includes a CC index (e.g., CC1) and event index information (e.g., event #1), and CSI Part 2 includes beam index #1, predefined values, beam quality #1, and predefined values; as Figure 7 As shown in (c), the CSI Part 1 of this measurement report includes a CC index (e.g., CC1), event index information (e.g., event #1), and the number of reported beams, while CSI Part 2 includes beam index #1 and beam quality #1. The above is merely an example illustration of the fields contained in the first and second parts of a measurement report for ease of understanding; other implementations are not excluded.

[0607] In other words, if a network device is configured with a measurement report, it means that the measurement results for at least one event corresponding to M1 cells are all contained in a single measurement report. In this case, the first part of the measurement report can be placed first, and the second part can be placed after the first part. Specifically, the first part of the measurement results related to at least one event corresponding to M1 cells is contained in the first part of the single measurement report, and the second part of the measurement results related to at least one event corresponding to M1 cells is contained in the second part of the single measurement report. The first and second parts can be encoded independently.

[0608] Scenario 2: A measurement report is configured to be associated with only one cell, that is, the terminal device reports the measurement results of at least one event corresponding to one of the M1 cells through a measurement report.

[0609] Step 1: Determine the load size required to report the measurement results related to one of the X events. For the specific implementation method, please refer to the relevant description of Step 1 in Case 1 above. For the sake of brevity, it will not be repeated here.

[0610] Optionally, a measurement report includes a first part, CSIPart 1, and a second part, CSIPart 2. Multiple measurement report configurations are provided for M cells, and the terminal device sends multiple measurement reports according to the priority ordering information of the multiple measurement report configurations. The first part of the multiple measurement reports includes at least one event-related first part corresponding to M1 cells, and the second part of the multiple measurement reports includes a second part of the measurement results related to at least one event corresponding to M1 cells.

[0611] Step 2: Determine the load size for event triggering reporting for one of the M cells (or a CC). The specific implementation can be found in the descriptions of Step 2 or Step 3 (M1=1) in Case 1 above. For simplicity, these details will not be repeated here. The load size for subsequent measurement reports from each cell can be determined based on the load size required for reporting the cell-related measurement results in Step 2 of Case 1 above.

[0612] Step 3: Determine the load size of the multiple measurement reports. Each measurement report includes event-related measurement results for one of the M1 cells. In other words, one measurement report corresponds to one cell, and one measurement report carries the event-related measurement results for that one cell.

[0613] (1) Measurement reports associated with different CCs are submitted in order of predefined priority.

[0614] As an example, if multiple measurement reports corresponding to one or more CCs are associated with the same scheduling request or indication resource, and the scheduling request or indication resource does not carry cell information and / or measurement report configuration index for the event, if no event occurs in the event associated with a certain measurement report, then the reporting position of that measurement report is filled with a predefined value, such as 0. The length of the predefined value is the load size required by that measurement report. The load size required by the measurement report can be determined according to the aforementioned case where M1=1.

[0615] If a network device is configured to report events triggered by K cell associations through the same reporting resource, then the load of the measurement report is the sum of the loads of the measurement reports associated with those K cells. When no event occurs in the measurement report corresponding to a certain CC, the reporting space for that CC can be filled with a special value. Alternatively, if one or more measurement reports are reported through the same reporting resource, and each measurement report is associated with one cell, then the load required to report these one or more measurement reports is the sum of the loads of those one or more measurement reports, or the sum of the loads required to report events triggered by all cells associated with the one or more measurement reports.

[0616] As shown in Table 11 below, for example, when CC#1, CC#2, and CC#3 are associated with event-triggered reports, each of the three CCs corresponds to a measurement report, such as measurement report #1, measurement report #2, and measurement report #3. The measurement report for CC#1 has a higher priority than CC#2, and CC#2 has a higher priority than CC#3. Therefore, the terminal device reports measurement reports #1, #2, and #3 corresponding to CC#1, CC#2, and CC#3 in sequence according to their reporting priority. For example, if no event occurs for CC#2, a predefined value, such as 0, will be filled in measurement report #2 corresponding to CC#2.

[0617] Table 11

[0618] Measurement report #1 corresponding to CC#1 Measurement report #2 corresponding to CC#2 [Fill in predefined values] Measurement report #3 corresponding to CC#3

[0619] As another example, if multiple measurement reports corresponding to multiple CCs are configured to be associated with different scheduling requests or indication resources, or if multiple measurement reports corresponding to multiple CCs are configured to be associated with the same scheduling request or indication resource, but the scheduling request or indication resource carries cell information of the cell where the event occurred or cell information of the measurement results triggered by the event that needs to be reported, then the measurement reports corresponding to different CCs where the event occurred are reported in order of predefined priority.

[0620] If a network device is configured to report K cell-related events triggered by a terminal device through the same reporting resource, then the load size of the measurement report is the sum of the load sizes required for all CCs (Common Control Points) where an event has occurred or where reporting of event-triggered measurement results is required. Alternatively, if one or more measurement reports are reported through the same reporting resource, then the load size required to report these one or more measurement reports is the sum of the load sizes of the measurement reports among these one or more that contain events.

[0621] As shown in Table 12, the terminal device reports events triggered by multiple cells, such as CC#1, CC#2, and CC#3. Each of the three CCs corresponds to a measurement report, such as measurement report #1, measurement report #2, and measurement report #3. The measurement report for CC#1 has a higher priority than CC#2, and CC#2 has a higher priority than CC#3. Therefore, the terminal device can report measurement reports #1, #2, and #3 corresponding to CC#1, CC#2, and CC#3 in sequence according to their reporting priority. For example, if no event occurs in CC#2, then measurement report #2 corresponding to CC#2 does not need to be reported. That is, the terminal device only needs to report measurement reports #1 and #3 corresponding to CC#1 and CC#3 in sequence according to their priority.

[0622] Table 12

[0623] CC#1 Measurement Report#1 CC#3 Measurement Report #3

[0624] (2) A measurement report consists of a first part, CSI Part 1, and a second part, CSI Part 2. The reporting size of CSI Part 2 is determined based on CSI Part 1. CSI Part 1 of different measurement reports is coded in order of priority, and CSI Part 2 of different measurement reports is coded in order of priority. CSI Part 1 and CSI Part 2 can be coded independently. Each measurement report is associated with a CC.

[0625] As an example, if multiple measurement reports corresponding to one or more CCs are configured to be associated with the same scheduling request or indication resource, and the scheduling request or indication resource does not carry cell information of the event, if there is no event in the event associated with a certain measurement report, then the reporting position corresponding to CSI part 1 of the measurement report is filled with a predefined value, and at this time the measurement report has no CSI Part 2.

[0626] Optionally, CSI Part 1 of each measurement report may include one or more of the following: whether an event occurred in the measurement report; information about the event (e.g., event index); and the number of reported parameters for each event. Optionally, the measurement results contained in CSI Part 2 of each measurement report are determined based on the information in CSI Part 1.

[0627] As shown in Table 13, a measurement report corresponding to CC#1 has a higher priority than a measurement report corresponding to CC#2, and the measurement report corresponding to CC#2 has a higher priority than a measurement report corresponding to CC#3. Therefore, the terminal device can report measurement reports #1, #2, and #3 corresponding to CC#1, CC#2, and CC#3 respectively in sequence according to their reporting priority. For example, if no event occurs for CC#2, then a predefined value, such as 0, will be filled in CSI part 1 of measurement report #2 corresponding to CC#2. Correspondingly, CSI part 2 of measurement report #2 corresponding to CC#2 is determined based on CSI part 1 and does not exist.

[0628] Table 13 shows the CSI Part 1 mapping order of measurement reports for multiple CCs.

[0629] CSI Part 1 of Measurement Report #1 corresponding to CC#1 CSI part 1 of measurement report #2 corresponding to CC#2 [Fill in predefined values] CSI Part 1 of Measurement Report #3 corresponding to CC#3

[0630] Part 2 mapping order of measurement reports for multiple CCs

[0631] CSI Part 2 of Measurement Report #1 corresponding to CC#1 CSI Part 2 of Measurement Report #3 corresponding to CC#3

[0632] As another example, if multiple measurement reports corresponding to multiple CCs are associated with different scheduling requests or indication resources, or if multiple measurement reports corresponding to multiple CCs are associated with the same scheduling request or indication resource, but the scheduling request or indication resource carries the cell information where the event occurred and / or the measurement report configuration index, if there is an event associated with a certain measurement report where no event has occurred, then the CSIPart1 and CSIPart2 of the measurement report corresponding to the measurement result triggered by the event or the event that needs to be reported will be reported in order of predefined priority.

[0633] As shown in Table 14, a measurement report corresponding to CC#1 has a higher priority than a measurement report corresponding to CC#2, and a measurement report corresponding to CC#2 has a higher priority than a measurement report corresponding to CC#3. Therefore, the terminal device can report measurement reports #1, #2, and #3 corresponding to CC#1, CC#2, and CC#3 in sequence according to their reporting priority. For example, if no event occurs for CC#2, then CSIPart1 and CSIPart2 of measurement report #2 corresponding to CC#2 do not need to be reported. That is, the terminal device only needs to report CSIPart1 of measurement reports #1 and #3 corresponding to CC#1 and CC#3, and CSI Part2 of measurement reports #1 and #3, in sequence according to their priority.

[0634] Table 14 Mapping order of Part 1 of measurement reports for multiple CCs

[0635] CSI Part 1 of Measurement Report #1 corresponding to CC#1 CSI Part 1 of Measurement Report #3 corresponding to CC#3

[0636] Part 2 mapping order of measurement reports for multiple CCs

[0637] CSI Part 2 of Measurement Report #1 corresponding to CC#1 CSI Part 2 of Measurement Report #3 corresponding to CC#3

[0638] Optionally, each of the M cells can correspond to the same reporting resource, or each of the M cells can correspond to different reporting resources, for example, the M cells and the M reporting resources are in one-to-one correspondence; or, at least two of the M cells correspond to different reporting resources, for example, the M cells and the N reporting resources are in correspondence, where M < N, and there is no restriction on this.

[0639] Based on the above scheme, terminal devices can report events across cells, thereby avoiding the reporting of invalid measurement reports to network devices. Furthermore, terminal devices can define a reporting format for measurement reports carrying measurement results related to one or more events, thus avoiding resource waste caused by allocating reporting resources for each event when the terminal device supports or is configured to handle one or more events occurring in multiple cells, and improving transmission performance.

[0640] It is understood that some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0641] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0642] It should also be understood that this application will present various aspects, embodiments, or features in relation to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0643] It should also be understood that in some of the above embodiments, the examples are mainly based on devices in existing network architectures (e.g., a first device or a second device, etc.), and it should be understood that the specific form of the device is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0644] It is understood that, in the above-described method embodiments, the methods and operations implemented by the device (e.g., the first device or the second device) can also be implemented by components of the device (e.g., a chip or circuit).

[0645] The above, combined with Figures 1 to 6 The method for reporting measurement results provided in the embodiments of this application is described in detail. The above method is mainly described from the perspective of the interaction between the first device and the second device. It is understood that, in order to achieve the above functions, the first device and the second device include hardware structures and / or software modules corresponding to the execution of each function.

[0646] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0647] The following, combined with Figures 8 to 11This application provides a detailed description of the communication device provided in the embodiments. The descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, for content not described in detail, please refer to the above method embodiments. For the sake of brevity, some content will not be repeated.

[0648] This application embodiment can divide the communication device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware, software, or a combination of both. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the division of functional modules according to each function as an example.

[0649] Figure 8 This is an exemplary block diagram of the communication device provided in the embodiments of this application. Figure 8 As shown, the communication device 1000 may include a chip system 1100, a memory 1200, a bus 1300, a power management module 1400, or a transceiver 1500, etc.

[0650] The chip system 1100 can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed through integrated logic circuits in the hardware of the chip system 1100 or through software instructions.

[0651] As an example and not a limitation, the chip system 1100 may include circuitry or chips responsible for signal processing (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) or SIP chip containing a modem core).

[0652] Optionally, the chip system 1100 may also include a memory (such as a cache) for storing instructions and data. In some embodiments, the memory in the chip system 1100 is a cache memory. This memory can store instructions or data that the chip system 1100 has just used or that are used repeatedly. If the chip system 1100 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the chip system 1100, and thus improves the efficiency of the system.

[0653] In some embodiments, the chip system 1100 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0654] The memory 1200 may include random access memory (RAM) and read-only memory (ROM). The memory 1200 may store computer-readable, computer-executable code, including instructions that, when executed, cause the processor to perform the various functions described in this application.

[0655] Optionally, the code may include instructions for implementing various aspects of the embodiments of this application, including instructions for supporting the generation or parsing of signals. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code may not be directly executable by the chip system 1100, but may enable a computer (e.g., at compile and execution time) to perform the functions described in this application. In some cases, memory 1200 may in particular contain a basic input / output (I / O) system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0656] For example, the chip system 1100 executes various functional applications and data processing of the communication device 1000 by running instructions stored in the memory 1200. For instance, when the communication device 1000 transfers files with other devices (e.g., terminal devices, network devices, or core network devices), the chip system 1100 of the communication device 1000 can call the computer-executable program code stored in the memory 1200 to implement the data and / or signaling transmission methods provided in the embodiments of this application.

[0657] Optionally, the memory 1200 may be integrated into the aforementioned chip system 1100, or may be independent of the chip system 1100.

[0658] Bus 1300 can be USB, used to support communication between various parts of communication device 1000.

[0659] The power management module 1400 is used to receive charging input from the charger. Optionally, the power management module 1400 can also supply power to the communication device 1000 while charging it (e.g., the battery module of the communication device 1000). By way of example and not limitation, the power management module 1400 can also supply power to other devices besides the communication device 1000.

[0660] Transceiver 1500 can communicate bidirectionally via one or more antennas, wired links, or wireless links. For example, transceiver 1500 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1500 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna. Transceiver 1500 may include a receiver and a transmitter, the receiver performing the function of receiving information and the transmitter performing the function of transmitting information.

[0661] In some cases, a wireless device may include a single antenna. However, in other cases, a device may have more than one antenna, such as... Figure 8 Antennas 1 and 2 shown may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Exemplarily, antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in communication device 1000 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch. Communication device 1000 can transfer files to other devices via wireless communication functions.

[0662] In one design, the communication device 1000 may correspond to the first device in the above method embodiment.

[0663] The device 1000 can implement the steps or processes corresponding to those performed by the first device in the above method embodiments, wherein the transceiver 1500 can be used to perform the transmission and reception related operations of the first device in the above method embodiments; and the chip system 1100 can be used to perform the processing related operations of the first device in the abo...

Claims

1. A reporting method of measurement results, characterized by, The method comprises: obtaining configuration information, the configuration information being used to indicate information of X events corresponding to M cells, M and X being integers greater than or equal to 1; sending a measurement report, the measurement report comprising measurement results of at least one event corresponding to M1 cells, the at least one event corresponding to the M1 cells being an event occurring in the X events, a load size of the measurement report being a load size required for reporting measurement results of a first event and / or a first cell, the M1 cells belonging to the M cells, M1 being a positive integer less than or equal to M.

2. A reporting method of measurement results, characterized by, The method comprises: sending configuration information, the configuration information being used to indicate information of X events corresponding to M cells, M and X being integers greater than or equal to 1; receiving a measurement report, the measurement report comprising measurement results of at least one event corresponding to M1 cells, the at least one event corresponding to the M1 cells being an event occurring in the X events, a load size of the measurement report being a load size required for reporting measurement results of a first event and / or a first cell, the M1 cells belonging to the M cells, M1 being a positive integer less than or equal to M.

3. The method according to claim 1 or 2, characterized in that, The M1 is equal to 1, and the at least one event is one event.

4. The method according to any one of claims 1 to 3, wherein the first event is an event with a maximum load in a load size required for reporting measurement results of the X events, the first cell is a cell with a maximum load in a load size required for reporting measurement results of the M cells.

5. The method according to any one of claims 1 to 3, wherein the first cell is the M cells, and the load size of the measurement report is a sum of load sizes required for reporting measurement results of the M cells.

6. The method according to any one of claims 1 to 5, characterized in that, a part of the measurement report other than the measurement results of the at least one event corresponding to the M1 cells is a predefined value.

7. The method of any one of claims 1, 3-6, wherein, The method further comprises: sending first information, the first information being used to indicate information of each of the M1 cells, and / or the load size of the measurement report.

8. The method of any one of claims 1, 3-7, wherein, The method further comprises: sending second information, the second information being used to indicate information of the at least one event corresponding to each of the M1 cells; and / or a reporting number of a reporting amount of each of the at least one event.

9. The method according to any one of claims 1 to 8, wherein the load size required for reporting measurement results of each of the M cells is determined according to an event with a maximum load size in load sizes required for reporting measurement results of one or more events corresponding to the each of the M cells; or the load size required for reporting measurement results of each of the M cells is determined according to a sum of load sizes required for reporting measurement results of all events corresponding to the each of the M cells.

10. The method according to any one of claims 1, 3 to 9, characterized in that, The method further comprises: determining a reporting amount of each of the X events, and a reporting number of the reporting amount of each of the X events.

11. The method of claim 10, wherein, A load size required for reporting a measurement result related to each event in the X events is determined according to a reporting quantity corresponding to each event and a reporting number of the reporting quantity.

12. The method of any one of claims 1 to 11, wherein, when M is greater than 1, at least two of the M cells correspond to different measurement report configurations; or, the M cells correspond to one measurement report configuration.

13. The method of claim 12, wherein, The measurement report configuration comprises one or more of: information of one or more of the M cells; one or more event information corresponding to one or more of the M cells; reference signal measurement resources corresponding to one or more events corresponding to one or more of the M cells; event trigger reporting resources corresponding to one or more of the M cells; scheduling request or indication resources corresponding to one or more of the M cells; a reporting quantity of an event corresponding to one or more of the M cells; or a reporting number of a reporting quantity of an event corresponding to one or more of the M cells.

14. The method of any one of claims 1, 3-13, wherein, The sending of the measurement report comprises: when the M cells correspond to one measurement report configuration, sending one measurement report, the one measurement report comprising at least one measurement result related to an event corresponding to the M1 cells, and an order of the at least one measurement result related to the event corresponding to the M1 cells in the one measurement report being determined according to cell priority order information corresponding to the M1 cells; or when the M cells correspond to multiple measurement report configurations, sending one or more measurement reports according to priority order information of the multiple measurement report configurations, the one or more measurement reports comprising at least one measurement result related to an event corresponding to the M1 cells.

15. The method of any one of claims 1, 3-14, wherein, The sending of the measurement report comprises: when the M cells correspond to one measurement report configuration, sending one measurement report, a first part of the one measurement report comprising a first part of at least one measurement result related to an event corresponding to the M1 cells, and a second part of the one measurement report comprising a second part of the at least one measurement result related to the event corresponding to the M1 cells, an order of the first part of the at least one measurement result related to the event corresponding to the M1 cells in the first part of the one measurement report being determined according to cell priority order information corresponding to the M1 cells, and an order of the second part of the at least one measurement result related to the event corresponding to the M1 cells in the second part of the one measurement report being determined according to the cell priority order information corresponding to the M1 cells; or when the M cells correspond to multiple measurement report configurations, sending one or more measurement reports according to priority order information of the multiple measurement report configurations, a first part of the one or more measurement reports comprising a first part of at least one measurement result related to an event corresponding to the M1 cells, and a second part of the one or more measurement reports comprising a second part of the at least one measurement result related to the event corresponding to the M1 cells.

16. The method of claim 15, wherein, the first part comprises one or more of: cell information of an event occurrence; whether the event occurs in a cell corresponding to the first part; information of the event occurrence in the cell corresponding to the first part; or, a reporting number of the reporting quantity corresponding to each of the at least one event; a load size corresponding to the second part is determined according to the first part.

17. The method according to any one of claims 14 to 16, characterized in that, the M cells correspond to a plurality of measurement report configurations, and the plurality of measurement report configurations one-to-one correspond to a plurality of measurement reports carried in a same reporting resource.

18. A communications device, characterized by comprising a module for implementing the method of any one of claims 1 to 17.

19. A communications device, characterized by comprising at least one processor configured to execute computer programs or instructions to cause the method of any one of claims 1 to 17 to be performed.

20. The communication apparatus of claim 19, wherein, the communication apparatus further comprises a memory configured to store the computer programs or instructions; and / or, the communication apparatus further comprises a communication interface coupled to the at least one processor, the communication interface configured to input and / or output information.

21. A computer-readable storage medium, characterized in that, the computer readable storage medium is configured to store computer programs, when the computer programs are run on a computer, cause the method of any one of claims 1 to 17 to be performed.

22. A computer program product, characterised in that, comprising computer programs or instructions, when the computer programs or instructions are executed by a processor, cause the method of any one of claims 1 to 17 to be performed.

Images