Event management method and device, equipment, storage medium and program product

Abstract

The invention discloses an event management method and device, equipment, a storage medium and a program product, and belongs to the technical field of Internet of Things. The method comprises: sending an event acquisition request to a second device (301); the event acquisition request comprises a first target event priority; and receiving at least one target event which is sent by the second device and is matched with the first target event in priority (302). According to the scheme, the event acquisition flexibility in the Internet of Things system can be improved.

Description

Event management method, device, equipment, storage medium and program product Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to an event management method, apparatus, device, storage medium, and program product. Background Art

[0002] With the continuous development of Internet of Things (IoT) technology, more and more IoT devices have brought great convenience to users' production and life in many fields such as smart homes and industrial production.

[0003] In an IoT system, an IoT device may need to obtain events from another IoT device. For example, a client device may need to obtain events related to a cluster on the client device in order to trigger operations such as reminders.

[0004] Summary of the Invention

[0005] The present invention provides an event management method, apparatus, device, storage medium, and program product. The technical solution is as follows:

[0006] In one aspect, an embodiment of the present application provides an event management method, which is performed by a first device and includes:

[0007] Sending an event acquisition request to the second device; the event acquisition request includes the first target event priority;

[0008] Receive at least one target event sent by the second device and matching the priority of the first target event.

[0009] In one aspect, an embodiment of the present application provides an event management method, the method being performed by a second device, the method comprising:

[0010] Receiving an event acquisition request sent by a first device; the event acquisition request includes a first target event priority;

[0011] At least one target event matching the first target event priority is sent to the first device.

[0012] On the other hand, an embodiment of the present application provides an event management method, which is performed by a first device and includes:

[0013] An event priority setting request is sent to a second device; the event priority setting request includes a second target event priority; the event priority setting request is used to instruct the second device to record at least one target event that matches the second target event priority.

[0014] On the other hand, an embodiment of the present application provides an event management method, which is performed by a second device and includes:

[0015] receiving an event priority setting request sent by a first device; wherein the event priority setting request includes a second target event priority;

[0016] At least one target event matching the second target event priority is recorded according to the event priority setting information.

[0017] On the other hand, an embodiment of the present application provides an event management device, the device comprising:

[0018] A sending module, configured to send an event acquisition request to the second device; the event acquisition request includes a first target event priority;

[0019] The receiving module is configured to receive at least one target event sent by the second device and matching the priority of the first target event.

[0020] On the other hand, an embodiment of the present application provides an event management device, the device comprising:

[0021] A receiving module, configured to receive an event acquisition request sent by a first device; the event acquisition request includes a first target event priority;

[0022] A sending module is configured to send at least one target event that matches the priority of the first target event to the first device.

[0023] On the other hand, an embodiment of the present application provides an event management device, the device comprising:

[0024] A sending module is used to send an event priority setting request to a second device; the event priority setting request includes a second target event priority; the event priority setting request is used to instruct the second device to record at least one target event that matches the second target event priority.

[0025] On the other hand, an embodiment of the present application provides an event management device, the device comprising:

[0026] A receiving module, configured to receive an event priority setting request sent by a first device; the event priority setting request includes a second target event priority;

[0027] A recording module is used to record at least one target event that matches the priority of the second target event according to the event priority setting information.

[0028] On the other hand, an embodiment of the present application provides a computer device, which includes a processor, a memory, and a transceiver. The memory stores a computer program, and the computer program is used to be executed by the processor to implement the above-mentioned event management method.

[0029] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement the above-mentioned event management method.

[0030] On the other hand, the present application also provides a chip, which is used to run in a computer device so that the computer device executes the above-mentioned event management method.

[0031] In another aspect, the present application provides a computer program product, the computer program product including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the above-mentioned event management method.

[0032] On the other hand, the present application provides a computer program, which is executed by a processor of a computer device to implement the above event management method.

[0033] The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

[0034] When a first device requests to obtain events from a second device, it can indicate the priority of the events to be obtained in the request. Accordingly, the second device can send events that match the priority to the first device, thereby filtering the obtained events by priority during the event acquisition process, thereby improving the flexibility of event acquisition in the Internet of Things system. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0036] FIG1 is a schematic diagram of a network architecture of the Internet of Things provided by one embodiment of the present application;

[0037] FIG2 is a schematic diagram of a Matter device data model involved in the embodiment shown in FIG1 ;

[0038] FIG3 is a flow chart of an event management method provided by an embodiment of the present application;

[0039] FIG4 is a flowchart of an event management method provided by an embodiment of the present application;

[0040] FIG5 is a framework diagram of event management provided by an exemplary embodiment of the present application;

[0041] FIG6 is a flowchart of an event management method provided by an embodiment of the present application;

[0042] FIG7 is a flow chart of event acquisition involved in the embodiment shown in FIG6 ;

[0043] FIG8 is a flowchart of an event management method provided by an embodiment of the present application;

[0044] FIG9 is a flowchart of an event management method provided by an embodiment of the present application;

[0045] FIG10 is a framework diagram of event management provided by an exemplary embodiment of the present application;

[0046] FIG11 is a flowchart of an event management method provided by an embodiment of the present application;

[0047] FIG12 is a flow chart of event record settings involved in the embodiment shown in FIG11;

[0048] FIG13 is a block diagram of an event management device provided by one embodiment of the present application;

[0049] FIG14 is a block diagram of an event management device provided by one embodiment of the present application;

[0050] FIG15 is a block diagram of an event management device provided by one embodiment of the present application;

[0051] FIG16 is a block diagram of an event management device provided by one embodiment of the present application;

[0052] FIG17 is a schematic diagram of the structure of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0054] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0055] Please refer to Figure 1, which shows a schematic diagram of the network architecture of the Internet of Things provided by one embodiment of the present application. The network architecture of the Internet of Things may include: an Internet of Things device 110 and an Internet of Things device 120;

[0056] The IoT device 110 and the IoT device 120 may be devices in the IoT for providing server functions and / or client functions corresponding to the IoT protocol.

