WO2023173872A2

WO2023173872A2 - Configuration method for multi-vendor integrated environment based on smart home client end

Info

Publication number: WO2023173872A2
Application number: PCT/CN2022/141025
Authority: WO
Inventors: 李波
Original assignee: 深圳市华曦达科技股份有限公司
Priority date: 2022-03-14
Filing date: 2022-12-22
Publication date: 2023-09-21
Also published as: CN114422285A; WO2023173872A3; CN114422285B

Abstract

The present invention provides a configuration method for a multi-vendor integrated environment based on a smart home client end, the method comprising: obtaining, from a server, user device set information that matches the identity of a user; analyzing the acquired device set information, establishing a data logic relationship for each device in the device set under different resource applications, and storing the data logic relationships in a cache; creating an integrated environment, adding execution tasks, obtaining a device that meets a task condition by traversing the data logic relationships, and establishing a task-device set, the task device set comprising an execution task ID and a task-device list; allocating different execution tasks to devices in the task-device set to generate integrated environment data; and transmitting the integrated environment data to a server, thereby completing the configuration of the integrated environment for multi-vendor smart home devices.

Description

A configuration method based on smart home client multi-vendor integration scenarios

Technical field

The present invention relates to the field of smart home technology, and specifically relates to a configuration method based on a smart home client multi-vendor integration scenario.

Background technique

Smart home is the embodiment of the Internet of Things under the influence of the Internet. Smart homes use Internet of Things technology to connect various devices in the home (such as audio and video equipment, lighting systems, curtain controls, air conditioning controls, security systems, digital cinema systems, audio and video servers, movie cabinet systems, network appliances, etc.) to provide Various functions and methods include home appliance control, lighting control, telephone remote control, indoor and outdoor remote control, anti-theft alarm, environmental monitoring, HVAC control, infrared forwarding and programmable timing control. Compared with ordinary homes, smart homes not only have traditional living functions, but also have construction, network communications, information appliances, and equipment automation, provide a full range of information interaction functions, and even save money on various energy costs.

Smart homes realize the intelligence of the whole house. After years of development, my country's smart home industry has entered the 2.0 smart interconnection stage. The industry market size shows a good growth trend. However, as more and more manufacturers join, the smart home industry is also facing Here comes a new challenge. Each manufacturer is establishing and developing its own smart ecosystem, which has led to the following disadvantages: It is difficult or almost impossible for existing smart terminal products that do not go through the manufacturer to communicate with each other. Once the user selects a smart product, In the future, you will not be able to choose better products from other manufacturers, and the limitations are very large; the client cannot be configured for multi-vendor integration scenarios, and can only configure its own products. As a result, a home user often needs to download multiple clients to meet daily needs and has considerable control. Trouble is, different devices cannot be linked directly, which is far from the original intention of smart home.

Contents of the invention

In view of this, the present invention provides a configuration method based on the smart home client multi-vendor integration scenario, which realizes the linkage and triggering of different work tasks of multiple devices of different manufacturers under current smart home users, and solves the traditional problem of It requires multiple clients or APPs to configure and control each manufacturer's equipment one by one, which is cumbersome and solves the technical problem that different devices from different manufacturers cannot be directly linked.

The technical solution of the present invention is as follows:

A configuration method for smart home client multi-vendor integration scenarios, applied to the client, including:

Send a device set information acquisition request message to the server, where the device set information acquisition request message includes user identity information; receive user device set information returned by the server; devices in the device set belong to different manufacturers;

Analyze the obtained device set information, establish data logical relationships under different resource applications for each device in the device set, and save it to the cache;

Create a fusion scenario, add execution tasks, obtain equipment that meets the task conditions by traversing the data logical relationship, and establish a task equipment set; the task equipment set includes an execution task ID and a task equipment list; for the task equipment set The device assigns different execution tasks and generates fusion scene data;

Transmit the fusion scene data to the server.

Preferably, the method of obtaining equipment that meets task conditions and establishing a task equipment set includes:

Display devices that meet the task conditions, receive user selections, and establish a task device set based on the devices selected by the user for the task conditions.

Preferably, the device set information obtained by the analysis is used to establish data logical relationships under different resource applications for each device in the device set, including:

