WO2023201587A1

WO2023201587A1 - Device control method and apparatus, device, and storage medium

Info

Publication number: WO2023201587A1
Application number: PCT/CN2022/088003
Authority: WO
Inventors: 李永华; 林兆阳; 茹昭; 张军; 包永明
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-04-20
Filing date: 2022-04-20
Publication date: 2023-10-26
Also published as: CN118525485A

Abstract

A device control method and apparatus, a device, and a storage medium, relating to the technical field of Internet of things. The method comprises: receiving attribute information of a first attribute sent by a first device (201); and when the attribute information of the first attribute of the first device satisfies a trigger condition of a target scene, sending a control instruction to a second device corresponding to the target scene (202), the control instruction being used for instructing the second device to adjust attribute information of a second attribute of the second device so as to realize the target scene. The solution expands a triggering mode for a scene in the Internet of things, and improves the application effect of the scene.

Description

Equipment control method, device, equipment and storage medium

Technical field

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

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.

Among related technologies, the Internet of Things can support the implementation of scenes. For example, if a user issues a voice command to "turn on home mode", the user's mobile phone can send start commands to lighting fixtures, air conditioners and other devices in the home Internet of Things to turn on the lighting fixtures and air conditioners.

Contents of the invention

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

On the one hand, embodiments of the present application provide a device control method, which is executed by a central node device in the Internet of Things. The method includes:

Receive attribute information of the first attribute sent by the first device;

When the attribute information of the first attribute of the first device meets the triggering condition of the target scene, send a control instruction to the second device corresponding to the target scene; the control instruction is used to instruct the second device Adjust the attribute information of the second attribute of the second device to achieve the target scenario.

On the one hand, embodiments of the present application provide a device control method, which is executed by a management device in the Internet of Things. The method includes:

Send an add rule instruction to the central node device; the add rule instruction includes rule information of a target rule; the target rule takes the first attribute of the first device as input, and the target rule is used to indicate the third The association between the first attribute of a device, the trigger condition and the scene information of the target scene;

Wherein, the add rule instruction is used to instruct the central node device to add the target rule in the first cluster, so that the central node device obtains the attribute information of the first attribute of the first device, and When the attribute information of the first attribute of the first device satisfies the trigger condition, a control instruction is sent to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the first attribute information of the second attribute of the two devices to achieve the target scenario.

On the one hand, embodiments of the present application provide a device control method, which is executed by a first device in the Internet of Things. The method includes:

Send the attribute information of the first attribute of the first device to the central node device, so that when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, the central node device sends the attribute information to the central node device. The second device corresponding to the target scene sends a control instruction; the control instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device to realize the target scene.

On the one hand, embodiments of the present application provide a device control method, which is executed by a second device in the Internet of Things. The method includes:

Receive a control instruction sent by the central node device; the control instruction is that the central node device receives the attribute information of the first attribute sent by the first device, and when the attribute information of the first attribute of the first device meets the target scenario An instruction sent when a condition is triggered; the target scene is a scene corresponding to the second device;

The attribute information of the second attribute of the second device is adjusted according to the control instruction to realize the target scenario.

On the other hand, embodiments of the present application provide an equipment control device, which includes:

A receiving module, configured to receive attribute information of the first attribute sent by the first device;

A sending module configured to send a control instruction to the second device corresponding to the target scene when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene; the control instruction is used to indicate The second device adjusts the attribute information of the second attribute of the second device to realize the target scenario.

A sending module, configured to send an add rule instruction to the central node device; the add rule instruction includes rule information of a target rule; the target rule takes the first attribute of the first device as input, and the target rule is Indicating the association between the first attribute of the first device, the trigger condition and the scene information of the target scene;

A sending module, configured to send the attribute information of the first attribute of the first device to the central node device, so that the central node device can satisfy the triggering condition of the target scene when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene. , sending a control instruction to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device to realize the target scene.

A receiving module, configured to receive a control instruction sent by the central node device; the control instruction is that the central node device receives the attribute information of the first attribute sent by the first device, and adds the attribute information of the first attribute to the first device. An instruction sent when the information satisfies the trigger condition of the target scene; the target scene is the scene corresponding to the second device;

An adjustment module, configured to adjust the attribute information of the second attribute of the second device according to the control instruction to achieve a target scenario.

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 device control 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 device control 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 device control 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 device control 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 device control method.

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

A central node device is set up in the Internet of Things. After the central node device obtains the attribute information of the first attribute of the first device, if the attribute information of the first attribute of the first device satisfies the trigger condition of the target scenario, it can pass Control the second device corresponding to the target scene to adjust the attribute information of the second attribute to realize the above target scene. User intervention is not required during the triggering process of the above target scene, thereby expanding the triggering method of the scene in the Internet of Things and improving the The application effect of the scene.

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 flow chart of a device control method provided by an embodiment of the present application;

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

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

Figure 5 is a system framework diagram of equipment control provided by an embodiment of the present application;

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

Figure 7 is a flow chart of a device control method provided by an embodiment of the present application;

Figure 8 is a schematic diagram of a device control framework related to the embodiment shown in Figure 7;

Figure 9 is a schematic diagram of another device control framework related to the embodiment shown in Figure 7;

Figure 10 is a block diagram of an equipment control device provided by an embodiment of the present application;

Figure 11 is a block diagram of an equipment control device provided by an embodiment of the present application;

Figure 12 is a block diagram of an equipment control device provided by an embodiment of the present application;

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

Figure 14 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: an Internet of Things device 110 (shown as an Internet of Things device 110a, an Internet of Things device 110b, and an Internet of Things device 110c in Figure 1), a central node device 120, and a management device 130;

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

For example, the IoT device 110 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 IoT device 110 may be an industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, etc.

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

Alternatively, the IoT device 110 may be an intelligent monitoring device, such as a surveillance camera, an infrared sensor, a sound sensor, a temperature sensor, etc.

The above-mentioned central node device 120 may be a device installed in the Internet of Things to provide services such as information interoperability and information maintenance for various Internet of Things devices and management devices in the Internet of Things. For example, the central node device 120 may be a home gateway device or the like.

Among them, the above-mentioned central node device 120 can be independent of each Internet of Things device 110 in terms of hardware, or the above-mentioned central node device 120 can also be the same device as a certain Internet of Things device 110 . For example, a home network device can simultaneously implement the Internet of Things device 110 and the central node device 120 in the Internet of Things.

In a possible implementation, the management device 130 may be a user-side terminal device. For example, the management device 130 can be a smart phone, a tablet, a smart watch, a smart TV, etc.; or the management device 130 can also be a personal computer, such as a desktop computer, a portable computer, a personal workstation, etc.

In another possible implementation, the management device 130 may also be a client entity (which may be a virtual entity) running on a terminal device. For example, the management device 130 may be running on a smartphone and used to manage Internet of Things devices. 110 and the central node device 120 for management and configuration APP.