[0057] For example, the IoT device 110 or the IoT device 120 may be a smart home device, such as a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, a smart speaker, a smart switch, and the like.

[0058] Alternatively, the IoT device 110 or the IoT device 120 may be industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, and the like.

[0059] Alternatively, the IoT device 110 or the IoT device 120 may be a commercial service device, such as an unmanned vending machine, etc.

[0060] Alternatively, the IoT device 110 or the IoT device 120 may be an intelligent monitoring device, such as a monitoring camera, an infrared sensor, a sound sensor, a temperature sensor, and the like.

[0061] In one possible implementation, IoT device 110 or IoT device 120 may also be a user-side terminal device. For example, IoT device 110 or IoT device 120 may be a smart controller, a smart remote control, a smartphone, a tablet computer, a smart watch, a smart TV, a gateway, etc. Alternatively, IoT device 110 or IoT device 120 may be a personal computer, such as a desktop computer, a laptop computer, a personal workstation, etc.

[0062] In an embodiment of the present application, the above-mentioned IoT device 110 and IoT device 120 can be electronic devices that meet the same or different IoT protocols. For example, they can be electronic devices that meet the Matter protocol (or the Connected Home over IP Working Group (CHIP) project) under the Connectivity Standards Alliance (CSA) (or Zigbee Alliance).

[0063] Matter is an IP-based IoT connectivity standard that addresses the compatibility, security, and connectivity issues currently facing the smart home market. Please refer to Figure 2, which shows a schematic diagram of the Matter device data model involved in an embodiment of this application.

[0064] As shown in Figure 2, the Matter device data model has the following characteristics:

[0065] 1) Matter device nodes contain one or more Endpoints, which are represented by Endpoint Numbers.

[0066] 2) Each endpoint contains multiple clusters, represented by cluster IDs. The same cluster can be divided into two roles: server and client. Data or commands are sent from the client to the server.

[0067] 3) Each Cluster contains multiple Attributes, Events, and Commands, which are represented by Attribute ID, Event ID, and Command ID respectively. Attribute is used to represent data, Event is used to represent events, and Command is used to represent operations.

[0068] Matter Event Introduction:

[0069] An event represents a record of something that happened in the past and can be considered a log entry. The event stream provides a chronological view of the state evolution on the device node.

[0070] Events have three priorities:

[0071] DEBUG (debugging) is used for debugging by engineers;

[0072] INFO (information) drives the user's understanding of the device, such as software update events and key press events;

[0073] CRITICAL: Events that affect the user's physical safety, such as switch equipment events and security alarm events.

[0074] Events are defined in the Cluster and represented by Event IDs.

[0075] The event record can be shown in Table 1 below:

[0076] Table 1

[0077]

[0078] Events can be read through a Read Request or subscribed to through a Subscribe Request.

[0079] The Read Request message is shown in Table 2 below, where Table 2 lists data related to the Event operation.

[0080] Table 2

[0081] IDFieldTypeConstraintConformanceDescription0x01EventRequestslist[EventPathIB]List0 event request 0x02EventFilterslist[EventFilterIB]List0 event filter

[0082] The Subscribe Request message is shown in Table 3 below. Table 3 lists data related to the Event operation.

[0083] Table 3

[0084]

[0085] EventPathIB: The composition of the event path information block is shown in Table 4 below.

[0086] Table 4

[0087] IDFieldTypeConstraintConformanceDescription0x00Node idUint162bytesONode id0x01Endpoint noUint162bytesOEndpoint value 0x02Cluster idUint162bytesOCluster ID value

[0088] 0x03Event idUint162bytesOEvent ID value 0x04IsUrgentBoolean O Whether it is an urgent event

[0089] "IsUrgent" is used to urgently report the Event ID specified in EventPathIB. When the device receives an event read or subscription request from the control end for an Event ID with "IsUrgent", it will urgently report the corresponding Event ID.

[0090] EventFilterIB: Event filtering information is shown in Table 5 below:

[0091] Table 5

[0092]

[0093] In one solution, there are Global Elements (global attribute information of the Cluster) in the Cluster. The global attribute information is shown in Table 6 below:

[0094] Table 6

[0095] Attribute IDNameType0xFFFAEventListlist[event-id]

[0096] In the above scheme, the attributes in Table 6 are read-only.

[0097] In actual user operations, the above solution does not consider the user's ability to filter events of different priorities, nor does it consider whether users can set the priority of device events so that the device only stores events of a certain priority in its event queue according to the user's intention and then reports them. This results in poor flexibility in event reporting.

[0098] Please refer to FIG3 , which shows a flowchart of an event management method provided by an embodiment of the present application. The method may be performed by a first device. For example, the first device may be one of the IoT devices 110 or 120 in the network architecture shown in FIG1 . The method may include the following steps:

[0099] Step 301: Send an event acquisition request to a second device; the event acquisition request includes a first target event priority.

[0100] The first target event priority may be used to indicate the priority of an event that the first device needs to obtain.

[0101] The second device may be another IoT device other than the first device in the IoT device 110 or the IoT device 120 of the system shown in FIG. 1 .

[0102] Step 302: Receive at least one target event sent by a second device that matches the priority of the first target event.

[0103] In an embodiment of the present application, after receiving the above-mentioned event acquisition request, the second device can send an event (ie, the above-mentioned target event) that matches the priority of the first target event in the event acquisition request to the first device.

[0104] To sum up, in the scheme shown in the embodiment of the present application, when the first device requests to obtain events in the second device, it can indicate the priority of the events to be obtained in the request. Accordingly, the second device can send events with matching priorities to the first device, thereby realizing filtering of the obtained events by priority during the event acquisition process, thereby improving the flexibility of event acquisition in the Internet of Things system.

[0105] Please refer to FIG4 , which shows a flow chart of an event management method provided by an embodiment of the present application. The method may be performed by a second device. For example, the second device may be one of the IoT devices 110 or 120 in the network architecture shown in FIG1 . The method may include the following steps:

[0106] Step 401: Receive an event acquisition request sent by a first device; the event acquisition request includes a first target event priority.

[0107] The first device may be another IoT device other than the second device in the IoT device 110 or the IoT device 120 of the system shown in FIG. 1 .

[0108] Step 402: Send at least one target event that matches the priority of the first target event to the first device.

[0109] To sum up, in the scheme shown in the embodiment of the present application, when the first device requests to obtain events in the second device, it can indicate the priority of the events to be obtained in the request. Accordingly, the second device can send events with matching priorities to the first device, thereby realizing filtering of the obtained events by priority during the event acquisition process, thereby improving the flexibility of event acquisition in the Internet of Things system.

[0110] Based on the solutions shown in Figures 3 and 4 above, please refer to Figure 5, which shows a framework diagram of event management provided by an exemplary embodiment of the present application. As shown in Figure 5, when the first device 51 needs to obtain certain cluster-related events from the second device 52, it can send an event acquisition request indicating the priority of the event to the second device 52.

[0111] After receiving the event acquisition request, the second device 52 searches for events with matching priorities in the relevant cluster according to the priority indicated in the event acquisition request, and sends the found events to the first device 51 .

[0112] Based on the solutions shown in FIG. 3 to FIG. 5 above, in one possible case, the priority of the first target event may be set by a user corresponding to the first device.

[0113] Please refer to Figure 6, which shows a flowchart of an event management method provided by an embodiment of the present application. The method can be interactively executed by a first device and a second device; for example, the first device and the second device can be IoT device 110 and IoT device 120 in the network architecture shown in Figure 1. The method can include the following steps.

[0114] Step 601: The first device receives a priority setting instruction.

[0115] Before sending the event acquisition request, the first device may first display a priority setting interface, and the user may set the priority of the event to be acquired in the priority setting interface.

[0116] Optionally, when the user sets the priority of the event to be obtained through the priority setting interface, the user can set the above priority corresponding to the specified target. For example, the user can select the target cluster, target endpoint, target node, etc. for the priority to take effect in the priority setting interface. In other words, the priority set by the user in the priority setting interface applies to the above target cluster, target endpoint and / or target node selected by the user. For example, when the user selects cluster ID 1, endpoint ID 2 and node ID 3 for the priority to take effect in the priority setting interface, where cluster ID 1 corresponds to cluster a, endpoint ID 2 corresponds to endpoint b, and node ID 3 corresponds to node c; subsequently, the priority will take effect on cluster a in endpoint b on node c.

[0117] Alternatively, the priority setting interface may be an interface fixedly corresponding to the target cluster in the target endpoint on the target node. After the user sets the priority in the priority setting interface, the set priority corresponds to the priority of the target cluster in the target endpoint on the target node.

[0118] Alternatively, users can set global priorities, that is, user-set priorities that are not restricted to a specific cluster, endpoint, or node.

[0119] Step 602: The first device sets the priority of the first target event according to the priority setting instruction.

[0120] In a possible implementation of the embodiment of the present application, the first device may set the first target event priority in the event acquisition request when generating the event acquisition request according to the priority setting instruction.

[0121] In another possible implementation scheme of the embodiment of the present application, the first device may also set the first target event priority according to the priority setting instruction and store it in a designated location before generating an event acquisition request, and add the pre-stored first target event priority to the event acquisition request when generating the event acquisition request.

[0122] Step 603: The first device sends an event acquisition request to the second device, and the second device receives the event acquisition request; the event acquisition request includes the first target event priority.

[0123] In an embodiment of the present application, when the first device needs to obtain an event in the second device, it can send an event acquisition request to the second device.

[0124] Optionally, in addition to the first target event priority, the above-mentioned event acquisition request may also include relevant information for indicating the event to be acquired, such as the node identification information of the second device, the endpoint identification information of the target endpoint in the second node, the cluster identification information of the target cluster in the second node, etc.

[0125] In a possible implementation, the event acquisition request includes an event subscription request or an event reading request.

[0126] For example, the event acquisition request sent by the first device to the second device may be a read request for reading an event.

[0127] Alternatively, the event acquisition request sent by the first device to the second device may be a subscription request Subscribe Request for subscribing to an event.

[0128] In a possible implementation, the first target event priority may be set in an event filtering information block of an event acquisition request.

[0129] In the solution shown in the embodiment of the present application, a connection may be established between the first device and the second device based on the Matter protocol;

[0130] The priority of the event recorded by the second device includes at least two of a debug priority, an information priority, and a CRITICAL priority;

[0131] The event recorded by the second device is an event recorded by the target cluster in the corresponding second device.

[0132] In the embodiment of the present application, the first target event priority may be set in the EventFilterIB (Information Blocks) of the Read Request or Subscribe Request.

[0133] For example, in the embodiment of the present application, the flag of the permission filter can be added to EventFilterIB, as shown in Table 7 below:

[0134] Table 7

[0135]

[0136] As shown in Table 7, in EventFilterIB, the 1-byte Priority attribute is used to indicate the priority level that the currently requested / subscribed event must meet.

[0137] Step 604: The second device sends at least one target event that matches the priority of the first target event to the first device; the first device receives the at least one target event.

[0138] In an embodiment of the present application, after the second device receives the event acquisition request sent by the first device, it determines the cluster to which the event that the first device wants to obtain belongs based on the endpoint identification information and cluster identification information in the event acquisition request, and then searches for events that match the priority of the first target event in the events corresponding to the cluster, filters out events that do not match the priority of the first target event, and sends the events obtained from the query (that is, the at least one target event mentioned above) to the first device.

[0139] In a possible implementation, the at least one target event includes an event whose priority is higher than or equal to the priority of the first target event.

[0140] In an embodiment of the present application, the first target event priority carried in the event acquisition request may indicate a single priority. When the second device returns an event to the first device, it returns events in the corresponding cluster that are not lower than the priority to the first device.

