Measurement reporting methods, terminal and network side device

Abstract

The present application belongs to the field of communications. Disclosed are measurement reporting methods, a terminal and a network side device. A measurement reporting method of the embodiments of the present application comprises: on the basis of a prediction result associated with at least one cell, a terminal determines that a prediction event is satisfied; on the basis of a RRM measurement result of the at least one cell, the terminal determines whether the prediction result is incorrect; and when it is determined that the prediction result is incorrect, the terminal reports a first measurement report to a network side device. The first measurement report comprises at least one of the following: first indication information, used for indicating that the measurement event associated with the at least one cell is not satisfied; second indication information, used for indicating that the prediction result associated with the at least one cell is incorrect; an identifier of the at least one cell; and the RRM measurement result of the at least one cell.

Description

Measurement reporting methods, terminals and network-side equipment

[0001] Cross-references to related applications

[0002] This application is based on and claims priority to Chinese Patent Application No. 202510094097.5, filed on January 21, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, and specifically relates to a measurement reporting method, a terminal, and a network-side device. Background Technology

[0004] In New Radio (NR) systems, measurement event prediction is introduced, supporting both direct and indirect prediction. Direct prediction outputs either whether an event will occur within a future timeframe, or it outputs the probability of an event occurring within a future timeframe. Indirect prediction outputs future Radio Resource Management (RRM) measurement predictions, and post-processing based on these predictions determines whether the measurement event will occur in the future.

[0005] After the introduction of measurement event prediction, measurement reporting will be triggered when the predicted event is met. However, if the prediction result is incorrect, it may cause abnormal problems such as terminal handover failure, and the wireless resources reserved on the network side will also be wasted. Summary of the Invention

[0006] This application provides a measurement reporting method, a terminal, and a network-side device, which can solve the problem that if the prediction result is incorrect after introducing measurement event prediction, the terminal will fail to switch over and the reserved wireless resources on the network side will be wasted.

[0007] Firstly, a measurement reporting method is provided, including:

[0008] The terminal determines that the predicted event has been met based on the prediction results associated with at least one cell;

[0009] The terminal determines whether the prediction result is incorrect based on the RRM measurement results of the at least one cell;

[0010] If the prediction result is determined to be incorrect, the terminal reports a first measurement report to the network-side device;

[0011] The first measurement report includes at least one of the following:

[0012] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0013] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0014] The identifier of the at least one cell;

[0015] The RRM measurement results of at least one cell.

[0016] Secondly, a measurement reporting method is provided, including:

[0017] The network-side device receives a measurement report triggered by at least one predicted event associated with a cell from the terminal;

[0018] The network-side device receives a first measurement report from the terminal;

[0019] The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following:

[0020] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0021] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0022] The identifier of the at least one cell;

[0023] Radio Resource Management (RRM) measurement results of at least one cell.

[0024] Thirdly, a measurement reporting device is provided, including: a processing module and a sending module;

[0025] The processing module is used to determine whether a predicted event has been met based on the prediction results associated with at least one cell.

[0026] The processing module is also used to determine whether the prediction result is incorrect based on the RRM measurement results of the at least one cell;

[0027] If the prediction result is determined to be incorrect, the sending module is used to report a first measurement report to the network-side device;

[0028] The first measurement report includes at least one of the following:

[0029] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0030] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0031] The identifier of the at least one cell;

[0032] The RRM measurement results of at least one cell.

[0033] Fourthly, a measurement reporting device is provided, comprising:

[0034] The receiving module is used to receive measurement reports triggered by at least one predicted event associated with a cell from the terminal;

[0035] The receiving module is further configured to receive a first measurement report from the terminal;

[0036] The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following:

[0037] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0038] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0039] The identifier of the at least one cell;

[0040] The Radio Resource Management (RRM) measurement results of at least one cell.

[0041] Fifthly, a measurement reporting device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0042] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0043] Seventhly, a terminal is provided, including a processor and a communication interface;

[0044] The processor is configured to determine whether a predicted event is satisfied based on the prediction results associated with at least one cell.

[0045] The processor is further configured to determine whether the prediction result is incorrect based on the RRM measurement results of the at least one cell;

[0046] If the prediction result is determined to be incorrect, the communication interface is also used to report a first measurement report to the network-side device;

[0047] The first measurement report includes at least one of the following:

[0048] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0049] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0050] The identifier of the at least one cell;

[0051] The RRM measurement results of at least one cell.

[0052] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0053] Ninthly, a network-side device is provided, including a processor and a communication interface;

[0054] The communication interface is used to receive measurement reports triggered by at least one predicted event associated with a cell from the terminal;

[0055] The communication interface is also used to receive a first measurement report from the terminal;

[0056] The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following:

[0057] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0058] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0059] The identifier of the at least one cell;

[0060] Radio Resource Management (RRM) measurement results of at least one cell.

[0061] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0062] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0063] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0064] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the measurement reporting method as described in the first aspect, or to implement the steps of the measurement reporting method as described in the second aspect.

[0065] In this embodiment, the terminal determines that a predicted event is satisfied based on the prediction results associated with at least one cell; the terminal determines whether the prediction results associated with at least one cell are incorrect based on the RRM measurement results of at least one cell; if the prediction results associated with at least one cell are incorrect, the terminal reports a first measurement report to the network-side device; wherein the first measurement report includes at least one of the following: first indication information for indicating that the measurement event associated with at least one cell is not satisfied; second indication information for indicating that the prediction results associated with at least one cell are incorrect; the identifier of at least one cell; and the RRM measurement results of at least one cell. Therefore, after receiving the first measurement report, the network-side device can know that the prediction results associated with at least one cell are incorrect, which can prevent incorrect handovers and also prevent the waste of reserved radio resources on the network side. In other words, in this embodiment, when the terminal determines that the previous prediction results are incorrect, triggering actual measurement reporting allows the network side to promptly cancel ongoing or upcoming handover preparations to avoid incorrect handovers and the waste of reserved radio resources on the network side, ensuring the normal operation of the measurement event prediction function and thus improving handover performance. Attached Figure Description

[0066] Figure 1 is a schematic diagram of a communication system architecture provided in an embodiment of this application.

[0067] Figure 2 is one of the schematic flowcharts of the measurement reporting method provided according to the embodiments of this application.

[0068] Figure 3 is a schematic diagram of the first time-triggered measurement reporting and the second time-triggered measurement reporting provided according to the embodiments of this application.

[0069] Figure 4 is a second schematic flowchart of the measurement reporting method provided according to an embodiment of this application.

[0070] Figure 5 is one of the schematic block diagrams of a measurement reporting device provided according to an embodiment of this application.

[0071] Figure 6 is a second schematic block diagram of a measurement reporting device provided according to an embodiment of this application.

[0072] Figure 7 is a schematic block diagram of a communication device provided according to an embodiment of this application.

[0073] Figure 8 is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application.

[0074] Figure 9 is a schematic block diagram of a network-side device provided according to an embodiment of this application. Detailed Implementation

[0075] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0076] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0077] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0078] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0079] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0080] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0081] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0082] To better understand the technical solution of this application, the following explains the artificial intelligence (AI) related to this application.

[0083] Artificial intelligence (AI) has been widely applied in various fields. Integrating AI into wireless communication networks to significantly improve technical indicators such as throughput, latency, and user capacity is an important task for future wireless communication networks. AI modules can be implemented in various ways, such as neural networks, decision trees, support vector machines, and Bayesian classifiers. This application uses neural networks as an example for illustration, but does not limit the specific type of AI module.

[0084] The parameters of a neural network are optimized using gradient optimization algorithms. Gradient optimization algorithms are a class of algorithms that minimize or maximize an objective function (sometimes called a loss function), which is often a mathematical combination of model parameters and data. For example, given data X and its corresponding label Y, a neural network model f(.) is constructed. With the neural network model, the predicted output f(x) can be obtained from the input x, and the difference between the predicted value and the true value (f(x)-Y) can be calculated; this is the loss function. The goal is to find suitable values ​​W and b that minimize the value of the loss function. The smaller the loss value, the closer the neural network model is to the reality.

[0085] Most common optimization algorithms are based on the error back propagation (BP) algorithm. The basic idea of ​​the BP algorithm is that the learning process consists of two parts: forward propagation of the signal and backward propagation of the error. During forward propagation, the input sample is introduced from the input layer, processed layer by layer by the hidden layers, and then propagated to the output layer. If the actual output of the output layer does not match the expected output, the process transitions to the error back propagation stage. Error back propagation involves propagating the output error back to the input layer layer by layer through the hidden layers, distributing the error to all units in each layer, thus obtaining the error signal of each unit. This error signal can be used as the basis for adjusting the weights of each unit. This process of adjusting the weights of each layer through forward and backward propagation is repeated continuously. This continuous adjustment of weights is the learning and training process of the neural network model. This process continues until the error of the neural network model's output is reduced to an acceptable level, or until the predetermined number of learning iterations is reached.

[0086] Common optimization algorithms include gradient descent, stochastic gradient descent (SGD), mini-batch gradient descent, momentum method, Nesterov (specifically, stochastic gradient descent with momentum), adaptive gradient descent, Adadelta, root mean square prop (RMSprop), and adaptive momentum estimation (Adam).

[0087] To better understand the technical solution of this application, the following describes the AI-based mobility enhancement related to this application.

[0088] AI-based mobility enhancements include: RRM measurement prediction, measurement event prediction, and prediction of radio link failure (RLF) or handover failure (HOF).

[0089] RRM measurement prediction includes prediction in the time domain, frequency domain, and spatial domain. Frequency domain RRM measurement prediction can be based on the RRM measurement result of one frequency point to predict the RRM measurement result of another frequency point.

[0090] For measurement event prediction, both direct and indirect measurement event prediction are supported. The output value of direct measurement event prediction is whether an event will occur or the probability of the event occurring within a future period. The output of indirect measurement event prediction is the future RRM measurement prediction result, and the determination of whether the measurement event will occur in the future is based on the processed predicted RRM measurement result.

[0091] To better understand the technical solution of this application, the following explains the RRM measurement reporting related to this application.

[0092] The measurement configuration mainly consists of the measurement object, the reporting configuration, and the measurement identifier.

[0093] Measurement Object (MO): such as the frequency point to be measured.

[0094] Report Configuration: Includes reporting criteria (periodic triggering or event triggering); reference signal type (Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS)); measurement reporting quantities (any combination of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Signal to Interference plus Noise Ratio (SINR)); whether to report beam measurement results; and the maximum number of beams that can be reported.

