Measurement event reporting method and apparatus, and measurement event configuration method and apparatus

WO2026199328A1PCT designated stage Publication Date: 2026-10-011FINITY INC +3
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/085379
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-03-27
Publication Date
2026-10-01

Smart Images

  • Figure CN2025085379_01102026_PF_FP_ABST
    Figure CN2025085379_01102026_PF_FP_ABST
Patent Text Reader

Abstract

A measurement event reporting method and apparatus, and a measurement event configuration method and apparatus. The reporting method comprises: a terminal device receiving first information indicated by a network device; and when determining that at least a first condition is met, the terminal device reporting a first event to the network device on the basis of the first information, wherein the first event is a measurement event predicted by the terminal device on the basis of AI / ML.
Need to check novelty before this filing date? Find Prior Art

Description

Methods for reporting measurement events, methods for configuring measurement events, and apparatus. Technical Field

[0001] This application relates to the field of communications. Background Technology

[0002] In 3GPP Release 19's research topic on Artificial Intelligence (AI) and Machine Learning (ML), specifically the application of AI / ML in mobility management, possible scenarios for predicting measurement events are being discussed, as well as how to apply the predicted measurement events to subsequent mobility-related decisions.

[0003] AI / ML-based prediction of measurement events can be either direct or indirect. In the direct prediction approach, the terminal device directly predicts whether a measurement event will be triggered in the future based on the measurement results from Radio Resource Management (RRM). In the indirect prediction approach, the terminal device uses AI / ML technology to predict the RRM measurement results, and then uses an algorithm to evaluate whether a measurement event will be triggered in the future based on the predicted RRM measurement results.

[0004] Terminal devices can report measurement events based on AI / ML predictions to network devices. Based on the information of the predicted measurement events received, network devices can perform mobility-related processing in advance, such as preparing for handover in advance, or even triggering the handover execution process in advance and instructing terminal devices to perform handover, so as to avoid handover failures caused by late handover execution or rapid signal quality fading of the current serving cell.

[0005] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention

[0006] Current discussions on RAN2 primarily focus on the accuracy of AI / ML-based measurement event predictions and the system-level impact of switching based on predicted measurement events. Extensive discussions have been held regarding reporting measurement events triggered entirely by actual measurement results, as well as methods for triggering switchover preparation and execution. However, the lack of standardization in triggering and reporting predicted measurement events has led to discrepancies in simulation results analysis of predicted metrics and system-level gains among different companies.

[0007] Since the measurement events defined in the current specifications are all triggered by actual measurement results, there is currently no definition for measurement events based on AI / ML predictions. However, according to the progress of RAN2, the terminal needs to report the predicted measurement events to the network device, and the network device will make subsequent decisions and processes based on the predicted measurement events. Therefore, it is necessary to consider defining the predicted measurement events.

[0008] Furthermore, since the predicted measurement events are derived based on AI / ML technology, on the one hand, the accuracy of the predicted measurement events needs to be considered. It may be necessary to set more stringent conditions for the events than those based entirely on actual measurement results, such as entry, exit, triggering, and reporting conditions. On the other hand, in order to further improve the system-level gain of the measurement events predicted by AI / ML technology, especially when actual measurement events may continue to be used as a guarantee during the switching process, it may be necessary to configure relevant conditions that are easier to meet than those based entirely on actual measurement results, so as to trigger and report the predicted measurement events earlier and improve system-level performance.

[0009] Based on the progress of RAN2, measurement events predicted using AI / ML technology and traditional measurement events based entirely on actual measurement results may coexist and need to be reported to network devices. Network devices may need to use both AI / ML-predicted and traditional measurement events based entirely on actual measurement results to jointly determine subsequent mobility-related processing.

[0010] Currently, there are no relevant definitions regarding the conditions and definitions of measurement events predicted based on AI / ML technology.

[0011] To address one or more of the aforementioned problems, embodiments of this application provide a method for reporting measurement events, a method for configuring measurement events, and an apparatus.

[0012] According to one aspect of the embodiments of this application, a measurement event reporting device is provided, the device being applied to a terminal device, the device comprising: a first receiving unit for receiving first information indicated by a network device; and a first sending unit for reporting a first event to the network device based on the first information, wherein the first event is a measurement event predicted by the terminal device based on AI / ML.

[0013] According to another aspect of the embodiments of this application, a configuration apparatus for measurement events is provided. The apparatus is applied to a network device and includes: a second sending unit that sends first information to a terminal device. The first information is used at least by the terminal device to report a first event, wherein the first event is a measurement event predicted by the terminal device based on AI / ML.

[0014] According to another aspect of the embodiments of this application, a communication system is provided, the communication system including a terminal device and / or a network device, the terminal device including the above-described measurement event reporting device according to the embodiments of this application, and the network device including the above-described measurement event configuration device according to the embodiments of this application.

[0015] According to another aspect of the embodiments of this application, a method for reporting measurement events is provided, the method being applied to a terminal device, the method comprising: the terminal device receiving first information indicated by a network device; the terminal device reporting a first event to the network device based on the first information, wherein the first event is a measurement event predicted by the terminal device based on AI / ML, and the terminal device determining that at least a first condition is met.

[0016] According to another aspect of the embodiments of this application, a method for configuring measurement events is provided, the method being applied to a network device, the method comprising: the network device sending first information to a terminal device, the first information being used at least for the terminal device to report a first event, the first event being a measurement event predicted by the terminal device based on AI / ML.

[0017] According to another aspect of the present application, a computer-readable program is provided, wherein when the program is executed in a measurement event reporting device or terminal device, the program causes the measurement event reporting device or terminal device to perform the measurement event reporting method described in the present application.

[0018] According to another aspect of the embodiments of this application, a computer-readable program is provided, wherein when the program is executed in a measurement event configuration device or network device, the program causes the measurement event configuration device or network device to perform the measurement event configuration method described in the embodiments of this application.

[0019] According to another aspect of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program causes a measurement event reporting device or terminal device to perform the measurement event reporting method described in the present application.

[0020] According to another aspect of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program causes a measurement event configuration device or network device to perform the measurement event configuration method described in the present application.

[0021] One of the beneficial effects of the embodiments of this application is that:

[0022] According to the first information indicated by the network device, the terminal device reports the measurement events based on AI / ML prediction to the network device when it is determined that at least the first condition is met. Compared with the existing reports of measurement events based entirely on the actual measurement results, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on the air interface signaling quantity limit and air interface channel quality, etc.

[0023] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0024] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0025] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

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

[0027] It should be emphasized that the term "including / comprises / have" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0028] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0029] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any creative effort. In the drawings:

[0030] Figure 1 is a schematic diagram of a communication system;

[0031] Figure 2 is another schematic diagram of the communication system;

[0032] Figure 3 is a schematic diagram of a method for reporting measurement events according to an embodiment of this application;

[0033] Figure 4 is a schematic diagram of a terminal device predicting a first event according to an embodiment of this application;

[0034] Figure 5 is a schematic diagram of a terminal device predicting and reporting a first event according to an embodiment of this application;

[0035] Figure 6 is another schematic diagram of a terminal device predicting and reporting a first event according to an embodiment of this application;

[0036] Figure 7 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application;

[0037] Figure 8 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application;

[0038] Figure 9 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application;

[0039] Figure 10 is another schematic diagram of a terminal device predicting and reporting a first event according to an embodiment of this application;

[0040] Figure 11 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application;

[0041] Figure 12 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application;

[0042] Figure 13 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application;

[0043] Figure 14 is a schematic diagram of a terminal device reporting a first event and exiting according to an embodiment of this application;

[0044] Figure 15 is another schematic diagram of the terminal device reporting the first event and exiting according to an embodiment of this application;

[0045] Figure 16 is another schematic diagram of a method for reporting measurement events according to an embodiment of this application;

[0046] Figure 17 is another schematic diagram of a method for reporting measurement events according to an embodiment of this application;

[0047] Figure 18 is another schematic diagram of a method for reporting measurement events according to an embodiment of this application;

[0048] Figure 19 is a schematic diagram of a measurement event reporting device according to an embodiment of this application;

[0049] Figure 20 is a schematic diagram of a configuration device for measuring events according to an embodiment of this application;

[0050] Figure 21 is a schematic block diagram of the system configuration of a terminal device according to an embodiment of this application;

[0051] Figure 22 is a schematic block diagram of the system configuration of a network device according to an embodiment of this application. Detailed Implementation