[0141] For example, event priorities are divided into three categories: DEBUG, INFO, and CRITICAL, where the order of priority from high to low is CRITICAL > INFO > DEBUG.

[0142] If the first device sets the Priority in EventFilterIB to DEBUG when issuing a Read&Subscribe request, the second device returns event messages with three priority levels: DEBUG, INFO, and CRITICAL; if the first device sets the Priority in EventFilterIB to INFO when issuing a Read&Subscribe request, the second device returns event messages with two priority levels: INFO and CRITICAL; if the first device sets the Priority in EventFilterIB to CRITICAL when issuing a Read&Subscribe request, the second device returns an event message with one priority level: CRITICAL.

[0143] In a possible implementation, the at least one target event includes an event having a priority equal to a priority of the first target event.

[0144] In an embodiment of the present application, the first target event priority carried in the event acquisition request can indicate a single or multiple priorities. When the second device returns an event to the first device, it returns the event corresponding to any priority of the single or multiple priorities in the corresponding cluster to the first device.

[0145] For example, if the first device sets the Priority in EventFilterIB to DEBUG when issuing a Read&Subscribe request, the second device returns an event message with a DEBUG priority; if the first device sets the Priority in EventFilterIB to INFO when issuing a Read&Subscribe request, the second device returns an event message with an INFO priority; if the first device sets the Priority in EventFilterIB to CRITICAL when issuing a Read&Subscribe request, the second device returns an event message with a CRITICAL priority.

[0146] For example, please refer to Figure 7, which shows a flow chart of an event acquisition involved in an embodiment of the present application. Assuming that the first device is a control terminal in the Internet of Things and the second device is a device terminal in the Internet of Things, as shown in Figure 7, the process may include the following steps:

[0147] S71, the user sets the Priority field of EventFileIB in the Read Request or Subscribe Request message in the control terminal to filter the priority events that the user is concerned about.

[0148] For example, the control end may be a user terminal such as a smartphone. The user views the information of the device end in the APP (Application) of the smartphone and clicks the event priority setting option of the device end to set the priority of reading or subscribing to events in the device end.

[0149] S72: The user sends a request to the control end to read or subscribe to events in one or more clusters on the device end.

[0150] For example, a user can click the event read / subscribe option on the device side in the APP to issue a request to read or subscribe to events in one or more clusters on the device side.

[0151] S73, the control end sends an event read / subscribe request to the device end, and the event read / subscribe request carries information indicating the priority.

[0152] For example, the Priority in the EventFilterIB of the event read / subscribe request is set to the value corresponding to the priority set by the user.

[0153] S74: The device returns to the control end the events that match the priority indicated by the event read / subscribe request.

[0154] In an embodiment of the present application, after the device receives the event read / subscription request sent by the control end, it can filter out events that meet the priority set by the user in the corresponding cluster and return the filtered events to the control end.

[0155] S75: The control end displays the event returned by the device end to the user.

[0156] To sum up, in the scheme shown in the embodiment of the present application, when the first device requests to obtain events in the second device, it can indicate the priority of the events to be obtained in the request. Accordingly, the second device can send events with matching priorities to the first device, wherein the above-mentioned priority can be set by the user, thereby realizing the filtering of the obtained events according to the priority specified by the user during the event acquisition process, thereby improving the flexibility of event acquisition in the Internet of Things system.

[0157] Please refer to FIG8 , which shows a flowchart of an event management method provided by an embodiment of the present application. The method may be performed by a first device. For example, the first device may be one of the IoT devices 110 or 120 in the network architecture shown in FIG1 . The method may include the following steps:

[0158] Step 801: Send an event priority setting request to the second device; the event priority setting request includes a second target event priority; the event priority setting request is used to instruct the second device to record at least one target event that matches the second target event priority.

[0159] To sum up, in the solution shown in the embodiment of the present application, the first device can instruct the second device to record events that meet the specified priority when recording events. When the first device subsequently reads events from the second device, the read events are events that meet the above-specified priority. This enables filtering of generated events by priority during the event recording process, thereby improving the flexibility of event recording and acquisition in the Internet of Things system.

[0160] Please refer to FIG9 , which shows a flowchart of an event management method provided by an embodiment of the present application. The method may be performed by a second device. For example, the second device may be one of the IoT devices 110 or 120 in the network architecture shown in FIG1 . The method may include the following steps:

[0161] Step 901: Receive an event priority setting request sent by a first device; the event priority setting request includes a second target event priority.

[0162] Step 902: Record at least one target event that matches the priority of the second target event according to the event priority setting information.

[0163] To sum up, in the solution shown in the embodiment of the present application, the first device can instruct the second device to record events that meet the specified priority when recording events. When the first device subsequently reads events from the second device, the read events are events that meet the above-specified priority. This enables filtering of generated events by priority during the event recording process, thereby improving the flexibility of event recording and acquisition in the Internet of Things system.

[0164] Based on the schemes shown in Figures 8 and 9 above, please refer to Figure 10, which shows a framework diagram of event management provided by an exemplary embodiment of the present application. As shown in Figure 10, the first device 1001 can send a setting request indicating the priority of events in a cluster to the second device 1002. After the second device 1002 receives the setting request, when it subsequently generates events related to the cluster, if the generated events meet the above priority, the events will be recorded; otherwise, the events will be discarded.

[0165] Subsequently, when the first device 1001 obtains events related to the cluster from the second device 1002 , the obtained events are all events that meet the above priority.

[0166] Based on the solutions shown in FIG. 8 to FIG. 10 above, in one possible case, the priority of the second target event can be set by the user corresponding to the first device.

[0167] Please refer to Figure 11, which shows a flowchart of an event management method provided by an embodiment of the present application. The method can be interactively executed by a first device and a second device; for example, the first device and the second device can be IoT device 110 and IoT device 120 in the network architecture shown in Figure 1. The method can include the following steps.

[0168] Step 1101: The first device receives a priority setting instruction.

[0169] Step 1102: The first device sets the priority of the second target event according to the priority setting instruction.