In the embodiment of the present application, the above-mentioned Internet of Things device 110, central node device 120, and management device 130 may be electronic devices that meet the same or different Internet of Things protocols. For example, they may be electronic devices that meet the Connectivity Standards Alliance (CSA) ) (or known as the Matter protocol of the Zigbee Alliance) (or known as the Connected Home over IP Working Group (CHIP) project).

Matter is an IP-based IoT connection standard that solves the compatibility, security and connectivity issues existing in the current smart home market.

In the Matter standard, a node (Node), that is, a device (Device), can contain one or more endpoints (EndPoint); an endpoint can contain one or more clusters (Cluster); among them, clusters can be regarded as interfaces and services. or object class, and is the lowest independent functional element in the data model. Each cluster can have its own attributes (Attribute), methods (Command), and events (Event) and other information.

In an implementation method involved in this application, a Cluster named Scene can be set up in the Matter protocol, and the Cluster is used for scene implementation. Through Scene Cluster, you can change multiple Attributes of multiple Clusters in one or more devices at one time to achieve the effect of a scene. The Server of Scene Cluster maintains a Scene Table that stores information about each Scene. Each piece of information includes the ID (Identity, ID), name, and all Attributes of all Clusters that need to be changed. .

For example, the information contained in each Scene in the Scene Table can be shown in Table 1 below.

Table 1

The group in Table 1 above refers to another Cluster, that is, Group Cluster, which refers to a group of device information. If the value is 0, it means that the scene is only related to this device. If it is not 0, it means that the scene is related to a group of devices. Device related, this group of devices is indicated by Group ID.

As shown in Table 1 above, the Client of Scene Cluster sets a certain Scene information by calling the AddScene method, calls a certain Scene by calling the RecallScene method, and then determines whether to trigger a group of devices based on the SceneGroupID of the Scene Table. The cluster attributes can still trigger the cluster attributes of a single device to realize the function of the scene. The Client can also call the RemoveScene function to remove the Scene.

However, the Scene Cluster shown in Table 1 above can only implement scene functions, such as using a client APP to set a home scene to control devices at home. When this scenario needs to be used, the client calls a method to invoke the scenario to implement the scenario, that is, to change multiple Attributes of multiple Clusters of the device. The above solution requires user intervention to trigger the scenario, and there is a lack of joint working mechanism between devices without user operation, resulting in limited application methods of scenarios in the Internet of Things.

To address the above problems, subsequent embodiments of the present application provide a setting and configuration solution, whereby the central node device can automatically control devices corresponding to scenarios in the Internet of Things without user intervention.

Please refer to Figure 2, which shows a flow chart of a device control method provided by an embodiment of the present application. This method can be executed by a central node device in the Internet of Things. For example, the central node device can be the network shown in Figure 1 The central node device 120 in the architecture; the method may include the following steps:

Step 201: Receive attribute information of the first attribute sent by the first device.

Step 202: When the attribute information of the first attribute of the first device satisfies the trigger condition of the target scene, send a control instruction to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the Attribute information of the second attribute to achieve the target scenario.

To sum up, the solution shown in the embodiment of the present application is to set up a central node device in the Internet of Things. After the central node device obtains the attribute information of the first attribute of the first device, if the first attribute of the first device is If the attribute information of the attribute meets the triggering conditions of the target scene, the above target scene can be realized by controlling the second device corresponding to the target scene to adjust the attribute information of the second attribute. User intervention is not required during the triggering process of the above target scene. This expands the triggering methods of scenarios in the Internet of Things and improves the application effects of scenarios.

Please refer to Figure 3, which shows a flow chart of a device control method provided by an embodiment of the present application. This method can be executed by a first device in the Internet of Things. For example, the first device can be the network shown in Figure 1 IoT device 110 in the architecture; the method may include the following steps:

Step 301: Send the attribute information of the first attribute of the first device to the central node device, so that when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, the central node device sends the attribute information of the first attribute of the first device to the target scene. The second device sends a control instruction; the control instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device to achieve the target scenario.

Please refer to Figure 4, which shows a flow chart of a device control method provided by an embodiment of the present application. This method can be executed by a second device in the Internet of Things. For example, the second device can be the network shown in Figure 1 IoT device 110 in the architecture; the method may include the following steps:

Step 401: Receive a control instruction sent by the central node device; the control instruction is that the central node device receives the attribute information of the first attribute sent by the first device, and when the attribute information of the first attribute of the first device satisfies The instruction is sent when the trigger condition of the target scene is the scene corresponding to the second device.

Step 402: Adjust the attribute information of the second attribute of the second device according to the control instruction to achieve the target scenario.

Through the solutions shown in Figures 2 to 4 of this application, the central node device can be connected to the first device and the second device involved in the target scenario, and maintain the triggering rules of the scenario in the Internet of Things, thereby automatically triggering the target scenario.

Please refer to FIG. 5 , which shows a system framework diagram of device control provided by an embodiment of the present application. In a possible application scenario, the central node device is a smart gateway 51, the first device is a temperature sensor 52, and the second device is a smart air conditioner 53. The target scenario is to turn on the air conditioner when the temperature is 30°, as shown in the figure. As shown in 5, the triggering rules of the target scenario are set in the smart gateway 51, and the smart gateway 51 establishes connections based on the Internet of Things protocol with the temperature sensor 52 and the smart air conditioner 53 respectively.

In the system framework shown in Figure 5, the equipment control process can be as follows:

S1. The temperature sensor 52 sends the measured indoor temperature value (that is, the attribute information of the first attribute) to the intelligent gateway 51.

S2, the smart gateway 51 determines whether the indoor temperature value reaches 30°.

S3, when the indoor temperature value reaches 30°, the smart gateway 51 sends a control instruction to start cooling to the smart air conditioner 53.

S4, the smart air conditioner 53 starts cooling according to the control instruction, for example, setting the target temperature to 18° (that is, adjusting the attribute information of the second attribute) to achieve the target scenario.

In the embodiments shown in FIGS. 2 to 4 of the present application, the central node device can trigger scenarios through a cluster (Cluster) used to manage scene rules. In addition, the cluster can provide external rule configuration and management. In other words, users can configure and manage scene triggering rules in the central node device through the management device.

Please refer to Figure 6, which shows a flow chart of a device control method provided by an embodiment of the present application. This method can be executed by a management device in the Internet of Things. For example, the management device can be in the network architecture shown in Figure 1 management device 130; the method may include the following steps:

Step 601: Send an add rule instruction to the central node device; the add rule instruction includes rule information of the target rule; the target rule takes the first attribute of the first device as input, and the target rule is used to indicate the first attribute of the first device, The correlation between trigger conditions and scene information of the target scene.

Wherein, the add rule instruction is used to instruct the central node device to add the target rule in the first cluster, so that the central node device obtains the attribute information of the first attribute of the first device, and the attribute information of the first attribute of the first device When the trigger condition is met, a control instruction is sent to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device to realize the target scene.