[0095] Measurement Identifier (measId): Used to associate a measurement object with a reporting configuration. A measurement object can be associated with multiple reporting configurations, and a reporting configuration can be associated with multiple measurement objects.

[0096] In NR, the measurement object, reporting configuration, and measurement identifier are linked together in the following way:

[0097] The reporting configuration can include event-triggered reporting. The measurement events defined in NR can be shown in Table 1.

[0098] Table 1

[0099] Taking event A3 as an example, the meanings of the parameters in the entry and exit conditions are as follows:

[0100] Mn: Neighbor cell measurement results, without considering any offset;

[0101] Ofn: Specific offset of the neighboring cell measurement object;

[0102] Ocn: Neighboring cell-level specific offset;

[0103] Mp: Measurement result of the primary serving cell (such as a special cell, SpCell), without considering any offset;

[0104] Ofp: SpCell measures a specific offset of an object;

[0105] Ocp: SpCell cell-level specific offset;

[0106] Hys: The hysteresis parameter of the event;

[0107] Off: The offset parameter for the event.

[0108] The parameters related to measurement and reporting also include the following:

[0109] Trigger Time (TTT): If the reporting type is event-triggered, in order to avoid frequent reporting or ping-pong handover, the base station configures the TTT parameter for each event;

[0110] Entering condition: If the L3 filtered signal quality of one or more candidate cells meets the event's entering condition within the TTT time, the cell is added to the triggered cell list and measurement reporting is triggered.

[0111] Leaving condition: If the layer 3 (L3) filtered signal quality of one or more cells in the cell triggered list meets the event's leaving condition during the TTT time, the cell is removed from the cell triggered list. If reportOnLeave is configured, measurement reporting is triggered.

[0112] Reporting Interval: Periodically reports the measurement results of cells in the cell triggering list according to the reporting interval;

[0113] Report Amount: Based on the report amount, the maximum number of times the measurement results of cells in the cell trigger list are periodically reported is determined;

[0114] ReportOnBestCellChange: When this instruction is configured, the terminal will only trigger measurement reporting after the best one or two cells measured have changed.

[0115] Entering / Leaving Report: Indicates whether the measurement report indicates the cell corresponding to the entry or departure event.

[0116] The measurement reporting method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0117] Figure 2 is a schematic flowchart of a measurement reporting method 200 according to an embodiment of this application. As shown in Figure 2, the measurement reporting method 200 may include at least some of the following:

[0118] S210, the terminal determines that the predicted event has been met based on the prediction results associated with at least one cell;

[0119] S220, the terminal determines whether the prediction result is incorrect based on the RRM measurement results of the at least one cell;

[0120] S230, if it is determined that the prediction result is incorrect, the terminal reports a first measurement report to the network-side device;

[0121] The first measurement report includes at least one of the following:

[0122] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0123] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0124] The identifier of the at least one cell;

[0125] The RRM measurement results of at least one cell.

[0126] It should be understood that Figure 2 illustrates the steps or operations of the measurement reporting method 200, but these steps or operations are merely examples, and other operations or variations of the operations shown in Figure 2 may also be performed in this application.

[0127] In this embodiment, the terminal determines that a predicted event is satisfied based on the prediction results associated with at least one cell; the terminal determines whether the prediction results associated with at least one cell are incorrect based on the RRM measurement results of at least one cell; if the prediction results are incorrect, the terminal reports a first measurement report to the network-side device; wherein the first measurement report includes at least one of the following: first indication information for indicating that the measurement event associated with at least one cell is not satisfied; second indication information for indicating that the prediction results associated with at least one cell are incorrect; the identifier of at least one cell; and the RRM measurement results of at least one cell. Therefore, after receiving the first measurement report, the network-side device can know that the prediction results associated with at least one cell are incorrect, which can prevent incorrect handovers and also prevent the waste of reserved radio resources on the network side. In other words, in this embodiment, when the terminal determines that the previous prediction results are incorrect, triggering actual measurement reporting allows the network side to promptly cancel ongoing or upcoming handover preparations to avoid incorrect handovers and the waste of reserved radio resources on the network side, ensuring the normal operation of the measurement event prediction function and thus improving handover performance.

[0128] In some embodiments, during S220 above, the terminal can determine whether the prediction result associated with the at least one cell is incorrect through a sampling method. Optionally, the sampling period or sampling time interval can be configured by the network side, or the sampling period or sampling time interval can be agreed upon by the protocol.

[0129] In this embodiment of the application, in the above S210, the terminal can determine that the predicted event associated with the at least one cell is satisfied through the AI ​​unit; or, the terminal can determine the prediction result of the at least one cell through the AI ​​unit, and the terminal determines that the predicted event associated with the at least one cell is satisfied based on the prediction result of the at least one cell.

[0130] The AI ​​unit described in this application embodiment may also be referred to as an AI model, AI model / AI unit, machine learning (ML) model, ML unit, AI structure, AI function, AI characteristic, neural network, neural network function, neural network functionality, etc. Alternatively, the AI ​​unit described in this application embodiment may refer to a processing unit capable of implementing specific algorithms, formulas, processing flows, capabilities, etc., related to AI. Or, the AI ​​unit described in this application embodiment may be a processing method, algorithm, function, module, or unit for a specific dataset. Alternatively, the AI ​​unit described in this application embodiment may be a processing method, algorithm, function, module, or unit running on AI / ML related hardware such as a graphics processing unit (GPU), neural processing unit (NPU), tensor processing unit (TPU), or application-specific integrated circuit (ASIC). This application embodiment does not specifically limit these aspects. Optionally, the specific dataset includes the input or output of the AI ​​unit.

[0131] For example, AI features combined with specific configurations can yield AI functions. For instance, an AI feature might be beam management, and an AI function might be time-domain beam prediction configured for a base station with 32 transmit beams.

[0132] Optionally, the identifier of the AI ​​unit described in the embodiments of this application may be an AI model identifier, an AI structure identifier, an AI algorithm identifier, or an identifier of a specific dataset associated with the AI ​​unit, or an identifier of a specific scenario, environment, channel characteristics, or device related to AI / ML, or an identifier of a function, feature, capability, or module related to AI / ML. The embodiments of this application do not specifically limit this.

[0133] In some embodiments, the at least one cell includes at least one of the following:

[0134] The service area includes one or more neighboring communities.

[0135] Optionally, the identifier of the at least one cell may be a Physical Cell Identifier (PCI), an NR Cell Global Identifier (NCGI), or another cell identifier (ID).

[0136] Optionally, the first indication information may occupy 1 bit, wherein a value of 0 indicates that the measurement event associated with the at least one cell has not been satisfied, or a value of 1 indicates that the measurement event associated with the at least one cell has not been satisfied.

[0137] Optionally, the second indication information may occupy 1 bit, wherein a value of 0 indicates that the prediction result associated with the at least one cell is incorrect, or a value of 1 indicates that the prediction result associated with the at least one cell is incorrect.

[0138] In some embodiments, in S210 above, the terminal determines that the predicted event is satisfied based on the prediction result associated with at least one cell, including at least one of the following:

[0139] If it is determined based on the prediction results associated with the at least one cell that the predicted event is continuously satisfied within the first time period, the terminal determines that the predicted event associated with the at least one cell is satisfied.

[0140] If, based on the prediction results of the at least one cell association and the measurement results of the at least one cell association, it is determined that the predicted event is continuously satisfied within the first time period, the terminal determines that the predicted event of the at least one cell association is satisfied.

[0141] If it is predicted that the predicted event associated with at least one cell is satisfied within the second time period, the terminal determines that the predicted event associated with at least one cell is satisfied.

[0142] If the probability that the predicted event associated with at least one cell is satisfied within the second time period is greater than or equal to the first threshold, the terminal determines that the predicted event associated with at least one cell is satisfied.

[0143] Optionally, the unit of the first duration may include, but is not limited to, one of the following:

[0144] Symbol, time slot, subframe, frame, second, millisecond, microsecond.

[0145] Optionally, the unit of the second duration may include, but is not limited to, one of the following:

[0146] Symbol, time slot, subframe, frame, second, millisecond, microsecond.

[0147] In some implementations, the first duration can be TTT.

[0148] Optionally, the first threshold may be agreed upon by a protocol, or the first threshold may be configured by the network side, or the first threshold may be determined by the terminal.

[0149] In some embodiments, S210 may be a step executed by the terminal at a first time, and S220 may be a step executed by the terminal at a second time. The second time is later than the first time.

[0150] In some embodiments, the second time is the end point of the first duration; or, the second time is the end point of the maximum permissible event timing difference (ETD) after the first duration; or, the second time is the end point of the second duration; or, the second time is the end point of the maximum permissible event timing difference after the second duration. For example, the second time is the end point of the first duration after the first time; or, the second time is the end point of the maximum permissible event timing difference (ETD) after the first time and the first duration; or, the second time is the end point of the second duration after the first time; or, the second time is the end point of the maximum permissible event timing difference after the second duration and the first time. For example, the end point of the first duration is T1, the second time is T1, or, the second time is T1+ETD.

[0151] For example, the end time of the second duration is T2, the second time is T2, or the second time is T2+ETD.

[0152] Optionally, the ETD can be agreed upon by a protocol, or the ETD can be configured by the network side.