[0170] In a possible implementation of the embodiment of the present application, the first device may set the second target event priority in the event priority setting request when generating the event priority setting request according to the priority setting instruction.

[0171] In another possible implementation scheme of the embodiment of the present application, the first device may also set the priority of the second target event according to the priority setting instruction and store it in a designated location before generating an event priority setting request, and add the pre-stored event priority setting request to the event acquisition request when generating an event priority setting request.

[0172] Step 1103: The first device sends an event priority setting request to the second device, and the second device receives the event priority setting request; the event priority setting request includes the second target event priority.

[0173] In an embodiment of the present application, when a user needs to control the second device to record events in a cluster that meet specific priority requirements, the first device can be triggered to send an event priority setting request to the second device, and the request carries the second target event priority corresponding to the priority previously set by the user.

[0174] Optionally, in addition to the second target event priority, the above-mentioned event priority setting request may also include relevant information for indicating the event to be prioritized and filtered, for example, the node identification information of the second device, the endpoint identification information of the target endpoint in the second node, the cluster identification information of the target cluster in the second node, and so on.

[0175] Step 1104: The second device records at least one target event that matches the priority of the second target event according to the event priority setting information.

[0176] In an embodiment of the present application, after the second device receives an event priority setting request, when it subsequently generates an event in the corresponding cluster, it can compare the priority of the newly generated event with the priority corresponding to the event priority setting information. If the priority of the newly generated event matches the priority corresponding to the event priority setting information, the event is recorded; otherwise, the event is not recorded.

[0177] Optionally, when the second device receives an event priority setting request, if there is an existing event in the cluster corresponding to the event priority setting request, the second device can also filter the existing event. For example, when the priority of the existing event matches the priority corresponding to the event priority setting information, the existing event is retained; otherwise, the existing event is deleted.

[0178] In a possible implementation, the second target event priority includes a write attribute instruction; the write attribute instruction is used to instruct the second device to write an event priority attribute corresponding to the second target event priority in the target cluster.

[0179] Accordingly, before the second device records at least one target event that matches the second target event priority according to the event priority setting information, it may write an event priority attribute corresponding to the second target event priority in the target cluster. The process of the second device recording at least one target event that matches the second target event priority according to the event priority setting information may include:

[0180] When the target cluster generates a first event and the first event matches the event priority attribute, the first event is recorded as a target event of the target cluster.

[0181] In the solution shown in the embodiment of the present application, a connection may be established between the first device and the second device based on the Matter protocol;

[0182] The priority of the event recorded by the second device includes at least two of a debug priority, an information priority, and a CRITICAL priority;

[0183] The event recorded by the second device is an event recorded by the target cluster in the corresponding second device.

[0184] In an embodiment of the present application, a writable attribute (event priority attribute) can be added to the global attributes (Global Elements) of the IoT device cluster to indicate the priority of the events recorded in the cluster. For example, the writable attribute can be as shown in Table 8 below:

[0185] Table 8

[0186] Attribute IDNameType0xFFF7EventPriorityEnum

[0187] In a possible implementation, the at least one target event includes an event whose priority is higher than or equal to the priority of the second target event.

[0188] Through the scheme shown in the embodiment of the present application, the user can set the priority of the event recorded by the second device through the event priority attribute. For example, the attribute priority is divided into three categories: DEBUG, INFO, and CRITICAL, CRITICAL>INFO>DEBUG, and the setting scheme can be as follows:

[0189] If the first device sets the EventPriority of the corresponding Cluster in the second device to DEBUG, the second device will generate events of three priorities: DEBUG, INFO, and CRITICAL (i.e., generate and record them); if the first device sets the EventPriority of the corresponding Cluster in the second device to INFO, the second device will generate event messages of two priorities: INFO and CRITICAL (messages of DEBUG priority can be generated and not recorded, or not generated); if the first device sets the EventPriority of the corresponding Cluster in the second device to CRITICAL, the second device will generate event messages of one priority: CRITICAL (messages of DEBUG and INFO priority can be generated and not recorded, or not generated).

[0190] In a possible implementation, the at least one target event includes an event having a priority equal to a priority of the second target event.

[0191] For example, the attribute priority is divided into three categories: DEBUG, INFO, and CRITICAL. CRITICAL>INFO>DEBUG. The setting scheme can be as follows:

[0192] If the first device sets the EventPriority of the Cluster corresponding to the second device to DEBUG, the second device will generate an event message with a DEBUG priority (event messages of the other two priorities can be generated but not recorded, or not generated); if the first device sets the EventPriority of the Cluster corresponding to the second device to INFO, the second device will generate an event message with an INFO priority; if the first device sets the EventPriority of the Cluster corresponding to the second device to CRITICAL, the second device will generate an event message with a CRITICAL priority.

[0193] For example, please refer to Figure 12, which shows a flow chart of an event record setting involved in an embodiment of the present application. Taking the above-mentioned first device as a control terminal in the Internet of Things and the second device as a device terminal in the Internet of Things as an example, as shown in Figure 12, the process may include the following steps:

[0194] S1201: The user sets the event priority EventPriority attribute of a cluster in the control terminal.

[0195] For example, the control end may be a user terminal such as a smartphone. The user views the information of the device end in the smartphone APP and clicks the event priority setting option of the device end to set the priority of the event generated by the device end.

[0196] S1202: The user triggers the control terminal to issue a write attribute instruction.

[0197] For example, a user can click on the event priority setting option on the device side in the APP to issue an instruction to write the event priority attribute in a cluster on the device side.

[0198] S1203: The control end sends a write attribute instruction to the device end.

[0199] For example, the write attribute instruction may carry the above-mentioned event priority attribute, or carry priority indication information corresponding to the above-mentioned event priority attribute.

[0200] S1204: The device records event messages of corresponding priorities according to the EventPriority attribute set by the user.

[0201] After receiving the write attribute command, the device can write the event priority attribute into the global attributes of the corresponding cluster. When an event related to the cluster subsequently occurs on the device, if the event priority meets the priority requirements of the event priority attribute, the device records the event; otherwise, the event is not recorded.