[0052] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

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

[0054] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

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

[0056] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, as well as 5G, 5G-Advanced, New Radio (NR), 6G, etc., and / or other currently known or future communication protocols.

[0057] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), OAM (Operations, Administration, and Maintenance), OAM domain nodes, core network, core network domain nodes, core network domain network elements, such as AMF, SMF, UPF, AUSF, UDM, UDR, NSSF, NEF, PCF, NRF, AF, DN, etc.

[0058] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), Centralized Units (CUs), Distributed Units (DUs), etc. They may also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" can encompass some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0059] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.

[0060] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

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

[0062] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0063] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0064] Figure 1 is a schematic diagram of a communication system, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and a terminal device 102.

[0065] In this embodiment of the application, network device 101 may be a network device of RAN, such as the second network device 102 being a base station, etc.

[0066] For simplicity, Figure 1 is illustrated using only one terminal device and one network device as an example, but the embodiments of this application are not limited thereto.

[0067] Figure 2 is another schematic diagram of the communication system, illustrating the situation of terminal equipment and network equipment as examples, as well as the communication between terminal equipment and network equipment.

[0068] As shown in Figure 2, the network-side equipment includes an RU (radio frequency unit) for air interface transmission and reception, and a CU / DU for related radio access (RAN). It also includes core network-related processing units (CT / OAM / related processing units), edge computing-related processing units, and data units related to the core network or RAN side.

[0069] Figure 2 is merely an illustrative example; the relevant equipment units can be deployed in a centralized or distributed manner. Furthermore, the network-side equipment, excluding the RU, considers a hardware-software hybrid device based on a CPU / GPU architecture. The related signal processing extensively utilizes AI / ML models for implementation. The network equipment specifically refers to the equipment corresponding to the air interface-related RAN-side CU / DU units and their connected RU units, forming the traditional base station function, or the network equipment of the new architecture of 6G communication systems. The terminal-side equipment, in addition to the air interface-facing terminal equipment, may also include terminal-related server equipment and related data storage or data management units. The term "terminal-side equipment" here refers to its logical affiliation, not its actual physical location; for example, the terminal-side data unit may also exist within the network-side equipment. Similarly, the terminal-side equipment or the terminal equipment's signal processing unit also extensively utilizes AI / ML models for implementation.

[0070] Various embodiments of the present application will now be described with reference to the accompanying drawings. These embodiments are merely exemplary and are not intended to limit the scope of the present application.

[0071] First aspect of the embodiments

[0072] This application provides a method for reporting measurement events, which is applied to a terminal device, such as terminal device 102 in FIG1.

[0073] Figure 3 is a schematic diagram of a method for reporting measurement events according to an embodiment of this application. As shown in Figure 3, the method includes:

[0074] 301: The terminal device receives the first information indicated by the network device;

[0075] 302: Based on the first information, the terminal device reports a first event to the network device when it determines that at least the first condition is met. The first event is a measurement event predicted by the terminal device based on AI / ML.

[0076] In this way, the terminal device reports measurement events based on AI / ML predictions to the network device when it is determined that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events based entirely on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0077] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0078] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0079] In operation 301, the terminal device receives the first information indicated by the network device.

[0080] In the embodiments of this application, the first information is used to at least indicate a first configuration, which is used to configure the indication of the first event and / or the related conditions of the first event.

[0081] In this embodiment of the application, the relevant conditions for the first event include at least one of the following:

[0082] The entry conditions for this first event;

[0083] The exit conditions for this first event;

[0084] The triggering condition for this first event;

[0085] The reporting conditions for this first incident.

[0086] In this embodiment of the application, the first information is also used to indicate at least one of the following:

[0087] The indication of the first event;

[0088] The configuration of the relevant conditions for the second event;

[0089] The connection between the first event and the second event;

[0090] Does the network device allow the terminal device to use the terminal device's AI / ML model to predict the first event?

[0091] The way the terminal device reports the first event and / or the second event.

[0092] In the embodiments of this application, the indication of the first event includes at least one of AI / ML indication and prediction indication.

[0093] For example, the second configuration of the second event or the report about the second event may include AI / ML related indications or prediction indications, or may include AI / ML switches or prediction switches.

[0094] In this embodiment, the second event is a measurement event entirely based on real measurement results, i.e., a real measurement event. Further, the second event is a measurement event associated with the first event that is also entirely based on real measurement results, and the first event is a predicted measurement event related to the second event. The first event is a predicted measurement event obtained by applying AI / ML technology to predict the second event; it can also be called a predicted event related to the second event, an AI / ML event related to the second event, a real event related to the first event, or a non-AI / ML event related to the first event.

[0095] In the embodiments of this application, the second event is a measurement event obtained entirely based on the actual measurement results. The second event can include all existing measurement-related events. For example, the second event can be any measurement event defined in Rel-18 38.331 regarding the triggering of measurement reports (e.g., Section 5.5.4), such as events A1, A2, A3, A4, A5, and A6. The second event can also include any measurement events that will be introduced in the future that are obtained entirely based on the actual measurement results.

[0096] For example, if the second event is the A3 event that neighboring cell Cell A is better than special cell SpCell-B, then the first event is the A3 event predicted by the terminal device that neighboring cell Cell A is better than special cell SpCell-B.

[0097] In this embodiment of the application, the relevant conditions for the second event include at least one of the following:

[0098] The entry conditions for this second event;

[0099] The exit conditions for this second event;

[0100] The triggering condition for this second event;

[0101] The reporting conditions for this second incident.

[0102] In this application embodiment, the association between the first event and the second event is indicated by at least one of the following:

[0103] The same measurement identifier is used, for example, the same measurement identifier is applied when reporting the first event and the second event;

[0104] The same measurement event report, for example, uses a second event to report a first event, including an indication that the first event was predicted by AI / ML, and also includes a measurement identifier of the second event;

[0105] The same object of measurement, for example, the first reported event and the second reported event respectively indicate the same object of measurement;

[0106] Same report identifier.

[0107] In the embodiments of this application, an AI / ML-specific measurement identifier and / or a measurement identifier of a real measurement event can be indicated in the first event.

[0108] For example, an AI / ML-specific measurement identifier indicates that the first event is a measurement event based on AI / ML prediction, and a measurement identifier of the actual measurement event indicates a second event associated with the first event, which has the measurement identifier of the actual measurement event indicated in the first event; in addition, the AI / ML-specific measurement identifier can also be replaced with an AI / ML-specific report identifier, and the report identifier of the actual measurement event can also be replaced with the report identifier of the actual measurement event.

[0109] In this embodiment of the application, a new identifier may also be used in the report of the first event, which is included in the second event to indicate the first event associated with the second event.

[0110] In embodiments of this application, the type of the first event can be indicated in the first configuration regarding the first event and in the report regarding the first event.

[0111] In one implementation, the event type of the first event may be predefined, for example, defined by a newly introduced measurement event type, such as the newly introduced measurement event type used to indicate a predicted measurement event.

[0112] For example, the type of the first event can be defined as Event AI-XxYy, Event XxYy-AI, or Event AIMobXxYy, etc., where X, Y, and y are optional. For example, the type of the first event can be simplified to Event AI-Xx or Event AIMobx, etc. The uppercase letters X and Y are the letter codes for the event type, such as A, B, C, D, H, X, Y, Z (as X) and H (as Y) in existing second event types. The lowercase letters x and y are the numerical codes for the event type, such as 1, 2, 3, 4, 5, 6 used in existing second event types.

[0113] Taking the second event as Event A3 as an example, the type of the first event related to the second event may be Event AI-A3 or Event A3-AI or Event AIMobA3 or Event AIMob3, etc.

[0114] In another implementation, the event type of the first event can also be indicated by adding an indication of the first event to the second event. For example, the first event can be indicated by adding AI / ML indications or prediction indications to the relevant configuration and / or reports of the second event.

[0115] Since the first event is a measurement event predicted by AI / ML rather than a real measurement event, when the terminal device predicts the first event, the predicted time of the first event may not have arrived yet, and the real second event related to the first event may not have met the triggering or reporting conditions yet.

[0116] Figure 4 is a schematic diagram of a terminal device predicting a first event according to an embodiment of this application.

[0117] As shown in Figure 4, the terminal device predicts at time t1 that the conditions for the first event will be met at time t2, but based entirely on the actual measurement results, the second event related to the first event will occur at time t3.