Obtain the client's smart home gateway information; for each gateway information, establish the parent object model GatewayModel, the first child object model DeviceModel of the parent object model GatewayModel, and the second child object model DevicePointModel of the first child object model DeviceModel;

The first child object model DeviceModel is a child object of the parent object model GatewayModel; the second child object model DevicePointModel is a child object of the first child object model DeviceModel.

Preferably, the device set information obtained by the analysis is used to establish a data logical relationship under different resource applications for each device in the device set, and further includes:

Initialize the parent object model GatewayModel, which is used to store gateway attribute data;

Initialize the first sub-object model DeviceModel, which stores the attribute data of the corresponding device under the smart home gateway, and puts the first sub-object model DeviceModel into the parent object model GatewayModel;

Initialize the second sub-object model DevicePointModel. The second sub-object model DevicePointModel stores different resource node attribute data of the corresponding device and is added to the first sub-object model DeviceModel in the form of a collection.

Preferably, the fusion scenario is created, execution tasks are added, and devices that meet the task conditions are obtained by traversing the logical relationships of the data, including:

Create a scenario of integrated equipment and centralized equipment, and set task trigger conditions;

Create a scene execution task, traverse all device models of the parent object model GatewayModel, display devices that meet the conditions for executing the task, and save the mapping relationship between the scene execution task ID and the user-selected device set according to the user's selection;

To generate an execution task, traverse all the device models of the parent object model GatewayModel, select the devices that meet the conditions for executing the task, store the pre-created execution device collection, and display it.

Preferably, the task triggering conditions include: triggering the execution of the task according to the user's manual triggering information; and/or setting the trigger time to trigger the execution of the task when a certain trigger time is reached; and/or setting the first device to reach a certain condition. , triggering the second device to perform the task.

Preferably, allocating different execution tasks to the devices in the task device set and generating fusion scene data; transmitting the fusion scene data to the server includes:

Generate fusion scene data according to the execution task data, task triggering conditions and scene identifiers assigned by the equipment in the task equipment set;

The fusion scene data is encrypted and sent to the server.

In addition, a configuration method for smart home client multi-vendor integration scenarios is also proposed, which is applied to the server, including:

In response to the device set information acquisition request message sent by the client, obtain the device set information and send it to the client; the device set information acquisition request message includes user identity information; the devices in the device set belong to different manufacturers;

Receive the fusion scene data sent by the client and save it;

The fusion scenario data is generated in the following ways: parsing the device set information and establishing data logical relationships under different resource applications for each device in the device set; creating a fusion scenario, adding execution tasks, and traversing the data logical relationships, Obtain devices that meet the task conditions and establish a task device set; the task device set includes an execution task ID and a task device list; assign different execution tasks to the devices in the task device set and generate fusion scene data.

In addition, an electronic device is also proposed, including a memory and a processor. The memory stores instructions, and the processor executes the instructions to implement the above method steps.

In addition, a storage medium is also proposed, the storage medium stores a program; the program is loaded and executed by a processor to implement the method steps as described above.

In the solution of the present invention, based on the configuration method of the smart home client multi-vendor integration scenario, the user device set information that conforms to the user's identity is obtained from the server; and the obtained device set information is parsed to obtain each device in the device set. Establish data logical relationships under different resource applications and save them to the cache; further, create a fusion scenario, add execution tasks, obtain devices that meet the task conditions by traversing the data logical relationships, and establish a task device set; the task device set Including execution task ID and task device list; assigning different execution tasks to the devices in the task device set to generate fusion scenario data; transmitting the fusion scenario data to the server to complete the fusion scenario of smart home devices from multiple manufacturers Configuration, so that during the operation process of the client user, as long as the client is opened and the scene configured in the present invention is selected, the linkage and triggering of different work tasks of multiple devices of different manufacturers under the current smart home user can be realized. It solves the traditional tedious problem of requiring multiple clients or APPs to configure and control each manufacturer's devices one by one, and also solves the problem that different devices from different manufacturers cannot be directly linked.

Description of the drawings

Figure 1 is a flow chart of a configuration method for a smart home client multi-vendor integration scenario according to Embodiment 1 of the present invention;

