WO2023216042A1

WO2023216042A1 - Event management method and apparatus, device, storage medium, and program product

Info

Publication number: WO2023216042A1
Application number: PCT/CN2022/091579
Authority: WO
Inventors: 包永明
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-05-08
Filing date: 2022-05-08
Publication date: 2023-11-16

Abstract

An event management method and apparatus, a device, a storage medium, and a program product, relating 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 comprising a first target event priority; and receiving at least one target event sent by the second device and matching the first target event priority (302). The solution can improve the flexibility of event acquisition in an Internet of things system.

Description

Event management methods, devices, equipment, storage media and program products

Technical field

This application relates to the technical field of the Internet of Things, and in particular to an event management method, device, equipment, storage medium and program product.

Background technique

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.

In an IoT system, an IoT device may need to obtain an event on another IoT device. For example, a client device needs to obtain an event related to a certain cluster on the client device in order to trigger a reminder. Wait for operations.

Contents of the invention

Embodiments of the present application provide an event management method, device, equipment, storage medium and program product. The technical solutions are as follows:

On the one hand, embodiments of the present application provide an event management method, which is executed by a first device. The method includes:

Send 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 that matches the priority of the first target event.

On the one hand, embodiments of the present application provide an event management method, which is executed by a second device. The method includes:

Receive an event acquisition request sent by the first device; the event acquisition request includes the first target event priority;

At least one target event matching the priority of the first target event is sent to the first device.

On the other hand, embodiments of the present application provide an event management method, which is executed by the first device. The method includes:

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 the event related to the second target event. At least one target event whose priority matches.

On the other hand, embodiments of the present application provide an event management method, which is executed by a second device. The method includes:

Receive an event priority setting request sent by the first device; the event priority setting request includes the second target event priority;

According to the event priority setting information, at least one target event matching the second target event priority is recorded.

On the other hand, an embodiment of the present application provides an event management device, which includes:

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

A receiving module configured to receive at least one target event sent by the second device that matches the priority of the first target event.

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

A sending module configured to send at least one target event matching the priority of the first target event to the first device.

A sending module, configured 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 the At least one target event whose priority matches the second target event.

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

A recording module configured to record at least one target event matching the second target event priority according to the event priority setting information.

In yet another aspect, embodiments of the present application provide a computer device, which includes a processor, a memory, and a transceiver. The memory stores a computer program, and the computer program is configured to be executed by the processor, so as to Implement the above event management methods.

On another aspect, embodiments of the present application also provide a computer-readable storage medium, in which a computer program is stored, and the computer program is loaded and executed by a processor to implement the above event management method.

In another aspect, the present application also provides a chip, which is used to run in a computer device, so that the computer device executes the above event management method.

In yet another aspect, the present application provides a computer program product including computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above event management method.

In another aspect, the present application provides a computer program, which is executed by a processor of a computer device to implement the above event management method.

The technical solutions provided by the embodiments of this application can bring the following beneficial effects:

When the first device requests to obtain events in the second device, it can indicate the priority of the event that needs to be obtained in the request. Correspondingly, the second device can send the event with matching priority to the first device, thereby achieving event processing. During the acquisition process, the acquired events are filtered by priority, which improves the flexibility of event acquisition in the Internet of Things system.

Description of the drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic diagram of the network architecture of the Internet of Things provided by an embodiment of the present application;

Figure 2 is a schematic diagram of the Matter device data model involved in the embodiment shown in Figure 1;

Figure 3 is a flow chart of an event management method provided by an embodiment of the present application;

Figure 4 is a flow chart of an event management method provided by an embodiment of the present application;

Figure 5 is a framework diagram of event management provided by an exemplary embodiment of the present application;

Figure 6 is a flow chart of an event management method provided by an embodiment of the present application;

Figure 7 is a flow chart of event acquisition involved in the embodiment shown in Figure 6;

Figure 8 is a flow chart of an event management method provided by an embodiment of the present application;

Figure 9 is a flow chart of an event management method provided by an embodiment of the present application;

Figure 10 is a framework diagram of event management provided by an exemplary embodiment of the present application;