[0118] As shown in Figure 4(a), the occurrence time t3 of the second event may be later than the time t2 predicted by the terminal device, or as shown in Figure 4(b), the occurrence time t3 of the second event may be earlier than the time t2 predicted by the terminal device.

[0119] The timing of the terminal device reporting the first event will affect the network device's mobility management decisions, such as when to prepare for and execute a handover, and will ultimately affect handover frequency, handover success rate, handover time, and service interruption time.

[0120] In connection with the above, in operation 302, the terminal device reports the first event to the network device based on the first information, provided that at least the first condition is met.

[0121] In this embodiment of the application, the first condition may include at least one of the following:

[0122] The terminal device predicted the occurrence of this first event;

[0123] The terminal device predicted the occurrence of the first event, and the first event was predicted to occur for the first time.

[0124] The terminal device predicted the occurrence of the first event, which had not yet been reported.

[0125] The terminal device predicts that the first event will occur, and predicts that the triggering conditions and / or reporting conditions of the first event will be met. For example, the triggering conditions of the first event include at least one of a trigger time (TTT) condition and a trigger count condition.

[0126] In this application embodiment, the terminal device predicting the occurrence of the first event may include: the terminal device predicting that the entry conditions of the first event are met, and / or the terminal device predicting that the first event will be triggered within a certain time range.

[0127] In this embodiment, reporting a first event to the network device when at least a first condition is met includes: reporting the first event at a first time (or a first moment), where the first time is the time when the terminal device determines that the first condition is met. That is, the terminal device reports the first event when it predicts that the relevant conditions for the first event will be met, without waiting for the predicted time when the relevant conditions for the first event will be met, or waiting for the relevant conditions for a second event related to the first event to be met. In this way, the terminal device can report the predicted first event to the network device earlier, allowing the network device to process the predicted event earlier, such as preparing for or even executing a handover in advance.

[0128] In this embodiment of the application, the terminal device may report the first event only at the first time (or the first moment), or it may periodically report the first event starting from the first time until the terminal device determines that the first condition is no longer met, or until the time when the terminal device predicts that the relevant conditions for the first event will be met arrives, or until it is determined according to network instructions that reporting is not required, and then stop reporting the first event.

[0129] Alternatively, in this embodiment of the application, reporting the first event to the network device upon determining that at least the first condition is met includes: reporting the first event at a second time (or a second moment), where the second time is a time predicted by the terminal device, indicated by the first condition determined to be met by the terminal device. That is, the terminal device needs to wait until the time predicted by the terminal device for the relevant conditions of the first event to be met before reporting the first event.

[0130] For example, the terminal device reports at the predicted time (or moment) when the first event occurs; or at the predicted time (or moment) when the first event first occurs; or at the predicted time (or moment) when the first event has not yet been reported; or at the predicted time (or moment) when the triggering or reporting conditions for the first event are met. In this way, the terminal device's reporting at the time when the relevant conditions for the predicted first event are met can provide a purely prediction-based method when real measurement results are lacking, saving the resource and power consumption overhead caused by measurement and calculation.

[0131] In other words, the terminal device may report the predicted first event at the time (or moment) when the first condition is met; or at the time (or moment) predicted by the terminal device as indicated by the first condition that the terminal device determines is met, i.e., at the time (or moment) when the predicted first event occurs.

[0132] The following section provides a detailed explanation of how a terminal device reports a first event, taking into account different scenarios: the first condition and the terminal device predicting the occurrence of the first event.

[0133] Case 1-1: The first condition is that the terminal device predicts that the first event will occur, and the terminal device predicts that the first event will occur means that the terminal device predicts that the entry conditions of the first event will be met.

[0134] Figure 5 is a schematic diagram of a terminal device predicting and reporting a first event according to an embodiment of this application. As shown in Figure 5, the terminal device predicts at time t10 that the entry condition for the first event will be met at time t20. At time t11, the terminal device also predicts that the entry condition for the first event will still be met at time t21, and so on. That is, the terminal device predicts at times t10, t11, t12, and t13 that the first event will occur at times t20, t21, t22, and t23, respectively. Therefore, if the first condition is met at times t10, t11, t12, and t13, the terminal device reports the predicted first event at times t10, t11, t12, and t13, respectively.

[0135] Alternatively, the terminal device may report the first event at the time predicted by the terminal device as indicated by the first condition, i.e., the terminal device reports the predicted first event at times t20, t21, t22, and t23 respectively.

[0136] Case 1-2: The first condition is that the terminal device predicts that the first event will occur, and the terminal device predicts that the first event will occur within a certain time range.

[0137] Figure 6 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application. As shown in Figure 6, the terminal device predicts at time t10 that the first event will be triggered within the prediction window PW0, and at time t11 that the first event will also be triggered within the prediction window PW1, and so on. That is, the terminal device predicts the first event at t10, t11, t12, and t13. Therefore, if the first condition is met at times t10, t11, t12, and t13, the terminal device reports the predicted first event at times t10, t11, t12, and t13, respectively.

[0138] Alternatively, the terminal device may report the first event at a time predicted by the terminal device as indicated by the first condition, i.e., the terminal device reports the predicted first event at one of the beginning, middle, or end times of PW0, PW1, PW2, and PW3, respectively.

[0139] Case 2-1: The first condition is that the terminal device predicts the occurrence of the first event, and the first event is predicted to occur for the first time. The prediction of the occurrence of the first event by the terminal device means that the terminal device predicts that the entry conditions of the first event are met.

[0140] Figure 7 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application. As shown in Figure 7, the terminal device predicts at time t10 that the entry condition for the first event is not met at time t20, and predicts at times t11, t12, and t13 that the entry condition for the first event is met at times t21, t22, and t23, respectively. Therefore, the first event is predicted at time t11, and since the first event is predicted for the first time and the first condition is met, the terminal device reports the predicted first event at time t11.

[0141] Alternatively, the terminal device may report the first event at the time predicted by the terminal device as indicated by the first condition, i.e., the terminal device reports the predicted first event at time t21. Case 2-2: The first condition is that the terminal device predicts the occurrence of the first event, and the first event is predicted to occur for the first time, and the terminal device predicting the occurrence of the first event means that the terminal device predicts that the first event will be triggered within a certain time range.

[0142] Figure 8 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application. As shown in Figure 8, the terminal device predicts at time t10 that the first event will not occur within the prediction window PW0, and predicts at times t11, t12, and t13 that the first event will occur within PW1, PW2, and PW3, respectively. Therefore, the first event is predicted at time t11, and since the first event is predicted for the first time, the first condition is met, and the terminal device reports the predicted first event at time t11.

[0143] Alternatively, the terminal device may report the first event at a time predicted by the terminal device, as indicated by the determination that the first condition is met, i.e., at one of the times in PW1, such as the beginning, middle, or end of PW1, the terminal device reports the predicted first event.

[0144] Case 3-1: The first condition is that the terminal device predicts the occurrence of the first event, and the first event has not yet been reported. The prediction of the occurrence of the first event by the terminal device means that the terminal device predicts that the entry conditions of the first event are met.

[0145] Figure 9 is another schematic diagram of a terminal device predicting and reporting a first event according to an embodiment of this application. As shown in Figure 9, the terminal device predicts at time t11 that the entry condition for the first event will be met at time t21, and the terminal device has not reported any reports about the first event, thus satisfying the first condition. At time t11, the terminal device initiates the process of reporting the predicted first event.

[0146] Alternatively, the terminal device may report the first event at the time predicted by the terminal device as indicated by the first condition, i.e., the terminal device reports the predicted first event at times t21, t22, and t23, even if it has not yet reported the first event.

[0147] Case 3-2: The first condition is that the terminal device predicts the occurrence of the first event, and the first event has not yet been reported. Furthermore, the terminal device predicts the occurrence of the first event by predicting that the first event will be triggered within a certain time range.

[0148] Figure 10 is another schematic diagram of a terminal device predicting and reporting a first event according to an embodiment of this application. As shown in Figure 10, the terminal device predicts at time t11 that the first event will be triggered within the prediction window PW1, and the terminal device has not reported any reports about the first event, thus satisfying the first condition. At time t11, the terminal device initiates the process of reporting the predicted first event. However, before sending a report about the first event, the terminal device predicts again at time t12 that the first event will be triggered within the prediction window PW2, and the terminal device has not reported any reports about the first event. In this case, the terminal device still satisfies the first condition, and the terminal device initiates the process of reporting the first event at time t12. The report content may include the prediction information at time t11 and / or time t12.