[0153] In some implementations, if it is determined based on the prediction results associated with at least one cell that the predicted event will be continuously satisfied within the first duration, the terminal determines that the predicted event associated with at least one cell is satisfied; or, if it is determined based on the prediction results associated with at least one cell and the measurement results associated with at least one cell that the predicted event will be continuously satisfied within the first duration, the terminal determines that the predicted event associated with at least one cell is satisfied. Assuming that at least one cell includes the serving cell (cell#0) and neighboring cells (cell#1), the first duration is TTT, ETD = 0, and the predicted event is event A3, the specific procedures of S210 and S220 above can be shown in Figure 3.

[0154] In some embodiments, if it is determined that the prediction result is incorrect, the measurement reporting method 200 further includes:

[0155] The terminal removes at least one cell from the first cell list;

[0156] The first cell list includes cells that meet the measurement reporting trigger mechanism.

[0157] In this embodiment, if the terminal determines that the prediction result associated with the at least one cell is incorrect based on the RRM measurement results of the at least one cell, the terminal removes the at least one cell from the first cell list. This allows the network side to cancel ongoing or upcoming handover preparations in a timely manner, avoiding erroneous handovers and preventing the waste of reserved radio resources on the network side.

[0158] In this embodiment, when the terminal determines that the predicted event is satisfied based on the prediction results associated with the at least one cell, the terminal adds the at least one cell to the first cell list.

[0159] Optionally, the first cell list can be a list of triggered cells.

[0160] In some embodiments, the first cell list is a list of cells corresponding to the predicted event; or...

[0161] The first cell list is a shared list of cells for both predicted and measured events.

[0162] It should be noted that the cell list corresponding to the predicted event can be understood as follows: when the predicted event is met, the cells that meet the predicted event will be added to this cell list and reported to the network in the measurement report.

[0163] It should be noted that the cell list corresponding to the measurement event can be understood as follows: when the measurement event is met, the cells that meet the measurement event will be added to this cell list and reported to the network in the measurement report.

[0164] In some embodiments, the first cell list is a cell list corresponding to the predicted event;

[0165] Among them, the predicted event and the measured event are associated with different measurement identifiers, or the predicted event and the measured event are associated with different reporting configuration identifiers; or the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

[0166] In this embodiment, the predicted event and the measured event are associated with different measurement identifiers, or the predicted event and the measured event are associated with different reporting configuration identifiers. Since the measurement reports associated with different measurement identifiers are reported independently, when the measured event and the predicted event are associated with different measurement identifiers, the existing measurement reporting mechanism (such as reportOnLeave, reportInterval, etc.) can be directly reused for the measurement reporting triggered by the predicted event, and the reporting configuration is also clearer.

[0167] In this embodiment, since the reporting configurations of measurement events and predicted events may have many duplicate elements, the predicted events and measurement events may be associated with the same measurement identifier, or the predicted events and measurement events may be associated with the same reporting configuration identifier, thereby reducing Radio Resource Control (RRC) signaling overhead and avoiding duplicate signaling configurations in the reporting configuration.

[0168] In some embodiments, when the first cell list is a cell list corresponding to a predicted event, the measurement reporting method 200 further includes:

[0169] For cells in the first cell list, the terminal does not perform the evaluation of the departure conditions for the predicted event; or,

[0170] For a cell in the first cell list, the terminal determines, according to network-side instructions, whether to evaluate the departure conditions of the predicted event based on measurement results or prediction results.

[0171] In this embodiment, when the first cell list is a cell list corresponding to the predicted event, since the evaluation of the departure condition of the predicted event is of low importance, the terminal does not perform the evaluation of the departure condition of the predicted event for cells in the first cell list, thereby reducing the terminal power consumption.

[0172] In this embodiment, when the first cell list is a cell list corresponding to the predicted event, for the cells in the first cell list, the terminal determines whether to evaluate the departure conditions of the predicted event based on the measurement results or the prediction results according to the network side instructions. The importance of the departure conditions of the predicted event is lower than that of the entry conditions of the predicted event. The gain of triggering the evaluation of the departure conditions of the predicted event in advance is not significant. Therefore, the departure conditions of the predicted event can be evaluated by measurement values ​​to reduce the AI ​​power consumption caused by inference.

[0173] In some implementations, measurement events and prediction events are associated with different measurement identifiers (meas IDs) or reporting configuration identifiers (ReportConfig). For example, measurement events and prediction events are configured in different reporting configurations. For instance, meas ID 1 is associated with [MO 1, ReportConfig 1], and meas ID 2 is associated with [MO 2, ReportConfig 2]. Here, ReportConfig 1 is configured with traditional measurement events, and ReportConfig 2 is configured with prediction events. Both are associated with the same measurement object.

[0174] The measurement reporting triggering mechanism for predicted events includes at least one of the following:

[0175] If it is predicted that Cell#0 will continuously meet the event entry conditions within the first time period, Cell#0 will be added to the first cell list (e.g., cellsTriggeredList) and measurement reporting will be triggered.

[0176] If it is predicted that Cell#0 will continuously meet the event's leave condition within the first duration, Cell#0 will be removed from the first cell list (e.g., cellsTriggeredList), and measurement reporting will be triggered when reportOnLeave is configured.

[0177] For cells already in the first cell list (e.g., cellsTriggeredList), the evaluation of leave conditions based on predicted events (e.g., evaluation of leave conditions based on measurement results) is not performed, or the evaluation of leave conditions based on measurement results or prediction results is determined by the network configuration.

[0178] It should be noted that since measurement reports associated with different measurement identifiers are reported independently, when measurement events and predicted events are associated with different measurement identifiers, existing measurement reporting mechanisms (such as reportOnLeave, reportInterval, etc.) can be directly reused for measurement reporting triggered by predicted events, while the configuration is clearer.

[0179] In some implementations, measurement events and prediction events are associated with the same measurement identifier or reporting configuration identifier. The cells triggered by the measurement event and the cells triggered by the prediction event use different `cellsTriggeredList`s. For example, a first cell list is used for cells triggered by prediction events, and a second cell list is used for cells triggered by measurement events. For instance, `meas ID 1` is associated with `[MO 1, ReportConfig 1]`, where `ReportConfig 1` contains configurations for both measurement and prediction events. The measurement reporting behavior includes at least one of the following:

[0180] When the measurement value of Cell#0 continuously meets the event entry conditions within the first time period, Cell#0 is added to the second cell list and measurement reporting is triggered.

[0181] When it is predicted that Cell#0 will continuously meet the entry conditions of the event during the second time period, or when it is predicted that Cell#0 will meet the event, Cell#0 will be added to the first cell list and measurement reporting will be triggered.

[0182] If it is predicted that Cell#0 will continue to meet the event's leave condition during the second time period, Cell#0 will be removed from the first cell list (cellsTriggeredList), and measurement reporting will be triggered when reportOnLeave is configured.

[0183] For cells already in the first cell list (cellsTriggeredList), the evaluation of leave conditions based on predicted events is not performed (the evaluation of leave conditions is based on measurement results), or the evaluation of leave conditions based on measurement results or prediction results is determined by the network configuration.

[0184] It should be noted that the reporting configurations for measured events and predicted events may have many duplicate elements, which can reduce RRC signaling overhead and avoid duplicate signaling configurations in the reporting configuration.

[0185] Optionally, the first time period and the second time period can be the same, or the first time period and the second time period can be different.

[0186] In some embodiments, the first cell list is a cell list shared by predicted events and measured events;

[0187] Among them, the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

[0188] In this embodiment, since the reporting configurations of measurement events and predicted events may have many duplicate elements, the predicted events and measurement events are associated with the same measurement identifier, or the predicted events and measurement events are associated with the same reporting configuration identifier. This can reduce RRC signaling overhead and avoid duplicate signaling configurations in the reporting configuration.

[0189] In some embodiments, where the first cell list is a cell list shared by predicted events and measurement events, the measurement reporting method 200 further includes:

[0190] For cells added to the first cell list based on the prediction results, the terminal continues to evaluate the entry conditions of the measurement event, and if it is determined that the prediction results are incorrect, the terminal triggers measurement reporting and removes the corresponding cell from the first cell list;

[0191] And / or,

[0192] For cells added to the first cell list based on the prediction results, the terminal continues to evaluate the entry conditions of the measurement event, and if the prediction results are determined to be correct, the terminal triggers measurement reporting;

[0193] And / or,

[0194] For cells in the first cell list, the terminal does not perform the evaluation of the entry conditions for the predicted event, or the terminal does not perform the evaluation of the entry conditions for the measurement event, or the terminal determines whether to perform the evaluation of the entry conditions for the measurement event according to the network side instruction, or the terminal determines whether to perform the evaluation of the entry conditions for the predicted event according to the network side instruction.

[0195] And / or,

[0196] For cells in the first cell list, the terminal does not perform the evaluation of the departure conditions for the predicted event, or the terminal determines whether to perform the evaluation of the departure conditions for the predicted event based on instructions from the network side.

[0197] In this embodiment, when the first cell list is a shared cell list for both prediction and measurement events, if the prediction result is determined to be incorrect, the terminal triggers a measurement report and removes the corresponding cell from the first cell list. This allows the network side to promptly cancel ongoing or upcoming handover preparations to avoid erroneous handovers and to prevent the waste of reserved radio resources on the network side.

[0198] In this embodiment, when the first cell list is a shared cell list for both predicted and measured events, for cells added to the first cell list based on the prediction results, the terminal continues to evaluate the entry conditions for the measured event, and if the prediction result is determined to be correct, the terminal triggers a measurement report. Thus, the network side can obtain model monitoring information of the AI ​​unit (associated with the predicted event) based on the measurement report reported by the terminal.

[0199] In this embodiment, when the first cell list is a shared cell list for both predicted and measured events, the terminal does not perform the evaluation of the entry conditions for predicted events, or the terminal does not perform the evaluation of the entry conditions for measured events, thereby reducing terminal power consumption. Alternatively, when the first cell list is a shared cell list for both predicted and measured events, the terminal determines whether to perform the evaluation of the entry conditions for measured events, or the terminal determines whether to perform the evaluation of the entry conditions for predicted events, based on network-side instructions, for each cell in the first cell list. This avoids unnecessary evaluation of the entry conditions for either measured or predicted events, thereby reducing terminal power consumption.

[0200] In this embodiment, when the first cell list is a shared cell list for both predicted and measured events, the terminal does not perform the evaluation of the departure conditions for the predicted event for any cell in the first cell list. Alternatively, the terminal determines whether to perform the evaluation of the departure conditions for the predicted event based on instructions from the network side. The departure conditions for the predicted event are less important than the entry conditions, and the gain from prematurely triggering the evaluation of the departure conditions is minimal. Therefore, the departure conditions for the predicted event can be evaluated using measured values ​​to reduce AI power consumption caused by inference.

[0201] In some implementations, measurement events and prediction events are associated with the same measurement identifier or reporting configuration identifier. The cells triggered by the measurement event and the cells triggered by the prediction event share a single `cellsTriggeredList`, i.e., the first cell list. For example, `meas ID 1` is associated with `[MO 1, ReportConfig 1]`, where `ReportConfig 1` contains both the configuration for the measurement event and the configuration for the prediction event. The measurement reporting behavior includes at least one of the following:

[0202] When the measurement value of Cell#0 continuously meets the event entry conditions within the first time period, Cell#0 is added to the first cell list and measurement reporting is triggered.

[0203] When it is predicted that Cell#0 will continuously meet the entry conditions of the event during the first time period, or when it is predicted that Cell#0 will meet the event, Cell#0 will be added to the first cell list and measurement reporting will be triggered.

[0204] For cells added to the first cell list based on the prediction results, continue to evaluate the measurement event entry conditions. If it is determined that the prediction result is incorrect, trigger measurement reporting and remove the corresponding cell from the first cell list.

[0205] For cells added to the first cell list based on the prediction results, continue to evaluate the measurement event entry conditions, and trigger measurement reporting when the prediction results are confirmed to be correct;

[0206] For cells already in the first cell list, the evaluation of the entry conditions for measurement events or prediction events is not performed, or whether to perform the evaluation of measurement events or prediction events is determined by the network-side configuration;

[0207] For cells already in the first cell list, the evaluation of the predicted event's departure conditions is not performed, or whether the evaluation of the predicted event's departure conditions is performed is determined by the network-side configuration.

[0208] In some embodiments, the terminal determines the cells in the first cell list (such as cellsTriggeredList) based on the measurement reporting triggering mechanism.

[0209] In some embodiments, the terminal performs RRM measurement prediction on cells in a first cell list (such as cellsTriggeredList) and reports the prediction results. This allows the accuracy of cells in the first cell list to be determined based on the RRM prediction results, avoiding incorrect handovers caused by errors in the first cell list and preventing the waste of reserved radio resources on the network side.

[0210] Optionally, the terminal may periodically report the RRM measurement prediction results of cells in the first cell list (e.g., cellsTriggeredList) according to the reporting frequency and reporting period configured on the network side.

[0211] In some embodiments, the measurement reporting method 200 further includes:

[0212] The terminal receives configuration information from the network-side device.

[0213] Optionally, the configuration granularity of the configuration information includes, but is not limited to, one of the following: terminal granularity (per UE), measurement object (MO) granularity (per MO). That is, the configuration information can be configured for a terminal, such as each terminal having its own set of configuration information. Alternatively, the configuration information can be configured for a measurement object, such as each measurement object having its own set of configuration information.

[0214] In some embodiments, the configuration information is used to indicate at least one of the following:

[0215] List of cells where measurement event prediction can be performed;

[0216] A list of frequency points from which measurement event predictions can be performed;

[0217] List of cells where measurement event prediction is not feasible;

[0218] List of frequency points for events for which measurement prediction is not feasible;

[0219] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0220] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0221] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0222] The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