Figure 2 is a flowchart showing a configuration method execution flow chart under manual triggering conditions in a multi-vendor integration scenario of a smart home client according to Embodiment 1 of the present invention;

Figure 3 is a flowchart showing the execution flow chart of the configuration method under timing trigger conditions in a smart home client multi-vendor integration scenario according to Embodiment 1 of the present invention;

Figure 4 is a flowchart showing the execution flow chart of the configuration method under device linkage triggering conditions in a smart home client multi-vendor integration scenario according to Embodiment 1 of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present invention.

Embodiment 1

As shown in Figure 1, this embodiment implements a configuration method for a smart home client multi-vendor integration scenario, which is applied to the client and includes:

S110. Send a device set information acquisition request message to the server, where the device set information acquisition request message includes user identity information; receive the user device set information returned by the server; the devices in the device set belong to different manufacturers;

Specifically, in this embodiment, the client architecture includes a user module, a device management module, and a scene configuration module. Among them, the user module is responsible for user login, registration and other management; the device management module: uniformly manages the gateway devices of various manufacturers and outputs a unified device model; the scene configuration module: the scene configuration module will store the devices of each manufacturer selected by the user. It is transmitted to the backend server through certain protocol rules. The user logs in through the account and password on the client, and sends a device set information acquisition request message to the server. The device set information acquisition request message carries the user identity account information; after receiving the user identity information, the server obtains the device set corresponding to the user. ; Here the user needs to add the devices under his own account in advance to form a device set under the user's identity; the devices in the device set belong to different manufacturers;

S120. Parse the obtained device set information, establish a data logical relationship under different resource applications for each device in the device set, and save it to the cache.

Further, the client receives the user device set information returned by the server, and the device management module parses the device sets of all manufacturers obtained by the user. By parsing the obtained device set information, a data logical relationship under different resource applications is established for each device in the device set, and is saved in the cache. After parsing the obtained device set information, a parent object model GatewayModel, a first sub-object model DeviceModel of the parent object model GatewayModel, and a second sub-object model DevicePointModel of the first sub-object model DeviceModel are established for each gateway information. Press The logical relationship is stored in the client memory; the first sub-object model DeviceModel is a sub-object of the parent object model GatewayModel; the second sub-object model DevicePointModel is a sub-object of the first sub-object model DeviceModel. For example: assume that the user owns a smart home gateway, and there is an intelligent three-way relay switch device under the gateway. The switch device has three resource nodes. Initialize the GatewayModel object and store the attribute data of the smart home gateway; initialize the DeviceModel object and store the attribute data of the smart home gateway in it. Store the attribute data of the intelligent three-way relay switch and put the DeviceModel object into the GatewayModel object. At this time, the DeviceModel object becomes a sub-object of the GatewayModel object. In the same way, initialize the DevicePointModel object to store the attribute data of a single resource node of the switch device and use The collection form is added to the DeviceModel object. At this time, the data structure is: DevicePointModel is a DeviceModel sub-object, and DeviceModel is a GatewayModel sub-object.