To sum up, according to the solution shown in the embodiment of this application, a central node device is set up in the Internet of Things, a first cluster can be set up in the central node device, and the management device can set a target rule in the first cluster, and the target rule is based on The first attribute of the first device is input and includes the association between the first attribute, the trigger condition and the scene information of the target scene; through the target rule in the first cluster, the central node device obtains the first After the attribute information of the first attribute of the device is obtained, if the attribute information of the first attribute of the first device meets the trigger condition of the target scene, the attribute information of the second attribute can be adjusted by controlling the second device corresponding to the target scene. To achieve the above target scenario, no user intervention is required during the triggering process of the above target scenario, thereby expanding the triggering method of scenarios in the Internet of Things and improving the application effect of the scenario.

Please refer to FIG. 7 , which shows a flow chart of a device control method provided by an embodiment of the present application. The method can be interactively executed by a management device, a central node device, a first device, and a second device. For example, the management device and the central node device may be the management device 130 and the central node device 120 in the network architecture shown in Figure 1 respectively; the first device and the second device may be different devices in the network architecture shown in Figure 1 Internet of Things device 110; the method may include the following steps:

Step 701: The management device sends an add rule instruction to the central node device; accordingly, the central node device receives the add rule instruction sent by the management device.

Among them, the add rule instruction contains the rule information of the target rule.

The above target rule takes the first attribute of the first device as input, and the target rule is used to indicate the association between the first attribute of the first device, the trigger condition, and the scene information of the target scene.

For example, the management device contains the client of the first cluster, and the central node device contains the server of the first cluster; the client of the first cluster in the management device can send a message to the server of the first cluster in the central node device. Add rule directive.

The target rule corresponding to the above adding rule instruction can be set by the user in the interactive interface of the management device.

Step 702: The central node device adds the target rule in the first cluster according to the rule information of the target rule.

In this embodiment of the present application, after receiving the above-mentioned rule-adding instruction, the central node device can add a new rule, that is, the above-mentioned target rule, in the first cluster.

For example, a rule table (Rule Table) can be set up in the first cluster, which contains each set rule.

In a possible implementation, the management device can also send a rule enabling instruction of the target rule to the central node device; the rule enabling instruction is used to instruct the central node device to set the target rule to an enabled state. Correspondingly, the central node device can receive the rule activation instruction of the target rule sent by the management device; and set the target rule to the enabled state according to the rule activation instruction of the target rule.

In this embodiment of the present application, each rule in the first cluster may have a corresponding enabled state or a non-enabled state.

In another possible implementation, the management device can also send a target rule deactivation instruction to the central node device; the target rule deactivation instruction is used to instruct the central node device to set the target rule to a non-enabled state. Correspondingly, the central node device can receive the target rule deactivation instruction sent by the management device; and set the target rule to a non-enabled state according to the target rule deactivation instruction.

When the central node device adds a new rule in the first cluster, it can set the newly added rule to the default state, for example, set it to the default enabled state, or set it to the default non-enabled state. Subsequent management devices can The rules in the first cluster are enabled through the rule enabling instruction, or the rules in the first cluster are turned off through the rule closing instruction.

In a possible implementation, the management device can also send information acquisition instructions to the central node device; and receive the device information of each Internet of Things device connected to the central node device sent by the central node device; wherein, in each Internet of Things device, Contains a first device and a second device.

Correspondingly, the central node device can receive the information acquisition instruction sent by the management device; and according to the information acquisition instruction, send the device information of each Internet of Things device connected to the central node device to the management device.

In the embodiment of this application, the management device can obtain the device information of each Internet of Things device connected to the central node device by sending an information acquisition instruction to the central node device, so that the user of the management device can check which Internet of Things devices can construct a scenario. , that is, it is convenient for users to check which IoT devices can trigger other IoT devices to perform scene-related actions, so that users can set corresponding rules accordingly.

In a possible implementation manner, the management device can also send a rule viewing instruction to the central node device; and receive the rule information of each rule in the first cluster sent by the central node device.

Correspondingly, the central node device can receive the rule viewing instruction sent by the management device; and according to the rule viewing instruction, send the rule information of each rule in the first cluster to the management device.

In this embodiment of the present application, the management device can obtain the rule information of each rule that has been set in the first cluster of the central node device by sending a rule viewing instruction to the central node device, so that the user of the management device can check that the central node device has What rules are there to facilitate users to decide whether to add or delete rules.

In a possible implementation, the management device may also send a rule removal instruction of the first rule to the central node device; the first rule is part or all of the rules in the first cluster; the rule removal instruction of the first rule is Instructing the central node device to remove the first rule from the first cluster.

Correspondingly, the central node device can receive the rule removal instruction of the first rule sent by the management device; the first rule is part or all of the rules in the first cluster; according to the rule removal instruction of the first rule, the first rule is removed from the first cluster. Remove the first rule.

In this embodiment of the present application, the management device can remove some or all of the rules in the first cluster of the central node device by sending a rule deletion instruction to the central node device.

The above-mentioned rule removal instruction may be an instruction to remove one or more rules specified in the first cluster. Optionally, when the user wants to remove multiple specified rules in the first cluster, the management device can include the multiple rules that need to be removed in the rule removal instruction. For example, the rule removal instruction can include the rules that need to be moved. Identification information of each rule excepted.

Optionally, the above rule removal instruction may also be an instruction to remove all rules in the first cluster. Optionally, in this case, the rule removal instruction can carry a complete removal identification information. Correspondingly, after the central node device receives the rule removal instruction, it parses to obtain the above all removal identification information. That is, all rules in the first cluster can be removed.

For example, the method (Command) corresponding to the above-mentioned first cluster may be as shown in Table 2 below.

Table 2

In the above Table 2, V in the Access column indicates viewing permissions, O indicates operating permissions, and M indicates management permissions. The M in the Conformance column indicates that the corresponding method is required. The Direction column indicates the direction in which instructions/responses are sent after calling the corresponding method; for example, "Client->Server" indicates that the corresponding method is called by the client to send instructions/responses to the server.

The various methods involved in Table 2 are introduced below:

1) GetInfo:

After the Client calls this method, it will send a request to the server to obtain information about other devices configured on the server device, that is, to check which Attribute IDs of which Cluster IDs on which Node IDs can be used as the input of the rules, and can be passed The situation of other device nodes subscribed by the central node device (server) determines what kind of messages the central node device can receive as the input of the rule. Optionally, you can also check which Scene id on which Node id can be used as the scene triggered by the rule. And, check which scenes are configured on the central node device. Client needs to request this information before setting rules in order to set effective rules. Server can return the corresponding information by calling the GetInfoResp method.

2)AddRule:

After the Client calls this method, it will send a request to the server. The request can carry information about a Rule in the Rule Table, which is used to add rules on the server side. After receiving the call of this method, the Server side will add the corresponding rules to the Rule Table and respond through AddRuleResp.

3) EnableRule:

After the Client calls this method, it will send a request to the server to request the activation of a certain rule. For example, the request carries the Rule Id of a rule added previously to enable this rule. After receiving the request to enable the rule, the server can subscribe to the input attributes of the enabled rule. After receiving the reported information of the corresponding attribute, it will compare the triggering conditions to determine whether to trigger the rule. If the rule is triggered, the corresponding device will be called. a scene on. This method initiates rule management so that devices can work together without user intervention. Implement the function of regular scenarios. The server can feed back the result of rule activation to the client by calling EnableRuleResp.

4)ViewRule:

After the Client calls this method, it will send a request to the server, and the server will return the existing rule information in the Rule Table. The returned information can be sent by calling ViewRuleResp.

5)RemoveRule:

After the Client calls this method, it will send a request to the server to remove a certain rule. After the rule is removed, the subsequent effects will disappear. Removal results can be sent by the server by calling RemoveRuleResp.

6)RemoveAllRule:

After the Client calls this method, it will send a request to the server to remove all rules. Removal results can be sent by the server by calling RemoveAllRuleResp.

In one possible implementation, the target rule includes the following information:

Identification information of the first device, identification information of the first attribute, trigger conditions, and scene information of the target scene.

In a possible implementation manner, the identification information of the first device includes: node identification information of the first device, and endpoint identification information corresponding to the first attribute in the first device.

In a possible implementation, the identification information of the first attribute includes: cluster identification information of the first attribute and an attribute ID (Attribute ID) of the first attribute; the cluster identification information is used to indicate the cluster to which the first attribute belongs.

In a possible implementation, triggering conditions include:

The target attribute value corresponding to the first attribute; and, when the trigger condition is established, the relationship between the target attribute value and the attribute information of the first attribute.

For example, the relationship between the above-mentioned target attribute value and the attribute information of the first attribute may include a size relationship, a matching relationship, and so on.

Step 703: The first device sends the attribute information of the first attribute of the first device to the central node device; the central node device receives the attribute information of the first attribute sent by the first device.

In an exemplary solution of the embodiment of this application, after the management device configures the target rule on the central node device, or after the management device configures the target rule on the central node device and activates it, the central node device can send a request to the first The device subscribes to the attribute information of the first attribute, and accordingly, the first device periodically/aperiodically sends its attribute information of the first attribute to the central node device.

Step 704: The central node device queries the first cluster for a target rule using the first attribute of the first device as input.

Because the target rule includes the first attribute of the first device, the trigger condition, and the scene information of the target scene. Therefore, in this embodiment of the present application, after the central node device receives the attribute information of the first attribute sent by the first device, it can query the above-mentioned target rule in the first cluster with the first attribute of the first device as input, and obtain the target Scenarios and their triggering conditions.

Step 705: If the attribute information of the first attribute of the first device satisfies the trigger condition of the target scene, send a control instruction to the second device corresponding to the target scene; the second device receives the control instruction.

In this embodiment of the present application, when the central node device determines that the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, the central node device may send a message to the second device corresponding to the target scene according to the scene information of the target scene. Control instructions to trigger the target scene.

In a possible implementation, when the attribute information of the first attribute of the first device meets the triggering condition of the target scenario and the target rule is in an enabled state, the control instruction is sent to the second device.

In the embodiment of the present application, when the target rule has an enabled state/non-enabled state, and the central node device determines that the attribute information of the first attribute of the first device satisfies the triggering condition of the target scenario, the central node device may also check Whether the target rule is enabled, and if the target rule is enabled, send the control instruction to the second device.

Or, in another possible implementation, when the target rule is in the enabled state, the central node device subscribes to the first device for attribute information of the first attribute; conversely, when the target rule is in the non-enabled state , the central node device may stop subscribing to the first device for the attribute information of the first attribute.

Step 706: The second device adjusts the attribute information of the second attribute of the second device according to the control instruction to achieve the target scenario.

In a possible implementation manner, the scene information of the target scene includes at least one of scene identification information of the target scene and a scene group identification of the target scene. Correspondingly, when the attribute information of the first attribute of the first device meets the triggering condition of the target scene, the central node device can send a scene cluster calling instruction to the second device; the scene cluster calling instruction is used to instruct the second device to call The target scene configured in the scene cluster in the second device is used to adjust the attribute information of the second attribute of the second device.

In a possible solution of the embodiment of this application, the central node device can combine the first cluster and the scene cluster to implement the automatic triggering function of the scene. That is to say, after the central node device determines that the target scene is triggered through the first cluster, it can trigger the second device to adjust the attribute information of the second attribute according to the target scene set in the scene cluster by calling the method of the scene cluster.

For example, in a possible implementation of the embodiment of this application, a RuleManager Cluster (ie, the above-mentioned first cluster) can be added to the Internet of Things on the basis of the scene cluster for rule management. RuleManager Cluster represents the function of rule management. The functions of this Cluster on the client side (such as being set in the APP of the management device) include setting rules, and the function of the server side (such as being set in the central node device) includes executing rules. In other words, the functions of RuleManager Cluster are composed of the functions of RuleManager client and the functions of RuleManager server.

In the embodiment of this application, the above-mentioned RuleManager provides attributes and methods to set rules, start rules, and implement rule operations. For the method part, please refer to Table 2 above.

On the server side of RuleManager, a rule table (Rule Table) can be maintained. The Rule Table records all the set rules. The client side of RuleManager sets and starts the rules, and the server side of RuleManager implements the management of rule scenarios.

Among them, the classification of the above-mentioned RuleManager Cluster can be shown in Table 3 below.

table 3

Hierarchy(层级)Hierarchy	RoleRole	PICS CodePICS Code	Primary TransactionPrimary Transaction
BaseBase	ApplicationApplication	RR	Type 1(client to server)Type 1(client to server)

The hierarchy column in Table 3 above indicates that the cluster is a basic cluster, and the role column indicates that the cluster is an application cluster. PICS code indicates that the abbreviation of this cluster is R. The Primary Transaction column indicates that the main control direction of this cluster is from Client to Server.

The cluster definition of the above RuleManager Cluster can be shown in Table 4 below.

Table 4

IdentifierIdentifier	NameName
0x10050x1005	RuleManagerRuleManager

Among them, the implementation of the above-mentioned RuleManager cluster needs to rely on the Scene cluster; that is to say, the endpoint that implements the RuleManager cluster also needs to implement the Scene cluster.

The server side of the above-mentioned RuleManager Cluster maintains a Rule Table. The rule table stores each rule set by the Client and is executed by the Server. The information contained in each rule in the rule table of the above-mentioned RuleManager Cluster cluster can be shown in Table 5 below.

table 5