[0223] It should be noted that for measurement event prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In the embodiments of this application, the network-side device can configure a list of cells or frequencies for which measurement event prediction can be performed, and a list of cells or frequencies for which measurement event prediction cannot be performed, etc., for the terminal, so that the terminal can determine the cells or frequencies for which measurement event prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0224] In some embodiments, the configuration information may be used to indicate at least one of the following:

[0225] List of cells where RRM measurement prediction can be performed;

[0226] List of frequency points where RRM measurement predictions can be performed;

[0227] List of cells where RRM measurement prediction is not feasible;

[0228] List of frequency points where RRM measurement prediction is not possible;

[0229] The fifth indication information is used to indicate whether RRM measurement prediction can be performed at P frequency points, where P is a positive integer;

[0230] A third identifier associated with P frequency points, wherein the frequency points whose associated third identifier is the same as the third identifier associated with the service frequency point are the frequency points for which RRM measurement prediction can be performed, and P is a positive integer;

[0231] The sixth indication information is used to indicate whether RRM measurement prediction can be performed in Q cells, where Q is a positive integer;

[0232] A fourth identifier associated with Q cells, wherein cells among the Q cells whose associated fourth identifier is the same as the fourth identifier associated with the serving cell are cells for which RRM measurement prediction can be performed, and Q is a positive integer.

[0233] It should be noted that for RRM measurement prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In the embodiments of this application, the network-side device can configure a list of cells or frequencies for which RRM measurement prediction can be performed, and a list of cells or frequencies for which RRM measurement prediction cannot be performed, etc., for the terminal, so that the terminal can determine the cells or frequencies for which RRM measurement prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0234] In some embodiments, the configuration information may be used to indicate at least one of the following:

[0235] List of cells where measurement event prediction can be performed;

[0236] A list of frequency points from which measurement event predictions can be performed;

[0237] List of cells where measurement event prediction is not feasible;

[0238] List of frequency points for events for which measurement prediction is not feasible;

[0239] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0240] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0241] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0242] The second identifier is associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer;

[0243] List of cells where RRM measurement prediction can be performed;

[0244] List of frequency points where RRM measurement predictions can be performed;

[0245] List of cells where RRM measurement prediction is not feasible;

[0246] List of frequency points where RRM measurement prediction is not possible;

[0247] The fifth indication information is used to indicate whether RRM measurement prediction can be performed at P frequency points, where P is a positive integer;

[0248] A third identifier associated with P frequency points, wherein the frequency points whose associated third identifier is the same as the third identifier associated with the service frequency point are the frequency points for which RRM measurement prediction can be performed, and P is a positive integer;

[0249] The sixth indication information is used to indicate whether RRM measurement prediction can be performed in Q cells, where Q is a positive integer;

[0250] A fourth identifier associated with Q cells, wherein cells among the Q cells whose associated fourth identifier is the same as the fourth identifier associated with the serving cell are cells for which RRM measurement prediction can be performed, and Q is a positive integer.

[0251] It should be noted that for measurement event prediction or RRM measurement prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In the embodiments of this application, the network-side device can configure the terminal with a list of cells or frequencies for which measurement event prediction can be performed, a list of cells or frequencies for which measurement event prediction cannot be performed, a list of cells or frequencies for which RRM measurement prediction can be performed, and a list of cells or frequencies for which RRM measurement prediction cannot be performed, so that the terminal can determine the cells or frequencies for which measurement event prediction and RRM measurement prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0252] Optionally, the first identifier may be agreed upon by a protocol, or the first identifier may be configured by the network side.

[0253] Optionally, the second identifier may be agreed upon by a protocol, or the second identifier may be configured by the network side.

[0254] Optionally, the third identifier may be agreed upon by the protocol, or the third identifier may be configured by the network side.

[0255] Optionally, the fourth identifier may be agreed upon by the protocol, or the fourth identifier may be configured by the network side.

[0256] In some implementations, prior to S210 above, the terminal receives the configuration information from the network-side device.

[0257] The cell list described in this application embodiment may include cell identifiers, such as PCI, NCGI, etc.

[0258] The terminal-side embodiments of this application have been described in detail above with reference to Figures 2 and 3. The network-side embodiments of this application have been described in detail below with reference to Figure 4. It should be understood that the network-side embodiments correspond to the terminal-side embodiments, and similar descriptions can be referred to the terminal-side embodiments.

[0259] Figure 4 is a schematic flowchart of a measurement reporting method 300 according to an embodiment of this application. As shown in Figure 4, the measurement reporting method 300 may include at least some of the following:

[0260] S310, The network-side device receives a measurement report triggered by at least one predicted event associated with a cell from the terminal;

[0261] S320, the network-side device receives a first measurement report from the terminal;

[0262] The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following:

[0263] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0264] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0265] The identifier of the at least one cell;

[0266] The RRM measurement results of at least one cell.

[0267] It should be understood that Figure 4 illustrates the steps or operations of the measurement reporting method 300, but these steps or operations are merely examples, and other operations or variations of the operations in Figure 4 may also be performed in this application.

[0268] In this embodiment, the network-side device receives a measurement report triggered by a prediction event associated with at least one cell from the terminal, and also receives a first measurement report from the terminal. The first measurement report is triggered by an error in the prediction result associated with at least one cell, and includes at least one of the following: first indication information indicating that the measurement event associated with at least one cell was not satisfied; second indication information indicating that the prediction result associated with at least one cell was incorrect; the identifier of at least one cell; and the RRM measurement result of at least one cell. After receiving the first measurement report, the network-side device can know that the prediction result associated with at least one cell is incorrect, thus avoiding incorrect handover and preventing the waste of reserved radio resources on the network side. In other words, in this embodiment, when the terminal determines that the previous prediction result is incorrect, triggering the actual measurement report allows the network side to promptly cancel ongoing or upcoming handover preparations to avoid incorrect handover and the waste of reserved radio resources on the network side. This ensures the normal operation of the measurement event prediction function and improves handover performance.

[0269] In some embodiments, the at least one cell includes at least one of the following:

[0270] The service area includes one or more neighboring communities.

[0271] Optionally, the identifier of the at least one cell can be PCI, NCGI, or other cell identifiers (IDs).

[0272] Optionally, the first indication information may occupy 1 bit, wherein a value of 0 indicates that the measurement event associated with the at least one cell has not been satisfied, or a value of 1 indicates that the measurement event associated with the at least one cell has not been satisfied.

[0273] Optionally, the second indication information may occupy 1 bit, wherein a value of 0 indicates that the prediction result associated with the at least one cell is incorrect, or a value of 1 indicates that the prediction result associated with the at least one cell is incorrect.

[0274] In some embodiments, the measurement reporting method 300 further includes:

[0275] The network-side device sends configuration information to the terminal.

[0276] Optionally, the configuration granularity of the configuration information includes, but is not limited to, one of the following:

[0277] Terminal granularity (per UE), MO granularity (per MO).

[0278] In some embodiments, the configuration information is used to indicate at least one of the following:

[0279] List of cells where measurement event prediction can be performed;

[0280] A list of frequency points from which measurement event predictions can be performed;

[0281] List of cells where measurement event prediction is not feasible;

[0282] List of frequency points for events for which measurement prediction is not feasible;

[0283] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0284] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0285] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0286] The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

[0287] It should be noted that for measurement event prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In the embodiments of this application, the network-side device can configure a list of cells or frequencies for which measurement event prediction can be performed, and a list of cells or frequencies for which measurement event prediction cannot be performed, etc., for the terminal, so that the terminal can determine the cells or frequencies for which measurement event prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0288] In some embodiments, the configuration information may be used to indicate at least one of the following:

[0289] List of cells where RRM measurement prediction can be performed;

[0290] List of frequency points where RRM measurement predictions can be performed;

[0291] List of cells where RRM measurement prediction is not feasible;

[0292] List of frequency points where RRM measurement prediction is not possible;

[0293] The fifth indication information is used to indicate whether RRM measurement prediction can be performed at P frequency points, where P is a positive integer;

[0294] A third identifier associated with P frequency points, wherein the frequency points whose associated third identifier is the same as the third identifier associated with the service frequency point are the frequency points for which RRM measurement prediction can be performed, and P is a positive integer;

[0295] The sixth indication information is used to indicate whether RRM measurement prediction can be performed in Q cells, where Q is a positive integer;