[0149] Alternatively, the terminal device may report the first event at a time predicted by the terminal device as indicated by the first condition, i.e., when the terminal device reports the predicted first event at one of the beginning, middle, or end times of PW1, PW2, or PW3, and has not yet reported the first event.

[0150] Case 4-1: The first condition is that the terminal device predicts that the first event will occur, and predicts that the triggering condition and / or reporting condition of the first event will be met. The prediction that the first event will occur means that the terminal device predicts that the entry condition of the first event will be met.

[0151] Figure 11 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application. As shown in Figure 11, if the trigger time (TTT) or the number of triggers of the first event is predicted to meet a preset condition at time t13, thereby satisfying the first condition, the terminal device reports the first event at time t13.

[0152] Alternatively, the terminal device may report the first event at a time predicted by the terminal device as indicated by the first condition, i.e., the terminal device predicts that the condition regarding the trigger time TTT or the number of triggers of the first event will be met at time t23, and the terminal device reports the first event at time t23.

[0153] Case 4-2: The first condition is that the terminal device predicts that the first event will occur, and predicts that the triggering condition and / or reporting condition of the first event will be met. The terminal device predicting that the first event will occur means that the terminal device predicts that the first event will be triggered within a certain time range.

[0154] Figure 12 is another schematic diagram of the terminal device predicting and reporting the first event according to an embodiment of this application. As shown in Figure 12, if the trigger time (TTT) or the number of triggers is predicted to meet a preset condition at time t13, thereby satisfying the first condition, the terminal device reports the first event at time t13.

[0155] Alternatively, the terminal device may report the first event at a time predicted by the terminal device as indicated by the first condition, i.e., the terminal device predicts that the condition regarding the trigger time TTT or the number of triggers of the first event will be met during PW3, and the terminal device reports the first event at one of the following times in PW3: the beginning, middle, or end of PW3.

[0156] In this embodiment of the application, when the terminal device determines to report the first event, a second condition related to the second event may also be introduced. That is, if it is determined that the first condition and the second condition are met, the first event is reported to the network device, and the second condition is a related condition of the second event.

[0157] As described above, the second event is a measurement event that is entirely based on actual measurement results and is associated with the first event, which is a predicted measurement event related to the second event.

[0158] In this embodiment of the application, the second condition may include at least one of the following:

[0159] The terminal device detected that the entry condition for the second event was met;

[0160] The terminal device detected that the exit condition for the second event was met;

[0161] The terminal device detected that the triggering condition for the second event was met;

[0162] The terminal device detected that the reporting conditions for the second event were met.

[0163] In this embodiment of the application, reporting a first event to the network device when it is determined that the first condition and the second condition are met includes: reporting the first event at a third time, where the third time is the time when the terminal device determines that the first condition and the second condition are met.

[0164] In this way, by leveraging AI / ML technology to report potential measurement events to network devices in advance while also taking into account actual measurement results, the likelihood of the predicted measurement events actually occurring is further increased. Network devices applying this method can make more reliable decisions regarding handover and other mobility management based on the first event.

[0165] Figure 13 is another schematic diagram of a terminal device predicting and reporting a first event according to an embodiment of this application. As shown in Figure 13, the terminal device predicts at time t11 that the first event will meet the entry condition at time t21, and reports the first event at the moment when it detects that the entry condition of the second event is met.

[0166] In this embodiment of the application, the method may further include:

[0167] If the third condition is met, the terminal device reports the first event exit to the network device.

[0168] In this application embodiment, the third condition may include at least one of the following:

[0169] The terminal device reported this first event;

[0170] The terminal device is determined not to meet the first condition;

[0171] The terminal device predicted that the exit condition for the first event was met;

[0172] The terminal device determines that the first condition is not met, and the terminal device detects that the second condition is met;

[0173] The terminal device determines that the first condition is no longer met, and the terminal device detects that the second condition has not yet been met.

[0174] As described above, the second condition includes at least one of the following: an entry condition, an exit condition, a trigger condition, and a reporting condition for a measurement event that is entirely based on actual measurement results and is associated with the first event.

[0175] Figure 14 is a schematic diagram of a terminal device reporting a first event exit according to an embodiment of this application. As shown in Figure 14, the terminal device predicts that the first event meets the exit condition, that is, the first condition is not met, and the terminal device detects that the trigger condition of the second event is met, that is, the second condition is met, then the terminal device reports the first event exit.

[0176] Figure 15 is another schematic diagram of a terminal device reporting a first event and exiting according to an embodiment of this application. As shown in Figure 15, the terminal device that reported the first event predicted that the first condition was no longer met and the second condition had not yet been met, and the terminal device reported the first event and exited.

[0177] Additionally, in Figures 7 to 10 and Figures 13 to 15, the symbol “×” indicates that the entry condition for the first event is not met at that moment, or the exit condition for the first event is met at that moment.

[0178] As can be seen from the above embodiments, the terminal device reports measurement events based on AI / ML predictions to the network device when it determines that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events that are completely based on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0179] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0180] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0181] Second aspect of the embodiments

[0182] This application provides a method for reporting measurement events, which is applied to a network device and corresponds to the method for reporting measurement events applied to a terminal device described in the first aspect embodiment. The same or corresponding content can be found in the description of the first aspect embodiment. This method is applied to a network device, such as network device 101 in FIG1.

[0183] Figure 16 is another schematic diagram of a method for reporting measurement events according to an embodiment of this application. As shown in Figure 16, the method includes:

[0184] 1601: A network device sends first information to a terminal device, the first information being used at least by the terminal device to report a first event, the first event being a measurement event predicted by the terminal device based on AI / ML.

[0185] In this embodiment of the application, the first information is at least used to indicate a first configuration, which is used to configure the indication of the first event and / or the related conditions of the first event.

[0186] The relevant conditions for this first event include at least one of the following:

[0187] The entry conditions for this first event;

[0188] The exit conditions for this first event;

[0189] The triggering condition for this first event;

[0190] The reporting conditions for this first incident.

[0191] In this embodiment of the application, the first information is also used to indicate at least one of the following:

[0192] The indication of the first event;

[0193] The configuration of the relevant conditions for the second event;

[0194] The connection between the first event and the second event;

[0195] Does the network device allow the terminal device to use the terminal device's AI / ML model to predict the first event?

[0196] The way the terminal device reports the first event and / or the second event.

[0197] The second event is a measurement event that is completely based on actual measurement results and is associated with the first event.

[0198] The first event is a predicted measurement event related to the second event.

[0199] In this application embodiment, the association between the first event and the second event is indicated by at least one of the following:

[0200] Same measurement markings;

[0201] Same measurement event report;

[0202] Same measurement object;

[0203] Same report identifier.

[0204] In the embodiments of this application, the indication of the first event includes at least one of AI / ML indication and prediction indication.

[0205] In this embodiment of the application, the relevant conditions for the second event include at least one of the following:

[0206] The entry conditions for this second event;

[0207] The exit conditions for this second event;

[0208] The triggering condition for this second event;

[0209] The reporting conditions for this second incident.

[0210] In this embodiment of the application, the event type of the first event is predefined, and / or the event type of the first event is indicated by adding an indication of the first event to the second event.

[0211] In this embodiment of the application, the method may further include: the network device receiving a report about the first event sent by the terminal device.

[0212] In this embodiment of the application, the network device receives a report about the first event sent by the terminal device at a first time, a second time, or a third time.

[0213] The first time is the time when the terminal device determines that the first condition is met, and / or the second time is the time predicted by the terminal device as indicated by the first condition that the terminal device determines is met, and / or the third time is the time when the terminal device determines that the first condition and the second condition are met.

[0214] In this embodiment of the application, the method may further include: the network device receiving a report from the terminal device regarding the exit of the first event.

[0215] As can be seen from the above embodiments, the terminal device reports measurement events based on AI / ML predictions to the network device when it determines that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events that are completely based on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0216] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0217] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0218] Third aspect of the embodiments

[0219] This application also provides another method for reporting measurement events. This method is applied to a terminal device, and some of its content is similar to the reporting method described in the first aspect embodiment. The same or corresponding content can be referred to the description in the first aspect embodiment. This method is applied to a terminal device, such as terminal device 102 in FIG1.

[0220] This application also provides another method for configuring measurement events. This method is applied to a network device, and some of its contents are similar to the configuration method described in the second aspect embodiment. The same or corresponding contents can be referred to the description in the second aspect embodiment. This method is applied to a network device, for example, network device 101 in FIG1.