Among them, the IsEnable information in the above Table 5 indicates whether the corresponding rule is in an enabled state; the RuleInputNodeId and RuleInputEndpointId in the above Table 5 correspond to the identification information of the above first device; the RuleInputClusterId in the above Table 5 corresponds to the identification information of the above first attribute; RuleValue and RuleRelation in the above Table 5 correspond to the above trigger conditions; SceneNodeId and SceneEndpointId in the above Table 5 correspond to the identification information of the above second device; SceneId in the above Table 5 corresponds to the scene information of the above target scene.

In addition, in addition to string, the type of RuleValue in Table 5 above can also be a type such as numerical value, Boolean, etc. that can perform threshold comparison.

The attributes of the above-mentioned RuleManager Cluster cluster can be shown in Table 6 below.

Table 6

IDID	NameName	TypeType	ConstraintConstraint	DefaultDefault	AccessAccess	ConformanceConformance
0x00000x0000	RuleCountRuleCount	Uint8Uint8	allall	00	RVRV	MM
0x00010x0001	NameSupportNameSupport	Map8Map8	descdesc	00	RVRV	MM

RuleCount in Table 6 above is used to indicate how many Rules there are in the Rule Table.

NameSupport in Table 6 above is used to indicate whether this RuleManager Cluster supports setting RuleName.

Taking the rule information contained in Table 5 as an example, please refer to Figure 8, which shows a schematic diagram of a device control framework involved in the embodiment of the present application. As shown in Figure 8, the device control process can be as follows:

The Server side of RuleManager Cluster can be placed on a device similar to the home hub (that is, the above-mentioned central node device), or the Server side can be placed in a mobile APP. This device has information about other devices and can subscribe to and control them. Other devices include reporting devices and controlled devices. The reporting device is mainly responsible for sending changes to its own attributes, while the controlled devices can be controlled. Both can use one physical device or multiple physical devices. The client of RuleManager Cluster can be located on the user APP. When the user wants to use the rule scenario function, the Client of the RuleManager Cluster first requests the existing device information from the RuleManager Server. Based on the received information, the Client sets and adds rules and sends them to the Server. After the Server receives the information, Add rules to the Rule Table. After a rule is enabled by the Client, the Server will subscribe to the device attributes input by the corresponding rule. When notification information is sent back to the Server, the Server will compare it with the Rule Table to see whether a certain rule is triggered. If If triggered, the corresponding scene on the corresponding device is called according to the rules. The Scene Cluster function allows home hub devices to trigger scenes set on one or more devices, controlled by the SceneGroupID in the Scene Table. Achieve linkage between devices without user operation.

For example, suppose the user wants to automatically turn on the air conditioner and fan when the temperature is greater than 30 degrees. You can first use the function settings of Scene Cluster to set turning on the air conditioner and turning on the fan as a scene. Then use the RuleManager Cluster function. Set this rule. After activating this rule. RuleManager Server will subscribe to the temperature sensor. When the temperature sensor's reported degree is greater than 30, the RuleManager Server will determine that this rule is triggered, and will call the Scene Client to send instructions to the corresponding Scene Server to call the scene of turning on the air conditioner and turning on the fan. Realize automated linkage between devices.

Taking the application to the Matter protocol as an example, through the solution shown in Figure 8 above, after adding the RuleManager Cluster, Matter has a mechanism for setting rules and autonomous linkage between devices. It makes up for the defect that the scene function provided by Scene Cluster can only realize scene control and cannot set rules to trigger automatically. By adding the Cluster method of RuleManager, devices can work autonomously and collaboratively, making them more intelligent.

In another possible implementation, the scene information of the target scene includes node identification information of the second device, endpoint identification information of the second device corresponding to the second attribute, attribute identification information of the second attribute, and the target attribute value; When the attribute information of the first attribute of the first device satisfies the triggering condition of the target scenario, the central node device may send a request to the third device based on the node identification information of the second device and the endpoint identification information of the second device corresponding to the second attribute. The second device sends an attribute adjustment instruction; the attribute adjustment instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device according to the attribute identification information of the second attribute and the target attribute value.

In another possible implementation solution of the embodiment of this application, RuleManager Cluster can also independently implement the functions of Scene Cluster. Make the function of RuleManager not dependent on Scene Cluster. At this time, each rule in the Rule Table of RuleManager can contain information as shown in Table 7 below.

Table 7

Taking the rule information contained in Table 7 as an example, please refer to Figure 9, which shows a schematic diagram of a device control framework involved in the embodiment of the present application. As shown in Figure 9, the device control process can be as follows:

The Server side of RuleManager Cluster can be placed on a device similar to a home hub, or the Server side can be placed in a mobile APP client. This device has information about other devices and can subscribe to and control them. Other devices include reporting devices or controlled devices. The reporting device is mainly responsible for sending changes to its own attributes, while the controlled device can be controlled by the client. Both can use one physical device or multiple physical devices. The client can be located on the user client APP. When the user wants to use the rule scenario function, the Client of the RuleManager first requests the existing device information from the Server of the RuleManager. Based on the received information, the Client sets and adds rules and sends them to the Server. After the Server receives the information, it will Rules are added to the Rule Table. After a rule is enabled by the Client, the Server will subscribe to the device attributes input by the corresponding rule. When notification information is sent back to the Server, the Server will compare it with the Rule Table to see whether a certain rule is triggered. If Triggered, control and change the attribute values of the corresponding device or a group of devices based on the SceneMessages information in the RuleTable. Realize automatic linkage between devices.

Please refer to FIG. 10 , which shows a block diagram of a device control device provided by an embodiment of the present application. The device has the function of being executed by the central node device in implementing the method shown in FIG. 2 or FIG. 7 . As shown in Figure 10, the equipment control device 1000 may include:

The receiving module 1001 is configured to receive attribute information of the first attribute sent by the first device;

The sending module 1002 is configured to send a control instruction to the second device corresponding to the target scene when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene; the control instruction is used to Instruct the second device to adjust the attribute information of the second attribute of the second device to achieve the target scenario.

In a possible implementation, the device further includes:

A query module configured to query the target rule in the first cluster with the first attribute of the first device as input before the sending module sends a control instruction to the second device corresponding to the target scenario; the target The rule is used to indicate an association relationship between the first attribute of the first device, the trigger condition, and the scene information of the target scene.

In a possible implementation, the target rule includes the following information:

The identification information of the first device, the identification information of the first attribute, the trigger condition, and the scene information of the target scene.

In a possible implementation manner, the identification information of the first device includes: node identification information of the first device, and endpoint identification information of the first device corresponding to the first attribute.

In a possible implementation, the identification information of the first attribute includes: cluster identification information of the first attribute; and the cluster identification information is used to indicate the cluster to which the first attribute belongs.

In a possible implementation, the triggering conditions include:

In a possible implementation, the identification information of the second device includes:

In a possible implementation manner, the scene information of the target scene includes at least one of scene identification information of the target scene and a scene group identification of the target scene.

In a possible implementation, the sending module is configured to send a scene cluster calling instruction to the second device when the attribute information of the first attribute of the first device meets the triggering condition of the target scene. ; The scene cluster calling instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device by calling the target scene configured in the scene cluster in the second device.

In a possible implementation, the scene information of the target scene includes node identification information of the second device, endpoint identification information of the second device corresponding to the second attribute, the second attribute attribute identification information and target attribute value;

The sending module 1002 is configured to: when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, the sending module 1002 is configured to: according to the node identification information of the second device, the second device and the third Send an attribute adjustment instruction to the second device based on the endpoint identification information corresponding to the two attributes; the attribute adjustment instruction is used to instruct the second device to adjust the attribute according to the attribute identification information of the second attribute and the target attribute value. Attribute information of the second attribute of the second device.

In a possible implementation, the receiving module is further configured to receive an add rule instruction sent by the management device before receiving the attribute information of the first attribute sent by the first device; the add rule instruction includes the Rule information of the target rule;

The device also includes:

An adding module, configured to add the target rule in the first cluster according to the rule information of the target rule.

In a possible implementation, the receiving module is further configured to receive the target rule sent by the management device before the sending module sends a control instruction to the second device corresponding to the target scenario. Rule enablement instructions;

The device also includes:

A status setting module, configured to set the target rule to an enabled status according to the rule enabling instruction of the target rule;

The sending module is configured to send the control instruction to the second device when the attribute information of the first attribute of the first device meets the triggering condition of the target scenario and the target rule is in an enabled state. .

In a possible implementation, the receiving module is also configured to receive a rule deactivation instruction of the target rule sent by the management device;

The status setting module is also configured to set the target rule to a non-enabled state according to the rule deactivation instruction of the target rule.

In a possible implementation, the receiving module is also used to receive information acquisition instructions sent by the management device;

The sending module is also configured to send the device information of each Internet of Things device connected to the central node device to the management device according to the information acquisition instruction; each of the Internet of Things devices includes the first device and the second device.

In a possible implementation, the receiving module is also configured to receive a rule viewing instruction sent by the management device;

The sending module is also configured to send rule information of each rule in the first cluster to the management device according to the rule viewing instruction.

In a possible implementation, the receiving module is also configured to receive a rule removal instruction of the first rule sent by the management device; the first rule is part or all of the rules in the first cluster;

The apparatus further includes: a removal module configured to remove the first rule from the first cluster according to a rule removal instruction of the first rule.

Please refer to FIG. 11 , which shows a block diagram of a device control device provided by an embodiment of the present application. The device has the function of implementing the method performed by the management device in the above-mentioned method shown in FIG. 6 or FIG. 7 . As shown in Figure 11, the equipment control device 1100 may include:

Sending module 1101, configured to send an add rule instruction to the central node device; the add rule instruction includes rule information of a target rule; the target rule takes the first attribute of the first device as input, and the target rule Used to indicate the association between the first attribute of the first device, the trigger condition and the scene information of the target scene;

In a possible implementation, the sending module is further configured to send a rule enabling instruction of the target rule to the central node device; the rule enabling instruction is used to instruct the central node device to send the target rule to the central node device. The rule is set to enabled.

In a possible implementation, the sending module is further configured to send a rule deactivation instruction of the target rule to the central node device; the rule deactivation instruction is used to instruct the central node device to The above target rule is set to inactive state.

In a possible implementation, the sending module is also configured to send an information acquisition instruction to the central node device;

The device further includes: a first receiving module, configured to receive the device information of each Internet of Things device connected to the central node device sent by the central node device; each of the Internet of Things devices includes the first device and said second device.

In a possible implementation, the sending module is also configured to send a rule viewing instruction to the central node device;

The device further includes: a second receiving module, configured to receive the rule information of each rule in the first cluster sent by the central node device.

In a possible implementation, the sending module is also configured to send a rule removal instruction of a first rule to the central node device; the first rule is part or all of the rules in the first cluster. ; The rule removal instruction of the first rule is used to instruct the central node device to remove the first rule from the first cluster.

Please refer to FIG. 12 , which shows a block diagram of a device control device provided by an embodiment of the present application. The device has the function of realizing the function performed by the first device in the method shown in FIG. 3 or FIG. 7 . As shown in Figure 12, the equipment control device 1200 may include:

The sending module 1201 is configured to send the attribute information of the first attribute of the first device to the central node device, so that the attribute information of the first attribute of the first device of the central node device satisfies the triggering condition of the target scene. when, sending a control instruction to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device to realize the target scene.

Please refer to Figure 13, which shows a block diagram of a device control device provided by an embodiment of the present application. The device has the function of realizing the function performed by the second device in the method shown in FIG. 4 or FIG. 7 . As shown in Figure 13, the equipment control device 1300 may include:

The receiving module 1301 is configured to receive a control instruction sent by the central node device; the control instruction is that the central node device receives the attribute information of the first attribute sent by the first device, and adds the attribute information to the first attribute of the first device. An instruction sent when the attribute information satisfies the trigger condition of the target scene; the target scene is the scene corresponding to the second device;

The adjustment module 1302 is configured to adjust the attribute information of the second attribute of the second device according to the control instruction to achieve the target scenario.

It should be noted that when the device provided in the above embodiment implements its functions, only the division of the above functional modules is used as an example. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.

Regarding the devices in the above embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Please refer to Figure 14, which shows a schematic structural diagram of a computer device 1400 provided by an embodiment of the present application. The computer device 1400 may include a processor 1401, a receiver 1402, a transmitter 1403, a memory 1404, and a bus 1405.

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

The receiver 1402 and the transmitter 1403 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 1404 is connected to processor 1401 through bus 1405.

The memory 1404 can be used to store a computer program, and the processor 1401 is used to execute the computer program to implement various steps performed by the central node device, the management device, the first device or the second device in the above method embodiment.

Additionally, memory 1404 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.

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 Figure 2, Figure 3, Figure 4, Figure 6 or In the method shown in Figure 7, all or part of the steps are performed by the central node device, the management device, 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 Figure 2, Figure 3, Figure 4, Figure 6 or Figure 7, by the central node device, All or part of the steps performed by the management device, 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, so that the computer device performs the method shown in Figure 2, Figure 3, Figure 4, Figure 6 or Figure 7, by All or part of the steps performed by the central node device, the management device, 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 Figure 2, Figure 3, Figure 4, Figure 6 or Figure 7, by the central node device, management All or part of the steps performed by the device, the first device or the second device.

Those skilled in the art should realize that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

The above are only exemplary embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims

A device control method, characterized in that the method is executed by a central node device in the Internet of Things, and the method includes:

Receive attribute information of the first attribute sent by the first device;