[0202] When the control end subsequently obtains events related to the cluster recorded by the device end, it can be guaranteed that the obtained events are events that meet the priority set by the user.

[0203] To sum up, in the scheme shown in the embodiment of the present application, the first device can instruct the second device to record events that meet the priority specified by the user when recording events. When the first device subsequently reads events from the second device, the read events are events that meet the above-specified priority. This enables filtering of generated events according to the priority set by the user during the event recording process, thereby improving the flexibility of event recording and acquisition in the Internet of Things system.

[0204] Among them, through the solutions shown in Figures 3 to 7 of the present application, users can obtain event messages of corresponding priorities on the device according to their own intentions.

[0205] Through the solutions shown in Figures 8 to 12 of the present application, users can make the device record events of priority that the user is concerned about according to their own intentions.

[0206] The above two schemes can be used independently, or the above two schemes can be used in combination. For example, the user first uses the scheme shown in Figures 8 to 12 of this application to enable the device to record events of priority that the user is concerned about, for example, through the scheme shown in Figures 8 to 12 above, the device records events of CRITICAL and INFO priorities; subsequently, when the user obtains event messages, the scheme shown in Figures 3 to 7 above is used to read events of specified priority from the device, for example, read events of CRITICAL or INFO priority from the device.

[0207] Please refer to Figure 13, which shows a block diagram of an event management device provided by an embodiment of the present application. The event management device 1300 has the functions of implementing the method shown in Figure 3 or Figure 6 above, which is performed by the first device. As shown in Figure 13, the event management device 1300 may include:

[0208] The sending module 1301 is configured to send an event acquisition request to the second device; the event acquisition request includes a first target event priority;

[0209] The receiving module 1302 is configured to receive at least one target event sent by the second device and matching the priority of the first target event.

[0210] In a possible implementation manner, the first target event priority is set in an event filtering information block of the event acquisition request.

[0211] In a possible implementation, at least one of the target events includes an event having a priority higher than or equal to the priority of the first target event;

[0212] Alternatively, at least one of the target events includes an event having a priority equal to the priority of the first target event.

[0213] In a possible implementation, the apparatus further includes:

[0214] An instruction receiving module, configured to receive a priority setting instruction before the sending module 1301 sends an event acquisition request to the second device;

[0215] A setting module is configured to set the priority of the first target event according to the priority setting instruction.

[0216] In a possible implementation, the event acquisition request includes an event subscription request or an event reading request.

[0217] In the solution shown in the embodiment of the present application, a connection may be established between the first device and the second device based on the Matter protocol;

[0218] The priority of the event recorded by the second device includes at least two of a debug priority, an information priority, and a CRITICAL priority;

[0219] The event recorded by the second device is an event recorded by the target cluster in the corresponding second device.

[0220] To sum up, in the scheme shown in the embodiment of the present application, when the first device requests to obtain events in the second device, it can indicate the priority of the events to be obtained in the request. Accordingly, the second device can send events with matching priorities to the first device, thereby realizing filtering of the obtained events by priority during the event acquisition process, thereby improving the flexibility of event acquisition in the Internet of Things system.

[0221] Please refer to Figure 14, which shows a block diagram of an event management device provided by an embodiment of the present application. The event management device 1400 has the function of implementing the method shown in Figure 4 or Figure 6 above, which is performed by the second device. As shown in Figure 14, the event management device 1400 may include:

[0222] Receiving module 1401 is configured to receive an event acquisition request sent by a first device; the event acquisition request includes a first target event priority;

[0223] The sending module 1402 is configured to send at least one target event that matches the priority of the first target event to the first device.

[0224] In a possible implementation manner, the first target event priority is set in an event filtering information block of the event acquisition request.

[0225] In a possible implementation, at least one of the target events includes an event having a priority higher than or equal to the priority of the first target event;

[0226] Alternatively, at least one of the target events includes an event having a priority equal to the priority of the first target event.

[0227] In a possible implementation, the event acquisition request includes an event subscription request or an event reading request.

[0228] In the solution shown in the embodiment of the present application, a connection may be established between the first device and the second device based on the Matter protocol;

[0229] The priority of the event recorded by the second device includes at least two of a debug priority, an information priority, and a CRITICAL priority;

[0230] The event recorded by the second device is an event recorded by the target cluster in the corresponding second device.

[0231] To sum up, in the scheme shown in the embodiment of the present application, when the first device requests to obtain events in the second device, it can indicate the priority of the events to be obtained in the request. Accordingly, the second device can send events with matching priorities to the first device, thereby realizing filtering of the obtained events by priority during the event acquisition process, thereby improving the flexibility of event acquisition in the Internet of Things system.

[0232] Please refer to Figure 15, which shows a block diagram of an event management device provided by an embodiment of the present application. The event management device 1500 has the functions of implementing the method shown in Figure 8 or Figure 11 above, which is performed by the first device. As shown in Figure 15, the event management device 1500 may include:

[0233] Sending module 1501 is used to send an event priority setting request to the second device; the event priority setting request includes a second target event priority; the event priority setting request is used to instruct the second device to record at least one target event that matches the second target event priority.

[0234] In a possible implementation, the second target event priority includes a write attribute instruction; the write attribute instruction is used to instruct the second device to write an event priority attribute corresponding to the second target event priority in the target cluster.

[0235] In a possible implementation, at least one of the target events includes an event having a priority higher than or equal to the priority of the second target event;

[0236] Alternatively, at least one of the target events includes an event having a priority equal to the priority of the second target event.

[0237] In a possible implementation, the apparatus further includes:

[0238] An instruction receiving module, configured to receive a priority setting instruction before the sending module 1501 sends an event priority setting request to the second device;

[0239] A setting module is configured to set the priority of the second target event according to the priority setting instruction.

[0240] In the solution shown in the embodiment of the present application, a connection may be established between the first device and the second device based on the Matter protocol;