Figure 11 is a flow chart of an event management method provided by an embodiment of the present application;

Figure 12 is a flow chart of event recording settings related to the embodiment shown in Figure 11;

Figure 13 is a block diagram of an event management device provided by an embodiment of the present application;

Figure 14 is a block diagram of an event management device provided by an embodiment of the present application;

Figure 15 is a block diagram of an event management device provided by an embodiment of the present application;

Figure 16 is a block diagram of an event management device provided by an embodiment of the present application;

Figure 17 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The network architecture and business scenarios described in the embodiments of this application are to more clearly explain the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the network architecture evolution and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

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

The Internet of Things device 110 and the Internet of Things device 120 may be devices used to provide server functions and/or client functions corresponding to the Internet of Things protocol in the Internet of Things.

For example, the IoT device 110 or the IoT device 120 may be a smart home device, such as smart lamps, smart TVs, smart air conditioners, smart refrigerators, smart microwave ovens, smart rice cookers, sweeping robots, smart speakers, smart switches, and so on.

Alternatively, the Internet of Things device 110 or the Internet of Things device 120 may be an industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, or the like.

Alternatively, the Internet of Things device 110 or the Internet of Things device 120 may be a commercial service device, such as an unmanned vending machine or the like.

Alternatively, the Internet of Things device 110 or the Internet of Things device 120 may be an intelligent monitoring device, such as a surveillance camera, an infrared sensor, a sound sensor, a temperature sensor, etc.

In a possible implementation, the Internet of Things device 110 or the Internet of Things device 120 may also be a user-side terminal device. For example, the IoT device 110 or the IoT device 120 can be a smart controller, a smart remote control, a smart phone, a tablet, a smart watch, a smart TV, a gateway, etc.; or, the IoT device 110 or the IoT device 120 can also be Is a personal computer, such as a desktop computer, laptop computer, personal workstation, etc.

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

Matter is an IP-based IoT connection standard that solves the compatibility, security and connectivity issues existing in the current smart home market. Please refer to Figure 2, which shows a schematic diagram of the Matter device data model involved in the embodiment of the present application.

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

1) The Matter device node contains one or more Endpoints, represented by Endpoint Number;

2) Each Endpoint contains multiple Clusters (clusters), represented by Cluster ID (cluster identification). The same Cluster is divided into two roles: Server (server) and Client (client). Data or commands are sent to the Server by the Client. ;

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.

Matter Event introduction:

Event represents a record of something that happened in the past and can be thought of as a log entry. The event stream provides a time-series view of the state evolution on the device node.

Events have 3 priorities:

DEBUG (debugging) is used for debugging by engineers;

INFO (information) drives the user's understanding of the device, such as software update events, key events, etc.;

CRITICAL (important) events that affect the user's physical security, such as switch equipment events and security alarm events.

Event is defined in Cluster and represented by Event ID.

Event records can be shown in Table 1 below:

Table 1

Events can be read through Read Request or subscribed through Subscribe Request.

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

Table 2

IDID	FieldField	TypeType	ConstraintConstraint	ConformanceConformance	DescriptionDescription
0x010x01	EventRequestsEventRequests	list[EventPathIB]list[EventPathIB]	ListList	OO	事件请求event request
0x020x02	EventFiltersEventFilters	list[EventFilterIB]list[EventFilterIB]	ListList	OO	事件过滤event filtering

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

table 3

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

Table 4

IDID	FieldField	TypeType	ConstraintConstraint	ConformanceConformance	DescriptionDescription
0x000x00	Node idNode id	Uint16Uint16	2bytes2bytes	OO	Node idNode id
0x010x01	Endpoint noEndpoint no	Uint16Uint16	2bytes2bytes	OO	Endpoint值Endpoint value
0x020x02	Cluster idCluster id	Uint16Uint16	2bytes2bytes	OO	Cluster ID值Cluster ID value

0x030x03	Event idEvent id	Uint16Uint16	2bytes2bytes	OO	Event ID值Event ID value
0x040x04	IsUrgentIsUrgent	BooleanBoolean		OO	是否为紧急EventWhether it is an emergency event