When the attribute information of the first attribute of the first device meets the triggering condition of the target scene, send a control instruction to the second device corresponding to the target scene; the control instruction is used to instruct the second device Adjust the attribute information of the second attribute of the second device to achieve the target scenario.
The method according to claim 1, characterized in that, when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, sending the message to the second device corresponding to the target scene. Before the control instruction, it also includes:

Query the target rule in the first cluster that takes the first attribute of the first device as input; the target rule is used to indicate the first attribute of the first device, the trigger condition, and the scene information of the target scene. relationship between them.
The method according to claim 2, characterized in that the target rules include the following information:

The identification information of the first device, the identification information of the first attribute, the trigger condition, and the scene information of the target scene.
The method of claim 3, wherein the identification information of the first device includes: node identification information of the first device, and an endpoint identification of the first device corresponding to the first attribute. information.
The method according to claim 3, wherein the identification information of the first attribute includes: cluster identification information of the first attribute; and the cluster identification information is used to indicate the cluster to which the first attribute belongs.
The method according to claim 3, characterized in that the triggering condition includes:

The target attribute value corresponding to the first attribute; and, when the trigger condition is established, the relationship between the target attribute value and the attribute information of the first attribute.
The method according to any one of claims 3 to 6, characterized in that the scene information of the target scene includes at least one of scene identification information of the target scene and a scene group identification of the target scene.
The method according to claim 7, characterized in that, when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, sending the message to the second device corresponding to the target scene. Control instructions include:

When the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, a scene cluster calling instruction is sent to the second device; the scene cluster calling instruction is used to instruct the second device to pass The target scene configured in the scene cluster in the second device is called to adjust the attribute information of the second attribute of the second device.
The method according to any one of claims 3 to 6, characterized in that the scene information of the target scene includes node identification information of the second device, an endpoint in the second device corresponding to the second attribute Identification information, attribute identification information of the second attribute and target attribute value;

If the attribute information of the first attribute of the first device meets the triggering condition of the target scene, sending a control instruction to the second device corresponding to the target scene includes:

When the attribute information of the first attribute of the first device satisfies the triggering condition of the target scenario, based on the node identification information of the second device and the endpoint identification information of the second device corresponding to the second attribute, Send an attribute adjustment instruction to the second device; the attribute adjustment instruction is used to instruct the second device to adjust the second attribute of the second device according to the attribute identification information of the second attribute and the target attribute value. Property information for the property.
The method according to any one of claims 2 to 9, characterized in that before receiving the attribute information of the first attribute sent by the first device, it further includes:

Receive an add rule instruction sent by the management device; the add rule instruction includes rule information of the target rule;

Add the target rule in the first cluster according to the rule information of the target rule.
The method according to any one of claims 2 to 10, characterized in that, in the case where the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, the method corresponding to the target scene is Before the second device sends the control command, it also includes:

Receive the rule activation instruction of the target rule sent by the management device;

Set the target rule to an enabled state according to the rule enabling instruction of the target rule;

If the attribute information of the first attribute of the first device meets the triggering condition of the target scene, sending a control instruction to the second device corresponding to the target scene includes:

When the attribute information of the first attribute of the first device meets the triggering condition of the target scenario and the target rule is in an enabled state, the control instruction is sent to the second device.
The method according to claim 11, characterized in that, the method further includes:

Receive the rule deactivation instruction of the target rule sent by the management device;

Set the target rule to a non-enabled state according to the rule deactivation instruction of the target rule.
The method according to any one of claims 2 to 12, characterized in that the method further includes:

Receive information acquisition instructions sent by the management device;

According to the information acquisition instruction, send the device information of each Internet of Things device connected to the central node device to the management device;

Each of the Internet of Things devices includes the first device and the second device.
The method according to any one of claims 2 to 13, characterized in that the method further includes:

Receive rule viewing instructions sent by the management device;

According to the rule viewing instruction, the rule information of each rule in the first cluster is sent to the management device.
The method according to any one of claims 2 to 14, characterized in that the method further includes:

Receive the rule removal instruction of the first rule sent by the management device; the first rule is part or all of the rules in the first cluster;

The first rule is removed from the first cluster according to a rule removal instruction of the first rule.
A device control method, characterized in that the method is executed by a management device in the Internet of Things, and the method includes:

Send an add rule instruction to the central node device; the add rule instruction includes rule information of a target rule; the target rule takes the first attribute of the first device as input, and the target rule is used to indicate the third The association between the first attribute of a device, the trigger condition and the scene information of the target scene;

Wherein, the add rule instruction is used to instruct the central node device to add the target rule in the first cluster, so that the central node device obtains the attribute information of the first attribute of the first device, and When the attribute information of the first attribute of the first device satisfies the trigger condition, a control instruction is sent to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the first attribute information of the second attribute of the two devices to achieve the target scenario.
The method of claim 16, further comprising:

Send a rule enabling instruction of the target rule to the central node device; the rule enabling instruction is used to instruct the central node device to set the target rule to an enabled state.
The method according to claim 16 or 17, characterized in that, the method further includes:

Send a rule deactivation instruction of the target rule to the central node device; the rule deactivation instruction is used to instruct the central node device to set the target rule to a non-enabled state.
The method according to any one of claims 16 to 18, characterized in that the method further includes:

Send information acquisition instructions to the central node device;

Receive device information of each Internet of Things device connected to the central node device sent by the central node device; each of the Internet of Things devices includes the first device and the second device.
The method according to any one of claims 16 to 19, characterized in that the method further includes:

Send a rule viewing instruction to the central node device;

Receive rule information of each rule in the first cluster sent by the central node device.
The method according to any one of claims 16 to 20, characterized in that the method further includes:

Send a rule removal instruction of the first rule to the central node device; the first rule is part or all of the rules in the first cluster; the rule removal instruction of the first rule is used to instruct the center A node device removes the first rule from the first cluster.
A device control method, characterized in that the method is executed by a first device in the Internet of Things, and the method includes:

Send the attribute information of the first attribute of the first device to the central node device, so that when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, the central node device sends the attribute information to the central node device. The second device corresponding to the target scene sends a control instruction; the control instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device to realize the target scene.
A device control method, characterized in that the method is executed by a second device in the Internet of Things, and the method includes:

Receive a control instruction sent by the central node device; the control instruction is that the central node device receives the attribute information of the first attribute sent by the first device, and when the attribute information of the first attribute of the first device meets the target scenario An instruction sent when a condition is triggered; the target scene is a scene corresponding to the second device;

The attribute information of the second attribute of the second device is adjusted according to the control instruction to realize the target scenario.
An equipment control device, characterized in that the device includes:

A receiving module, configured to receive attribute information of the first attribute sent by the first device;

A sending module configured to send a control instruction to the second device corresponding to the target scene when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene; the control instruction is used to indicate The second device adjusts the attribute information of the second attribute of the second device to realize the target scenario.
The device according to claim 24, characterized in that the device further includes:

A query module configured to query the first cluster for a target rule using the first attribute of the first device as input before the sending module sends a control instruction to the second device corresponding to the target scenario; the target rule Used to indicate the association between the first attribute of the first device, the trigger condition and the scene information of the target scene.
The device according to claim 25, wherein the target rule includes the following information:

The identification information of the first device, the identification information of the first attribute, the trigger condition, and the scene information of the target scene.
The apparatus according to claim 26, wherein the identification information of the first device includes: node identification information of the first device, and an endpoint identification of the first device corresponding to the first attribute. information.
The device according to claim 26, wherein the identification information of the first attribute includes: cluster identification information of the first attribute; and the cluster identification information is used to indicate the cluster to which the first attribute belongs.
The device according to claim 25, wherein the trigger condition includes:

The target attribute value corresponding to the first attribute; and, when the trigger condition is established, the relationship between the target attribute value and the attribute information of the first attribute.
The device according to any one of claims 26 to 29, wherein the scene information of the target scene includes at least one of scene identification information of the target scene and a scene group identification of the target scene.
The device according to claim 30, characterized in that the sending module is configured to send the attribute information of the first attribute of the first device to the second device when the attribute information satisfies the triggering condition of the target scene. Scene cluster call instruction; the scene cluster call instruction is used to instruct the second device to adjust the second attribute of the second device by calling the target scene configured in the scene cluster in the second device. attribute information.
The device according to any one of claims 26 to 29, wherein the scene information of the target scene includes node identification information of the second device, an endpoint in the second device corresponding to the second attribute Identification information, attribute identification information of the second attribute and target attribute value;

The sending module is further configured to: when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene, according to the node identification information of the second device, the second device and the third Send an attribute adjustment instruction to the second device based on the endpoint identification information corresponding to the two attributes; the attribute adjustment instruction is used to instruct the second device to adjust the attribute according to the attribute identification information of the second attribute and the target attribute value. Attribute information of the second attribute of the second device.
The device according to any one of claims 25 to 32, wherein the receiving module is further configured to receive an add rule instruction sent by the management device before receiving the attribute information of the first attribute sent by the first device; The add rule instruction includes rule information of the target rule;

The device also includes:

An adding module, configured to add the target rule in the first cluster according to the rule information of the target rule.
The device according to any one of claims 25 to 33, characterized in that the receiving module is further configured to receive the management information before the sending module sends a control instruction to the second device corresponding to the target scene. The rule activation instruction of the target rule is sent by the device;

The device also includes:

A status setting module, configured to set the target rule to an enabled status according to the rule enabling instruction of the target rule;

The sending module is configured to send the control instruction to the second device when the attribute information of the first attribute of the first device meets the triggering condition of the target scenario and the target rule is in an enabled state. .
The device according to claim 34, wherein the receiving module is further configured to receive a rule deactivation instruction of the target rule sent by the management device;

The status setting module is also configured to set the target rule to a non-enabled state according to the rule deactivation instruction of the target rule.
The device according to any one of claims 25 to 35, characterized in that:

The receiving module is also used to receive information acquisition instructions sent by the management device;

The sending module is also configured to send the device information of each Internet of Things device connected to the central node device to the management device according to the information acquisition instruction; each of the Internet of Things devices includes the first device and the second device.
The device according to any one of claims 25 to 36, characterized in that,

The receiving module is also used to receive rule viewing instructions sent by the management device;

The sending module is also configured to send rule information of each rule in the first cluster to the management device according to the rule viewing instruction.
The device according to any one of claims 25 to 37, characterized in that:

The receiving module is also configured to receive the rule removal instruction of the first rule sent by the management device; the first rule is part or all of the rules in the first cluster;

The device also includes:

A removal module configured to remove the first rule from the first cluster according to the rule removal instruction of the first rule.
An equipment control device, characterized in that the device includes:

A sending module, configured to send an add rule instruction to the central node device; the add rule instruction includes rule information of a target rule; the target rule takes the first attribute of the first device as input, and the target rule is Indicating the association between the first attribute of the first device, the trigger condition and the scene information of the target scene;

Wherein, the add rule instruction is used to instruct the central node device to add the target rule in the first cluster, so that the central node device obtains the attribute information of the first attribute of the first device, and When the attribute information of the first attribute of the first device satisfies the trigger condition, a control instruction is sent to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the first attribute information of the second attribute of the two devices to achieve the target scenario.
The apparatus according to claim 39, wherein the sending module is further configured to send a rule activation instruction of the target rule to the central node device; the rule activation instruction is used to instruct the central node device to Set the target rule to enabled.
The device according to claim 38 or 39, characterized in that the sending module is further configured to send a rule deactivation instruction of the target rule to the central node device; the rule deactivation instruction is used to instruct the The central node device sets the target rule to a non-enabled state.
The device according to any one of claims 39 to 41, characterized in that the sending module is also used to send information acquisition instructions to the central node device;

The device also includes:

The first receiving module is used to receive the device information of each Internet of Things device connected to the central node device sent by the central node device; each of the Internet of Things devices includes the first device and the second device. .
The device according to any one of claims 39 to 42, characterized in that the sending module is also used to send a rule viewing instruction to the central node device;

The device also includes:

The second receiving module is configured to receive the rule information of each rule in the first cluster sent by the central node device.
The device according to any one of claims 39 to 43, wherein the sending module is further configured to send a rule removal instruction of the first rule to the central node device; the first rule is the third rule. Some or all rules in a cluster; the rule removal instruction of the first rule is used to instruct the central node device to remove the first rule from the first cluster.
An equipment control device, characterized in that the device includes:

A sending module, configured to send the attribute information of the first attribute of the first device to the central node device, so that the central node device can satisfy the triggering condition of the target scene when the attribute information of the first attribute of the first device satisfies the triggering condition of the target scene. , sending a control instruction to the second device corresponding to the target scene; the control instruction is used to instruct the second device to adjust the attribute information of the second attribute of the second device to realize the target scene.
An equipment control device, characterized in that the device includes:

A receiving module, configured to receive a control instruction sent by the central node device; the control instruction is that the central node device receives the attribute information of the first attribute sent by the first device, and adds the attribute information of the first attribute to the first device. An instruction sent when the information satisfies the trigger condition of the target scene; the target scene is the scene corresponding to the second device;

An adjustment module, configured to adjust the attribute information of the second attribute of the second device according to the control instruction to achieve a target scenario.
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 device control method as shown in any one of the above claims 1 to 23.
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 device control method as shown in any one of claims 1 to 23.
A chip, characterized in that the chip is used to run in a computer device, so that the computer device executes the device control method as shown in any one of claims 1 to 23.
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 device control method as shown in any one of claims 1 to 23.
A computer program, characterized in that the computer program is executed by a processor of a computer device to implement the device control method as shown in any one of claims 1 to 23.