[0221] Furthermore, the content of the third aspect's embodiments can also be applied to or incorporated into the embodiments of the first and second aspects.

[0222] Figure 17 is another schematic diagram of a method for reporting measurement events according to an embodiment of this application. As shown in Figure 17, the method includes:

[0223] 1701: The terminal device receives the first information indicated by the network device;

[0224] 1702: The terminal device reports a first event based at least on the first information, the first event being a measurement event predicted by the terminal device based on AI / ML.

[0225] In this embodiment of the application, the first information is used to at least indicate a first configuration, which is used to configure the first event indication and / or the related conditions of the first event.

[0226] In this embodiment of the application, the relevant conditions for the first event include at least one of the following:

[0227] The entry conditions for this first event;

[0228] The exit conditions for this first event;

[0229] The triggering condition for this first event;

[0230] The reporting conditions for this first incident.

[0231] In this embodiment of the application, the first information is also used to indicate at least one of the following:

[0232] This first event indicates;

[0233] The connection between the first event and the second event;

[0234] Does the network device allow the terminal device to use the terminal device's AI / ML model to predict the first event?

[0235] The way the terminal device reports the first event and / or the second event.

[0236] The second event is a measurement event that is completely based on actual measurement results and is associated with the first event, while the first event is a predicted measurement event related to the second event.

[0237] In this embodiment of the application, the method may further include:

[0238] The terminal device receives a second configuration indicated by the network device, which is a configuration of the conditions related to the second event.

[0239] In this embodiment of the application, the relevant conditions for the second event include at least one of the following:

[0240] The entry conditions for this second event;

[0241] The exit conditions for this second event;

[0242] The triggering condition for this second event;

[0243] The reporting conditions for this second incident.

[0244] In this embodiment, the second configuration is included in the first information, or the second configuration is included in the second information indicated by the network device. That is, the second configuration and the first configuration can both be included in the first information, or they can be indicated by different information.

[0245] In this embodiment of the application, the triggering condition of the first event includes at least one of the conditions of triggering time and triggering number.

[0246] In this application embodiment, the first configuration is indicated by at least one of the following methods:

[0247] The first configuration and the second configuration are exactly the same; for example, the parameter values ​​of the relevant configuration of at least one of the entry, exit, trigger, and reporting conditions of the first event indicated by the network device are the same as the parameter values ​​of the relevant configuration of at least one of the entry, exit, trigger, and reporting conditions of the corresponding second event.

[0248] The first configuration and the second configuration have the same parameters and the same value range for the parameters; for example, the relevant configuration of at least one of the entry, exit, triggering, and reporting conditions of the first event indicated by the network device has the same parameters and the same value range for the relevant configuration of at least one of the entry, exit, triggering, and reporting conditions of the corresponding second event.

[0249] The parameters in the first configuration are optional. When a parameter in the first configuration does not appear, the terminal device uses the value of the corresponding parameter in the second configuration as the parameter in the first configuration.

[0250] The first configuration contains parameters that are the same as or related to those in the second configuration. The parameter values ​​in the first configuration are relative or incremental values ​​to the same or related parameters in the second configuration. These values ​​are used to set differences in at least one of the same or related parameters relative to the second configuration, i.e., to set conditions for at least one of the event entry, triggering, exiting, or reporting that are stricter or more lenient than those in the second configuration. For example, if the second event is an A3 event, and the second configuration is for the A3 event, indicating a3-Offset (e.g., a3-Offset = 3), and the first event related to the second event is a predicted A3 event, and the first configuration for this first event contains parameters related to a3-Offset in the second configuration (e.g., a3-Offset-AI = 0.2), then when the terminal device predicts the first event, the applied offset = a3-Offset + a3-Offset-AI = 3.2, or the applied offset = a3-Offset - a3-Offset-AI = 2.8.

[0251] The first configuration is included in the second configuration, that is, a specific parameter related to the first event is added to the second configuration. And / or, the terminal device uses the value of this specific parameter as the value of the relevant parameter in the first configuration; otherwise, the terminal device uses the parameter value in the second configuration as the value of the relevant parameter in the first configuration. Taking the a3-Offset of event A3 as an example, if the second configuration includes a specific parameter for the first event, such as a3-Offset-AI, where a3-Offset-AI is an absolute value, the terminal device applies a3-Offset-AI as the offset for predicting event A3; if a3-Offset-AI is a relative value, the terminal device applies a3-Offset+a3-Offset-AI or a3-Offset-a3-Offset-AI as the offset for predicting event A3. If the second configuration does not include a specific parameter for the first event, for example, there is no first event-specific parameter related to a3-Offset, the terminal device applies a3-Offset as the offset for predicting event A3.

[0252] In this embodiment of the application, for the case where the first configuration and the second configuration are exactly the same,

[0253] The first configuration and the second configuration are respectively indicated by the network device, and the parameters in the first configuration and the second configuration are the same, and the corresponding parameter values ​​of the associated parameters are also the same; or,

[0254] The terminal device uses the second configuration as the first configuration only if the second configuration is indicated by the network device.

[0255] Figure 18 is another schematic diagram of a method for reporting measurement events according to an embodiment of this application. As shown in Figure 18, the method includes:

[0256] 1801: A network device sends first information to a terminal device, the first information being used at least by the terminal device to report a first event, the first event being a measurement event predicted by the terminal device based on AI / ML.

[0257] In this embodiment of the application, the first information is used to at least indicate a first configuration, which is used to configure the first event indication and / or the related conditions of the first event.

[0258] In this embodiment of the application, the relevant conditions for the first event include at least one of the following:

[0259] The entry conditions for this first event;

[0260] The exit conditions for this first event;

[0261] The triggering condition for this first event;

[0262] The reporting conditions for this first incident.

[0263] In this embodiment of the application, the first information is also used to indicate at least one of the following:

[0264] This first event indicates;

[0265] The connection between the first event and the second event;

[0266] Does the network device allow the terminal device to use the terminal device's AI / ML model to predict the first event?

[0267] The way the terminal device reports the first event and / or the second event.

[0268] The second event is a measurement event that is completely based on actual measurement results and is associated with the first event.

[0269] The first event is a predicted measurement event related to the second event.

[0270] In this embodiment of the application, the method may further include:

[0271] The terminal device receives a second configuration indicated by the network device, which is a configuration of the conditions related to the second event.

[0272] The relevant conditions for this second event include at least one of the following:

[0273] The entry conditions for this second event;

[0274] The exit conditions for this second event;

[0275] The triggering condition for this second event;

[0276] The reporting conditions for this second incident.

[0277] In this application embodiment, the second configuration is included in the first information, or the second configuration is included in the second information indicated by the network device.

[0278] In this embodiment of the application, the triggering condition of the first event includes at least one of the conditions of triggering time and triggering number.

[0279] In this application embodiment, the first configuration is indicated by at least one of the following methods:

[0280] The first configuration and the second configuration are exactly the same.

[0281] The first configuration and the second configuration have the same parameters and the same range of values ​​for these parameters;

[0282] The parameters in the first configuration are optional. When a parameter in the first configuration does not appear, the terminal device uses the value of the corresponding parameter in the second configuration as the parameter in the first configuration.

[0283] The first configuration is configured with the same or related parameters as the second configuration. The parameter values ​​in the first configuration are relative or incremental values ​​relative to the values ​​of the same or related parameters in the second configuration, and are used to set the value difference of at least one of the same or related parameters in the second configuration.

[0284] Include the first configuration in the second configuration.

[0285] In this embodiment of the application, for the case where the first configuration and the second configuration are exactly the same,

[0286] The network device indicates both the first configuration and the second configuration, where the parameters in the first configuration and the second configuration are the same, and the corresponding parameter values ​​of the associated parameters are also the same; or,

[0287] The network device only indicates the second configuration, and the terminal device uses the second configuration as the first configuration.

[0288] In the embodiments of this application, the specific implementation of the above operations can be referred to the relevant descriptions in the embodiments of the first aspect and the second aspect, which will not be repeated here.

[0289] As can be seen from the above embodiments, the terminal device reports measurement events based on AI / ML predictions to the network device when it determines that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events that are completely based on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0290] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0291] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0292] Fourth aspect of the embodiment