[0296] A fourth identifier associated with Q cells, wherein cells among the Q cells whose associated fourth identifier is the same as the fourth identifier associated with the serving cell are cells for which RRM measurement prediction can be performed, and Q is a positive integer.

[0297] It should be noted that for RRM measurement prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In the embodiments of this application, the network-side device can configure a list of cells or frequencies for which RRM measurement prediction can be performed, and a list of cells or frequencies for which RRM measurement prediction cannot be performed, etc., for the terminal, so that the terminal can determine the cells or frequencies for which RRM measurement prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0298] In some embodiments, the configuration information may be used to indicate at least one of the following:

[0299] List of cells where measurement event prediction can be performed;

[0300] A list of frequency points from which measurement event predictions can be performed;

[0301] List of cells where measurement event prediction is not feasible;

[0302] List of frequency points for events for which measurement prediction is not feasible;

[0303] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0304] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0305] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0306] The second identifier is associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer;

[0307] List of cells where RRM measurement prediction can be performed;

[0308] List of frequency points where RRM measurement predictions can be performed;

[0309] List of cells where RRM measurement prediction is not feasible;

[0310] List of frequency points where RRM measurement prediction is not possible;

[0311] The fifth indication information is used to indicate whether RRM measurement prediction can be performed at P frequency points, where P is a positive integer;

[0312] A third identifier associated with P frequency points, wherein the frequency points whose associated third identifier is the same as the third identifier associated with the service frequency point are frequency points for which RRM measurement prediction can be performed, and P is a positive integer;

[0313] The sixth indication information is used to indicate whether RRM measurement prediction can be performed in Q cells, where Q is a positive integer;

[0314] A fourth identifier associated with Q cells, wherein cells among the Q cells whose associated fourth identifier is the same as the fourth identifier associated with the serving cell are cells for which RRM measurement prediction can be performed, and Q is a positive integer.

[0315] It should be noted that for measurement event prediction or RRM measurement prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In the embodiments of this application, the network-side device can configure the terminal with a list of cells or frequencies for which measurement event prediction can be performed, a list of cells or frequencies for which measurement event prediction cannot be performed, a list of cells or frequencies for which RRM measurement prediction can be performed, and a list of cells or frequencies for which RRM measurement prediction cannot be performed, so that the terminal can determine the cells or frequencies for which measurement event prediction and RRM measurement prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0316] Optionally, the first identifier may be agreed upon by a protocol, or the first identifier may be configured by the network side.

[0317] Optionally, the second identifier may be agreed upon by a protocol, or the second identifier may be configured by the network side.

[0318] Optionally, the third identifier may be agreed upon by the protocol, or the third identifier may be configured by the network side.

[0319] Optionally, the fourth identifier may be agreed upon by a protocol, or the fourth identifier may be configured by the network side.

[0320] In some implementations, prior to S310 above, the network-side device sends the configuration information to the terminal.

[0321] The cell list described in this application embodiment may include cell identifiers, such as PCI, NCGI, etc.

[0322] The technical solution of this application is described in detail below through specific embodiments.

[0323] Example 1, taking the following scheme as an example: When the terminal determines that the event prediction result is incorrect, it triggers measurement reporting.

[0324] In Example 1, if the terminal determines that the previous measurement event prediction result is incorrect, it triggers the actual measurement reporting to avoid erroneous switching.

[0325] The specific process of Example 1 may include some or all of the following S1-1 to S1-3.

[0326] S1-1. The terminal determines that the predicted event has been met based on the prediction results associated with at least one cell, and triggers measurement reporting.

[0327] Optionally, the at least one cell includes at least one of the following:

[0328] The service area includes one or more neighboring communities.

[0329] Optionally, the predicted event may include direct prediction or indirect prediction.

[0330] Indirect prediction: Based on the prediction results of at least one cell, determine whether the predicted events associated with at least one cell are continuously satisfied within a first time period (e.g., timeToTrigger). Alternatively, based on the measurement results and prediction results of at least one cell, determine whether the predicted events associated with at least one cell are continuously satisfied within a first time period (e.g., timeToTrigger) (e.g., the prediction event is evaluated based on the measurement results in the first period of the first time period, and the prediction event is evaluated based on the prediction results in the second period of the first time period). When the predicted event is satisfied, measurement reporting is triggered.

[0331] Direct prediction: Directly predict whether the predicted event associated with at least one cell within the second time period is satisfied, or directly predict the probability that the predicted event associated with at least one cell within the second time period is satisfied. Measurement reporting will be triggered when the predicted event associated with at least one cell within the second time period is satisfied, or the probability that the predicted event associated with at least one cell within the second time period is satisfied is greater than the first threshold.

[0332] Optionally, the unit of the first duration may include, but is not limited to, one of the following:

[0333] Symbol, time slot, subframe, frame, second, millisecond, microsecond.

[0334] Optionally, the unit of the second duration may include, but is not limited to, one of the following:

[0335] Symbol, time slot, subframe, frame, second, millisecond, microsecond.

[0336] In some implementations, the first duration can be TTT.

[0337] Optionally, the first threshold may be agreed upon by a protocol, or the first threshold may be configured by the network side, or the first threshold may be determined by the terminal.

[0338] S1-2. The terminal determines that the prediction result associated with at least one cell is incorrect based on the RRM measurement results of at least one cell, and the terminal reports the first measurement report to the network-side device;

[0339] The first measurement report includes at least one of the following:

[0340] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0341] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0342] The identifier of at least one cell (such as PCI, NCGI, etc.);

[0343] The RRM measurement results of at least one cell.

[0344] In S1-2 above, the terminal can determine, at a second time, that the prediction result associated with at least one cell is incorrect based on the RRM measurement results of at least one cell.

[0345] For indirect prediction: the second time is the end time of the first duration mentioned above, or the second time is the end time of the first duration mentioned above plus ETD, where ETD is configured by the network side or is agreed upon by the protocol;

[0346] For direct prediction: the second time is the end time of the aforementioned second duration, or the second time is the end time of the aforementioned second duration plus ETD, where ETD is configured by the network side or is agreed upon by the protocol.

[0347] Optionally, the terminal determines that the prediction result of the first time is incorrect based on the RRM measurement results of at least one cell at the second time. For example, if the cell whose prediction result of the first time is incorrect is determined to be incorrect at the second time, or within the time period of [second time - ETD, second time + ETD], does not actually meet the measurement event.

[0348] S1-3. The terminal removes at least one cell (the cell with the incorrect prediction result) from the first cell list (cells Triggered List).

[0349] In some implementations, it is assumed that at least one cell includes a serving cell (cell#0) and a neighboring cell (cell#1), the first duration is TTT, ETD=0, and the predicted event is event A3. The specific process of embodiment 1 can be shown in Figure 3.

[0350] In Example 1, after the predicted event is met and measurement reporting is triggered in advance, the network side will select a target neighboring cell for handover preparation based on the reported measurement report. If the terminal determines that the prediction is incorrect, it can promptly trigger measurement reporting, allowing the network side to cancel ongoing or upcoming handover preparations in a timely manner, avoiding waste of reserved network resources and preventing erroneous handovers.

[0351] Example 2, taking the following scheme as an example: The network side configures a predictable list of cells or frequency points for the terminal.

[0352] In Example 2, for RRM measurement prediction or measurement event prediction, some frequency points or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. Therefore, the network side can configure a list of predictable cells or frequency points for the terminal to enable the terminal to determine the predictable cells or frequency points.

[0353] In Example 2, the network-side device sends configuration information to the terminal.

[0354] Optionally, the configuration granularity of the configuration information includes, but is not limited to, one of the following:

[0355] Terminal granularity (per UE), MO granularity (per MO).

[0356] Optionally, the configuration information is used to indicate at least one of the following:

[0357] List of cells where measurement event prediction can be performed;

[0358] A list of frequency points from which measurement event predictions can be performed;

[0359] List of cells where measurement event prediction is not feasible;

[0360] List of frequency points for events for which measurement prediction is not feasible;

[0361] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0362] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0363] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0364] The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

[0365] It should be noted that for measurement event prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In this embodiment, the network-side device can configure a list of cells or frequencies for which measurement event prediction can be performed, and a list of cells or frequencies for which measurement event prediction cannot be performed, through configuration information. This allows the terminal to determine the cells or frequencies for which measurement event prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0366] Optionally, the configuration information may be used to indicate at least one of the following:

[0367] List of cells where RRM measurement prediction can be performed;

[0368] List of frequency points where RRM measurement predictions can be performed;

[0369] List of cells where RRM measurement prediction is not feasible;

[0370] List of frequency points where RRM measurement prediction is not possible;

[0371] The fifth indication information is used to indicate whether RRM measurement prediction can be performed at P frequency points, where P is a positive integer;

[0372] A third identifier associated with P frequency points, wherein the frequency points whose associated third identifier is the same as the third identifier associated with the service frequency point are the frequency points for which RRM measurement prediction can be performed, and P is a positive integer;

[0373] The sixth indication information is used to indicate whether RRM measurement prediction can be performed in Q cells, where Q is a positive integer;

[0374] A fourth identifier associated with Q cells, wherein cells among the Q cells whose associated fourth identifier is the same as the fourth identifier associated with the serving cell are cells for which RRM measurement prediction can be performed, and Q is a positive integer.

[0375] It should be noted that for RRM measurement prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In this embodiment, the network-side device can configure a list of cells or frequencies for which RRM measurement prediction can be performed, and a list of cells or frequencies for which RRM measurement prediction cannot be performed, through configuration information. This allows the terminal to determine the cells or frequencies for which RRM measurement prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect predictions.

[0376] Optionally, the configuration information may be used to indicate at least one of the following:

[0377] List of cells where measurement event prediction can be performed;

[0378] A list of frequency points from which measurement event predictions can be performed;

[0379] List of cells where measurement event prediction is not feasible;

[0380] List of frequency points for events for which measurement prediction is not feasible;

[0381] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0382] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0383] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0384] The second identifier is associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer;

[0385] List of cells where RRM measurement prediction can be performed;

[0386] List of frequency points where RRM measurement predictions can be performed;

[0387] List of cells where RRM measurement prediction is not feasible;

[0388] List of frequency points where RRM measurement prediction is not possible;

[0389] The fifth indication information is used to indicate whether RRM measurement prediction can be performed at P frequency points, where P is a positive integer;