"IsUrgent" mainly performs emergency reporting for the Event ID event specified in EventPathIB. When the device receives an event reading or subscription request with an Event ID with the word "IsUrgent" from the control end, it will urgently report the corresponding Event ID event.

EventFilterIB: Event filtering information is shown in Table 5 below:

table 5

In one solution, there will be Global Elements (Cluster's global attribute information) in the Cluster. The global attribute information is shown in Table 6 below:

Table 6

Attribute IDAttribute ID	NameName	TypeType
0xFFFA0xFFFA	EventListEventList	list[event-id]list[event-id]

In the above scenario, the properties in Table 6 are read-only.

In actual user operations, the above solution does not consider the user's filtering operations for events of different priorities, nor does it consider whether the user can set the priority of device events so that the device only stores certain events in its event queue according to the user's intention. priority events and then report them. This results in less flexibility in incident reporting.

Please refer to Figure 3, which shows a flow chart of an event management method provided by an embodiment of the present application. The method can be executed by a first device. For example, the first device can be an object in the network architecture shown in Figure 1. One of the networking device 110 or the Internet of Things device 120; the method may include the following steps:

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

Wherein, the above-mentioned first target event priority may be used to indicate the priority of the event that the first device needs to obtain.

The above-mentioned second device may be the Internet of Things device 110 of the system shown in Figure 1 or another Internet of Things device 120 among the Internet of Things devices except the first device.

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

In this embodiment of the present application, after receiving the above-mentioned event acquisition request, the second device can send an event matching the priority to the first device (i.e., the above-mentioned target event) according to the priority of the first target event in the event acquisition request. .

To sum up, in the solution 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 event that needs to be obtained in the request. Correspondingly, the second device can prioritize Events matching the level are sent to the first device, thereby filtering the acquired events by priority during the event acquisition process, and improving the flexibility of event acquisition in the Internet of Things system.

Please refer to Figure 4, which shows a flow chart of an event management method provided by an embodiment of the present application. The method can be executed by a second device. For example, the second device can be an object in the network architecture shown in Figure 1. One of the networking device 110 or the Internet of Things device 120; the method may include the following steps:

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

The first device may be the IoT device 110 of the system shown in FIG. 1 or another IoT device among the IoT devices 120 except the second device.

Step 402: Send at least one target event matching the priority of the first target event to the first device.

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 FIG. 5 , when the first device 51 needs to obtain certain cluster-related events in the second device 52 , it may send an event acquisition request indicating the priority of the event to the second device 52 .

After receiving the event acquisition request, the second device 52 queries the relevant cluster for events with matching priorities according to the priority indicated by the event acquisition request, and sends the queried events to the first device 51 .

Based on the solutions shown in FIGS. 3 to 5 , in one possible case, the priority of the first target event may be set by the user corresponding to the first device.

Please refer to Figure 6, which shows a flow chart of an event management method provided by an embodiment of the present application. This method can be interactively executed by a first device and a second device; for example, the above-mentioned first device and second device can be as shown in Figure 6. The IoT device 110 and the IoT device 120 in the network architecture shown in 1. The method may include the following steps.

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

Before sending the event acquisition request, the first device may first display a priority setting interface, and the user sets the priority of the event to be obtained in the priority setting interface.

Optionally, when the user sets the priority of the events 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 set priority to take effect in the priority setting interface. Target cluster, target endpoint, target node, etc. That is to say, the priority set by the user in this priority setting interface is applicable to the above-mentioned 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 with valid priorities in the priority setting interface, cluster ID 1 corresponds to cluster a, endpoint ID 2 corresponds to endpoint b, and node ID 3 corresponds to node c; Subsequently, this priority will take effect in cluster a in endpoint b on node c.

Alternatively, the above priority setting interface can also be an interface 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 is the one corresponding to the target cluster on the target node. The priority of the target cluster in the target endpoint.

Alternatively, users can set global priorities, which means that the priorities they set are not limited to specific clusters, endpoints, or nodes.

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

In a possible implementation solution of the embodiment of the present application, the first device may set the above-mentioned first target event priority in the event acquisition request when generating the event acquisition request according to the priority setting instruction.

In another possible implementation of the embodiment of this application, the first device can also set the first target event priority according to the priority setting instruction and store it in a designated location before generating the event acquisition request. When, the pre-stored first target event priority is added to the event acquisition request.

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.

In this 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.

Optionally, in addition to the priority of the first target event, the above event acquisition request may also include relevant information indicating the event to be acquired. For example, it may include the node identification information of the second device, the endpoint identification information for the target endpoint, cluster identification information for the target cluster in the second node, and so on.

In a possible implementation, the above event acquisition request includes an event subscription request or an event reading request.

For example, the event acquisition request sent by the first device to the second device may be a Read Request for reading events.

Alternatively, the event acquisition request sent by the first device to the second device may be a Subscribe Request for subscribing to events.

In a possible implementation manner, the above-mentioned first target event priority may be set in the event filtering information block of the event acquisition request.

In the solution shown in the embodiment of this application, a connection can be established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device correspond to events recorded by the target cluster in the second device.

In the embodiment of this application, the above-mentioned first target event priority can be set in the EventFilterIB (Information Blocks, information block) of Read Request or Subscribe Request.

For example, in the embodiment of this application, the permission filtering identifier can be added to EventFilterIB, as shown in the following Table 7:

Table 7

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

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.

In this embodiment of the present application, after receiving the event acquisition request sent by the first device, the second device determines the cluster to which the event that the first device wants to acquire belongs to based on the endpoint identification information and cluster identification information in the event acquisition request, and then Query events corresponding to the cluster that match the priority of the first target event, filter out events that do not match the priority of the first target event, and send the queried events (i.e., at least one of the above target events) to the first equipment.

In a possible implementation manner, at least one target event includes an event with a priority higher than or equal to the priority of the first target event.

In this embodiment of the present application, the first target event priority carried in the event acquisition request can indicate a single priority. When the second device returns an event to the first device, it will return events in the corresponding cluster that are not lower than this priority to the first device. First device.

For example, the priority of events is divided into three categories: DEBUG, INFO, and CRITICAL. The priority order from high to low is CRITICAL>INFO>DEBUG.

If the first device sets the Priority in EventFilterIB to DEBUG when it sends a Read&Subscribe request, the second device returns event messages with three priorities: DEBUG, INFO, and CRITICAL; if the first device sets the Priority in EventFilterIB when it sends a Read&Subscribe request. is INFO, the second device returns event messages with two priorities, INFO and CRITICAL; if the first device sets the Priority in EventFilterIB to CRITICAL when issuing a Read&Subscribe request, the second device returns event messages with one priority, CRITICAL.

In a possible implementation manner, at least one target event includes an event with a priority equal to the priority of the first target event.

In this 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, the single or multiple priorities in the corresponding cluster will be Events of any priority in the level are returned to the first device.

For example, if the first device sets the Priority in EventFilterIB to DEBUG when sending a Read&Subscribe request, the second device returns an event message with DEBUG priority; if the first device sets the Priority in EventFilterIB to INFO when sending a Read&Subscribe request, the second device returns an event message with DEBUG priority. The second device returns an event message with 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 CRITICAL priority.

For example, please refer to FIG. 7 , which shows a flow chart of event acquisition related to an embodiment of the present application. Taking the above-mentioned first device as the control terminal in the Internet of Things and the second device as the device terminal in the Internet of Things as an example, as shown in Figure 7, the process may include the following steps:

S71, the user sets the Priority field of EventFileterIB in the Read Request or Subscribe Request message in the control terminal to filter the priority events that the user cares about.

For example, the control terminal can be a user terminal such as a smartphone. The user views the device-side information in the smartphone's APP (Application), and clicks the event priority setting option on the device-side to read or subscribe to the device-side information. The priority of the event.

S72: The user sends a request to the control terminal to read or subscribe to one or more events in the cluster on the device terminal.

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

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

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

S74: The device side returns events matching the priority indicated by the event reading/subscription request to the control side.

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

S75: The control terminal displays the event returned by the device terminal to the user.

To sum up, in the solution 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 event that needs to be obtained in the request. Correspondingly, the second device can prioritize Events matching the level are sent to the first device, where the above-mentioned priority can be set by the user, thereby achieving filtering of the acquired events through the user-specified priority during the event acquisition process, improving the efficiency of the Internet of Things system. Flexibility in event acquisition.

Please refer to Figure 8, which shows a flow chart of an event management method provided by an embodiment of the present application. The method can be executed by a first device. For example, the first device can be an object in the network architecture shown in Figure 1. One of the networking device 110 or the Internet of Things device 120; the method may include the following steps:

Step 801: Send an event priority setting request to the second device; the event priority setting request contains the second target event priority; the event priority setting request is used to instruct the second device to record at least one event that matches the second target event priority. A target event.

To sum up, according to 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. Subsequently, when the first device reads events from the second device, it reads The retrieved events are those that meet the above-specified priority. This enables filtering of generated events by priority during the event recording process, improving the flexibility of event recording and acquisition in the Internet of Things system.

Please refer to Figure 9, which shows a flow chart of an event management method provided by an embodiment of the present application. The method can be executed by a second device. For example, the second device can be an object in the network architecture shown in Figure 1. One of the networking device 110 or the Internet of Things device 120; the method may include the following steps:

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

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

Based on the solutions shown in FIGS. 8 and 9 above, please refer to FIG. 10 , which shows a framework diagram of event management provided by an exemplary embodiment of the present application. As shown in FIG. 10 , the first device 1001 may send a setting request indicating the priority of events in a certain cluster to the second device 1002 . After the second device 1002 receives the setting request, when subsequently generating an event related to the cluster, if the generated event meets the above priority, the event will be recorded; otherwise, the event will be discarded.

When the first device 1001 subsequently acquires events related to the cluster from the second device 1002, the acquired events are all events that satisfy the above priority.

Based on the solutions shown in FIGS. 8 to 10 , in one possible case, the second target event priority may be set by the user corresponding to the first device.

Please refer to Figure 11, which shows a flow chart of an event management method provided by an embodiment of the present application. This method can be interactively executed by a first device and a second device; for example, the above-mentioned first device and second device can be as shown in Figure 11. The IoT device 110 and the IoT device 120 in the network architecture shown in 1. The method may include the following steps.

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

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

In a possible implementation solution of the embodiment of the present application, the first device may set the above-mentioned second target event priority in the event priority setting request when generating the event priority setting request according to the priority setting instruction.

In another possible implementation of the embodiment of this application, the first device can also set the second target event priority according to the priority setting instruction and store it in a designated location before generating the event priority setting request. When making a priority setting request, add the pre-stored event priority setting request to the event acquisition request.

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.

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

Optionally, in addition to the second target event priority, the above-mentioned event priority setting request may also include relevant information used to indicate the event to be set for priority filtering. For example, it may include the node identifier of the second device. information, endpoint identification information for the target endpoint in the second node, cluster identification information for the target cluster in the second node, and so on.

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.

In this embodiment of the present application, after the second device receives the 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 will be recorded; otherwise, the event will not be recorded.

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

In a possible implementation, the above-mentioned second target event priority includes a write attribute instruction; the write attribute instruction is used to instruct the second device to write the event priority attribute corresponding to the second target event priority in the target cluster.

Correspondingly, before recording at least one target event matching the second target event priority according to the event priority setting information, the second device may write the 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 priority of the second target event according to the event priority setting information may include:

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

In this embodiment of the present application, a writable attribute (event priority attribute) can be added to the global attributes (Global Elements) in the cluster of Internet of Things devices to indicate the priority of events recorded in the cluster. For example, the writable attribute can be shown in Table 8 below:

Table 8

Attribute IDAttribute ID	NameName	TypeType
0xFFF70xFFF7	EventPriorityEventPriority	EnumEnum

In a possible implementation manner, at least one target event includes an event with a priority higher than or equal to the priority of the second target event.

Through the solution shown in the embodiment of this 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, CRITICAL, CRITICAL>INFO>DEBUG, then The setting scheme can be as follows:

If the first device sets the EventPriority of the corresponding Cluster in the second device to DEBUG, the second device will generate (ie generate and record) events with three priorities: DEBUG, INFO, and CRITICAL; if the first device sets the corresponding Cluster in the second device to If the Cluster's EventPriority is set to INFO, the second device will generate event messages with two priorities, INFO and CRITICAL (DEBUG priority messages can be generated and not recorded, or not generated); if the first device sets the second device to the Cluster The EventPriority is set to CRITICAL, and the device will generate event messages with CRITICAL priority (DEBUG and INFO priority messages can be generated and not recorded, or not generated).

In a possible implementation manner, at least one target event includes an event with a priority equal to the priority of the second target event.

For example, if the attribute priority is divided into three categories: DEBUG, INFO, and CRITICAL, CRITICAL>INFO>DEBUG, the setting plan can be as follows:

If the first device sets the EventPriority of the Cluster corresponding to the second device to DEBUG, the second device will generate event messages with DEBUG priority (the other two priority event messages can be generated and not recorded, or not generated); if the second device If one device sets the EventPriority of the second device corresponding to the Cluster to INFO, the second device will generate event messages with INFO priority; if the first device sets the EventPriority of the second device corresponding to the Cluster to CRITICAL, the second device will have CRITICAL priority. Level event messages are generated.

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

S1201, the user sets the EventPriority attribute of a certain cluster in the control terminal.

For example, the control terminal can be a user terminal such as a smartphone. The user views device-side information in the smartphone APP and clicks the event priority setting option on the device to set the priority of events generated by the device.

S1202, the user triggers the control terminal to issue a write attribute instruction.

For example, the user can click 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.

S1203. The control end sends a write attribute instruction to the device end.

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.

S1204: The device records the event message of the corresponding priority according to the EventPriority attribute set by the user.

Among them, after the device side receives the above write attribute instruction, it can write the event priority attribute into the global attribute of the corresponding cluster. When subsequent events related to the cluster occur on the device, if the priority of the event meets the priority requirements corresponding to the above event priority attributes, the device will record the event, otherwise the event will not be recorded.

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

To sum up, according to the solution shown in the embodiment of this application, the first device can instruct the second device to record events that meet the priority specified by the user when recording events. Subsequently, when the first device reads events from the second device, The events read are those that meet the above specified priorities, thus enabling filtering of generated events through the priorities set by the user during the event recording process, improving event recording and acquisition in the Internet of Things system flexibility.

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

Through the solution shown in FIGS. 8 to 12 of the present application, the user can make the device record the priority events that the user cares about according to his own intention.

The above two solutions can be used independently, or the above two solutions can also be used in combination. For example, the user first uses the solutions shown in Figures 8 to 12 of the present application to cause the device to record priority events that the user is concerned about, such as, Through the above-mentioned scheme shown in Figure 8 to Figure 12, the device records two priority events, CRITICAL and INFO; when subsequent users obtain the event message, they can read it from the device through the above-mentioned scheme shown in Figure 3 to Figure 7. Events with specified priority, for example, reading CRITICAL or INFO priority events from the device.

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 function of being executed by the first device in implementing the method shown in FIG. 3 or FIG. 6 . As shown in Figure 13, the event management device 1300 may include:

Sending module 1301, configured to send an event acquisition request to the second device; the event acquisition request includes the first target event priority;

The receiving module 1302 is configured to receive at least one target event sent by the second device that matches the priority of the first target event.

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

In a possible implementation, 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;

Alternatively, at least one of the target events includes an event with a priority equal to the priority of the first target event.

In a possible implementation, the device further includes:

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;

A setting module configured to set the first target event priority according to the priority setting instruction.

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

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 being executed by the second device in implementing the method shown in FIG. 4 or FIG. 6 . As shown in Figure 14, the event management device 1400 may include:

The receiving module 1401 is configured to receive an event acquisition request sent by the first device; the event acquisition request includes the first target event priority;

The sending module 1402 is configured to send at least one target event matching the priority of the first target event to the first device.

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 function of being executed by the first device in implementing the method shown in FIG. 8 or FIG. 11 . As shown in Figure 15, the event management device 1500 may include:

The sending module 1501 is used to send an event priority setting request to the second device; the event priority setting request includes the second target event priority; the event priority setting request is used to instruct the second device to record and At least one target event whose priority matches the second target event.

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 in the target cluster the same as the second target event priority. The corresponding event priority attribute.

In a possible implementation, 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;

Alternatively, at least one of the target events includes an event with a priority equal to the priority of the second target event.

In a possible implementation, the device further includes:

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;

A setting module configured to set the second target event priority according to the priority setting instruction.

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 being executed by the second device in implementing the method shown in FIG. 9 or FIG. 11 . As shown in Figure 16, the event management device 1600 may include:

The receiving module 1601 is configured to receive an event priority setting request sent by the first device; the event priority setting request includes the second target event priority;

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.

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

The device also includes:

An attribute writing module, configured to write the content of the first target event in the target cluster before the recording module 1602 records at least one target event matching the priority of the second target event according to the event priority setting information. The event priority attribute corresponding to the priority of the second target event;

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

Please refer to Figure 17, which shows a schematic structural diagram of a computer device 1700 provided by an 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.

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.

The receiver 1702 and the transmitter 1703 can be implemented as a communication component, and the communication component can be a communication chip. This communication chip can also be called a transceiver.

Memory 1704 is connected to processor 1701 through bus 1705.

The memory 1704 can be used to store a computer program, and the processor 1701 is used to execute the computer program to implement various steps in the above method embodiments.

Additionally, memory 1704 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-only memory, erasable programmable read-only memory, static ready-access memory, read-only memory, magnetic memory, flash memory, programmable read-only memory.

Wherein, the process performed by the processor and/or transceiver in the computer device 1700 may refer to the method shown in any one of the above-mentioned FIG. 3, FIG. 4, FIG. 6, FIG. 8, FIG. 9 or FIG. 11, by the first device. or individual steps performed by the second device.

Embodiments of the present application also provide a computer-readable storage medium. A computer program is stored in the storage medium. The computer program is loaded and executed by a processor to implement the above-mentioned Figures 3, 4, 6, and 8. In the method shown in either Figure 9 or Figure 11, each step is performed by the first device or the second device.

This application also provides a chip, which is used to run in a computer device, so that the computer device executes the method shown in any one of the above-mentioned Figure 3, Figure 4, Figure 6, Figure 8, Figure 9 or Figure 11, Various steps performed by the first device or the second device.

The application also provides a computer program product, which computer program product or computer program includes computer instructions, and the computer instructions 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 the processor executes the computer instructions, causing the computer device to execute any one of the above figures 3, 4, 6, 8, 9 or 11. In the method, each step is performed by the first device or the second device.

This application also provides a computer program, which is executed by the processor of the computer device to implement the method shown in any one of the above-mentioned Figure 3, Figure 4, Figure 6, Figure 8, Figure 9 or Figure 11, by Various steps performed by the first device or the second device.

Claims

An event management method, characterized in that the method is executed by a first device, and the method includes:

Send 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 that matches the priority of the first target event.
The method according to claim 1, characterized in that the first target event priority is set in the event filtering information block of the event acquisition request.
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 with a priority equal to the priority of the first target event.
The method according to any one of claims 1 to 3, characterized in that before sending the event acquisition request to the second device, it further includes:

Receive priority setting instructions;

The first target event priority is set according to the priority setting instruction.
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.
The method according to any one of claims 1 to 5, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
An event management method, characterized in that the method is executed by a second device, and the method includes:

Receive an event acquisition request sent by the first device; the event acquisition request includes the first target event priority;

At least one target event matching the priority of the first target event is sent to the first device.
The method according to claim 7, characterized in that the first target event priority is set in the event filtering information block of the event acquisition request.
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 with a priority equal to the priority of the first target event.
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.
The method according to any one of claims 7 to 10, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priority of the event recorded by the second device includes at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
An event management method, characterized in that the method is executed by a first device, and the method includes:

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 the event related to the second target event. At least one target event whose priority matches.
The method of claim 12, wherein the second target event priority includes a write attribute instruction; the write attribute instruction is used to instruct the second device to write the same content as the second device in the target cluster. The event priority attribute corresponding to the target event priority.
The method according to claim 12 or 13, characterized in that,

At least one of the second 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 with a priority equal to the priority of the second target event.
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, it further includes:

Receive priority setting instructions;

The second target event priority is set according to the priority setting instruction.
The method according to any one of claims 12 to 15, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
An event management method, characterized in that the method is executed by a second device, and the method includes:

Receive an event priority setting request sent by the first device; the event priority setting request includes the second target event priority;

According to the event priority setting information, at least one target event matching the second target event priority is recorded.
The method of claim 17, wherein the second target event priority includes a write attribute instruction;

Before recording at least one target event matching the second target event priority according to the event priority setting information, the method further includes:

Write an event priority attribute corresponding to the second target event priority in the target cluster;

Recording at least one target event matching the second target event priority 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 one of the target events of the target cluster.
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 with a priority equal to the priority of the second target event.
The method according to any one of claims 17 to 19, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
An event management device, characterized in that the device includes:

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

A receiving module configured to receive at least one target event sent by the second device that matches the priority of the first target event.
The device according to claim 21, characterized in that the first target event priority is set in the event filtering information block of the event acquisition request.
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 with a priority equal to the priority of the first target event.
The device according to any one of claims 21 to 23, characterized in that the device further includes:

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

A setting module configured to set the first target event priority according to the priority setting instruction.
The device according to any one of claims 21 to 24, wherein the event acquisition request includes an event subscription request or an event reading request.
The method according to any one of claims 21 to 25, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
An event management device, characterized in that the device includes:

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

A sending module configured to send at least one target event matching the priority of the first target event to the first device.
The device according to claim 27, characterized in that the first target event priority is set in an event filtering information block of the event acquisition request.
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 with a priority equal to the priority of the first target event.
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.
The method according to any one of claims 27 to 30, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
An event management device, characterized in that the device includes:

A sending module, configured 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 the At least one target event whose priority matches the second target event.
The apparatus of claim 32, wherein the second target event priority includes a write attribute instruction; the write attribute instruction is used to instruct the second device to write the same information as the second device in the target cluster. The event priority attribute corresponding to the target event priority.
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 with a priority equal to the priority of the second target event.
The device according to any one of claims 32 to 34, characterized in that the device further includes:

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

A setting module configured to set the second target event priority according to the priority setting instruction.
The method according to any one of claims 32 to 35, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
An event management device, characterized in that the device includes:

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

A recording module configured to record at least one target event matching the second target event priority according to the event priority setting information.
The device according to claim 37, wherein the second target event priority includes a write attribute instruction;

The device also includes:

An attribute writing module, configured to write the second target event in the 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 event priority attribute corresponding to the target event priority;

The recording module is configured to, when the target cluster generates a first event and the first event matches the event priority attribute, record the first event as a target item of the target cluster. event.
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 with a priority equal to the priority of the second target event.
The method according to any one of claims 37 to 39, characterized in that a connection is established between the first device and the second device based on the Matter protocol;

The priorities of events recorded by the second device include at least two of debugging DEBUG priority, information INFO priority, and important CRITICAL priority;

The events recorded by the second device are events recorded corresponding to the target cluster in the second device.
A computer device, characterized in that the computer device includes a processor, a memory and a transceiver;

A computer program is stored in the memory, 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.
A computer-readable storage medium, characterized in that a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the security domain management method as described in any one of claims 1 to 20 .
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.
A computer program product, characterized in that the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; and a processor of a computer device reads the computer instructions from the computer-readable storage medium. instructions, and execute the computer instructions, so that the computer device executes the event management method according to any one of claims 1 to 20.
A computer program, characterized in that the computer program is executed by a processor of a computer device to implement the event management method as claimed in any one of claims 1 to 20.