[0241] The priority of the event recorded by the second device includes at least two of a debug priority, an information priority, and a CRITICAL priority;

[0242] The event recorded by the second device is an event recorded by the target cluster in the corresponding second device.

[0243] To sum up, in the solution shown in the embodiment of the present application, the first device can instruct the second device to record events that meet the specified priority when recording events. When the first device subsequently reads events from the second device, the read events are events that meet the above-specified priority. This enables filtering of generated events by priority during the event recording process, thereby improving the flexibility of event recording and acquisition in the Internet of Things system.

[0244] Please refer to Figure 16, which shows a block diagram of an event management device provided by an embodiment of the present application. The event management device 1600 has the function of implementing the method shown in Figure 9 or Figure 11 above, which is performed by the second device. As shown in Figure 16, the event management device 1600 may include:

[0245] Receiving module 1601 is configured to receive an event priority setting request sent by a first device; the event priority setting request includes a second target event priority;

[0246] The recording module 1602 is configured to record at least one target event that matches the second target event priority according to the event priority setting information.

[0247] In a possible implementation, the second target event priority includes a write attribute instruction;

[0248] The device further comprises:

[0249] an attribute writing module, configured to write an event priority attribute corresponding to the second target event priority in the target cluster before the recording module 1602 records at least one target event matching the second target event priority according to the event priority setting information;

[0250] The recording module 1602 is configured to record a first event as a target event of the target cluster when the target cluster generates a first event and the first event matches the event priority attribute.

[0251] In a possible implementation, at least one of the target events includes an event having a priority higher than or equal to the priority of the second target event;

[0252] Alternatively, at least one of the target events includes an event having a priority equal to the priority of the second target event.

[0253] In the solution shown in the embodiment of the present application, a connection may be established between the first device and the second device based on the Matter protocol;

[0254] The priority of the event recorded by the second device includes at least two of a debug priority, an information priority, and a CRITICAL priority;

[0255] The event recorded by the second device is an event recorded by the target cluster in the corresponding second device.

[0256] To sum up, in the solution shown in the embodiment of the present application, the first device can instruct the second device to record events that meet the specified priority when recording events. When the first device subsequently reads events from the second device, the read events are events that meet the above-specified priority. This enables filtering of generated events by priority during the event recording process, thereby improving the flexibility of event recording and acquisition in the Internet of Things system.

[0257] Please refer to FIG17 , which shows a schematic diagram of the structure of a computer device 1700 provided in one embodiment of the present application. The computer device 1700 may include: a processor 1701 , a receiver 1702 , a transmitter 1703 , a memory 1704 , and a bus 1705 .

[0258] The processor 1701 includes one or more processing cores. The processor 1701 executes various functional applications and information processing by running software programs and modules.

[0259] The receiver 1702 and the transmitter 1703 may be implemented as a communication component, which may be a communication chip, which may also be called a transceiver.

[0260] The memory 1704 is connected to the processor 1701 via a bus 1705 .

[0261] The memory 1704 may be used to store a computer program, and the processor 1701 may be used to execute the computer program to implement each step in the above method embodiment.

[0262] In addition, memory 1704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disk or optical disk, electrically erasable programmable read-only memory, erasable programmable read-only memory, static random access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0263] Among them, the process executed by the processor and / or transceiver in the above-mentioned computer device 1700 can refer to the various steps executed by the first device or the second device in any of the methods shown in any of the above-mentioned Figures 3, 4, 6, 8, 9 or 11.

[0264] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. The computer program is loaded and executed by a processor to implement the various steps performed by the first device or the second device in any of the methods shown in Figures 3, 4, 6, 8, 9 or 11 above.

[0265] The present application also provides a chip, which is used to run in a computer device so that the computer device executes each step performed by the first device or the second device in any of the methods shown in Figures 3, 4, 6, 8, 9 or 11 above.

[0266] The present application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform each step performed by the first device or the second device in any of the methods shown in Figures 3, 4, 6, 8, 9, or 11.

[0267] The present application also provides a computer program, which is executed by a processor of a computer device to implement the various steps performed by the first device or the second device in any of the methods shown in Figures 3, 4, 6, 8, 9 or 11 above.

Claims

1. An event management method, characterized in that: The method is performed by a first device, and includes: Sending an event acquisition request to the second device; the event acquisition request includes the first target event priority; Receive at least one target event sent by the second device and matching the priority of the first target event.

2. The method according to claim 1, characterized in that The first target event priority is set in the event filter information block of the event acquisition request.

3. The method according to claim 1 or 2, characterized in that At least one of the target events includes an event with a priority higher than or equal to the priority of the first target event; or, At least one of the target events includes an event having a priority equal to the priority of the first target event.

4. The method according to any one of claims 1 to 3, characterized in that Before sending the event acquisition request to the second device, the method further includes: receiving priority setting instructions; The first target event priority is set according to the priority setting instruction.

5. The method according to any one of claims 1 to 4, characterized in that: The event acquisition request includes an event subscription request or an event reading request.

6. The method according to any one of claims 1 to 5, characterized in that: Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

7. An event management method, characterized in that: The method is performed by a second device, and includes: Receiving an event acquisition request sent by a first device; the event acquisition request includes a first target event priority; At least one target event matching the first target event priority is sent to the first device.

8. The method according to claim 7, characterized in that The first target event priority is set in the event filter information block of the event acquisition request.

9. The method according to claim 7 or 8, characterized in that At least one of the target events includes an event with a priority higher than or equal to the priority of the first target event; or, At least one of the target events includes an event having a priority equal to the priority of the first target event.

10. The method according to any one of claims 7 to 9, characterized in that: The event acquisition request includes an event subscription request or an event reading request.

11. The method according to any one of claims 7 to 10, characterized in that: Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

12. An event management method, characterized in that: The method is performed by a first device, and includes: An event priority setting request is sent to a second device; the event priority setting request includes a second target event priority; the event priority setting request is used to instruct the second device to record at least one target event that matches the second target event priority.