[0390] A third identifier associated with P frequency points, wherein the frequency points whose associated third identifier is the same as the third identifier associated with the service frequency point are the frequency points for which RRM measurement prediction can be performed, and P is a positive integer;

[0391] The sixth indication information is used to indicate whether RRM measurement prediction can be performed in Q cells, where Q is a positive integer;

[0392] A fourth identifier associated with Q cells, wherein cells among the Q cells whose associated fourth identifier is the same as the fourth identifier associated with the serving cell are cells for which RRM measurement prediction can be performed, and Q is a positive integer.

[0393] It should be noted that for measurement event prediction or RRM measurement prediction, some frequencies or cells may be predictable, while others may not. For example, for inter-frequency prediction, only cells co-located with the serving cell may be predictable, while cells not co-located with the serving cell may not be predictable. In this embodiment, the network-side device can configure the terminal with a list of cells or frequencies for which measurement event prediction can be performed, a list of cells or frequencies for which measurement event prediction cannot be performed, a list of cells or frequencies for which RRM measurement prediction can be performed, and a list of cells or frequencies for which RRM measurement prediction cannot be performed, so that the terminal can determine the cells or frequencies for which measurement event prediction and RRM measurement prediction can be performed, thus avoiding erroneous measurement reporting caused by incorrect prediction.

[0394] Optionally, the first identifier may be agreed upon by a protocol, or the first identifier may be configured by the network side.

[0395] Optionally, the second identifier may be agreed upon by a protocol, or the second identifier may be configured by the network side.

[0396] Optionally, the third identifier may be agreed upon by the protocol, or the third identifier may be configured by the network side.

[0397] Optionally, the fourth identifier may be agreed upon by the protocol, or the fourth identifier may be configured by the network side.

[0398] The cell list described in this embodiment may include cell identifiers, such as PCI, NCGI, etc.

[0399] Example 3, taking the following scheme as an example: the association between measured events and predicted events and the reporting configuration.

[0400] Option 1: Measurement events and predicted events are associated with different measurement identifiers (meas IDs) or reporting configuration identifiers (ReportConfig). For example, measurement events and predicted events are configured in different reporting configurations. For instance, meas ID 1 is associated with [MO 1, ReportConfig 1], and meas ID 2 is associated with [MO 2, ReportConfig 2]. ReportConfig 1 configures traditional measurement events, while ReportConfig 2 configures predicted events; both are associated with the same measurement object. The measurement reporting trigger mechanism for predicted events includes at least one of the following:

[0401] If it is predicted that Cell#0 will continuously meet the event entry conditions within the first time period, Cell#0 will be added to the first cell list (e.g., cellsTriggeredList) and measurement reporting will be triggered.

[0402] If it is predicted that Cell#0 will continuously meet the event's leave condition within the first duration, Cell#0 will be removed from the first cell list (e.g., cellsTriggeredList), and measurement reporting will be triggered when reportOnLeave is configured.

[0403] For cells already in the first cell list (e.g., cellsTriggeredList), the evaluation of leave conditions based on predicted events (e.g., evaluation of leave conditions based on measurement results) is not performed, or the evaluation of leave conditions based on measurement results or prediction results is determined by the network configuration.

[0404] For example, for cells already in the first cell list (e.g., cellsTriggeredList), the evaluation of the leave conditions for the predicted event is not performed (e.g., the evaluation of the leave conditions based on the measurement results), or the evaluation of the leave conditions based on the measurement results or the prediction results is determined by the network configuration. The importance of the leave conditions is lower than that of the entry conditions, and the gain from early triggering is not significant. Therefore, the leave conditions can be evaluated using the measurement values ​​to reduce the AI ​​power consumption caused by inference.

[0405] It should be noted that since measurement reports associated with different measurement identifiers are reported independently, when measurement events and predicted events are associated with different measurement identifiers, existing measurement reporting mechanisms (such as reportOnLeave, reportInterval, etc.) can be directly reused for measurement reporting triggered by predicted events, while the configuration is clearer.

[0406] Option 2: Measurement events and prediction events are associated with the same measurement identifier or reporting configuration identifier. The cells triggering the measurement event and the cells triggering the prediction event share a single `cellsTriggeredList`, i.e., the first cell list. For example, `meas ID 1` is associated with `[MO 1, ReportConfig 1]`, where `ReportConfig 1` contains both the configuration for the measurement event and the configuration for the prediction event. The measurement reporting behavior includes at least one of the following:

[0407] When the measurement value of Cell#0 continuously meets the event entry conditions within the first time period, Cell#0 is added to the first cell list and measurement reporting is triggered.

[0408] When it is predicted that Cell#0 will continuously meet the entry conditions of the event during the first time period, or when it is predicted that Cell#0 will meet the event, Cell#0 will be added to the first cell list and measurement reporting will be triggered.

[0409] For cells added to the first cell list based on the prediction results, continue to evaluate the measurement event entry conditions. If the prediction is found to be incorrect, trigger measurement reporting and remove the corresponding cell from the first cell list.

[0410] For cells added to the first cell list based on the prediction results, the evaluation of the measurement event entry conditions continues. When the prediction is confirmed to be correct, measurement reporting is triggered to provide the network with model monitoring information.

[0411] For cells already in the first cell list, the evaluation of the entry conditions for measurement events or prediction events is not performed, or whether to perform the evaluation of measurement events or prediction events is determined by the network-side configuration;

[0412] For cells already in the first cell list, the evaluation of the predicted event's departure conditions is not performed, or whether the evaluation of the predicted event's departure conditions is performed is determined by the network-side configuration.

[0413] For example, for cells already in the first cell list, the evaluation of the leave conditions for the predicted event is not performed, or whether the evaluation of the leave conditions for the predicted event is performed is determined by the network side configuration. The importance of the leave conditions is lower than that of the entry conditions, and the gain from early triggering is not significant. Therefore, the leave conditions can be evaluated using measured values ​​to reduce the AI ​​power consumption caused by inference.

[0414] Option 3: Measurement events and prediction events are associated with the same measurement identifier or reporting configuration identifier. Cells triggered by measurement events and prediction events use different `cellsTriggeredList`s. For example, a first cell list is used for cells triggered by prediction events, and a second cell list is used for cells triggered by measurement events. For instance, `meas ID 1` is associated with `[MO 1, ReportConfig 1]`, where `ReportConfig 1` contains configurations for both measurement and prediction events. The measurement reporting behavior includes at least one of the following:

[0415] When the measurement value of Cell#0 continuously meets the event entry conditions within the first time period, Cell#0 is added to the second cell list and measurement reporting is triggered.

[0416] When it is predicted that Cell#0 will continuously meet the entry conditions of the event during the second time period, or when it is predicted that Cell#0 will meet the event, Cell#0 will be added to the first cell list and measurement reporting will be triggered.

[0417] If it is predicted that Cell#0 will continue to meet the event's leave condition during the second time period, Cell#0 will be removed from the first cell list (cellsTriggeredList), and measurement reporting will be triggered when reportOnLeave is configured.

[0418] For cells already in the first cell list (cellsTriggeredList), the evaluation of leave conditions based on predicted events is not performed (the evaluation of leave conditions is based on measurement results), or the evaluation of leave conditions based on measurement results or prediction results is determined by the network configuration.

[0419] It should be noted that the reporting configurations for measured events and predicted events may have many duplicate elements, which can reduce RRC signaling overhead and avoid duplicate signaling configurations in the reporting configuration.

[0420] Optionally, the first time period and the second time period can be the same, or the first time period and the second time period can be different.

[0421] In this embodiment, the reporting configuration of measured events and predicted events may have many duplicate elements. Schemes 2 and 3 described above can reduce RRC signaling overhead and avoid duplicate signaling configuration in the reporting configuration.

[0422] Example 4, taking the following scheme as an example: predicting cell selection.

[0423] The terminal determines the cells in the first cell list (such as cellsTriggeredList) based on the measurement reporting trigger mechanism.

[0424] The terminal performs RRM measurement prediction on the cells in the first cell list (e.g., cellsTriggeredList) and reports the prediction results. This allows the terminal to determine the accuracy of the cells in the first cell list based on the RRM prediction results, avoiding incorrect handovers caused by errors in the first cell list and preventing the waste of reserved radio resources on the network side.

[0425] Optionally, the terminal may periodically report the RRM measurement prediction results of cells in the first cell list (e.g., cellsTriggeredList) according to the reporting frequency and reporting period configured on the network side.

[0426] The measurement reporting method provided in this application can be executed by a measurement reporting device. This application uses the measurement reporting device executing the measurement reporting method as an example to illustrate the measurement reporting device provided in this application.

[0427] This application provides a measurement reporting device. As an example, the measurement reporting device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0428] The measurement reporting device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0429] Referring to Figure 5, when the measurement reporting device is a terminal or a component in a terminal, the measurement reporting device 400 includes: a processing module 401 and a sending module 402;

[0430] The processing module 401 is used to determine whether a predicted event is satisfied based on the prediction results associated with at least one cell.

[0431] The processing module 401 is further configured to determine whether the prediction result is incorrect based on the Radio Resource Management (RRM) measurement results of the at least one cell;

[0432] If the prediction result is determined to be incorrect, the sending module 402 is used to report a first measurement report to the network-side device;

[0433] The first measurement report includes at least one of the following:

[0434] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0435] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0436] The identifier of the at least one cell;

[0437] The RRM measurement results of at least one cell.

[0438] In some embodiments, if it is determined that the prediction result is incorrect, the processing module 401 is further configured to remove the at least one cell from the first cell list;

[0439] The first cell list includes cells that meet the measurement reporting trigger mechanism.

[0440] In some embodiments, the first cell list is a list of cells corresponding to the predicted event; or...

[0441] The first cell list is a shared list of cells for both predicted and measured events.

[0442] In some embodiments, the first cell list is a cell list corresponding to the predicted event;

[0443] Among them, the predicted event and the measured event are associated with different measurement identifiers, or the predicted event and the measured event are associated with different reporting configuration identifiers; or the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

[0444] In some embodiments, for cells in the first cell list, the processing module 401 is further configured to not perform an evaluation of the departure conditions for the predicted event; or,

[0445] For cells in the first cell list, the processing module 401 is further configured to determine, based on network-side instructions, whether to evaluate the departure conditions of the predicted event based on measurement results or prediction results.

[0446] In some embodiments, the first cell list is a cell list shared by predicted events and measured events;

[0447] Among them, the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