The device set information obtained by the analysis establishes data logical relationships under different resource applications for each device in the device set, and also includes: initializing a parent object model GatewayModel, and the parent object model GatewayModel is used to store gateway attribute data; Initialize the first sub-object model DeviceModel, which stores the attribute data of the corresponding device under the smart home gateway, and puts the first sub-object model DeviceModel into the parent object model GatewayModel; initialize the second sub-object model DevicePointModel, the second sub-object model DevicePointModel stores different resource node attribute data of the corresponding device, and is added to the first sub-object model DeviceModel in the form of a collection. Specifically, the attribute data of the smart home gateway includes gateway name, address and other information; the first sub-object model DeviceModel includes the name of the device, the mac address of the device, the uuid of the device, and the current status of the device (for example, for Light (whether the current status is on or off), the online status of the device; taking a light as an example, the second sub-object model DevicePointModel stores different resource node attribute data of the corresponding device, then for the sub-object model of the light, you can set Open, close, reverse (execute the control state opposite to the current state); then based on the description of different resource nodes of a three-way relay switch, the first resource node of the three-way relay switch can be allocated (1. Open ; 2. Close); The control of the second node is reversed to execute the control state opposite to the current state, etc.

Furthermore, this embodiment uses smart curtains from manufacturer A and smart lights from manufacturer B as examples. Among them, the established three-level logical relationship of the parent object model GatewayModel, the first sub-object model DeviceModel, and the second sub-object model DevicePointModel corresponds to To the specific application, for example, the home gateway corresponds to the parent object model GatewayModel; the first sub-object model DeviceModel includes smart home equipment such as lights and curtains; the second sub-object model DevicePointModel, for lights, includes: open, close, Or reverse (representing the opposite operation to the current state); for curtains, the second sub-object model DevicePointModel can have opening, closing, opening to a specified percentage, and closing to a specified percentage. Therefore, based on the design of this hierarchical logical relationship, this application can subsequently create and set different scenarios to control different devices from different manufacturers to perform different task operation controls.

S130. Create a fusion scenario, add execution tasks, obtain devices that meet task conditions by traversing the data logical relationship, and establish a task device set; the task device set includes execution task IDs and task device lists; for the task devices Centralized devices allocate different execution tasks and generate fusion scene data.

The task device set includes an execution task ID and a task device list; different execution tasks are assigned to the devices in the task device set to generate fusion scene data. Specifically, during the process of configuring the fusion scenario, the user can click to create the fusion scenario. The scenario configuration module will provide a concise and easy-to-understand page (Page A) to the user. The page includes: scenario name, trigger conditions, execution tasks, scenario icons, Appear on the home page, etc. Click to add a trigger condition, enter page B, select manual click and return to page A. At this time, the trigger condition changes to manual click, indicating that after the creation of this fusion scene is completed, the user must manually click or control the voice speaker to execute it.

Preferably, the step of creating a fusion scenario, adding an execution task, and traversing the data logical relationship to obtain devices that meet task conditions includes: creating a scenario in which the fusion device concentrates devices, setting task trigger conditions; creating a scenario to execute the task, and traversing the All device models of the parent object model GatewayModel display the devices that meet the conditions for executing the task, and according to the user's selection, save the mapping relationship between the scene execution task ID and the device set selected by the user; to generate an execution task, all device models of the parent object model GatewayModel are traversed, Select the equipment that meets the conditions for executing the task, save the pre-created execution equipment set, and display it.

Specifically, by clicking Add Execution Task and entering page C, the scene configuration module will take out the device set from the device management module, and loop the device set, traverse all device models under GatewayModel, and find the device that meets the conditions for executing the task ( Sensor devices such as smart door magnets and smart smoke alarms cannot be used to perform tasks; smart door locks, which are highly secure devices, cannot be used as execution devices). Save the pre-created execution device collection (ActionDeviceList) and list it by manufacturer. The UUID (VenderUuid) category is displayed to the user.

Preferably, the method of obtaining devices that meet the task conditions and establishing a task device set includes: displaying devices that meet the task conditions, receiving user selections, and establishing a task device set based on the devices selected by the user for the task conditions. Specifically, the user selects the device set he wants to execute and clicks the completion button to return to page A. The selected device set will appear in the execution task; for example, the user selects the first position of a three-way relay switch from manufacturer A. Resource node, smart curtains from manufacturer B. Click on a single execution device to enter page D and assign specific execution tasks to each execution device. The scene configuration module will assign different execution tasks according to different manufacturers and devices. For example, curtains can be assigned (1. Open; 2. Close; 3. , open to the specified percentage; 4. close to the specified percentage), the first resource node of the three-way relay switch can be allocated (1. open; 2. closed). Assume that the user selects the first resource node of the three-way relay switch to open, closes the curtain, clicks Finish, returns to page A, and assembles the correct DevicePointModel under each execution device into a fusion scene according to certain rules (the user manually clicks this button displayed on the APP The scene will execute the first one of the three-way relay switch of manufacturer A to open, and the smart curtain of manufacturer B to close) to execute the task data.

Based on the fusion scenario, a scene identifier and/or a scene name can be defined. After the configuration is completed, subsequent users can trigger the scenario startup as long as they meet certain trigger conditions, and the tasks corresponding to the scenario can be started, and then trigger The status of the device in the task list under the scenario is started. For example, we define that scene M is executed every 6 p.m., and the implementation defines scene M to close the curtains to a percentage of 80% and then turn on the lights; therefore, as long as the time condition of 6 p.m. is reached, based on the configuration of this embodiment, The gateway of the system can automatically close the curtains of manufacturer A to 80%, and then the curtain controller feedbacks a completion signaling to the gateway, and the gateway further controls the indoor lights to turn on the lights and receives the completion command, thereby achieving one-time integration. The use of scenes.

S140. Transmit the fusion scene data to the server.

Preferably, different execution tasks are assigned to the devices in the task device set, and fusion scenario data is generated; and the fusion scenario data is transmitted to the server, including: execution task data and task triggering assigned by the devices in the task device set. Conditions and scene identifiers to generate fusion scene data; the fusion scene data is encrypted and sent to the server. In this embodiment, the execution task data, trigger conditions, scene identifiers and other data are encrypted and then jointly transmitted to the server.

Further, the task triggering conditions include: triggering the execution of the task according to the user's manual triggering information; and/or setting the trigger time to trigger the execution of the task when a certain trigger time is reached; and/or setting the first device to reach a certain condition, Trigger the second device to perform the task. Specifically, Figure 2 shows the execution flow chart of the configuration method under manual triggering conditions. When manual triggering is selected, triggering can only be achieved through manual clicks, such as manual clicks or voice speaker control; specifically, the user Log in to the server through the account and password, and after verifying the user's identity, the server obtains the manufacturer's gateway and device under the user and returns it to the client. It parses and stores each manufacturer's device data through the client's device management module to obtain the device set; further, Create manual fusion scenarios through manual user clicks, select manual execution, select execution tasks, filter qualified device set data through traversal analysis, use ActionDeviceList collection storage, and display by VenderUuid classification, assign specific execution actions to execution devices, and assemble The fusion scene data is transmitted to the server.

Figure 3 shows the configuration method execution flow chart under scheduled trigger conditions. If scheduled trigger is selected, the user sets the trigger time. For example, the scene module determines whether the time is reasonable and is greater than three minutes of the current time. After completion, the trigger condition becomes has a scheduled trigger, indicating that after the creation of this integration scenario is completed, it will be executed when the time reaches the set trigger time; specifically, the user logs in to the server through the account and password, and after verifying the user's identity, the server obtains the manufacturer's gateway and device under the user. And return to the client, the device management module of the client parses and stores the device data of each manufacturer to obtain the device set; further, the user clicks to create a scheduled integration scenario, selects a scheduled trigger, and the user sets a specific time and sets the time through judgment Is it reasonable and greater than three minutes of the current time? If so, select the execution task, filter the qualified device set data through traversal analysis, use the ActionDeviceList collection to store, and display it according to the VenderUuid classification, and assign specific execution actions to the execution device to assemble it. The fusion scene data is transmitted to the server.

In addition, Figure 4 shows the execution flow chart of the configuration method under device linkage triggering conditions. By setting the device linkage fusion scenario configuration, specifically, the user logs in to the server through the account and password, and after verifying the user's identity, the server obtains the user The manufacturer's gateways and devices under the command are returned to the client, and the device management module of the client parses and stores the device data of each manufacturer to obtain the device set; click Add trigger conditions, select device trigger, and the scene configuration module takes out all the device data from the device module. Device sets (for example, sensor devices and high-security devices can be used as trigger conditions) are available for users to select. After the user selects, they are stored using ConditionDeviceList; click on a single trigger device to assign specific trigger conditions and scene configuration to each trigger device. The module will allocate different trigger conditions according to different manufacturers and devices, such as water immersion sensor allocation (1. Flood alarm; 2. Flood release). After clicking Finish, it will be judged whether all the selected condition devices support triggering at the same time or support Any trigger, if the triggers are met at the same time, a pop-up box will be provided for the user to choose between simultaneous trigger and any trigger. If it is any trigger, the user will not be able to choose; click Add Execution Task, the scene configuration module will be triggered from the device management Remove all device sets from the module, loop the device set through for loop, traverse all device models under GatewayModel, remove the device models that are the same as the trigger set (ConditionDeviceList), find out the devices that meet the conditions for executing the task, and store them in the pre-created execution device set. (ActionDeviceList) (for example, you can set up smart door sensors, smart smoke alarms and other sensor devices cannot be used as execution tasks; smart door locks and other highly secure devices cannot be used as execution devices), and display them to the manufacturer according to their UUID classification Users (displayed by VenderUuid classification) select the device set they want to execute and click Finish. The selected device set will appear in the execution task.

Embodiment 2

This embodiment also proposes a configuration method for a smart home client multi-vendor integration scenario, which is applied to the server and includes:

Receive the fusion scene data sent by the client and save it;

The fusion scene data is generated by parsing the device set information and establishing data logical relationships under different resource applications for each device in the device set;

Create a fusion scenario, add execution tasks, obtain equipment that meets the task conditions by traversing the logical relationship of the data, and establish a task equipment set; the task equipment set includes an execution task ID and a task equipment list;

Different execution tasks are assigned to the devices in the task device set to generate fusion scene data.

Among them, obtaining equipment that meets the task conditions and establishing a task equipment set include:

The device set information obtained by the analysis establishes data logical relationships under different resource applications for each device in the device set, including:

The device set information obtained by the analysis establishes data logical relationships under different resource applications for each device in the device set, and also includes:

Create a fusion scenario, add execution tasks, and obtain devices that meet the task conditions by traversing the logical relationships of the data, including:

The task triggering conditions include:

Trigger the execution of the task according to the user's manual trigger information; and/or set the trigger time to trigger the execution of the task when a certain trigger time is reached; and/or set the first device to reach a certain condition to trigger the second device to execute the task.

Assign different execution tasks to the devices in the task device set and generate fusion scenario data; transmit the fusion scenario data to the server, including:

The fusion scene data is encrypted and sent to the server.

In addition, an electronic device is also proposed, which protects a memory and a processor. The memory stores instructions, and the processor executes the instructions to implement the method steps as described above.

Based on the above embodiments, the present invention obtains user equipment set information that conforms to the user's identity from the server; and parses the obtained device set information to establish data logical relationships under different resource applications for each device in the device set. and save it to the cache; further, create a fusion scenario, add execution tasks, obtain devices that meet the task conditions by traversing the data logical relationship, and establish a task device set; the task device set includes an execution task ID and a task device list; Allocate different execution tasks to the devices in the task device set to generate fusion scene data; transmit the fusion scene data to the server to complete the configuration of the fusion scene of smart home devices from multiple manufacturers, so that during the client user operation process As long as the client is opened and the scene configured in the present invention is opened, the linkage and triggering of different work tasks of multiple devices of different manufacturers under the current smart home user can be realized, which solves the traditional problem of requiring multiple clients or The APP realizes the tedious configuration and control of each manufacturer's equipment one by one, and solves the problem that different devices from different manufacturers cannot be directly linked.

Those of ordinary skill in the art can understand that all or part of the steps involved in implementing the methods of the above embodiments can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium. When the program is executed, , including one of the steps of the method embodiment or a combination thereof.

In addition, each functional unit in various embodiments of the present invention can be integrated into a processing module, or each unit can exist physically alone, or two or more units can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software function modules. If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, etc.) embodying computer-usable program code therein.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the invention. In this way, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