[0293] This application provides a reporting device for measurement events, which is installed in a terminal device. Since the principle by which this device solves the problem is similar to the method in the first aspect embodiment, its specific implementation can refer to the implementation of the method described in the first aspect embodiment; the same or related parts will not be repeated.

[0294] Figure 19 is a schematic diagram of a measurement event reporting device according to an embodiment of this application. As shown in Figure 19, the measurement event reporting device 1900 includes:

[0295] The first receiving unit 1901 receives the first information indicated by the network device;

[0296] The first transmitting unit 1902, based on the first information, reports a first event to the network device if it determines that at least a first condition is met.

[0297] The first event is a measurement event predicted by the terminal device based on AI / ML.

[0298] In the embodiments of this application, the first information is used to at least indicate a first configuration, which is used to configure the indication of the first event and / or the related conditions of the first event.

[0299] In this embodiment of the application, the relevant conditions for the first event include at least one of the following:

[0300] The entry conditions for this first event;

[0301] The exit conditions for this first event;

[0302] The triggering condition for this first event;

[0303] The reporting conditions for this first incident.

[0304] In this embodiment of the application, the first condition includes at least one of the following:

[0305] The terminal device predicted the occurrence of this first event;

[0306] The terminal device predicted the occurrence of the first event, and the first event was predicted to occur for the first time.

[0307] The terminal device predicted the occurrence of the first event, which had not yet been reported.

[0308] The terminal device predicts that the first event will occur, and predicts that the triggering conditions and / or reporting conditions of the first event will be met.

[0309] In this embodiment of the application, the terminal device predicts the occurrence of the first event as follows:

[0310] The terminal device predicts that the entry conditions for the first event are met, and / or the terminal device predicts that the first event will be triggered within a certain time range.

[0311] In this embodiment of the application, the first information is also used to indicate at least one of the following:

[0312] The indication of the first event;

[0313] The configuration of the relevant conditions for the second event;

[0314] The connection between the first event and the second event;

[0315] Does the network device allow the terminal device to use the terminal device's AI / ML model to predict the first event?

[0316] The way the terminal device reports the first event and / or the second event.

[0317] In this embodiment of the application, reporting a first event to the network device when at least a first condition is met includes:

[0318] If the first and second conditions are determined to be met, the first event is reported to the network device.

[0319] The second condition is a relevant condition for the second event.

[0320] The second event is a measurement event that is entirely based on actual measurement results and is associated with the first event.

[0321] The first event is a predicted measurement event related to the second event.

[0322] In this application embodiment, the association between the first event and the second event is indicated by at least one of the following:

[0323] Same measurement markings;

[0324] Same measurement event report;

[0325] Same measurement object;

[0326] Same report identifier.

[0327] In the embodiments of this application, the indication of the first event includes at least one of AI / ML indication and prediction indication.

[0328] In this embodiment of the application, the relevant conditions for the second event include at least one of the following:

[0329] The entry conditions for this second event;

[0330] The exit conditions for this second event;

[0331] The triggering condition for this second event;

[0332] The reporting conditions for this second incident.

[0333] In this embodiment of the application, the event type of the first event is predefined, and / or the event type of the first event is indicated by adding an indication of the first event to the second event.

[0334] In this application embodiment, the second condition includes at least one of the following:

[0335] The terminal device detected that the entry condition for the second event was met;

[0336] The terminal device detected that the exit condition for the second event was met;

[0337] The terminal device detected that the triggering condition for the second event was met;

[0338] The terminal device detected that the reporting conditions for the second event were met.

[0339] In this embodiment of the application, reporting a first event to the network device when at least a first condition is met includes:

[0340] The first event is reported at the first moment, where the first moment is the time when the terminal device determines that the first condition is met, and / or,

[0341] The first event is reported at a second time, which is the time predicted by the terminal device as indicated by the first condition that the terminal device determines to be met.

[0342] In this embodiment of the application, reporting a first event to the network device when it is determined that the first condition and the second condition are met includes:

[0343] The first event is reported at a third time, which is the time when the terminal device determines that the first condition and the second condition are met.

[0344] In this embodiment of the application, the first sending unit also reports the first event exit to the network device when the third condition is met.

[0345] In this application embodiment, the third condition includes at least one of the following:

[0346] The terminal device reported this first event;

[0347] The terminal device is determined not to meet the first condition;

[0348] The terminal device predicts that the exit condition of the first event is met; the terminal device determines that the first condition is not met, and the terminal device detects that the second condition is met;

[0349] The terminal device determines that the first condition is no longer met, and the terminal device detects that the second condition has not yet been met.

[0350] The second condition includes at least one of the following: entry condition, exit condition, trigger condition, and reporting condition for a measurement event that is entirely based on actual measurement results and is associated with the first event.

[0351] As can be seen from the above embodiments, the terminal device reports measurement events based on AI / ML predictions to the network device when it determines that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events that are completely based on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0352] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0353] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0354] Fifth aspect of the embodiment

[0355] This application provides a configuration apparatus for measuring events, which is applied to a network device. Since the principle by which this apparatus solves the problem is similar to the method in the second aspect of the embodiment, its specific implementation can refer to the implementation of the method described in the second aspect of the embodiment; the same or related parts will not be repeated.

[0356] Figure 20 is a schematic diagram of a measurement event configuration apparatus according to an embodiment of this application. As shown in Figure 20, the measurement event configuration apparatus 2000 includes:

[0357] The second sending unit 2001 sends the first information to the terminal device.

[0358] This first information is used at least for the terminal device to report the first event.

[0359] The first event is a measurement event predicted by the terminal device based on AI / ML.

[0360] In the embodiments of this application, the first information is used to at least indicate a first configuration, which is used to configure the indication of the first event and / or the related conditions of the first event.

[0361] In this embodiment of the application, the relevant conditions for the first event include at least one of the following:

[0362] The entry conditions for this first event;

[0363] The exit conditions for this first event;

[0364] The triggering condition for this first event;

[0365] The reporting conditions for this first incident.

[0366] In this embodiment of the application, the first information is also used to indicate at least one of the following:

[0367] The indication of the first event;

[0368] The configuration of the relevant conditions for the second event;

[0369] The connection between the first event and the second event;

[0370] Does the network device allow the terminal device to use the terminal device's AI / ML model to predict the first event?

[0371] The way the terminal device reports the first event and / or the second event.

[0372] The second event is a measurement event that is completely based on actual measurement results and is associated with the first event.

[0373] The first event is a predicted measurement event related to the second event.

[0374] In this application embodiment, the association between the first event and the second event is indicated by at least one of the following:

[0375] Same measurement markings;

[0376] Same measurement event report;

[0377] Same measurement object;

[0378] Same report identifier.

[0379] In the embodiments of this application, the indication of the first event includes at least one of AI / ML indication and prediction indication.

[0380] In this embodiment of the application, the relevant conditions for the second event include at least one of the following:

[0381] The entry conditions for this second event;

[0382] The exit conditions for this second event;

[0383] The triggering condition for this second event;

[0384] The reporting conditions for this second incident.

[0385] In this embodiment of the application, the event type of the first event is predefined, and / or,

[0386] The event type of the first event is indicated by adding an indication of the first event to the second event.

[0387] In this embodiment of the application, as shown in FIG20, the device 2000 further includes:

[0388] The second receiving unit 2002 receives the report about the first event sent by the terminal device.

[0389] In this embodiment of the application, the second receiving unit receives a report about the first event sent by the terminal device at a first time, a second time, or a third time.

[0390] The first time is the time when the terminal device determines that the first condition is met, and / or the second time is the time predicted by the terminal device as indicated by the first condition that the terminal device determines is met, and / or the third time is the time when the terminal device determines that the first condition and the second condition are met.

[0391] In this embodiment of the application, the second receiving unit 2002 also receives a report from the terminal device regarding the exit of the first event.

[0392] As can be seen from the above embodiments, the terminal device reports measurement events based on AI / ML predictions to the network device when it determines that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events that are completely based on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0393] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0394] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0395] Implementation of the sixth aspect

[0396] This application provides a terminal device that includes a measurement event reporting device according to an embodiment of the fourth aspect.

[0397] Figure 21 is a schematic block diagram of the system configuration of a terminal device according to an embodiment of this application. As shown in Figure 21, the terminal device 2100 may include a processor 2110 and a memory 2120; the memory 2120 is coupled to the processor 2110. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0398] In one implementation, the function of the event reporting device can be integrated into the processor 2110.