[0448] In some embodiments, for cells added to the first cell list based on the prediction result, the processing module 401 is further configured to continue to perform the evaluation of the entry conditions of the measurement event, and if it is determined that the prediction result is incorrect, the processing module 401 is further configured to trigger measurement reporting and remove the corresponding cell from the first cell list;

[0449] And / or,

[0450] For cells added to the first cell list based on the prediction results, the processing module 401 is further configured to continue to perform the evaluation of the entry conditions of the measurement event, and if the prediction results are determined to be correct, the processing module 401 is further configured to trigger measurement reporting.

[0451] And / or,

[0452] For cells in the first cell list, the processing module 401 is further configured to not perform the evaluation of the entry conditions for the predicted event, or the processing module 401 is further configured to not perform the evaluation of the entry conditions for the measurement event, or the processing module 401 is further configured to determine whether to perform the evaluation of the entry conditions for the measurement event according to the network side instruction, or the processing module 401 is further configured to determine whether to perform the evaluation of the entry conditions for the predicted event according to the network side instruction.

[0453] And / or,

[0454] For cells in the first cell list, the processing module 401 is further configured not to perform the evaluation of the departure conditions for the predicted event, or the processing module 401 is further configured to determine whether to perform the evaluation of the departure conditions for the predicted event according to the network side instruction.

[0455] In some embodiments, the processing module 401 is specifically configured to perform at least one of the following:

[0456] If it is determined based on the prediction results of the at least one cell association that the predicted event is continuously satisfied within the first time period, then the prediction event of the at least one cell association is determined to be satisfied.

[0457] If, based on the prediction results of the at least one cell association and the measurement results of the at least one cell association, it is determined that the predicted event is continuously satisfied within the first time period, then the predicted event of the at least one cell association is determined to be satisfied.

[0458] If it is predicted that the predicted event associated with at least one cell is satisfied within the second time period, it is determined that the predicted event associated with at least one cell is satisfied.

[0459] If the probability that the predicted event associated with at least one cell is satisfied within the second time period is greater than or equal to the first threshold, it is determined that the predicted event associated with at least one cell is satisfied.

[0460] In some embodiments, the measurement reporting device 400 further includes:

[0461] The receiving module 403 is used to receive configuration information from the network-side device;

[0462] The configuration information is used to indicate at least one of the following:

[0463] List of cells where measurement event prediction can be performed;

[0464] A list of frequency points from which measurement event predictions can be performed;

[0465] List of cells where measurement event prediction is not feasible;

[0466] List of frequency points for events for which measurement prediction is not feasible;

[0467] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0468] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0469] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0470] The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

[0471] Therefore, in this embodiment, the terminal determines that the predicted event is satisfied based on the prediction results associated with at least one cell; the terminal determines whether the prediction results associated with at least one cell are incorrect based on the RRM measurement results of at least one cell; if the prediction results associated with at least one cell are incorrect, the terminal reports a first measurement report to the network-side device; wherein the first measurement report includes at least one of the following: a first indication information for indicating that the measurement event associated with at least one cell is not satisfied; a second indication information for indicating that the prediction results associated with at least one cell are incorrect; the identifier of at least one cell; and the RRM measurement results of at least one cell. Thus, after receiving the first measurement report, the network-side device can know that the prediction results associated with at least one cell are incorrect, which can prevent incorrect handovers and also prevent the waste of reserved radio resources on the network side. In other words, in this embodiment, when the terminal determines that the previous prediction results are incorrect, triggering actual measurement reporting allows the network side to promptly cancel ongoing or upcoming handover preparations to avoid incorrect handovers and the waste of reserved radio resources on the network side, ensuring the normal operation of the measurement event prediction function and thus improving handover performance.

[0472] Referring to Figure 6, when the measurement reporting device is a network-side device or a component in a network-side device, the measurement reporting device 500 includes: a receiving module 501;

[0473] The receiving module 501 is used to receive from the terminal a measurement report triggered by a predicted event associated with at least one cell;

[0474] The receiving module 501 is also configured to receive a first measurement report from the terminal;

[0475] The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following:

[0476] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0477] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0478] The identifier of the at least one cell;

[0479] Radio Resource Management (RRM) measurement results of at least one cell.

[0480] In some embodiments, the measurement reporting device 500 further includes:

[0481] The sending module 502 is used to send configuration information to the terminal;

[0482] The configuration information is used to indicate at least one of the following:

[0483] List of cells where measurement event prediction can be performed;

[0484] A list of frequency points from which measurement event predictions can be performed;

[0485] List of cells where measurement event prediction is not feasible;

[0486] List of frequency points for events for which measurement prediction is not feasible;

[0487] The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer;

[0488] The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer;

[0489] The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer;

[0490] The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

[0491] In this embodiment, the network-side device receives a measurement report triggered by a prediction event associated with at least one cell from the terminal, and also receives a first measurement report from the terminal. The first measurement report is triggered by an error in the prediction result associated with at least one cell, and includes at least one of the following: first indication information indicating that the measurement event associated with at least one cell was not satisfied; second indication information indicating that the prediction result associated with at least one cell was incorrect; the identifier of at least one cell; and the RRM measurement result of at least one cell. After receiving the first measurement report, the network-side device can know that the prediction result associated with at least one cell is incorrect, thus avoiding erroneous handovers and preventing the waste of reserved radio resources on the network side. In other words, in this embodiment, when the terminal determines that a previous prediction result is incorrect, triggering an actual measurement report allows the network side to promptly cancel ongoing or upcoming handover preparations, thereby avoiding erroneous handovers and preventing the waste of reserved radio resources on the network side.

[0492] The measurement reporting device provided in this application embodiment can realize the various processes implemented in the method embodiments of Figures 2 to 4 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0493] As shown in Figure 7, this application embodiment also provides a communication device 600, including a processor 601 and a memory 602, wherein the memory 602 stores programs or instructions that can run on the processor 601.

[0494] For example, when the communication device 600 is a terminal, the program or instruction executed by the processor 601 implements the various steps executed by the terminal in the above measurement reporting method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0495] For example, when the communication device 600 is a network-side device, the program or instruction executed by the processor 601 implements the various steps executed by the network-side device in the above measurement reporting method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0496] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the measurement reporting device 400 shown in FIG5.

[0497] Specifically, Figure 8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0498] The terminal 700 includes, but is not limited to, at least some of the following components: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

[0499] Those skilled in the art will understand that the terminal 700 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 710 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 8 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0500] It should be understood that, in this embodiment, the input unit 704 may include a graphics processor 7041 and a microphone 7042. The graphics processor 7041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0501] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 701 can transmit it to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network-side device. Typically, the radio frequency unit 701 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0502] The memory 709 can be used to store software programs or instructions, as well as various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 709 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0503] Processor 710 may include one or more processing units; optionally, processor 710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 710.

[0504] In some embodiments, the processor 710 is configured to determine that a predicted event is satisfied based on a prediction result associated with at least one cell;

[0505] The processor 710 is further configured to determine whether the prediction result is incorrect based on the RRM measurement results of the at least one cell;

[0506] If the prediction result is determined to be incorrect, the radio frequency unit 701 is used to report a first measurement report to the network-side device;

[0507] The first measurement report includes at least one of the following:

[0508] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0509] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0510] The identifier of the at least one cell;

[0511] The RRM measurement results of at least one cell.

[0512] Therefore, in this embodiment, the terminal determines that the predicted event is satisfied based on the prediction results associated with at least one cell; the terminal determines whether the prediction results associated with at least one cell are incorrect based on the RRM measurement results of at least one cell; if the prediction results are determined to be incorrect, the terminal reports a first measurement report to the network-side device; wherein the first measurement report includes at least one of the following: a first indication information for indicating that the measurement event associated with at least one cell is not satisfied; a second indication information for indicating that the prediction results associated with at least one cell are incorrect; the identifier of at least one cell; and the RRM measurement results of at least one cell. Thus, after receiving the first measurement report, the network-side device can know that the prediction results associated with at least one cell are incorrect, which can avoid incorrect handover and also prevent the waste of reserved radio resources on the network side. In other words, in this embodiment, when the terminal determines that the previous prediction results are incorrect, triggering the actual measurement report allows the network side to promptly cancel ongoing or upcoming handover preparations to avoid incorrect handover and the waste of reserved radio resources on the network side, ensuring the normal operation of the measurement event prediction function and thus improving handover performance.

[0513] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0514] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG4. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0515] This application embodiment also provides a network-side device, which may be the measurement reporting device 500 shown in FIG6.

[0516] Specifically, as shown in Figure 9, the network-side device 800 includes: an antenna 81, a radio frequency (RF) device 82, a baseband device 83, a processor 84, and a memory 85. The antenna 81 is connected to the RF device 82. In the uplink direction, the RF device 82 receives information through the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes the information to be transmitted and sends it to the RF device 82. The RF device 82 processes the received information and then transmits it through the antenna 81.

[0517] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 83, which includes a baseband processor.

[0518] The baseband device 83 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG9. One of the chips is, for example, a baseband processor, which is connected to the memory 85 via a bus interface to call the program or instructions in the memory 85 to execute the operation of the network-side device shown in the above method embodiment.

[0519] The network-side device may also include a network interface 86, such as a Common Public Radio Interface (CPRI).

[0520] The radio frequency device 82 is used to receive a measurement report triggered by a predicted event associated with at least one cell from the terminal;

[0521] The radio frequency device 82 is also configured to receive a first measurement report from the terminal;

[0522] The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following:

[0523] The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied;

[0524] The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect;

[0525] The identifier of the at least one cell;

[0526] Radio Resource Management (RRM) measurement results of at least one cell.

[0527] In this embodiment, the network-side device receives a measurement report triggered by a prediction event associated with at least one cell from the terminal, and also receives a first measurement report from the terminal. The first measurement report is triggered by an error in the prediction result associated with at least one cell, and includes at least one of the following: first indication information indicating that the measurement event associated with at least one cell was not satisfied; second indication information indicating that the prediction result associated with at least one cell was incorrect; the identifier of at least one cell; and the RRM measurement result of at least one cell. After receiving the first measurement report, the network-side device can know that the prediction result associated with at least one cell is incorrect, thus avoiding incorrect handover and preventing the waste of reserved radio resources on the network side. In other words, in this embodiment, when the terminal determines that the previous prediction result is incorrect, triggering the actual measurement report allows the network side to promptly cancel ongoing or upcoming handover preparations to avoid incorrect handover and the waste of reserved radio resources on the network side. This ensures the normal operation of the measurement event prediction function and improves handover performance.