A configuration method for smart home client multi-vendor integration scenarios, applied to the client, is characterized by including:

Send a device set information acquisition request message to the server, where the device set information acquisition request message includes user identity information; receive the user device set information returned by the server; the devices in the device set belong to different manufacturers;

Analyze the obtained device set information, establish data logical relationships under different resource applications for each device in the device set, and save it to the cache;

Create a fusion scenario, add execution tasks, obtain equipment that meets the task conditions by traversing the data logical relationship, and establish a task equipment set; the task equipment set includes an execution task ID and a task equipment list; for the task equipment set The device assigns different execution tasks and generates fusion scene data;

Transmit the fusion scene data to the server;

The device set information obtained by the analysis establishes data logical relationships under different resource applications for each device in the device set, including: obtaining the client's smart home gateway information; establishing a parent object model GatewayModel, parent The first sub-object model DeviceModel of the object model GatewayModel, and the second sub-object model DevicePointModel of the first sub-object model DeviceModel; the first sub-object model DeviceModel is a sub-object of the parent object model GatewayModel; the second sub-object model DevicePointModel It is the sub-object of the first sub-object model DeviceModel;

Initialize the parent object model GatewayModel, which is used to store gateway attribute data; initialize the first child object model DeviceModel, which stores the attribute data of the corresponding device under the smart home gateway, and stores the attribute data of the corresponding device under the smart home gateway. A sub-object model DeviceModel is put into the parent object model GatewayModel; a second sub-object model DevicePointModel is initialized. The second sub-object model DevicePointModel stores different resource node attribute data of the corresponding device and is added to the first sub-object model in the form of a collection. DeviceModel.
The configuration method for multi-vendor integration scenarios of smart home clients according to claim 1, characterized in that said obtaining devices that meet task conditions and establishing a task device set includes:

Display devices that meet the task conditions, receive user selections, and establish a task device set based on the devices selected by the user that meet the task conditions.
The configuration method of a smart home client multi-vendor integration scenario according to claim 1, characterized in that the creation of the integration scenario, adding execution tasks, and obtaining devices that meet the task conditions by traversing the data logical relationships include:

Create a scenario of integrated equipment and centralized equipment, and set task trigger conditions;

Create a scene execution task, traverse all device models of the parent object model GatewayModel, display devices that meet the conditions for executing the task, and save the mapping relationship between the scene execution task ID and the user-selected device set according to the user's selection;

To generate an execution task, traverse all the device models of the parent object model GatewayModel, select the devices that meet the conditions for executing the task, store the pre-created execution device collection, and display it.
The configuration method of smart home client multi-vendor integration scenario according to claim 3, characterized in that the task triggering conditions include:

Trigger the execution of the task according to the user's manual trigger information; and/or set the trigger time to trigger the execution of the task when a certain trigger time is reached; and/or set the first device to reach a certain condition to trigger the second device to execute the task.
The configuration method for a multi-vendor fusion scenario of a smart home client according to claim 4, characterized in that: allocating different execution tasks to the devices in the task device set to generate fusion scenario data; and transmitting the fusion scenario data to Servers, including:

Generate fusion scene data according to the execution task data, task triggering conditions and scene identifiers assigned by the equipment in the task equipment set;

The fusion scene data is encrypted and sent to the server.
A configuration method for smart home client multi-vendor integration scenarios, applied to servers, is characterized by including:

In response to the device set information acquisition request message sent by the client, obtain the device set information and send it to the client; the device set information acquisition request message includes user identity information; the devices in the device set belong to different manufacturers;

Receive the fusion scene data sent by the client and save it;

The fusion scenario data is generated in the following ways: parsing the device set information and establishing data logical relationships under different resource applications for each device in the device set; creating a fusion scenario, adding execution tasks, and traversing the data logical relationships, Obtain devices that meet the task conditions and establish a task device set; the task device set includes an execution task ID and a task device list; assign different execution tasks to the devices in the task device set and generate fusion scenario data;

The device set information obtained by the analysis establishes data logical relationships under different resource applications for each device in the device set, including: obtaining the client's smart home gateway information; establishing a parent object model GatewayModel, parent The first sub-object model DeviceModel of the object model GatewayModel, and the second sub-object model DevicePointModel of the first sub-object model DeviceModel; the first sub-object model DeviceModel is a sub-object of the parent object model GatewayModel; the second sub-object model DevicePointModel It is the sub-object of the first sub-object model DeviceModel;

Initialize the parent object model GatewayModel, which is used to store gateway attribute data; initialize the first child object model DeviceModel, which stores the attribute data of the corresponding device under the smart home gateway, and stores the attribute data of the corresponding device under the smart home gateway. A sub-object model DeviceModel is put into the parent object model GatewayModel; a second sub-object model DevicePointModel is initialized. The second sub-object model DevicePointModel stores different resource node attribute data of the corresponding device and is added to the first sub-object model in the form of a collection. DeviceModel.
An electronic device includes a memory and a processor, the memory stores instructions, and the processor executes the instructions to implement the method steps described in any one of claims 1-5 or to implement the method described in claim 6 method steps.
A storage medium, the storage medium stores a program; the program is loaded and executed by a processor to implement the method steps as described in any one of the above claims 1-5, or the method steps as claimed in claim 6 .