[0399] The processor 2110 is configured to: receive first information indicated by the network device; and, based on the first information, report a first event to the network device, wherein the first event is a measurement event predicted by the terminal device based on AI / ML, if at least a first condition is met.

[0400] In another embodiment, the event reporting device can be configured separately from the processor 2110. For example, the event reporting device can be configured as a chip connected to the processor 2110, and the function of the event reporting device can be realized through the control of the processor 2110.

[0401] As shown in Figure 21, the terminal device 2100 may further include: a communication module 2130, an input unit 2140, a display 2150, and a power supply 2160. It is worth noting that the terminal device 2100 does not necessarily include all the components shown in Figure 21; furthermore, the terminal device 2100 may also include components not shown in Figure 21, which can be found in related technologies.

[0402] As shown in Figure 21, the processor 2110, sometimes also called a controller or operation control, may include a microprocessor or other processor device and / or logic device. The processor 2110 receives input and controls the operation of various components of the terminal device 2100.

[0403] The memory 2120 may be, for example, one or more of a cache, flash memory, hard drive, removable medium, volatile memory, non-volatile memory, or other suitable means. It can store various types of data, and also programs for executing related information. The processor 2110 can execute the program stored in the memory 2120 to perform information storage or processing, etc. The functions of other components are similar to those in existing systems and will not be described further here. The components of the terminal device 2100 can be implemented using dedicated hardware, firmware, software, or a combination thereof without departing from the scope of the invention.

[0404] As can be seen from the above embodiments, the terminal device reports measurement events based on AI / ML predictions to the network device when it determines that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events that are completely based on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0405] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0406] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0407] Seventh aspect of the embodiment

[0408] This application provides a network device that includes a configuration means for measurement events according to a fifth aspect embodiment.

[0409] Figure 22 is a schematic block diagram of the system configuration of a network device according to an embodiment of this application. As shown in Figure 22, the network device 2200 may include a processor 2210 and a memory 2220; the memory 2220 is coupled to the processor 2210. The memory 2220 can store various types of data; it also stores an information processing program 2230, and executes the program 2230 under the control of the processor 2210 to receive various types of information sent by terminal devices and to send various types of information to terminal devices.

[0410] In one implementation, the functionality of the event configuration device can be integrated into the processor 2210.

[0411] The processor 2210 can be configured such that the network device sends first information to the terminal device, the first information being used at least for the terminal device to report a first event, the first event being a measurement event predicted by the terminal device based on AI / ML.

[0412] In another embodiment, the measurement event configuration device can be configured separately from the processor 2210. For example, the measurement event configuration device can be configured as a chip connected to the processor 2210, and the function of the measurement event configuration device can be implemented through the control of the processor 2210.

[0413] In addition, as shown in Figure 22, network device 2200 may also include: transceiver 2240 and antenna 2250, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 2200 does not necessarily have to include all the components shown in Figure 22; in addition, network device 2200 may also include components not shown in Figure 22, which can be referred to in the prior art.

[0414] As can be seen from the above embodiments, the terminal device reports measurement events based on AI / ML predictions to the network device when it determines that at least the first condition is met, according to the first information indicated by the network device. Compared with the existing reports of measurement events that are completely based on actual measurement results, i.e. actual measurement events, the embodiments of this application provide a more flexible solution for reporting predicted measurement events. This allows the terminal device to determine the timing of reporting predicted measurement events based on the performance of the AI / ML prediction model, and to determine the necessary predicted measurement events to report based on air interface signaling quantity limits and air interface channel quality, etc.

[0415] Furthermore, by associating predicted measurement events with corresponding actual measurement events, network devices can jointly determine whether to prepare for or execute handover or other mobility management-related processes based on the mutual corroboration between the predicted and actual measurement events. This avoids the problems of frequent handovers and undesirable handover targets that may occur when relying solely on predicted measurement events in situations where the AI / ML prediction model is not accurate enough or the channel environment fluctuates drastically. It balances the accuracy of AI / ML-based predicted measurement events with the system-level gains of AI / ML-based predicted measurement events.

[0416] In addition, by reporting predicted measurement events that are triggered earlier than the actual measurement events, network devices are given more time. Network devices can prepare for handover in advance based on the predicted measurement event reports, reducing the possibility of handover failure. Furthermore, terminal devices also report predicted measurement events to the network devices to exit, enabling the network devices to avoid unnecessary handovers and further improving system-level performance.

[0417] Eighth aspect of the embodiment

[0418] This application provides a communication system, including a terminal device according to an embodiment of the sixth aspect and / or a network device according to an embodiment of the seventh aspect. Specific details can be found in the descriptions of the embodiments of the sixth and seventh aspects.

[0419] For example, the structure of the communication system can be seen in FIG1. ​​As shown in FIG1, the communication system 100 includes a network device 101 and a terminal device 102. The terminal device 102 may be the same as the terminal device described in the sixth aspect embodiment, and / or the network device 101 may be the same as the network device described in the seventh aspect embodiment. Repeated content will not be described again.

[0420] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. Logic components include, for example, field-programmable logic devices (FPGAs), microprocessors, and processors used in computers. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, and flash memory.

[0421] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or one or more combinations of functional block diagrams shown in FIG19 can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in FIG3, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

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

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

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

[0425] According to the various embodiments disclosed in this application, the following notes are also disclosed:

[0426] 1. A method for reporting measurement events, the method being applied to a terminal device, the method comprising:

[0427] The terminal device receives the first information indicated by the network device;

[0428] The terminal device shall, at least based on the first information, report the first event.

[0429] The first event is a measurement event predicted by the terminal device based on AI / ML.

[0430] 2. According to the method described in Appendix 1, wherein,

[0431] The first information is used to at least indicate a first configuration, which is used to configure the first event indication and / or the related conditions of the first event.

[0432] The conditions for the first event include at least one of the following:

[0433] The entry conditions for the first event;

[0434] The exit condition for the first event;

[0435] The triggering condition for the first event;

[0436] The reporting conditions for the first event

[0437] And / or,

[0438] The first information is also used to indicate at least one of the following:

[0439] The first event indication;

[0440] The relationship between the first event and the second event;

[0441] Does the network device allow the terminal device to use the terminal device-side AI / ML model to predict the first event?

[0442] The manner in which the terminal device reports the first event and / or the second event.

[0443] The second event is a measurement event that is entirely based on actual measurement results and is associated with the first event, while the first event is a predicted measurement event related to the second event.

[0444] 3. The method according to Appendix 2, wherein the method further comprises:

[0445] The terminal device receives a second configuration indicated by the network device, wherein the second configuration is a configuration of conditions related to the second event.

[0446] The relevant conditions for the second event include at least one of the following:

[0447] The entry condition for the second event;

[0448] The exit condition for the second event;

[0449] The triggering condition for the second event;

[0450] The reporting conditions for the second event,

[0451] And / or,

[0452] The second configuration is included in the first information, or the second configuration is included in the second information indicated by the network device.

[0453] And / or,

[0454] The triggering conditions for the first event include at least one of the conditions of triggering time and triggering number.

[0455] 4. The method according to Appendix 3, wherein the first configuration is indicated by at least one of the following:

[0456] The first configuration and the second configuration are exactly the same.

[0457] The first configuration and the second configuration have the same parameters and the same range of values ​​for the parameters;

[0458] The parameters in the first configuration are optional. When a parameter in the first configuration does not appear, the terminal device will use the value of the corresponding parameter in the second configuration as the parameter in the first configuration.

[0459] The first configuration is configured with the same or related parameters as the second configuration. The parameter values ​​in the first configuration are relative or incremental values ​​relative to the same or related parameter values ​​in the second configuration, and are used to set the value difference of at least one of the same or related parameters in the second configuration.

[0460] Include the first configuration in the second configuration.

[0461] 5. The method according to Appendix 4, wherein, for the case where the first configuration and the second configuration are exactly the same,

[0462] The first configuration and the second configuration are respectively indicated by the network device, and the parameters in the first configuration and the second configuration are the same, and the corresponding parameter values ​​of the associated parameters are also the same; or,

[0463] The terminal device uses the second configuration as the first configuration only if the second configuration is indicated by the network device.

[0464] 6. A method for configuring measurement events, the method being applied to a network device, the method comprising:

[0465] The network device sends the first information to the terminal device.

[0466] The first information is used at least in the terminal device to report the first event.

[0467] The first event is a measurement event predicted by the terminal device based on AI / ML.

[0468] 7. According to the method described in Appendix 6, wherein,