[0528] In addition, the network-side device 800 of this application embodiment also includes: a program or instructions stored in a memory 85 and executable on a processor 84. The processor 84 calls the program or instructions in the memory 85 to execute the methods executed by each module shown in FIG6 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0529] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described measurement reporting method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0530] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0531] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above measurement reporting method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0532] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0533] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described measurement reporting method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0534] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps executed by the terminal in the measurement reporting method described above, and the network-side device can be used to perform the steps executed by the network-side device in the measurement reporting method described above.

[0535] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0536] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0537] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A measurement reporting method, comprising: The terminal determines that the predicted event has been met based on the prediction results associated with at least one cell; The terminal determines whether the prediction result is incorrect based on the Radio Resource Management (RRM) measurement results of the at least one cell; If the prediction result is determined to be incorrect, the terminal reports a first measurement report to the network-side device; The first measurement report includes at least one of the following: The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied; The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect; The identifier of the at least one cell; The RRM measurement results of at least one cell.

2. The method according to claim 1, wherein, If the prediction result is determined to be incorrect, the method further includes: The terminal removes at least one cell from the first cell list; The first cell list includes cells that meet the measurement reporting trigger mechanism.

3. The method according to claim 2, wherein, The first cell list is a list of cells corresponding to the predicted event; or, The first cell list is a shared list of cells for both predicted and measured events.

4. The method according to claim 2 or 3, wherein, The first cell list is a list of cells corresponding to the predicted event; Among them, the predicted event and the measured event are associated with different measurement identifiers, or the predicted event and the measured event are associated with different reporting configuration identifiers; or the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

5. The method according to claim 4, wherein, The method further includes: For cells in the first cell list, the terminal does not perform the evaluation of the departure conditions for the predicted event; or, For a cell in the first cell list, the terminal determines, according to network-side instructions, whether to evaluate the departure conditions of the predicted event based on measurement results or prediction results.

6. The method according to claim 2 or 3, wherein, The first cell list is a shared list of cells for both predicted and measured events; Among them, the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

7. The method according to claim 6, wherein, The method further includes: For cells added to the first cell list based on the prediction results, the terminal continues to evaluate the entry conditions of the measurement event, and if it is determined that the prediction results are incorrect, the terminal triggers measurement reporting and removes the corresponding cell from the first cell list; And / or, For cells added to the first cell list based on the prediction results, the terminal continues to evaluate the entry conditions of the measurement event, and if the prediction results are determined to be correct, the terminal triggers measurement reporting; And / or, For cells in the first cell list, the terminal does not perform the evaluation of the entry conditions for the predicted event, or the terminal does not perform the evaluation of the entry conditions for the measurement event, or the terminal determines whether to perform the evaluation of the entry conditions for the measurement event according to the network side instruction, or the terminal determines whether to perform the evaluation of the entry conditions for the predicted event according to the network side instruction. And / or, For cells in the first cell list, the terminal does not perform the evaluation of the departure conditions for the predicted event, or the terminal determines whether to perform the evaluation of the departure conditions for the predicted event based on instructions from the network side.

8. The method according to any one of claims 1 to 7, wherein, The terminal determines, based on the prediction results associated with at least one cell, that the predicted event is satisfied including at least one of the following: If it is determined based on the prediction results associated with the at least one cell that the predicted event is continuously satisfied within the first time period, the terminal determines that the predicted event associated with the at least one cell is satisfied. If, based on the prediction results of the at least one cell association and the measurement results of the at least one cell association, it is determined that the predicted event is continuously satisfied within the first time period, the terminal determines that the predicted event of the at least one cell association is satisfied. If it is predicted that the predicted event associated with at least one cell is satisfied within the second time period, the terminal determines that the predicted event associated with at least one cell is satisfied. If the probability that the predicted event associated with at least one cell is satisfied within the second time period is greater than or equal to the first threshold, the terminal determines that the predicted event associated with at least one cell is satisfied.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: The terminal receives configuration information from the network-side device; The configuration information is used to indicate at least one of the following: List of cells where measurement event prediction can be performed; A list of frequency points from which measurement event predictions can be performed; List of cells where measurement event prediction is not feasible; List of frequency points for events for which measurement prediction is not feasible; The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer; The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer; The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer; The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

10. A measurement reporting method, comprising: The network-side device receives a measurement report triggered by at least one predicted event associated with a cell from the terminal; The network-side device receives a first measurement report from the terminal; The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following: The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied; The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect; The identifier of the at least one cell; Radio Resource Management (RRM) measurement results of at least one cell.

11. The method according to claim 10, wherein, The method further includes: The network-side device sends configuration information to the terminal; The configuration information is used to indicate at least one of the following: List of cells where measurement event prediction can be performed; A list of frequency points from which measurement event predictions can be performed; List of cells where measurement event prediction is not feasible; List of frequency points for events for which measurement prediction is not feasible; The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer; The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer; The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer; The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

12. A measurement reporting device, comprising: Processing module and sending module; The processing module is used to determine whether a predicted event has been met based on the prediction results associated with at least one cell. The processing module is further configured to determine whether the prediction result is incorrect based on the Radio Resource Management (RRM) measurement results of the at least one cell; If the prediction result is determined to be incorrect, the sending module is used to report a first measurement report to the network-side device; The first measurement report includes at least one of the following: The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied; The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect; The identifier of the at least one cell; The RRM measurement results of at least one cell.

13. The apparatus according to claim 12, wherein, If the prediction result is determined to be incorrect, the processing module is further configured to remove the at least one cell from the first cell list; The first cell list includes cells that meet the measurement reporting trigger mechanism.

14. The apparatus according to claim 13, wherein, The first cell list is a list of cells corresponding to the predicted event; Among them, the predicted event and the measured event are associated with different measurement identifiers, or the predicted event and the measured event are associated with different reporting configuration identifiers; or the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

15. The apparatus according to claim 14, wherein, For cells in the first cell list, the processing module is further configured to not perform an evaluation of the departure conditions for the predicted event; or, For cells in the first cell list, the processing module is further configured to determine, based on network-side instructions, whether to evaluate the departure conditions of the predicted event based on measurement results or prediction results.

16. The apparatus according to claim 13, wherein, The first cell list is a shared list of cells for both predicted and measured events; Among them, the predicted event and the measured event are associated with the same measurement identifier, or the predicted event and the measured event are associated with the same reporting configuration identifier.

17. The apparatus according to claim 16, wherein, For cells added to the first cell list based on the prediction results, the processing module is further configured to continue evaluating the entry conditions of the measurement event, and if it is determined that the prediction results are incorrect, the processing module is further configured to trigger measurement reporting and remove the corresponding cell from the first cell list; And / or, For cells added to the first cell list based on the prediction results, the processing module is further configured to continue evaluating the entry conditions of the measurement event, and if the prediction results are determined to be correct, the processing module is further configured to trigger measurement reporting; And / or, For cells in the first cell list, the processing module is further configured to not perform the evaluation of the entry conditions for the predicted event, or the processing module is further configured to not perform the evaluation of the entry conditions for the measurement event, or the processing module is further configured to determine whether to perform the evaluation of the entry conditions for the measurement event according to the network side instruction, or the processing module is further configured to determine whether to perform the evaluation of the entry conditions for the predicted event according to the network side instruction. And / or, For cells in the first cell list, the processing module is further configured to either not perform the evaluation of the departure conditions for the predicted event, or the processing module is further configured to determine whether to perform the evaluation of the departure conditions for the predicted event based on network-side instructions.

18. The apparatus according to any one of claims 12 to 17, wherein, The processing module is specifically used to perform at least one of the following: If it is determined based on the prediction results of the at least one cell association that the predicted event is continuously satisfied within the first time period, then the prediction event of the at least one cell association is determined to be satisfied. If, based on the prediction results of the at least one cell association and the measurement results of the at least one cell association, it is determined that the predicted event is continuously satisfied within the first time period, then the predicted event of the at least one cell association is determined to be satisfied. If it is predicted that the predicted event associated with at least one cell is satisfied within the second time period, it is determined that the predicted event associated with at least one cell is satisfied. If the probability that the predicted event associated with at least one cell is satisfied within the second time period is greater than or equal to the first threshold, it is determined that the predicted event associated with at least one cell is satisfied.

19. The apparatus according to any one of claims 12 to 18, wherein, The measurement reporting device also includes: The receiving module is used to receive configuration information from network-side devices; The configuration information is used to indicate at least one of the following: List of cells where measurement event prediction can be performed; A list of frequency points from which measurement event predictions can be performed; List of cells where measurement event prediction is not feasible; List of frequency points for events for which measurement prediction is not feasible; The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer; The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer; The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer; The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

20. A measurement reporting device, comprising: The receiving module is used to receive measurement reports triggered by at least one predicted event associated with a cell from the terminal; The receiving module is further configured to receive a first measurement report from the terminal; The first measurement report is a measurement report triggered by an error in the prediction result associated with the at least one cell, and the first measurement report includes at least one of the following: The first indication information is used to indicate that the measurement event associated with the at least one cell has not been satisfied; The second indication information is used to indicate that the prediction result associated with the at least one cell is incorrect; The identifier of the at least one cell; Radio Resource Management (RRM) measurement results of at least one cell.

21. The apparatus according to claim 20, wherein, The measurement reporting device also includes: The sending module is used to send configuration information to the terminal; The configuration information is used to indicate at least one of the following: List of cells where measurement event prediction can be performed; A list of frequency points from which measurement event predictions can be performed; List of cells where measurement event prediction is not feasible; List of frequency points for events for which measurement prediction is not feasible; The third indication information is used to indicate whether measurement event prediction can be performed at M frequency points, where M is a positive integer; The first identifier associated with M frequency points, wherein the frequency points whose first identifier is the same as the first identifier associated with the service frequency point are the frequency points for which measurement event prediction can be performed, and M is a positive integer; The fourth indication information is used to indicate whether measurement event prediction can be performed in N cells, where N is a positive integer; The second identifier associated with N cells, wherein the cells whose associated second identifier is the same as the second identifier associated with the serving cell are cells for which measurement event prediction can be performed, and N is a positive integer.

22. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the measurement reporting method as claimed in any one of claims 1 to 9.

23. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the measurement reporting method as claimed in claim 10 or 11.

24. A readable storage medium storing a program or instructions that, when executed by a processor, implement the measurement reporting method as claimed in any one of claims 1 to 9, or implement the steps of the measurement reporting method as claimed in claim 10 or 11.

Images