13. The method according to claim 12, characterized in that The second target event priority includes a write attribute instruction; the write attribute instruction is used to instruct the second device to write an event priority attribute corresponding to the second target event priority in the target cluster.

14. The method according to claim 12 or 13, characterized in that At least one of the second target events includes an event having a priority higher than or equal to the priority of the second target event; or, At least one of the target events includes an event having a priority equal to the priority of the second target event.

15. The method according to any one of claims 12 to 14, characterized in that: Before sending the event priority setting request to the second device, the method further includes: receiving priority setting instructions; The priority of the second target event is set according to the priority setting instruction.

16. The method according to any one of claims 12 to 15, characterized in that: Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

17. An event management method, characterized in that: The method is performed by a second device, and includes: receiving an event priority setting request sent by a first device; wherein the event priority setting request includes a second target event priority; At least one target event matching the second target event priority is recorded according to the event priority setting information.

18. The method according to claim 17, characterized in that The second target event priority includes a write attribute instruction; Before recording at least one target event that matches the second target event priority according to the event priority setting information, the method further includes: Writing an event priority attribute corresponding to the second target event priority in the target cluster; The step of recording at least one target event that matches the priority of the second target event according to the event priority setting information includes: When the target cluster generates a first event, and the first event matches the event priority attribute, the first event is recorded as a target event of the target cluster.

19. The method according to claim 17 or 18, characterized in that At least one of the target events includes an event with a priority higher than or equal to the priority of the second target event; or, At least one of the target events includes an event having a priority equal to the priority of the second target event.

20. The method according to any one of claims 17 to 19, characterized in that Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

21. An event management device, characterized in that: The device comprises: A sending module, configured to send an event acquisition request to the second device; the event acquisition request includes a first target event priority; The receiving module is configured to receive at least one target event sent by the second device and matching the priority of the first target event.

22. The device according to claim 21, characterized in that The first target event priority is set in the event filter information block of the event acquisition request.

23. The device according to claim 21 or 22, characterized in that At least one of the target events includes an event with a priority higher than or equal to the priority of the first target event; or, At least one of the target events includes an event having a priority equal to the priority of the first target event.

24. The device according to any one of claims 21 to 23, characterized in that The device further comprises: an instruction receiving module, configured to receive a priority setting instruction before the sending module sends the event acquisition request to the second device; A setting module is configured to set the priority of the first target event according to the priority setting instruction.

25. The device according to any one of claims 21 to 24, characterized in that The event acquisition request includes an event subscription request or an event reading request.

26. The method according to any one of claims 21 to 25, characterized in that Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

27. An event management device, characterized in that: The device comprises: A receiving module, configured to receive an event acquisition request sent by a first device; the event acquisition request includes a first target event priority; A sending module is configured to send at least one target event that matches the priority of the first target event to the first device.

28. The device according to claim 27, characterized in that The first target event priority is set in the event filter information block of the event acquisition request.

29. The device according to claim 27 or 28, characterized in that At least one of the target events includes an event with a priority higher than or equal to the priority of the first target event; or, At least one of the target events includes an event having a priority equal to the priority of the first target event.

30. The device according to any one of claims 27 to 29, characterized in that The event acquisition request includes an event subscription request or an event reading request.

31. The method according to any one of claims 27 to 30, characterized in that Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

32. An event management device, characterized in that: The device comprises: A sending module is used to send an event priority setting request to a second device; the event priority setting request includes a second target event priority; the event priority setting request is used to instruct the second device to record at least one target event that matches the second target event priority.

33. The device according to claim 32, characterized in that The second target event priority includes a write attribute instruction; the write attribute instruction is used to instruct the second device to write an event priority attribute corresponding to the second target event priority in the target cluster.

34. The device according to claim 32 or 33, characterized in that At least one of the target events includes an event with a priority higher than or equal to the priority of the second target event; or, At least one of the target events includes an event having a priority equal to the priority of the second target event.

35. The device according to any one of claims 32 to 34, characterized in that The device further comprises: an instruction receiving module, configured to receive a priority setting instruction before the sending module sends the event priority setting request to the second device; A setting module is configured to set the priority of the second target event according to the priority setting instruction.

36. The method according to any one of claims 32 to 35, characterized in that Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

37. An event management device, characterized in that: The device comprises: A receiving module, configured to receive an event priority setting request sent by a first device; the event priority setting request includes a second target event priority; A recording module is used to record at least one target event that matches the priority of the second target event according to the event priority setting information.

38. The device according to claim 37, characterized in that The second target event priority includes a write attribute instruction; The device further comprises: an attribute writing module, configured to write an event priority attribute corresponding to the second target event priority in a target cluster before the recording module records at least one target event matching the second target event priority according to the event priority setting information; The recording module is configured to record a first event as a target event of the target cluster when the target cluster generates a first event and the first event matches the event priority attribute.

39. The device according to claim 37 or 38, characterized in that At least one of the target events includes an event with a priority higher than or equal to the priority of the second target event; or, At least one of the target events includes an event having a priority equal to the priority of the second target event.

40. The method according to any one of claims 37 to 39, characterized in that Establishing a connection between the first device and the second device based on the Matter protocol; The priorities of the events recorded by the second device include at least two of a debug priority, an information priority, and a CRITICAL priority; The events recorded by the second device are events recorded by the target cluster in the corresponding second device.

41. A computer device, characterized in that The computer device includes a processor, a memory and a transceiver; The memory stores a computer program, and the processor executes the computer program so that the computer device implements the event management method as described in any one of claims 1 to 20 above.

42. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which is used to be executed by a processor to implement the security domain management method according to any one of claims 1 to 20.

43. A chip, characterized in that: The chip is used to run in a computer device, so that the computer device executes the event management method according to any one of claims 1 to 20.

44. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; the processor of the computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, so that the computer device executes the event management method as described in any one of claims 1 to 20.

45. A computer program, characterized in that The computer program is executed by a processor of a computer device to implement the event management method according to any one of claims 1 to 20.

Images