[0469] The first information is used to at least indicate a first configuration, which is used to configure the first event indication and / or the related conditions of the first event.

[0470] The conditions for the first event include at least one of the following:

[0471] The entry conditions for the first event;

[0472] The exit condition for the first event;

[0473] The triggering condition for the first event;

[0474] The reporting conditions for the first event

[0475] And / or,

[0476] The first information is also used to indicate at least one of the following:

[0477] The first event indication;

[0478] The relationship between the first event and the second event;

[0479] Does the network device allow the terminal device to use the terminal device-side AI / ML model to predict the first event?

[0480] The manner in which the terminal device reports the first event and / or the second event.

[0481] The second event is a measurement event that is completely based on actual measurement results and is associated with the first event.

[0482] The first event is a predicted measurement event related to the second event.

[0483] 8. The method according to Appendix 7, wherein the method further comprises:

[0484] The terminal device receives a second configuration indicated by the network device, wherein the second configuration is a configuration of conditions related to the second event.

[0485] The relevant conditions for the second event include at least one of the following:

[0486] The entry condition for the second event;

[0487] The exit condition for the second event;

[0488] The triggering condition for the second event;

[0489] The reporting conditions for the second event,

[0490] And / or,

[0491] The second configuration is included in the first information, or the second configuration is included in the second information indicated by the network device.

[0492] And / or,

[0493] The triggering conditions for the first event include at least one of the conditions of triggering time and triggering number.

[0494] 9. The method according to Appendix 8, wherein the first configuration is indicated by at least one of the following:

[0495] The first configuration and the second configuration are exactly the same.

[0496] The first configuration and the second configuration have the same parameters and the same range of values ​​for the parameters;

[0497] The parameters in the first configuration are optional. When a parameter in the first configuration does not appear, the terminal device will use the value of the corresponding parameter in the second configuration as the parameter in the first configuration.

[0498] The first configuration is configured with the same or related parameters as the second configuration. The parameter values ​​in the first configuration are relative or incremental values ​​relative to the same or related parameter values ​​in the second configuration, and are used to set the value difference of at least one of the same or related parameters in the second configuration.

[0499] Include the first configuration in the second configuration.

[0500] 10. The method according to Appendix 9, wherein, for the case where the first configuration and the second configuration are exactly the same,

[0501] The network device indicates both the first configuration and the second configuration, where the parameters in the first configuration and the second configuration are the same, and the corresponding parameter values ​​of the associated parameters are also the same; or,

[0502] The network device only indicates the second configuration, and the terminal device uses the second configuration as the first configuration.

Claims

A device for reporting measurement events, the device being applied to a terminal device, the device comprising: The first receiving unit receives the first information indicated by the network device; The first transmitting unit, based on the first information, reports the first event to the network device if it determines that at least a first condition is met. The first event is a measurement event predicted by the terminal device based on AI / ML. The apparatus according to claim 1, wherein, The first information is used at least to indicate a first configuration, which is used to configure the indication of the first event and / or the related conditions of the first event. The conditions for the first event include at least one of the following: The entry conditions for the first event; The exit condition for the first event; The triggering condition for the first event; The reporting conditions for the first event. The apparatus according to claim 1, wherein, The first condition includes at least one of the following: The terminal device predicts that the first event has occurred; The terminal device predicts that the first event will occur, and the first event is predicted to occur for the first time. The terminal device predicts that the first event has occurred, and the first event has not yet been reported. The terminal device predicts that the first event has occurred, and predicts that the triggering conditions and / or reporting conditions of the first event are met. The apparatus according to claim 3, wherein, The terminal device predicts the occurrence of the first event including: The terminal device predicts that the entry conditions of the first event are met, and / or the terminal device predicts that the first event will be triggered within a certain time range. The apparatus according to claim 1, wherein, The first information is also used to indicate at least one of the following: Indication of the first event; The configuration of the relevant conditions for the second event; The relationship between the first event and the second event; Does the network device allow the terminal device to use the terminal device-side AI / ML model to predict the first event? The manner in which the terminal device reports the first event and / or the second event. The apparatus according to claim 5, wherein, If at least a first condition is determined to be met, a first event is reported to the network device, including: If the first and second conditions are determined to be met, a first event is reported to the network device. The second condition is a relevant condition for the second event. The second event is a measurement event that is entirely based on actual measurement results and is associated with the first event. The first event is a predicted measurement event related to the second event. The apparatus according to claim 5, wherein, The association between the first event and the second event is indicated by at least one of the following: Same measurement markings; Same measurement event report; Same measurement object; Same report identifier, And / or, The indication of the first event includes at least one of AI / ML indications and prediction indications. And / or, The relevant conditions for the second event include at least one of the following: The entry condition for the second event; The exit condition for the second event; The triggering condition for the second event; The reporting conditions for the second event, And / or, The event type of the first event is predefined, and / or the event type of the first event is indicated by adding an indication of the first event to the second event. The apparatus according to claim 6, wherein, The second condition includes at least one of the following: The terminal device detects that the entry condition is met by the second event; The terminal device detects that the exit condition for the second event is met; The terminal device detects that the triggering condition of the second event is met; The terminal device detected that the reporting conditions for the second event were met. The apparatus according to claim 1, wherein, If at least a first condition is determined to be met, a first event is reported to the network device, including: The first event is reported at the first moment, where the first moment is the time when the terminal device determines that the first condition is met, and / or, The first event is reported at a second time, which is the time predicted by the terminal device as indicated by the terminal device when the first condition is determined to be met. The apparatus of claim 6, upon determining that the first condition and the second condition are met, reports a first event to the network device, comprising: The first event is reported at a third time, which is the time when the terminal device determines that the first condition and the second condition are met. The apparatus according to claim 1, wherein, If the third condition is met, the first sending unit also reports the first event exit to the network device. The apparatus according to claim 11, wherein, The third condition includes at least one of the following: The terminal device reported the first event; The terminal device determines that the first condition is not met; The terminal device predicts that the exit conditions of the first event are met; The terminal device determines that the first condition is not met, and the terminal device detects that the second condition is met; The terminal device determines that the first condition is no longer met, and the terminal device detects that the second condition has not yet been met. The second condition includes at least one of the following: entry condition, exit condition, trigger condition, and reporting condition of a measurement event that is entirely based on actual measurement results and is associated with the first event. A configuration apparatus for measuring events, the apparatus being applied to a network device, the apparatus comprising: The second sending unit sends the first information to the terminal device. The first information is used at least in the terminal device to report the first event. The first event is a measurement event predicted by the terminal device based on AI / ML. The apparatus according to claim 13, wherein, The first information is used at least to indicate a first configuration, which is used to configure the indication of the first event and / or the related conditions of the first event. The conditions for the first event include at least one of the following: The entry conditions for the first event; The exit condition for the first event; The triggering condition for the first event; The reporting conditions for the first event. The apparatus according to claim 13, wherein, The first information is also used to indicate at least one of the following: Indication of the first event; The configuration of the relevant conditions for the second event; The relationship between the first event and the second event; Does the network device allow the terminal device to use the terminal device-side AI / ML model to predict the first event? The manner in which the terminal device reports the first event and / or the second event. The second event is a measurement event that is completely based on actual measurement results and is associated with the first event. The first event is a predicted measurement event related to the second event. The apparatus according to claim 15, wherein, The association between the first event and the second event is indicated by at least one of the following: Same measurement markings; Same measurement event report; Same measurement object; Same report identifier, And / or, The indication of the first event includes at least one of AI / ML indications and prediction indications. And / or, The relevant conditions for the second event include at least one of the following: The entry condition for the second event; The exit condition for the second event; The triggering condition for the second event; The reporting conditions for the second event. The apparatus according to claim 15, wherein, The event type of the first event is predefined, and / or, The event type of the first event is indicated by adding an indication of the first event to the second event. The apparatus according to claim 13, wherein, The device further includes: The second receiving unit receives a report about the first event sent by the terminal device. The apparatus according to claim 18, wherein, The second receiving unit receives a report about the first event sent by the terminal device at a first time, a second time, or a third time. The first time is the time when the terminal device determines that the first condition is met, and / or the second time is the time predicted by the terminal device as indicated by the first condition that the terminal device determines is met, and / or the third time is the time when the terminal device determines that the first condition and the second condition are met. The apparatus according to claim 18, wherein, The second receiving unit also receives a report from the terminal device regarding the exit of the first event.