WO2023226768A1 - 设备控制方法、装置、设备及存储介质 - Google Patents

设备控制方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2023226768A1
WO2023226768A1 PCT/CN2023/093300 CN2023093300W WO2023226768A1 WO 2023226768 A1 WO2023226768 A1 WO 2023226768A1 CN 2023093300 W CN2023093300 W CN 2023093300W WO 2023226768 A1 WO2023226768 A1 WO 2023226768A1
Authority
WO
WIPO (PCT)
Prior art keywords
scene
devices
action
actions
control
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/093300
Other languages
English (en)
French (fr)
Inventor
宋永恒
黄灿武
游延筠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lumi United Technology Co Ltd
Original Assignee
Lumi United Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lumi United Technology Co Ltd filed Critical Lumi United Technology Co Ltd
Priority to EP23810841.9A priority Critical patent/EP4530761A4/en
Publication of WO2023226768A1 publication Critical patent/WO2023226768A1/zh
Priority to US18/920,955 priority patent/US20250060714A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B15/00—Systems controlled by a computer
    • G05B15/02—Systems controlled by a computer electric
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Program-control systems
    • G05B19/02—Program-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • H04L12/2818—Controlling appliance services of a home automation network by calling their functionalities from a device located outside both the home and the home network
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/26—Pc applications
    • G05B2219/2642—Domotique, domestic, home control, automation, smart house
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the present disclosure relates to the technical field of the Internet of Things. Specifically, the present disclosure relates to a device control method, device, equipment and storage medium.
  • Each embodiment of the present disclosure provides a device control method, device, device and storage medium, which can solve the problem of large network delay in multiple devices executing multiple actions existing in related technologies.
  • the technical solutions are as follows:
  • a device control method is executed by a server.
  • the method includes: obtaining scene control instructions for multiple devices; the scene control instructions are used to instruct each of the devices to respectively execute corresponding scene actions; identify the first device in each of the devices; the first device is a device that has been configured with scene action records; if at least one of the first devices is identified, send a message to each device according to the multicast transmission method.
  • the first device sends the scene control instruction to instruct each of the first devices to respond to the scene control instruction and synchronously execute the scene action recorded for the first device in the scene action record.
  • a device control method is executed by a smart device.
  • the method includes: receiving scene control instructions for multiple devices; the scene control instructions are used to instruct each of the devices to respectively execute corresponding scene action; based on the configured scene action record, in response to the scene control instruction, execute the scene action related to itself in the scene action record.
  • a device control method is executed by a device control system.
  • the device control system includes a server and a smart device.
  • the method includes: the server obtains scenes for multiple smart devices. control instructions, and when at least one first device is identified in each of the smart devices, send the scene control instructions to each of the first devices in a multicast transmission mode; the scene control instructions are used to indicate Each of the smart devices mentioned
  • the equipment respectively executes the corresponding scene action, and the first device is a smart device that has been configured with a scene action record; each of the first devices responds to the received scene control instruction and executes based on the configured scene action record.
  • a device control device includes: an instruction acquirer configured to acquire scene control instructions for multiple devices; the scene control instructions are used to instruct each of the devices to execute respectively The corresponding scene action; the device identifier, configured to identify the first device among the devices; the first device is a device that has been configured with a scene action record; the instruction transmitter, configured to identify at least one of the The first device sends the scene control instruction to each of the first devices in a multicast transmission manner to instruct each of the first devices to respond to the scene control instruction and synchronously execute the scene action record. Scene actions recorded by the first device.
  • the instruction acquirer includes: an instruction receiver configured to receive scene control instructions for multiple devices sent by a user terminal, where the scene control instructions are used to instruct the user terminal to The target scene constructed in is executed, and corresponding scene actions are configured for multiple devices in the target scene.
  • the instruction acquirer includes: a status data receiver configured to receive device status data sent by multiple devices, where the device status data is used to indicate the device status of the device; An instruction generator configured to, based on the received device status data, if it is determined that the trigger conditions in the device linkage data are met, generate instructions for multiple devices based on the corresponding actions performed by multiple devices in the device linkage data. scene control instructions.
  • the device identifier includes: a configuration detector configured to perform scene action recording configuration detection on each of the devices based on the scene control instruction, and determine at least one of the devices that has completed the configuration. a first device, and/or at least one second device that is not configured; the instruction sender includes: a multicast sender configured to use at least one of the first devices as a groupcast member to send messages to the group The broadcast members send the scene control instructions.
  • the instruction sender further includes: a unicast sender configured to, if at least one of the second devices is identified, send a message to each of the second devices in a unicast transmission manner.
  • the device control instructions corresponding to the scene control instructions enable each of the second devices to respectively respond to the device control instructions and execute corresponding scene actions.
  • the apparatus further includes: a status data receiver configured to receive, for each of the first devices, device status data sent by the first device, where the device status data is used to indicate the The device status after the first device performs the scene action; the instruction resender is configured to resend the device status data to each of the first devices according to the multicast transmission method if it detects that the device status data reception of the first device has timed out.
  • the scene control instructions configured to resend the device status data to each of the first devices according to the multicast transmission method if it detects that the device status data reception of the first device has timed out.
  • the apparatus further includes: a configuration data receiver configured to receive scene configuration data, where the scene configuration data at least indicates a plurality of scene actions that the device is configured to allow execution; a configurator, It is configured to request scene action recording configuration for a third device among the plurality of devices according to the scene configuration data; the third device is a device that supports scene action recording configuration.
  • the configurator includes: a device determiner configured to determine the third device among the plurality of devices based on the plurality of devices indicated by the scene configuration data; a snapshot Data getter, configured as From the scene configuration data, snapshot configuration data associated with the determined third device is obtained, the snapshot configuration data is used to indicate the scene actions that the third device is configured to allow execution; the snapshot data sender is configured as Send the snapshot configuration data to the associated third device, so that the third device configures scene action recording according to the snapshot configuration data.
  • the third device Convert to the first device that completes the configuration.
  • a device control device includes: an instruction receiver configured to receive scene control instructions for multiple devices; the scene control instructions are used to instruct each of the devices to execute respectively The corresponding scene action; the action executor is configured to execute the scene action related to itself in the scene action record in response to the scene control instruction based on the configured scene action record.
  • a device control system includes: a server configured to obtain scene control instructions for multiple smart devices and identify at least one first first in each smart device.
  • the scene control instructions are sent to each of the first devices in a multicast transmission mode; the scene control instructions are used to instruct each of the smart devices to perform corresponding scene actions respectively, and the first device It is an intelligent device that has been configured with a scene action record; each of the intelligent devices is configured to respond to the received scene control instruction and execute a scene related to itself in the scene action record based on the configured scene action record. action.
  • an electronic device includes at least one processor and at least one memory, wherein computer readable instructions are stored on the memory; the computer readable instructions are processed by one or more of the The processor executes, so that the electronic device implements the device control method as described above.
  • a storage medium has computer-readable instructions stored thereon, and the computer-readable instructions are executed by one or more processors to implement the device control method as described above.
  • a computer program product includes computer-readable instructions, the computer-readable instructions are stored in a storage medium, and one or more processors of an electronic device reads the computer-readable instructions from the storage medium. Read instructions, load and execute the computer readable instructions, so that the electronic device implements the device control method as described above.
  • Figure 1 is a schematic diagram of an implementation environment involved in an embodiment of the present disclosure
  • Figure 2 is a method flow chart of a scene construction process according to an embodiment of the present disclosure
  • Figure 3 is one of the schematic diagrams of the scene construction process involved according to an embodiment of the present disclosure
  • Figure 4 is a second schematic diagram of a scene construction process according to an embodiment of the present disclosure.
  • Figure 5 is a flow chart of a device control method according to an exemplary embodiment
  • Figure 6 is a method flow chart of a scene action recording configuration process according to an exemplary embodiment
  • Figure 7 is a flow chart of step 430 involved in the corresponding embodiment of Figure 6 in one embodiment
  • Figure 8 is a flow chart of another device control method according to an exemplary embodiment
  • Figure 9 is a flow chart of another device control method according to an exemplary embodiment.
  • Figure 10 is a schematic diagram showing a gateway sending different instructions to a first device and a second device according to an exemplary embodiment
  • Figure 11 is a flow chart of another device control method according to an exemplary embodiment
  • Figure 12 is a structural block diagram of an equipment control device according to an exemplary embodiment
  • Figure 13 is a structural block diagram of another device control device according to an exemplary embodiment
  • Figure 14 is a structural block diagram of a device control system according to an exemplary embodiment
  • Figure 15 is a hardware structure diagram of an electronic device according to an exemplary embodiment
  • Figure 16 is a structural block diagram of an electronic device according to an exemplary embodiment.
  • Multicast Also known as multi-target broadcast and multicast, it is a point-to-multipoint network communication method. It is also considered a network communication method for data transmission between a sender and multiple receivers. The sender Only one copy of data is sent, and the data received by multiple receivers are copies of this data, that is, the same data.
  • Unicast It is a point-to-point network communication method. It is mainly used for data transmission between a sender and a receiver. If it needs to be used for the transmission of the same data between a sender and multiple receivers, it can be used with the group The difference is that the sender still needs to send multiple copies of the same data.
  • the scene control instructions are used
  • scene control instructions can be sent to each first device according to the multicast transmission method.
  • scene control instructions can be sent to each first device according to the multicast transmission method.
  • scene control instructions can be sent to each first device according to the multicast transmission method.
  • scene control instructions can be sent to each first device according to the multicast transmission method.
  • scene control instructions can be sent to each first device according to the multicast transmission method.
  • scene control instructions can be sent to each first device according to the multicast transmission method.
  • scene action recorded for the first device in the scene action record that is, to record the scene action corresponding to the execution of at least one first device in the form of scene action recording. , and configure it to the first devices.
  • the first devices can be controlled and the configured scene actions can be executed synchronously.
  • the corresponding scene action recorded for the first device in the record avoids controlling multiple smart devices one by one based on multiple instructions, that is, it avoids multiple smart devices sequentially executing corresponding setting actions, thereby reducing the time required for multiple devices to execute multiple tasks.
  • the network delay of the action can effectively solve the problem of large network delay of multiple devices executing multiple actions existing in related technologies.
  • Figure 1 is a schematic diagram of an implementation environment involved in an embodiment of the present disclosure.
  • the implementation environment includes user terminal 110, smart device 130, gateway 150, server 170 and router 190.
  • the user terminal 110 which can also be considered as a user terminal or terminal, can deploy (also be understood as installation) the client associated with the smart device 130.
  • the user terminal 110 can be a smart phone, a tablet computer, a notebook computer, or a desktop computer. , intelligent control panels, other electronic devices with display and control functions, etc., are not limited here.
  • the client is associated with the smart device 130.
  • the user registers an account in the client and configures the smart device 130 in the client.
  • the configuration includes adding a device identifier to the smart device 130, etc., so that When the client is run in the user terminal 110, it can provide the user with functions such as device control of the smart device 130.
  • the client can be in the form of an application program or a web page.
  • the interface for the client to display the device can be It can be in the form of a program window or a web page, which is not limited here.
  • the smart device 130 is deployed in the gateway 150, communicates with the gateway 150 through its own configured communication module, and is then controlled by the gateway 150. It should be understood that the smart device 130 generally refers to one of multiple smart devices 130.
  • the embodiment of the present disclosure only takes the smart device 130 as an example. That is to say, the embodiment of the present disclosure does not depend on the number and number of smart devices deployed in the gateway 150. The type is not limited.
  • the smart device 130 accesses the gateway 150 through a local area network and is deployed in the gateway 150 .
  • the process of the intelligent device 130 accessing the gateway 150 through the local area network includes: the gateway 150 first establishes a local area network, and the intelligent device 130 joins the local area network established by the gateway 150 by connecting to the gateway 150 .
  • the smart device 130 can be a smart printer, a smart fax machine, a smart camera, a smart air conditioner, a smart door lock, a smart light, a smart fan, a smart speaker, or a human body sensor equipped with a communication module, a door and window sensor, a temperature and humidity sensor, a water immersion sensor, or a human body sensor equipped with a communication module. Sensors, natural gas alarms, smoke alarms, wall switches, wall sockets, wireless switches, wireless wall sticker switches, Rubik's Cube controllers, curtain motors and other electronic equipment. In various embodiments of the present disclosure, the smart device 130 specifically refers to a smart door lock.
  • the interaction between the user terminal 110 and the smart device 130 can be realized through a local area network or a wide area network.
  • the user terminal 110 establishes a wired or wireless communication connection with the gateway 150 through the router 190.
  • the wired or wireless communication connection includes but is not limited to WIFI, etc., so that the user terminal 110 and the gateway 150 are deployed In the same local area network, the user terminal 110 can interact with the smart device 130 through the local area network path.
  • the user terminal 110 establishes a wired or wireless communication connection with the gateway 150 through the server 170.
  • the wired or wireless communication connection includes but is not limited to 2G, 3G, 4G, 5G, WIFI. etc., so that the user terminal 110 and the gateway 150 are deployed in the same wide area network, so that the user terminal 110 can interact with the smart device 130 through the wide area network path.
  • the server side 170 can also be considered as a cloud, a cloud platform, a platform side, a server side, etc.
  • the server side 170 can be a server, a server cluster composed of multiple servers, or a server cluster composed of multiple servers.
  • a cloud computing center composed of multiple servers is used to better provide background services to a large number of user terminals 110.
  • background services include but are not limited to device control services and so on.
  • the server end 170 and the gateway 150 can both be considered as an embodiment of the server end, which is not specifically limited here.
  • FIG. 2 shows a method flow chart of the scene construction process in one embodiment.
  • Figure 3 shows a schematic diagram of the scene construction process in a user terminal in one embodiment.
  • the process of building a scenario can include the following steps:
  • Step 210 On the scene display page, display at least one constructed scene and a scene addition entry.
  • scene display page 301 the constructed scene 303, the scene 304, and the scene addition entry 302 are displayed.
  • scenes are uniquely represented by scene identifiers.
  • smart devices are uniquely represented by device identifiers
  • scene actions are uniquely represented by action identifiers.
  • These identifiers can be letters, numbers, strings, text, graphics, etc. The form is not limited here.
  • scene identifier A uniquely represents scene 303
  • scene identifier B uniquely represents scene 304.
  • Step 230 In response to the triggering operation of the scene addition entry, jump from the scene display page to the scene configuration page to add the scene.
  • At least one configured action as well as a scene name configuration entry and an action addition entry are displayed.
  • the scene display page 301 jumps to the scene configuration page 401.
  • the scene configuration page 401 not only the configured actions are displayed "Turn off the lights in the living room" 403, a scene name configuration entry 402 and an action configuration entry 404 are also displayed.
  • the user's click operation is regarded as a trigger operation for the scene configuration entrance.
  • Step 250 Add instructions based on the scene, determine the scene, and display it on the scene display page.
  • the scene adding instruction is triggered by at least one of the following operations: input operation, used to input a scene identifier for the scene; action configuration operation, used to configure at least one smart device to perform corresponding scene actions in the scene; scene confirmation Operation, used to confirm that the scene has been added.
  • "turn off all lights” can be input for the scene as the scene identifier of the setting device, and the user's input operation is regarded as an input operation; if the user clicks on the scene configuration page 401
  • the "+" control 404 indicates that the user wishes to add a scene action executed by a smart device in the scene, or if the user clicks the ">” control 406, it indicates that the user wishes to modify a scene action executed by a smart device in the scene.
  • the above-mentioned click operations of this user can be regarded as action configuration operations; if the user clicks the "Complete” control 405, it means that the user confirms that the scene has been added, and the user's click operation is regarded as a scene confirmation operation.
  • the generation of a scene adding instruction can be triggered, and the scene is determined to be represented by the scene identifier "turn off all lights” and displayed on the scene display page 302, that is, “turn off all lights”.
  • step 250 may also include the following steps: in response to the action configuration operation, jump from the scene configuration page to the action configuration page; based on the action configuration instructions triggered in the action configuration page, determine the scene to be executed by the smart device in the scene Action and displayed in the scene configuration page.
  • the action configuration instruction is triggered by at least one of the following operations: a device selection operation, used to select a smart device for the scene; a location selection operation, used to select a deployment location for the smart device selected in the scene, and the deployment location Including but not limited to: master bedroom, guest bedroom, bathroom, dining room, living room, study room, storage room, cloakroom, balcony, kitchen, corridor, etc.
  • the deployment location specifically limits the type of smart device, such as , if the deployment location of the "switch” is the restaurant, it means that the smart device is a "restaurant light", or if the deployment location of the "switch” is the living room, it means the smart device is a "living room light”; the action selection operation is used to The smart device selected in the scene selects the scene action; the action confirmation operation is used to confirm the configuration of the scene action in the scene.
  • the selection control 502 you can select a "switch" connected to the lamp for the scene.
  • the user's selection operation is regarded as a device selection operation; in the selection control 503, you can Select "Restaurant” for the switch as a deployment location for the smart device selected in the scene.
  • the user's selection operation is regarded as a location selection operation; in the selection control 504, you can select "Off” for the switch as a deployment location for the smart device selected in the scene.
  • the smart device selects a scene action; if the user clicks the "Next" control 505, it means that the user confirms that the scene action in the scene has been configured, and the user's click operation is regarded as an action confirmation operation.
  • the generation of action configuration instructions can be triggered, thereby determining that the scene action performed by the smart device "switch" deployed in the "restaurant” and connected to the light in the scene is “off” and displayed on the scene configuration page 401, which means "turn off the lights in the restaurant.”
  • Step 270 In response to the scene selection operation on the target scene, jump from the scene display page to the scene details page of the target scene.
  • the scene display page 301 jumps to the scene details page 601 of scene 305, that is, ""Turn off all lights", the scene details page 601 displays at least: scene actions performed by at least one smart device in scene 305, for example, the living room lights are turned off in scene 305, that is, “turn off living room lights”602; the dining room lights are in scene 305.
  • the shutdown is performed in 305, that is, "turn off the lights in the restaurant” and so on.
  • the user's click operation is regarded as a scene selection operation for the target scene.
  • the scene details page 601 also displays a scene execution entrance 603, which provides the user with the function of one-click execution of the scene, thereby instructing at least one smart device to perform corresponding scene actions in the scene.
  • a scene execution entrance 603 which provides the user with the function of one-click execution of the scene, thereby instructing at least one smart device to perform corresponding scene actions in the scene. For example, if the user clicks The scene execution entrance 603 is regarded as one-click execution of the "turn off all lights" scene, and the living room lights and dining room lights will be turned off accordingly, thereby achieving controlled execution of the all lights off scene.
  • an action configuration operation can also be formed through the control 603 and the action addition entry 604 to add/modify a scene action executed by a smart device in the scene based on the action configuration operation.
  • the scene configuration page and the scene details page can also be merged into the same page according to the user's experience, and this is not a specific limitation.
  • the controlled execution scene means that when the user clicks on the scene execution entrance, the smart device that has configured scene actions in the controlled execution scene will execute the corresponding scene action; and the automated scene means that if the automated scene If the trigger conditions configured in are met, the smart device configured with scene actions in the automation scene will automatically execute the corresponding scene actions.
  • the automation scene 306 has been constructed and is displayed in the scene display page 302 through the scene identification of "go home scene"
  • the user clicks on the scene identification he can enter the scene details page of the automation scene 306. 701.
  • the displayed trigger condition is: the smart door lock is turned on
  • the displayed scene actions are: turning on the living room lights, turning on the living room air conditioner, and also displays the condition adding entrance 703 for adding the trigger condition, and the An action addition entry 706 for adding a new scene action is added.
  • modifying the trigger condition can be implemented through the control 702, and modifying the scene action can be implemented through the controls 704 and 705.
  • the living room lights, scene actions configured in the automation scene 306 are The living room air conditioner will automatically perform corresponding scene actions, that is, automatically turn on the living room lights and automatically turn on the living room air conditioner, thereby realizing the automatic execution of the homecoming scene.
  • the specific behaviors of each of the above operations may also be different.
  • the user terminal is a smartphone equipped with a touch layer
  • the above operations can be gesture operations such as clicking and sliding
  • the user terminal is a laptop equipped with a mouse
  • the above operations can be dragging, clicking, and double-clicking. and other mechanical operations are not limited here. It can be seen that as the scene is constructed in the user terminal, the user can control multiple devices to perform multiple actions with the help of controlled execution scenarios or automated scenarios constructed in the user terminal.
  • the device control process specifically refers to, as shown in Figure 5, step 310, obtaining scene control instructions for multiple devices; the scene control instructions are used to instruct each device to perform corresponding scene actions; step 330, identifying the third device in each device.
  • One device; the first device is a device that has been configured with scene action recording; step 350, if at least one first device is identified, send scene control instructions to each first device according to the multicast transmission method to instruct each first device.
  • the device responds to the scene control instruction and synchronously executes the scene action recorded for the first device in the scene action record.
  • the electronic device may be the gateway 150 in Figure 1, or the server 170, user terminal 110, etc. in Figure 1, which is not specifically limited here.
  • the configuration process of scene action recording may include the following steps:
  • Step 410 Receive scene configuration data sent by the user terminal.
  • the scene configuration data is generated when building a scene in the user terminal, and the scene configuration data at least indicates scene actions that multiple devices are configured to allow execution.
  • a device may be configured to perform different scenario actions. For example, if the scene is the main bedroom, when the owner sleeps, the smart fan is turned on; if the scene is the bathroom, when the owner leaves, the smart fan is turned off. Therefore, the scene actions performed for device configuration are based on the scene. Different scenes, scene configuration The data also varies.
  • scenario configuration data A corresponds to a controlled execution scenario
  • scenario configuration data A is used to indicate scenario actions that multiple devices are configured to allow execution in the controlled execution scenario
  • scenario configuration data B corresponds to an automation scenario
  • scenario configuration data Data B is used to indicate the trigger conditions configured in the automation scenario, that is, it indicates the device status of multiple devices when they meet the trigger conditions in the automation scenario. It is also used to indicate the scenarios in which multiple devices are configured to allow execution in the automation scenario. action.
  • the scene configuration data at least includes: a scene identifier of the scene, a device identifier of at least one device, and an action identifier corresponding to the scene action of the device.
  • Step 430 Request scene action recording configuration for a third device among the plurality of devices according to the scene configuration data.
  • the third device is a device that supports scene action recording configuration.
  • the first device is a device that has completed configuration;
  • the second device is a device that does not support scene action recording configuration, that is, a device that has not been configured.
  • Scene action records are records of scene actions that the device is configured to allow in the scene. It can be understood as a kind of snapshot data for device functions. For example, the execution actions supported by the device can be packaged as snapshot actions, including this snapshot action. The data can be recorded for scene actions.
  • the configuration of the scene action record refers to storing the scene action record in the third device, so that the third device knows in advance the scene actions it can perform in the scene.
  • step 430 may include the following steps:
  • Step 431 Determine a third device among the multiple devices based on the multiple devices indicated by the scene configuration data.
  • whether the device supports the configuration of scene action recording is determined through the device identification.
  • the device identification that supports the configuration of scene action recording is pre-stored.
  • whether the device supports the configuration of scene action recording is determined by device version information.
  • device version information that supports the configuration of scene action recording is pre-stored.
  • whether the device supports scene actions The recorded configuration can also be determined by adding a snapshot identifier. For example, if the server recognizes that the snapshot identifier carried by the device is 1, it means that the device supports the configuration of scene action recording. This is not specifically limited here.
  • Step 433 Obtain snapshot configuration data associated with the determined third device from the scene configuration data.
  • the snapshot configuration data is used to indicate scene actions that the third device is configured to allow execution.
  • the snapshot configuration data at least includes: a device identifier of at least one third device and an action identifier corresponding to a scene action of the third device.
  • Step 435 Send the snapshot configuration data to the associated third device, so that the third device configures the scene action record according to the snapshot configuration data.
  • the third device is transformed into the first device that completes the configuration.
  • action identifier is C1
  • the brightness of lamp B2 is 50%
  • the temperature of air conditioner B3 is 26 degrees
  • the lamp B2 and the air conditioner B3 support the configuration of scene action recording
  • the wall switch B1 does not support the configuration of scene action recording.
  • scene configuration data ⁇ A, B1(C1), B2(C2), B3(C3) ⁇ .
  • the configuration of the scene action record specifically refers to storing the scene identifier of the scene, the device identifier of the third device, and the action identifier of the scene action in the third device.
  • the action identifier C2 for performing the scene action in scene A is stored. Then, in the subsequent process of multiple devices performing multiple actions in scene A, they can follow the pre-stored
  • the scene action represented by the action identifier C2 can also be considered as the execution of the scene action related to itself in the configured scene action record, that is, adjusting the brightness to 50%.
  • the gateway can deliver to each third device the part of the snapshot configuration data corresponding to the third device.
  • lamp B2 can only Receive the action identifier C2 for performing the scene action in the scene, thereby reducing the amount of data transmission between the gateway and the third device, which is beneficial to improving transmission efficiency; in another possible implementation, the gateway can also send a message to each third device.
  • the three devices deliver the complete part of the snapshot configuration data.
  • the lamp B2 can not only receive the action identifier C2 for performing the scene action in the scene, but also receive the action identifier C3 for the air conditioner B3 to perform the scene action in the scene.
  • lamp B2 needs to further configure the scene action record in conjunction with its own device identification B2, so that it can subsequently execute scene actions related to itself in the scene action record. , is not limited here.
  • the configuration of the device's scene action record is implemented, so that the subsequent device can quickly perform scene actions related to itself based on the configured scene action record.
  • a device control method is described by taking the method applied to an electronic device as an example.
  • the electronic device may be the smart device 130 in Figure 1 .
  • the device control method may include the following steps: Step 370, receive scene control instructions for multiple devices; the scene control instructions are used to instruct each device to perform corresponding scene actions respectively; Step 390, based on the configured Scene action records, in response to the scene control instructions, Execute the scene actions related to itself in the scene action record.
  • the method is executed by the device control system and implemented through interaction between the server and the smart device as an example.
  • the server includes but is not limited to the gateway 150 and the server shown in Figure 1. 170.
  • the smart device may be the smart device 130 in Figure 1.
  • the device control method may include the following steps: the server obtains scene control instructions for multiple smart devices, and identifies at least one third smart device in each smart device.
  • scene control instructions are sent to each first device according to the multicast transmission method; the scene control instructions are used to instruct each smart device to perform corresponding scene actions respectively, and the first device is a smart device that has been configured with scene action records.
  • each first device responds to the received scene control instruction and executes the scene action related to itself in the scene action record based on the configured scene action record.
  • multiple devices can be controlled to perform multiple actions at the same time by sending one instruction through the server (such as a gateway), thereby helping to solve the problem of large network delays in multiple devices executing multiple actions that exists in related technologies.
  • an embodiment of the present disclosure provides a device control method. This method is explained by taking the application of this method to an electronic device as an example.
  • the electronic device may be a server.
  • the server may be the gateway 150 in FIG. 1 or the server 170 in FIG. 1, which is not specifically limited here.
  • the device control method may include the following steps:
  • Step 510 Obtain scene control instructions for multiple devices.
  • the scene control instructions are used to instruct each device to perform corresponding scene actions respectively.
  • the scene control instruction at least includes: a scene identifier of the scene, a device identifier of at least one device, and an action identifier of a corresponding scene action performed by at least one device in the scene.
  • one possible implementation method specifically refers to receiving scene control instructions for multiple devices sent by the user terminal.
  • the scene control instruction is used to instruct the target scene constructed in the user terminal to be executed.
  • the target scene is configured with corresponding scene actions for multiple devices.
  • the scene control instruction is for the target scene to be a controlled execution scene.
  • the scene control instruction is generated when the user executes the target scene with one click, and is then sent to the gateway by the user terminal so that the gateway controls each device. Execute the corresponding scene actions configured in the controlled execution scene respectively.
  • one possible implementation method specifically refers to receiving device status data sent by multiple devices.
  • the device status data is used to indicate the device status of the device; according to the received device status data, if determined If the trigger conditions in the device linkage data are met, scene control instructions for multiple devices are generated based on the corresponding scene actions performed by multiple devices in the device linkage data. In this way, the scene control instruction is for the automation scene.
  • the scene control instruction is generated by the gateway, so that the gateway controls each device to execute the corresponding configuration configured in the automation scene. Scene action.
  • Step 520 Based on the scene control instruction, perform scene action record configuration detection on each device to determine at least one first device that has completed configuration and/or at least one second device that has not been configured.
  • the first device is a device that has been configured with scene action recording.
  • the second device is an unconfigured device.
  • Scene action records are records of scene actions that the device is configured to allow in the scene.
  • the configuration detection of scene action records refers to determining multiple devices according to the device identifiers in the scene control instructions, and then determining whether the scene identifiers of the scenes are stored in each device, and the scene actions performed by the devices in the scene. action identifier to determine whether each device has been configured with scene action recording.
  • the gateway performs a configuration detection of the scene action record on the device, including: the gateway sends a configuration detection request regarding the scene action record to the device; The device responds to the configuration detection request and returns a corresponding request response to the gateway.
  • the request response carries the scene identifier A stored in the device and the action identifier C3 of the scene action performed by the device in the scene. Then it is determined that the The device has been configured with scene action recording. That is, the scene action record records that the device performed the scene action represented by the action identifier C3 in the scene represented by the scene identifier A.
  • the configured device is regarded as the first device, and step 530 is executed, that is, in response to the scene control instruction, the scene action recorded for the first device in the scene action record is executed.
  • the unconfigured device is used as the second device, and step 550 is executed, that is, in response to the device control instruction corresponding to the scene control instruction, the scene action configured by the second device in the scene is executed.
  • Step 530 Use at least one first device as a multicast member and send a scene control instruction to the multicast member to instruct the multicast member to respond to the scene control instruction and synchronously execute the scene action recorded for the multicast member in the scene action record.
  • Figure 10 shows a schematic diagram of the gateway sending different instructions to the first device and the second device respectively.
  • the gateway 150 is essentially controlled through a scene control instruction (instruction 1) in a multicast transmission mode, so that the two first devices can synchronously execute scene actions related to themselves in the scene action records.
  • Step 550 Send the device control instructions corresponding to the scene control instructions to each second device respectively according to the unicast transmission mode, so that each second device responds to the device control instructions and executes the corresponding scene action.
  • the device The control instructions are extracted from the scene control instructions, and include at least the scene identifier of the scene and the action identifier of the scene action performed by the second device in the scene, so as to instruct the second device to perform the scene action in the scene.
  • the gateway 150 sends two device control instructions (instruction 2 and instruction 3) to each second device successively in a unicast transmission mode, so that the two second devices sequentially transmit the device control instructions in the order in which they are received. Perform its scene actions in the scene.
  • the device control process is implemented between the user terminal, the server, and the gateway.
  • the scene control instructions are forwarded from the server to the gateway.
  • the device control process can also be implemented between the user terminal and the gateway.
  • the scene control instruction is sent from the user terminal to the gateway.
  • the gateway still needs to Send multiple instructions to control multiple second devices one by one.
  • device control has been greatly improved, that is, the gateway only needs to send one instruction to control multiple first devices at the same time to perform multiple tasks. action, thereby avoiding the need for multiple devices to perform actions in the scene in sequence.
  • the gateway As the number of devices increases, it is more conducive to reducing the network delay of multiple devices executing actions, achieving the effect of rapid control of multiple devices at the same time, which is beneficial to users
  • the user experience has been greatly improved. For example, users want multiple devices to act in unison to achieve consistent action effects, rather than acting sequentially.
  • the configuration of scene action recording is not only suitable for multiple devices to perform the same action, but also suitable for multiple devices to perform different actions, effectively expanding the versatility of device control.
  • the device control method may further include the following steps:
  • Step 610 For each first device, receive the device status data sent by the first device.
  • the device status data is used to indicate the device status after the first device performs the scene action. For example, if the scene is a bathroom, if the smart fan performs the off action, the device status data is used to indicate that the smart fan's device status is off, or if the smart light performs the on action, the device status data is used to indicate the smart light device. The status is on.
  • Step 630 Check whether the reception of device status data times out.
  • step 650 the reception of device status data times out, that is, the first device reports device status data over time. If it is detected that at least one first device times out in reporting device status data, step 650 is executed. On the contrary, if it is detected that the device status data reported by each first device has not timed out, it is confirmed that all first devices have synchronously executed the scene action recorded for the first device in the scene action record.
  • Step 650 Resend the scene control instructions to each first device according to the multicast transmission mode.
  • the scene control instructions are re-sent to all first devices.
  • the first device that reports timeout resends the scene control instruction until it is confirmed that all first devices have synchronously executed the scene actions recorded for the first device in the scene action record, which can not only ensure the maximum The success rate of action execution ensures the success rate of equipment control and fully guarantees the stability of equipment control.
  • first devices may have performed scene actions, and the reported device status data has not timed out, then the first device may ignore the re-received scene control instructions, and for unscheduled For the first device that performs scene actions or reports device status data timeout, it needs to respond to the re-received scene control instructions again and re-execute the scene actions recorded for the first device in the scene action record.
  • the device status reporting detection is implemented.
  • the first device can receive the scene control instruction again and be controlled again before it can execute the scene action again, thus enhancing the robustness of the system and improving device control. stability.
  • an embodiment of the present disclosure provides a device control device 900, which is deployed on the server.
  • the device control device 900 includes but is not limited to: an instruction acquirer 910, a device identifier 930, and an instruction sender 950.
  • the instruction obtainer 910 is configured to obtain scene control instructions for multiple devices; the scene control instructions are used to instruct each device to perform corresponding scene action devices respectively.
  • the device identifier 930 is configured to identify the first device among the devices; the first device is a device that has been configured with a scene action record associated with the scene control instruction.
  • the instruction sender 950 is configured to, if at least one first device is identified, send a scene control instruction to each first device in a multicast transmission manner to instruct each first device to respond to the scene control instruction and execute scene action recording synchronously. in is the scene action recorded by the first device.
  • the instruction acquirer includes: an instruction receiver configured to receive scene control instructions for multiple devices sent by the user terminal, where the scene control instructions are used to instruct the target scene constructed in the user terminal to be executed, Corresponding scene actions are configured for multiple devices in the target scene.
  • the instruction acquirer includes: a status data receiver configured to receive device status data sent by multiple devices, where the device status data is used to indicate the device status of the device; an instruction generator configured to receive After receiving the device status data, if it is determined that the trigger conditions in the device linkage data are met, scene control instructions for multiple devices are generated based on the corresponding actions performed by multiple devices in the device linkage data.
  • the device identifier includes: a configuration detector configured to perform scene action recording configuration detection on each device based on the scene control instruction, and determine at least one first device that has completed the configuration, and/or, At least one second device that is not configured;
  • the instruction sender includes: a multicast sender configured to use at least one first device as a multicast member and send scene control instructions to the multicast members.
  • the instruction sender further includes: a unicast sender configured to, if at least one second device is identified, send the device corresponding to the scene control instruction to each second device in a unicast transmission manner.
  • the control instructions enable each second device to respectively respond to the device control instructions and execute corresponding scene actions.
  • the apparatus further includes: a status data receiver configured to receive, for each first device, device status data sent by the first device, where the device status data is used to instruct the first device to perform the scene action after the device performs the scene action. status; the instruction resender is configured to resend the scene control instruction to each first device according to the multicast transmission mode if it detects that the reception of the device status data of the first device has timed out.
  • the apparatus further includes: a configuration data receiver configured to receive scene configuration data, the scene configuration data at least indicating scene actions that a plurality of devices are configured to allow execution; a configurator configured to configure the data according to the scene , requesting configuration of scene action recording on a third device among multiple devices; the third device is a device that supports scene action recording configuration.
  • the configurator includes: a device determiner configured to determine a third device among the multiple devices based on the multiple devices indicated by the scene configuration data; a snapshot data acquirer configured to determine the third device from the scene configuration data , obtain snapshot configuration data associated with the determined third device, the snapshot configuration data is used to indicate scene actions that the third device is configured to allow execution; the snapshot data sender is configured to send the snapshot configuration data to the associated third device The device enables the third device to configure scene action recording according to the snapshot configuration data. When the scene action recording configuration is completed, the third device is converted into the first device that completes the configuration.
  • an embodiment of the present disclosure provides a device control device 1000, which is deployed on a smart device.
  • the device control device 1000 includes but is not limited to: an instruction receiver 1010 and an action executor 1030.
  • the instruction receiver 1010 is configured to receive scene control instructions for multiple devices; the scene control instructions are used to instruct each device to perform corresponding scene actions.
  • the action executor 1030 is configured to execute the scene action related to itself in the scene action record in response to the scene control instruction based on the configured scene action record associated with the scene control instruction.
  • an embodiment of the present disclosure provides a device control system, which includes but is not limited to: a server 300 and a smart device 400.
  • the server 300 is configured to obtain scene control instructions for multiple smart devices, and when at least one first device is identified in each smart device, send scene control instructions to each first device in a multicast transmission manner. Instructions; scene control instructions are used to instruct each smart device to perform corresponding scene actions respectively.
  • the first device is a smart device that has been configured with scene action records.
  • Each smart device 400 is configured to respond to the received scene control instruction and execute the scene action related to itself in the scene action record based on the configured scene action record.
  • Figure 15 shows a schematic structural diagram of an electronic device according to an exemplary embodiment.
  • the electronic device is suitable for the smart device 130, the gateway 150, and the server 170 in the implementation environment shown in Figure 1.
  • this electronic device is only an example adapted to the present disclosure and cannot be considered to provide any limitation on the scope of use of the present disclosure.
  • the electronic device is also not to be construed as being dependent on or required to have one or more components of the exemplary electronic device 2000 shown in FIG. 15 .
  • the hardware structure of the electronic device 2000 may vary greatly due to different configurations or performance.
  • the electronic device 2000 includes: a power supply 210, an interface 230, at least one memory 250, and at least one central processing unit (CPU). ,Central Processing Units)270.
  • CPU central processing unit
  • CPU Central Processing Unit
  • the power supply 210 is used to provide operating voltage for each hardware electronic device on the electronic device 2000 .
  • the interface 230 includes at least one wired or wireless network interface 231 for interacting with external electronic devices. For example, the interaction between the user terminal 110 and the gateway 150 in the implementation environment shown in FIG. 1 is performed.
  • the interface 230 may further include at least one serial-to-parallel conversion interface 233, at least one input-output interface 235, at least one USB interface 237, etc., as shown in Figure 15, which is not intended to be used here. This constitutes a specific limitation.
  • the memory 250 can be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc.
  • the resources stored thereon include the operating system 251, application programs 253, data 255, etc., and the storage method can be short-term storage or permanent storage. .
  • the operating system 251 is used to manage and control each hardware electronic device and the application program 253 on the electronic device 2000 to realize the operation and processing of the massive data 255 in the memory 250 by the central processor 270. It can be Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • the application program 253 is a computer-readable instruction based on the operating system 251 to complete at least one specific work. It may include at least one module (not shown in FIG. 15 ), and each module may include a computer program for the electronic device 2000 . Readable instructions.
  • the electronic device control device may be regarded as the application program 253 deployed on the electronic device 2000 .
  • the data 255 can be photos, pictures, etc. stored in the disk, or can also be device status data, scene configuration data, etc., stored in the memory 250 .
  • the central processing unit 270 may include one or more processors, and is configured to communicate with the memory 250 through at least one communication bus to read the computer readable instructions stored in the memory 250, and thereby implement processing of the massive data 255 in the memory 250. operation and processing.
  • the electronic device control method is completed by the central processor 270 reading a series of computer readable instructions stored in the memory 250 .
  • present disclosure can also be implemented through hardware circuits or hardware circuits combined with software. Therefore, implementation of the present disclosure is not limited to any specific hardware circuit, software, or combination of the two.
  • an electronic device 4000 is provided in an embodiment of the present disclosure.
  • the electronic device 4000 may include: a smart device, a gateway, a server, and so on.
  • the electronic device 4000 includes at least one processor 4001 , at least one communication bus 4002 and at least one memory 4003 .
  • the communication bus 4002 may include a path for transmitting data between the processor 4001 and the memory 4003.
  • the communication bus 4002 may be a PCI (Peripheral Component Interconnect, Peripheral Component Interconnect Standard) bus or an EISA (Extended Industry Standard Architecture) bus, etc.
  • the communication bus 4002 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 16, but it does not mean that there is only one bus or one type of bus.
  • the electronic device 4000 may also include a transceiver 4004, which may be used for data interaction between the device and other devices, such as data transmission and/or data reception.
  • a transceiver 4004 may be used for data interaction between the device and other devices, such as data transmission and/or data reception. It should be noted that in practical applications, the number of transceivers 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present disclosure.
  • the processor 4001 may be a CPU (Central Processing Unit, central processing unit), a general-purpose processor, a DSP (Digital Signal Processor, a data signal processor), an ASIC (Application Specific Integrated Circuit, an application specific integrated circuit), or an FPGA (Field Programmable Gate Array). , field programmable gate array) or other Programmed logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various illustrative logical blocks, modules and circuits described in connection with this disclosure.
  • the processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
  • the memory 4003 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, RAM (Random Access Memory) or other types that can store information and instructions.
  • Dynamic storage devices can also be EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compression Optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or can be used to carry or store the desired computer readable instructions in the form of instructions or data structures and can be used by the electronic device 4000 for access to any other media, but not limited to this.
  • Computer-readable instructions are stored in the memory 4003, and the processor 4001 can read the computer-readable instructions stored in the memory 4003 through the communication bus 4002.
  • an embodiment of the present disclosure provides a storage medium on which computer readable instructions are stored, and the computer readable instructions are loaded and executed by the processor to implement the device control method as described above.
  • An embodiment of the present disclosure provides a computer program product.
  • the computer program product includes computer-readable instructions.
  • the computer-readable instructions are stored in a storage medium.
  • the processor of the device reads the computer-readable instructions from the storage medium, loads and executes the computer-readable instructions.
  • Computer-readable instructions enable the device to implement the device control method as described above.
  • the computer program product can use any programming language and take the form of source code, object code or intermediate code between the source code and the object code, such as a partially compiled form or any other required form.
  • the scene action corresponding to at least one device in the scene is recorded in the form of scene action recording, and configured to the at least one device in the scene.
  • the scene action is recorded to the device in a multicast manner.
  • These devices send scene control instructions, and these devices can execute the corresponding scene actions according to the scene actions recorded for these devices in the configured scene action records, avoiding the need to control multiple devices one by one based on multiple instructions, that is,
  • This method avoids the sequential execution of corresponding scene actions by multiple devices, thereby reducing the network delay of multiple devices executing multiple actions, thereby effectively solving the problem of large network delays of multiple devices executing multiple actions existing in related technologies.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Selective Calling Equipment (AREA)

Abstract

一种设备控制方法，包括：获取针对多个设备的场景控制指令；场景控制指令用于指示各设备分别执行对应的场景动作（310）；识别各设备中的第一设备；第一设备为已配置有场景动作记录的设备（330）；若识别到至少一个第一设备，则按照组播传输方式，向各第一设备发送场景控制指令，以指示各第一设备响应于场景控制指令，同步执行场景动作记录中为第一设备记录的场景动作（350）。

Description

设备控制方法、装置、设备及存储介质
本公开要求2022年5月23日递交、发明名称为“设备控制方法、装置、设备及存储介质”的中国专利申请CN 202210565411.X的优先权，在此通过引用将其全部内容合并于此。
技术领域
本公开涉及物联网技术领域，具体而言，本公开涉及一种设备控制方法、装置、设备及存储介质。
背景技术
随着物联网技术的飞速发展，智能设备的应用逐渐广泛，为了提高用户对智能设备的操作便捷性，不仅可以设置设备联动，例如，若感测到客厅有人，则自动开灯，还可以设置各种模式，例如，当用户离家，通过离家模式，自动关闭空调、灯、插座开关等等。
然而，目前针对多个智能设备的控制，例如离家模式中的多个智能设备，往往需要基于多条指令逐一控制，也可以认为是，多个智能设备需要顺序执行对应的设定动作，由此产生了较大的网络延迟，容易影响用户的使用体验。
由上可知，如何减小多设备执行多动作的网络延迟尚待解决。
发明内容
本公开各实施例提供了一种设备控制方法、装置、设备及存储介质，可以解决相关技术中存在的多设备执行多动作网络延迟较大的问题。所述技术方案如下：
根据本公开实施例的一个方面，一种设备控制方法，由服务端执行，所述方法包括：获取针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；识别各所述设备中的第一设备；所述第一设备为已配置有场景动作记录的设备；若识别到至少一个所述第一设备，则按照组播传输方式，向各所述第一设备发送所述场景控制指令，以指示各所述第一设备响应于所述场景控制指令，同步执行所述场景动作记录中为所述第一设备记录的场景动作。
根据本公开实施例的一个方面，一种设备控制方法，由智能设备执行，所述方法包括：接收针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；基于已配置的场景动作记录，响应于所述场景控制指令，执行所述场景动作记录中与自身有关的场景动作。
根据本公开实施例的一个方面，一种设备控制方法，由设备控制系统执行，所述设备控制系统包括服务端和智能设备，所述方法包括：所述服务端获取针对多个智能设备的场景控制指令，并在各所述智能设备中识别到至少一个第一设备的情况下，按照组播传输方式，向各所述第一设备发送所述场景控制指令；所述场景控制指令用于指示各所述智能设 备分别执行对应的场景动作，所述第一设备为已配置有场景动作记录的智能设备；各所述第一设备响应于接收到的所述场景控制指令，基于已配置的场景动作记录，执行所述场景动作记录中与自身有关的场景动作。
根据本公开实施例的一个方面，一种设备控制装置，所述装置包括：指令获取器，配置为获取针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；设备识别器，配置为识别各所述设备中的第一设备；所述第一设备为已配置有场景动作记录的设备；指令发送器，配置为若识别到至少一个所述第一设备，则按照组播传输方式，向各所述第一设备发送所述场景控制指令，以指示各所述第一设备响应于所述场景控制指令，同步执行所述场景动作记录中为所述第一设备记录的场景动作。
在一示例性实施例中，所述指令获取器，包括：指令接收器，配置为接收用户终端发送的针对多个所述设备的场景控制指令，所述场景控制指令用于指示所述用户终端中构建的目标场景被执行，所述目标场景中为多个所述设备配置了对应的场景动作。
在一示例性实施例中，所述指令获取器，包括：状态数据接收器，配置为接收多个所述设备发送的设备状态数据，所述设备状态数据用于指示所述设备的设备状态；指令生成器，配置为根据接收到的设备状态数据，若确定设备联动数据中的触发条件满足，则根据所述设备联动数据中多个所述设备对应执行的动作，生成针对多个所述设备的场景控制指令。
在一示例性实施例中，所述设备识别器，包括：配置检测器，配置为基于所述场景控制指令，对各所述设备进行场景动作记录的配置检测，确定完成配置的至少一个所述第一设备，和/或，未进行配置的至少一个第二设备；所述指令发送器，包括：组播发送器，配置为以至少一个所述第一设备作为组播成员，向所述组播成员发送所述场景控制指令。
在一示例性实施例中，所述指令发送器还包括：单播发送器，配置为若识别到至少一个所述第二设备，则按照单播传输方式，分别向各所述第二设备发送所述场景控制指令对应的设备控制指令，使得各所述第二设备分别响应于所述设备控制指令，执行对应的场景动作。
在一示例性实施例中，所述装置还包括：状态数据接收器，配置为针对各所述第一设备，接收所述第一设备发送的设备状态数据，所述设备状态数据用于指示所述第一设备执行场景动作后的设备状态；指令重发器，配置为若检测到所述第一设备的设备状态数据接收超时，则按照组播传输方式，向各所述第一设备重新发送所述场景控制指令。
在一示例性实施例中，所述装置还包括：配置数据接收器，配置为接收场景配置数据，所述场景配置数据至少指示了多个所述设备被配置允许执行的场景动作；配置器，配置为根据所述场景配置数据，请求对多个所述设备中的第三设备进行场景动作记录的配置；所述第三设备为支持场景动作记录配置的设备。
在一示例性实施例中，所述配置器，包括：设备确定器，配置为基于所述场景配置数据指示的多个所述设备，确定多个所述设备中的所述第三设备；快照数据获取器，配置为 从所述场景配置数据中，得到与所确定的第三设备关联的快照配置数据，所述快照配置数据用于指示所述第三设备被配置允许执行的场景动作；快照数据发送器，配置为将所述快照配置数据发送至关联的所述第三设备，使得所述第三设备根据所述快照配置数据进行场景动作记录的配置，在完成场景动作记录配置的情况下，所述第三设备转化为完成配置的所述第一设备。
根据本公开实施例的一个方面，一种设备控制装置，所述装置包括：指令接收器，配置为接收针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；动作执行器，配置为基于已配置的场景动作记录，响应于所述场景控制指令，执行所述场景动作记录中与自身有关的场景动作。
根据本公开实施例的一个方面，一种设备控制系统，所述系统包括：服务端，配置为获取针对多个智能设备的场景控制指令，并在各所述智能设备中识别到至少一个第一设备的情况下，按照组播传输方式，向各所述第一设备发送所述场景控制指令；所述场景控制指令用于指示各所述智能设备分别执行对应的场景动作，所述第一设备为已配置有场景动作记录的智能设备；各所述智能设备，配置为响应于接收到的所述场景控制指令，基于已配置的场景动作记录，执行所述场景动作记录中与自身有关的场景动作。
根据本公开实施例的一个方面，一种电子设备，包括至少一个处理器以及至少一个存储器，其中，所述存储器上存储有计算机可读指令；所述计算机可读指令被一个或多个所述处理器执行，使得电子设备实现如上所述的设备控制方法。
根据本公开实施例的一个方面，一种存储介质，其上存储有计算机可读指令，所述计算机可读指令被一个或多个处理器执行，以实现如上所述的设备控制方法。
根据本公开实施例的一个方面，一种计算机程序产品，计算机程序产品包括计算机可读指令，计算机可读指令存储在存储介质中，电子设备的一个或多个处理器从存储介质读取计算机可读指令，加载并执行该计算机可读指令，使得电子设备实现如上所述的设备控制方法。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单地介绍。显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是根据本公开实施例所涉及的实施环境的示意图；
图2是根据本公开实施例所涉及的场景构建过程的方法流程图；
图3是根据本公开实施例所涉及的场景构建过程的示意图之一；
图4是根据本公开实施例所涉及的场景构建过程的示意图之二；
图5是根据一示例性实施例示出的一种设备控制方法的流程图；
图6是根据一示例性实施例示出的场景动作记录配置过程的方法流程图；
图7是图6对应实施例所涉及的步骤430在一个实施例中的流程图；
图8是根据一示例性实施例示出的另一种设备控制方法的流程图；
图9是根据一示例性实施例示出的另一种设备控制方法的流程图；
图10是根据一示例性实施例示出的网关向第一设备和第二设备发送不同指令的示意图；
图11是根据一示例性实施例示出的另一种设备控制方法的流程图；
图12是根据一示例性实施例示出的一种设备控制装置的结构框图；
图13是根据一示例性实施例示出的另一种设备控制装置的结构框图；
图14是根据一示例性实施例示出的一种设备控制系统的结构框图；
图15是根据一示例性实施例示出的一种电子设备的硬件结构图；
图16是根据一示例性实施例示出的一种电子设备的结构框图。
具体实施方式
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，仅用于解释本公开，而不能解释为对本公开的限制。
本技术领域技术人员可以理解，除非特意声明，这里使用的单数形式“一”、“一个”、“所述”和“该”也可包括复数形式。应该进一步理解的是，本公开的说明书中使用的措辞“包括”是指存在所述特征、整数、步骤、操作、元件和/或组件，但是并不排除存在或添加一个或多个其他特征、整数、步骤、操作、元件、组件和/或它们的组。应该理解，当我们称元件被“连接”或“耦接”到另一元件时，它可以直接连接或耦接到其他元件，或者也可以存在中间元件。此外，这里使用的“连接”或“耦接”可以包括无线连接或无线耦接。这里使用的措辞“和/或”包括一个或更多个相关联的列出项的全部或任一单元和全部组合。
下面是对本公开涉及的几个名词进行的介绍和解释：
组播：又称多目标广播、多播，是一种点对多点的网络通信方式，也认为是一种在一个发送者和多个接收者之间进行数据传输的网络通信方式，发送者只发送一份数据，多个接收者接收到的数据都是该份数据的拷贝，即相同数据。
单播：是一种点对点的网络通信方式，主要应用于一个发送者和一个接收者之间的数据传输，若需要应用于一个发送者与多个接收者之间进行相同数据的传输，与组播的区别在于，发送者仍需要发送多份相同数据。
本公开提供的技术方案带来的有益效果是：
在上述技术方案中，基于获取到的针对多个设备的场景控制指令，该场景控制指令用 于指示各设备分别执行对应的场景动作，那么，若识别到至少一个第一设备，即已配置有场景动作记录的设备，便能够按照组播传输方式，向各第一设备发送场景控制指令，以指示各第一设备响应于场景控制指令，执行场景动作记录中为第一设备记录的场景动作，也就是说，以场景动作记录的方式，对至少一个第一设备对应执行的场景动作进行记录，并配置给该些第一设备，那么，在设备控制过程中，通过组播传输方式向该些第一设备发送场景控制指令，便能够控制该些第一设备，同步执行已配置的场景动作记录中为第一设备记录的对应的场景动作，避免基于多条指令逐一控制多个智能设备，也即是避免了多个智能设备顺序执行对应的设定动作，进而减小了多设备执行多动作的网络延迟，从而能够有效的解决相关技术中存在的多设备执行多动作网络延迟较大的问题。
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
图1为本公开实施例所涉及的实施环境的示意图。该实施环境包括用户终端110、智能设备130、网关150、服务器端170和路由器190。
具体地，用户终端110，也可以认为是用户端或者终端，可进行智能设备130关联的客户端的部署(也理解为安装)，此用户终端110可以是智能手机、平板电脑、笔记本电脑、台式电脑、智能控制面板、其他具有显示和控制功能的设备等电子设备，在此不进行限定。
其中，客户端，与智能设备130关联，实质是用户在客户端中进行账户注册，并在客户端中对智能设备130进行配置，例如，该配置包括为智能设备130添加设备标识等，以使得用户终端110中运行客户端时，能够为用户提供关于智能设备130的设备控制等功能，此客户端可以是应用程序形式，也可以是网页形式，相应地，客户端进行设备显示的界面则可以是程序窗口形式，还可以是网页页面形式的，此处也并未加以限定。
智能设备130部署在网关150中，并通过其自身所配置的通信模块与网关150通信，进而受控于网关150。应当理解，智能设备130泛指多个智能设备130中的一个，本公开实施例仅以智能设备130举例说明，也即是，本公开实施例对部署在网关150中的智能设备的数量和设备类型并未加以限定。在一个应用场景中，智能设备130通过局域网络接入网关150，从而部署于网关150中。智能设备130通过局域网络接入网关150的过程包括：由网关150首先建立一个局域网络，智能设备130通过连接该网关150，从而加入该网关150建立的局域网络中。此局域网络包括但不限于：ZIGBEE或者蓝牙。其中，智能设备130可以是智能打印机、智能传真机、智能摄像机、智能空调、智能门锁、智能灯、智能风扇、智能音箱或者配置了通信模块的人体传感器、门窗传感器、温湿度传感器、水浸传感器、天然气报警器、烟雾报警器、墙壁开关、墙壁插座、无线开关、无线墙贴开关、魔方控制器、窗帘电机等电子设备。本公开各实施例中智能设备130尤其是指智能门锁。
用户终端110与智能设备130之间的交互，可以通过局域网络实现，还可以通过广域 网络实现。在一个应用场景中，用户终端110通过路由器190与网关150之间建立有线或者无线等方式的通信连接，例如，该有线或者无线等方式包括但不限于WIFI等，使得用户终端110与网关150部署于同一个局域网络，进而使得用户终端110可通过局域网络路径实现与智能设备130之间的交互。在另一个应用场景中，用户终端110通过服务器端170与网关150之间建立有线或者无线等方式的通信连接，例如，该有线或者无线等方式包括但不限于2G、3G、4G、5G、WIFI等，使得用户终端110与网关150部署于同一个广域网络，进而使得用户终端110可通过广域网络路径实现与智能设备130之间的交互。
其中，服务器端170，也可以认为是云端、云平台、平台端、服务端等等，此服务器端170可以是一台服务器，也可以是由多台服务器构成的一个服务器集群，或者是由多台服务器构成的云计算中心，以便于更好地向海量用户终端110提供后台服务。例如，后台服务包括但不限于设备控制服务等等。
值得一提的是，相对于用户终端110可以认为是用户端，服务器端170和网关150均可以认为是服务端的一种实施例，此处并未进行具体限定。
对本公开实施例所涉及的一种实施环境进行介绍之后，下面结合图2和图3对本公开实施例所涉及的场景构建过程进行介绍。其中，图2示出了一个实施例中场景构建过程的方法流程图。图3示出了一个实施例中用户终端中场景构建过程的示意图。
如图2所示，构建场景的过程，可以包括以下步骤：
步骤210，在场景显示页面中，显示已构建的至少一个场景、以及场景添加入口。
如图3所示，在场景显示页面301中，显示已构建的场景303、场景304、以及场景添加入口302。应当说明的是，场景通过场景标识唯一地表示，同理，智能设备通过设备标识唯一地表示，场景动作通过动作标识唯一地表示，该些标识可以是字母、数字、字符串、文字、图形等形式，此处并未加以限定。例如，场景标识A唯一地表示场景303，场景标识B唯一地表示场景304。
步骤230，响应于对场景添加入口的触发操作，从场景显示页面跳转至场景配置页面，以进行场景的添加。
在一个可能的实现方式，在场景配置页面中，显示已配置的至少一个动作、以及场景名称配置入口、动作添加入口。
如图3所示，如果用户点击场景显示页面301中的“+”控件302，从场景显示页面301跳转至场景配置页面401，同时，在场景配置页面401中，不仅显示有已配置的动作“关客厅灯”403、还显示有场景名称配置入口402和动作配置入口404。其中，用户的点击操作视为对场景配置入口的触发操作。
步骤250，基于场景添加指令，确定场景，并显示在场景显示页面。
在一个可能的实现方式，场景添加指令由以下至少一种操作触发：输入操作，用于为场景输入场景标识；动作配置操作，用于配置至少一个智能设备在场景执行对应的场景动作；场景确认操作，用于对场景完成添加进行确认。
如图3所示，在输入控件402中，可以为场景输入“关所有灯”，作为该设定设备的场景标识，此用户的输入操作视为输入操作；若用户点击场景配置页面401中的“+”控件404，则表示用户期望在场景中新增一个智能设备执行的场景动作，或者，若用户点击“>”控件406，则表示用户期望在场景中修改一个智能设备执行的场景动作，此用户的上述点击操作均可视为动作配置操作；若用户点击“完成”控件405，则表示用户确认场景完成添加，此用户的点击操作视为场景确认操作。基于上述至少一种操作，便能够触发生成场景添加指令，确定场景由场景标识“关所有灯”表示，并显示在场景显示页面302，即“关所有灯”。
可选地，步骤250中还可以包括以下步骤：响应于动作配置操作，从场景配置页面跳转至动作配置页面；基于动作配置页面中触发的动作配置指令，确定智能设备在场景中执行的场景动作，并显示在场景配置页面中。
在一个可能的实现方式，动作配置指令由以下至少一种操作触发：设备选择操作，用于为场景选择智能设备；位置选择操作，用于为场景中选择的智能设备选择部署位置，该部署位置包括但不限于：主卧室、客卧室、卫生间、餐厅、客厅、书房、储物室、衣帽间、阳台、厨房、走廊等等，也可以认为是，该部署位置具体限定了智能设备的类型，例如，若“开关”的部署位置为餐厅，则表示智能设备为“餐厅灯”，或者，若“开关”的部署位置为客厅，则表示智能设备为“客厅灯”；动作选择操作，用于为场景中选择的智能设备选择场景动作；动作确认操作，用于对场景中场景动作的配置进行确认。
如图3所示，在选择控件502中，可以为场景选择与灯连接的“开关”，作为为场景选择的智能设备，此用户的选择操作视为设备选择操作；在选择控件503中，可以为开关选择“餐厅”，作为为场景中选择的智能设备选择部署位置，此用户的选择操作视为位置选择操作；在选择控件504中，可以为开关选择“关”，作为为场景中选择的智能设备选择场景动作；若用户点击“下一步”控件505，则表示用户确认场景中场景动作完成配置，此用户的点击操作视为动作确认操作。基于上述至少一种操作，便能够触发生成动作配置指令，从而确定部署在“餐厅”中与灯连接的智能设备“开关”在场景中执行的场景动作为“关”，并显示在场景配置页面401中，即“关餐厅灯”。
步骤270，响应于对目标场景的场景选择操作，从场景显示页面跳转至目标场景的场景详情页面。
在图3中，如果用户点击场景标识“关所有灯”表示的场景305，表示用户选中场景305为目标场景，此时，从场景显示页面301跳转至场景305的场景详情页面601，即“关所有灯”，在该场景详情页面601中至少显示：至少一个智能设备在场景305执行的场景动作，例如，客厅灯在场景305中执行关闭，即“关客厅灯”602；餐厅灯在场景305中执行关闭，即“关餐厅灯”等等。其中，用户的点击操作视为对目标场景的场景选择操作。同时，在该场景详情页面601中还显示有场景执行入口603，为用户提供场景一键执行的功能，以此来指示至少一个智能设备在该场景中执行对应的场景动作。例如，若用户点击 场景执行入口603，视为一键执行“关所有灯”场景，则客厅灯和餐厅灯相应关闭，从而实现关所有灯场景的受控执行。
同理于场景配置页面401，场景详情页面601中，也可以通过控件603、动作添加入口604形成动作配置操作，以基于动作配置操作，在场景中新增/修改一个智能设备执行的场景动作。当然，在其他实施例中，场景配置页面和场景详情页面还可以根据用户的使用体验合并为同一页面，此处并非构成具体限定。
补充说明的是，用户终端中构建的场景，除了图3示出的受控执行场景，还存在一种自动化场景，构建过程与受控执行场景的构建过程基本一致，区别在于，自动化场景中除了需要配置相关的场景动作，还需要配置相关的触发条件。也就是说，受控执行场景，是在用户点击场景执行入口的情况下，在受控执行场景中进行了场景动作配置的智能设备方才执行对应的场景动作；而自动化场景，是指若自动化场景中配置的触发条件被满足，则在自动化场景中进行了场景动作配置的智能设备将自动执行对应的场景动作。
现结合图4，以自动化场景为回家场景举例，对自动化场景中区别于受控执行场景的触发条件进行如下详细地说明：
如图4所示，假设自动化场景306已构建，并通过“回家场景”的场景标识在场景显示页面302中显示，那么，当用户点击该场景标识，便可进入自动化场景306的场景详情页面701。在场景详情页面701中，显示的触发条件为：智能门锁开启，显示的场景动作为：开客厅灯、开客厅空调，还显示了用于新增触发条件的条件添加入口703、以及用于新增场景动作的动作添加入口706，此外，修改触发条件可通过控件702实施，修改场景动作可通过控件704、705实施。基于此，随着自动化场景306的构建，当用户回家使得智能门锁开启，便视为自动化场景306中配置的触发条件满足，此时，在自动化场景306中配置了场景动作的客厅灯、客厅空调便会自动执行对应的场景动作，亦即是自动打开客厅灯、自动打开客厅空调，从而实现回家场景的自动执行。
值得一提的是，根据用户终端所配置输入组件(例如显示屏幕上覆盖的触摸层、鼠标、键盘等)的不同，上述各操作的具体行为也可以有所差别。例如，用户终端为配置触摸层的智能手机，上述各操作可以是点击、滑动等手势操作；而对于用户终端为配置鼠标的笔记本电脑来说，上述各操作则可以是拖拽、单击、双击等机械操作，此处并未加以限定。由此可见，随着场景在用户终端中构建，用户便能够借助用户终端中构建的受控执行场景或者自动化场景，控制多设备执行多动作。
设备控制过程具体是指，如图5所示，步骤310，获取针对多个设备的场景控制指令；场景控制指令用于指示各设备分别执行对应的场景动作；步骤330，识别各设备中的第一设备；第一设备为已配置有场景动作记录的设备；步骤350，若识别到至少一个第一设备，则按照组播传输方式，向各第一设备发送场景控制指令，以指示各第一设备响应于场景控制指令，同步执行场景动作记录中为第一设备记录的场景动作。
上述过程中，实现了基于一条场景控制指令同时控制多设备执行多动作，避免基于多 条指令逐一控制多个智能设备，也即是避免了多个智能设备顺序执行对应的设定动作，进而减小了多设备执行多动作的网络延迟，从而能够有效的解决相关技术中存在的多设备执行多动作网络延迟较大的问题。
现结合图6至图7，首先对设备控制过程中场景动作记录的配置进行以下详细地说明，以该配置过程应用于电子设备为例进行说明。其中，电子设备可以是图1中的网关150，还可以是图1中的服务器端170、用户终端110等，此处并未构成具体限定。
如图6所示，场景动作记录的配置过程，可以包括以下步骤：
步骤410，接收用户终端发送的场景配置数据。
其中，场景配置数据是用户终端中构建场景时生成的，该场景配置数据至少指示了多个设备被配置允许执行的场景动作。
应当理解，随着场景的不同，即使是同一个智能设备(下文简称为设备)，被配置允许执行的场景动作也可能有所区别。例如，场景为主卧室，当主人睡觉，智能风扇开启；若场景为卫生间，当主人离开，智能风扇关闭，因此，为设备配置执行的场景动作是以场景为前提进行的，场景不同，场景配置数据也各不相同。例如，场景配置数据A对应于受控执行场景，该场景配置数据A用于指示多个设备在受控执行场景中被配置允许执行的场景动作；场景配置数据B对应于自动化场景，该场景配置数据B用于指示自动化场景中配置的触发条件，亦即是指示了多个设备在自动化场景中满足触发条件时的设备状态，还用于指示多个设备在自动化场景中被配置允许执行的场景动作。
在一个可能的实现方式，场景配置数据至少包括：场景的场景标识、至少一个设备的设备标识、对应于设备的场景动作的动作标识。
步骤430，根据场景配置数据，请求对多个设备中的第三设备进行场景动作记录的配置。
其中，第三设备为支持场景动作记录配置的设备。对应地，第一设备为完成配置的设备；第二设备为不支持场景动作记录配置的设备，亦即是未进行配置的设备。
场景动作记录，是对设备在场景中被配置允许执行的场景动作的记录，可以理解为是一种针对设备功能的快照数据，例如可以将设备支持的执行动作打包为快照动作，包含这个快照动作的数据则可以为场景动作记录。相应地，场景动作记录的配置，是指在第三设备中存储场景动作记录，以使得第三设备提前获知其自身能够在场景中执行的场景动作。
具体地，如图7所示，步骤430可以包括以下步骤：
步骤431，基于场景配置数据指示的多个设备，确定多个设备中的第三设备。
在一个可能的实现方式，设备是否支持场景动作记录的配置通过设备标识确定，例如，在服务器端，预先存储支持场景动作记录的配置的设备标识。在一个可能的实现方式，设备是否支持场景动作记录的配置通过设备版本信息确定，例如，在服务器端，预先存储支持场景动作记录的配置的设备版本信息。当然，在其他实施例中，设备是否支持场景动作 记录的配置还可以通过添加快照标识确定，例如，若服务器端识别到设备携带的快照标识为1，则表示该设备支持场景动作记录的配置，此处并非对此构成具体限定。
步骤433，从场景配置数据中，得到与所确定的第三设备关联的快照配置数据。
其中，快照配置数据用于指示第三设备被配置允许执行的场景动作。
在一个可能的实现方式，快照配置数据至少包括：至少一个第三设备的设备标识、对应于第三设备的场景动作的动作标识。
步骤435，将快照配置数据发送至关联的第三设备，使得第三设备根据快照配置数据进行场景动作记录的配置。
由此，在完成场景动作记录配置的情况下，第三设备转化为完成配置的第一设备。
举例来说，假设在场景A中，墙壁开关B1开启(动作标识为C1)，灯B2的亮度为50％(动作标识为C2)，空调B3温度为26度(动作标识为C3)。其中，灯B2和空调B3支持场景动作记录的配置，墙壁开关B1不支持场景动作记录的配置。
那么，场景配置数据＝{A、B1(C1)、B2(C2)、B3(C3)}。
灯B2和空调B3为第三设备，则得到该第三设备关联的快照配置数据＝{B2(C2)、B3(C3)}。
在一个可能的实现方式，场景动作记录的配置，具体是指，将场景的场景标识、第三设备的设备标识、场景动作的动作标识存储至第三设备。以前述例子进行说明，对于灯B2来说，存储有其在场景A中执行场景动作的动作标识C2，那么，在后续多设备于场景A中执行多动作的过程中，便能够按照预先存储的动作标识C2表示的场景动作，也可以认为是，已配置的场景动作记录中与自身有关的场景动作执行，即调整亮度至50％。
值得一提的是，场景动作记录的配置过程中，在一个可能的实现方式，网关可以向每一个第三设备下发快照配置数据中与该第三设备对应的部分，例如，灯B2仅能够接收到其在场景中执行场景动作的动作标识C2，以此减少网关与第三设备之间的数据量传输，有利于提升传输效率；在另一个可能的实施方式，网关还可以向每一个第三设备下发快照配置数据的完整部分，例如，灯B2不仅能够接收到其在场景中执行场景动作的动作标识C2，同时还能够接收到空调B3在场景中执行场景动作的动作标识C3，以此减轻网关的处理负担，有利于提升网关的处理效率，此时，灯B2需要进一步结合自身的设备标识B2进行场景动作记录的配置，以便于后续能够执行场景动作记录中与自身有关的场景动作，此处并未加以限定。
在上述过程中，实现关于设备的场景动作记录的配置，以便于后续设备基于已配置的场景动作记录快速地执行与自身有关的场景动作。
在一个可能的实现方式，一种设备控制方法，以该方法应用于电子设备为例进行说明，例如该电子设备可以是图1中的智能设备130。如图8所示，设备控制方法可以包括以下步骤：步骤370，接收针对多个设备的场景控制指令；该场景控制指令用于指示各设备分别执行对应的场景动作；步骤390，基于已配置的场景动作记录，响应于该场景控制指令， 执行场景动作记录中与自身有关的场景动作。在一个可能的实现方式，以该方法由设备控制系统执行，通过服务端与智能设备之间交互实现为例进行说明，其中，服务端包括但不限于图1所示出的网关150、服务器端170，智能设备则可以是图1中的智能设备130，相应地，设备控制方法可以包括以下步骤：服务端获取针对多个智能设备的场景控制指令，并在各智能设备中识别到至少一个第一设备的情况下，按照组播传输方式，向各第一设备发送场景控制指令；场景控制指令用于指示各智能设备分别执行对应的场景动作，第一设备为已配置有场景动作记录的智能设备；各第一设备响应于接收到的场景控制指令，基于已配置的场景动作记录，执行场景动作记录中与自身有关的场景动作。由此，通过服务端(例如网关)发送一条指令便能够同时控制多个设备执行多个动作，从而有利于解决相关技术中存在的多设备执行多动作网络延迟较大的问题。
请参阅图9，本公开实施例提供了一种设备控制方法，以该方法应用于电子设备为例进行说明。其中，电子设备可以是服务端，例如，该服务端可以是图1中的网关150，还可以是图1中的服务器端170，此处并未构成具体限定。
如图9所示，设备控制方法可以包括以下步骤：
步骤510，获取针对多个设备的场景控制指令。
其中，场景控制指令用于指示各设备分别执行对应的场景动作。
在一个可能的实现方式，场景控制指令至少包括：场景的场景标识、至少一个设备的设备标识、至少一个设备在场景中对应执行的场景动作的动作标识。
关于场景控制指令的获取，在一个可能的实现方式，具体是指，接收用户终端发送的针对多个设备的场景控制指令。其中，场景控制指令用于指示用户终端中构建的目标场景被执行，该目标场景中为多个设备配置了对应的场景动作。此种方式下，场景控制指令是针对目标场景为受控执行场景而言，该场景控制指令是在用户一键执行目标场景时生成的，进而由用户终端发送至网关，以使网关控制各设备分别执行在受控执行场景中配置的对应的场景动作。
关于场景控制指令的获取，在一个可能的实现方式，具体是指，接收多个设备发送的设备状态数据，该设备状态数据用于指示设备的设备状态；根据接收到的设备状态数据，若确定设备联动数据中的触发条件满足，则根据设备联动数据中多个设备对应执行的场景动作，生成针对多个设备的场景控制指令。此种方式下，场景控制指令针对自动化场景而言，在自动化场景中配置的触发条件被满足时，该场景控制指令由网关生成，以使网关控制各设备分别执行在自动化场景中配置的对应的场景动作。
步骤520，基于场景控制指令，对各设备进行场景动作记录的配置检测，确定完成配置的至少一个第一设备，和/或，未进行配置的至少一个第二设备。
其中，第一设备为已配置场景动作记录的设备。第二设备为未进行配置的设备。场景动作记录，是对设备在场景中被配置允许执行的场景动作的记录。
在一个可能的实现方式，场景动作记录的配置检测，是指根据场景控制指令中的设备标识确定多个设备，进而确定各设备中是否存储场景的场景标识、以及设备在场景中执行的场景动作的动作标识，以此来确定各设备是否已配置有场景动作记录。
例如，针对根据场景控制指令中设备标识确定的多个设备中的每一个设备，网关对该设备进行场景动作记录的配置检测，包括：网关向该设备发送关于场景动作记录的配置检测请求；该设备响应于该配置检测请求，而向网关返回相应的请求响应，该请求响应中携带了该设备中存储的场景标识A、该设备在该场景中执行的场景动作的动作标识C3，则确定该设备已配置有场景动作记录。即，该场景动作记录中记录了该设备在场景标识A所表示的场景中，执行动作标识C3所表示的场景动作。
将完成配置的设备，作为第一设备，并执行步骤530，即响应于场景控制指令，执行场景动作记录中为第一设备记录的场景动作。
将未进行配置的设备，作为第二设备，并执行步骤550，即响应于场景控制指令对应的设备控制指令，执行第二设备在场景中配置的场景动作。
步骤530，将至少一个第一设备作为组播成员，向组播成员发送场景控制指令，以指示组播成员响应于场景控制指令，同步执行场景动作记录中为组播成员记录的场景动作。
图10示出了网关分别向第一设备和第二设备发送不同指令的示意图。在图10中，由于二个第一设备完成了场景动作记录的配置，即该二个第一设备中记录了其在场景中对应执行的场景动作，故，对于该二个第一设备而言，网关150实质是以组播传输方式，通过一条场景控制指令(指令①)进行控制的，以此实现该二个第一设备同步执行场景动作记录中与自身有关的场景动作。
步骤550，按照单播传输方式，分别向各第二设备发送场景控制指令对应的设备控制指令，使得各第二设备分别响应于设备控制指令，执行对应的场景动作。
如前所述，对于第二设备而言，其中并未存储有任何场景的场景标识、以及该第二设备在该场景中执行的场景动作的动作标识，因此，在一个可能的实现方式，设备控制指令从场景控制指令中提取，至少包括场景的场景标识、该第二设备在该场景中执行的场景动作的动作标识，以指示第二设备在场景中执行场景动作。
继续参阅图10，由于二个第二设备未完成场景动作记录的配置，即该二个第二设备中并不知道其在场景中对应执行的场景动作，故，对于该二个第二设备而言，网关150以单播传输方式，先后发送了两条设备控制指令(指令②和指令③)至每一个第二设备，以使得该二个第二设备按照接收到设备控制指令的顺序，依次执行其在场景中的场景动作。
根据网络运营的实际需要，在一个应用场景中，设备控制的过程在用户终端、服务器端、网关之间实现，例如，场景控制指令由服务器端转发至网关。在另一个应用场景中，设备控制的过程还可以在用户终端、网关之间实现，例如，场景控制指令由用户终端发送至网关。
通过上述过程，就未进行配置的第二设备来说，设备控制未有改进，仍需要网关依次 发送多条指令来逐一控制多个第二设备，而就完成配置的第一设备来说，设备控制有了较大改进，即网关仅需要发送一条指令便能够同时控制多个第一设备执行多个动作，从而避免了多个设备按照顺序执行场景中的动作，随着设备数量的增加，更有利于减小多设备执行动作的网络延时，达到多设备同时快速控制的效果，有利于用户的使用体验大大提升，例如，用户希望多个设备统一动作，达到动作一致性的效果，而不是先后动作。
此外，场景动作记录的配置，不仅适用于多设备执行相同动作，还同样适用于多设备执行不同动作，有效地扩展了设备控制的通用性。
请参阅图11，在一示例性实施例中，设备控制方法还可以包括以下步骤：
步骤610，针对各第一设备，接收第一设备发送的设备状态数据。
其中，设备状态数据用于指示第一设备执行场景动作后的设备状态。例如，场景为卫生间，若智能风扇执行了关闭动作，则设备状态数据用于指示智能风扇的设备状态为关闭，或者，若智能灯执行了开启动作，则设备状态数据用于指示智能灯的设备状态为开启。
步骤630，检测设备状态数据是否接收超时。
相对于网关而言，设备状态数据的接收超时，亦即是第一设备上报设备状态数据超时。若检测到至少一个第一设备上报设备状态数据超时，则执行步骤650。反之，若检测到各第一设备上报设备状态数据均未超时，则确认所有第一设备均已同步执行了场景动作记录中为第一设备记录的场景动作。
步骤650，按照组播传输方式，向各第一设备重新发送场景控制指令。
在一个可能的实现方式，向所有第一设备重新发送场景控制指令。在一个可能的实现方式，向上报超时的第一设备重新发送场景控制指令，直至确认所有第一设备均已同步执行了场景动作记录中为第一设备记录的场景动作，不仅能够最大限度地保证动作执行的成功率，从而保证设备控制的成功率，而且还充分地保障了设备控制的稳定性。
应当说明的是，针对每一个第一设备，有的第一设备可能已执行了场景动作，并且上报设备状态数据未超时，则该第一设备可忽略重新接收到的场景控制指令，而对于未执行场景动作，或者，上报设备状态数据超时的第一设备来说，则需要再次响应重新接收到的场景控制指令，并重新执行场景动作记录中为该第一设备记录的场景动作。
上述过程中，实现了设备状态上报检测，通过超时重发机制，使得第一设备能够再次接收到场景控制指令而被再次控制，方能够再次执行场景动作，从而增强系统的健壮性，提高设备控制的稳定性。
下述为本公开装置实施例，可以用于执行本公开所涉及的设备控制方法。对于本公开装置实施例中未披露的细节，请参照本公开所涉及的设备控制方法的方法实施例。
请参阅图12，本公开实施例中提供了一种设备控制装置900，部署于服务端，该设备控制装置900包括但不限于：指令获取器910、设备识别器930、以及指令发送器950。
其中，指令获取器910，配置为获取针对多个设备的场景控制指令；场景控制指令用于指示各设备分别执行对应的场景动作设备。
设备识别器930，配置为识别各设备中的第一设备；第一设备为已配置有与场景控制指令关联的场景动作记录的设备。
指令发送器950，配置为若识别到至少一个第一设备，则按照组播传输方式，向各第一设备发送场景控制指令，以指示各第一设备响应于场景控制指令，同步执行场景动作记录中为第一设备记录的场景动作。
在一示例性实施例中，指令获取器，包括：指令接收器，配置为接收用户终端发送的针对多个设备的场景控制指令，场景控制指令用于指示用户终端中构建的目标场景被执行，目标场景中为多个设备配置了对应的场景动作。
在一示例性实施例中，指令获取器，包括：状态数据接收器，配置为接收多个设备发送的设备状态数据，设备状态数据用于指示设备的设备状态；指令生成器，配置为根据接收到的设备状态数据，若确定设备联动数据中的触发条件满足，则根据设备联动数据中多个设备对应执行的动作，生成针对多个设备的场景控制指令。
在一示例性实施例中，设备识别器，包括：配置检测器，配置为基于场景控制指令，对各设备进行场景动作记录的配置检测，确定完成配置的至少一个第一设备，和/或，未进行配置的至少一个第二设备；指令发送器，包括：组播发送器，配置为以至少一个第一设备作为组播成员，向组播成员发送场景控制指令。
在一示例性实施例中，指令发送器还包括：单播发送器，配置为若识别到至少一个第二设备，则按照单播传输方式，分别向各第二设备发送场景控制指令对应的设备控制指令，使得各第二设备分别响应于设备控制指令，执行对应的场景动作。
在一示例性实施例中，装置还包括：状态数据接收器，配置为针对各第一设备，接收第一设备发送的设备状态数据，设备状态数据用于指示第一设备执行场景动作后的设备状态；指令重发器，配置为若检测到第一设备的设备状态数据接收超时，则按照组播传输方式，向各第一设备重新发送场景控制指令。
在一示例性实施例中，装置还包括：配置数据接收器，配置为接收场景配置数据，场景配置数据至少指示了多个设备被配置允许执行的场景动作；配置器，配置为根据场景配置数据，请求对多个设备中的第三设备进行场景动作记录的配置；第三设备为支持场景动作记录配置的设备。
在一示例性实施例中，配置器，包括：设备确定器，配置为基于场景配置数据指示的多个设备，确定多个设备中的第三设备；快照数据获取器，配置为从场景配置数据中，得到与所确定的第三设备关联的快照配置数据，快照配置数据用于指示第三设备被配置允许执行的场景动作；快照数据发送器，配置为将快照配置数据发送至关联的第三设备，使得第三设备根据快照配置数据进行场景动作记录的配置，在完成场景动作记录配置的情况下，第三设备转化为完成配置的第一设备。
请参阅图13，本公开实施例中提供了一种设备控制装置1000，部署于智能设备，该设备控制装置1000包括但不限于：指令接收器1010、以及动作执行器1030。
其中，指令接收器1010，配置为接收针对多个设备的场景控制指令；场景控制指令用于指示各设备分别执行对应的场景动作。
动作执行器1030，配置为基于已配置的与场景控制指令关联的场景动作记录，响应于场景控制指令，执行场景动作记录中与自身有关的场景动作。
请参阅图14，本公开实施例中提供了一种设备控制系统，该系统包括但不限于：服务端300和智能设备400。
其中，服务端300，配置为获取针对多个智能设备的场景控制指令，并在各智能设备中识别到至少一个第一设备的情况下，按照组播传输方式，向各第一设备发送场景控制指令；场景控制指令用于指示各智能设备分别执行对应的场景动作，第一设备为已配置有场景动作记录的智能设备。
各智能设备400，配置为响应于接收到的场景控制指令，基于已配置的场景动作记录，执行场景动作记录中与自身有关的场景动作。
需要说明的是，上述实施例所提供的设备控制装置或系统在进行设备控制时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即设备控制装置或系统的内部结构将划分为不同的功能模块，以完成以上描述的全部或者部分功能。
另外，上述实施例所提供的设备控制装置或系统与设备控制方法的实施例属于同一构思，其中各个模块执行操作的具体方式已经在方法实施例中进行了详细描述，此处不再赘述。
图15根据一示例性实施例示出的一种电子设备的结构示意。该电子设备适用于图1所示出实施环境中的智能设备130、网关150、服务器端170。
需要说明的是，该电子设备只是一个适配于本公开的示例，不能认为是提供了对本公开的使用范围的任何限制。该电子设备也不能解释为需要依赖于或者必须具有图15示出的示例性的电子设备2000中的一个或者多个组件。
电子设备2000的硬件结构可因配置或者性能的不同而产生较大的差异，如图15所示，电子设备2000包括：电源210、接口230、至少一存储器250、以及至少一中央处理器(CPU,Central Processing Units)270。
具体地，电源210用于为电子设备2000上的各硬件电子设备提供工作电压。
接口230包括至少一有线或无线网络接口231，用于与外部电子设备交互。例如，进行图1所示出实施环境中用户终端110与网关150之间的交互。
当然，在其余本公开适配的示例中，接口230还可以进一步包括至少一串并转换接口233、至少一输入输出接口235以及至少一USB接口237等，如图15所示，在此并非对 此构成具体限定。
存储器250作为资源存储的载体，可以是只读存储器、随机存储器、磁盘或者光盘等，其上所存储的资源包括操作系统251、应用程序253及数据255等，存储方式可以是短暂存储或者永久存储。
其中，操作系统251用于管理与控制电子设备2000上的各硬件电子设备以及应用程序253，以实现中央处理器270对存储器250中海量数据255的运算与处理，其可以是Windows ServerTM、Mac OS XTM、UnixTM、LinuxTM、FreeBSDTM等。
应用程序253是基于操作系统251之上完成至少一项特定工作的计算机可读指令，其可以包括至少一模块(图15未示出)，每个模块都可以分别包含有对电子设备2000的计算机可读指令。例如，电子设备控制装置可视为部署于电子设备2000的应用程序253。
数据255可以是存储于磁盘中的照片、图片等，还可以是设备状态数据、场景配置数据等，存储于存储器250中。
中央处理器270可以包括一个或多个以上的处理器，并设置为通过至少一通信总线与存储器250通信，以读取存储器250中存储的计算机可读指令，进而实现对存储器250中海量数据255的运算与处理。例如，通过中央处理器270读取存储器250中存储的一系列计算机可读指令的形式来完成电子设备控制方法。
此外，通过硬件电路或者硬件电路结合软件也能同样实现本公开，因此，实现本公开并不限于任何特定硬件电路、软件以及两者的组合。
请参阅图16，本公开实施例中提供了一种电子设备4000，该电子设备4000可以包括：智能设备、网关、服务器等等。
在图16中，该电子设备4000包括至少一个处理器4001、至少一条通信总线4002以及至少一个存储器4003。
其中，处理器4001和存储器4003之间的数据交互，可以通过至少一个通信总线4002实现。该通信总线4002可包括一通路，用于在处理器4001和存储器4003之间传输数据。通信总线4002可以是PCI(Peripheral Component Interconnect，外设部件互连标准)总线或EISA(Extended Industry Standard Architecture，扩展工业标准结构)总线等。通信总线4002可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选地，电子设备4000还可以包括收发器4004，收发器4004可以用于该设备与其他设备之间的数据交互，如数据的发送和/或数据的接收等。需要说明的是，实际应用中收发器4004不限于一个，该电子设备4000的结构并不构成对本公开实施例的限定。
处理器4001可以是CPU(Central Processing Unit，中央处理器)，通用处理器，DSP(Digital Signal Processor，数据信号处理器)，ASIC(Application Specific Integrated Circuit，专用集成电路)，FPGA(Field Programmable Gate Array，现场可编程门阵列)或者其他可 编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本公开公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器4001也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等。
存储器4003可以是ROM(Read Only Memory，只读存储器)或可存储静态信息和指令的其他类型的静态存储设备，RAM(Random Access Memory，随机存取存储器)或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM(Electrically Erasable Programmable Read Only Memory，电可擦可编程只读存储器)、CD-ROM(Compact Disc Read Only Memory，只读光盘)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的计算机可读指令并能够由电子设备4000存取的任何其他介质，但不限于此。
存储器4003上存储有计算机可读指令，处理器4001可以通过通信总线4002读取存储器4003中存储的计算机可读指令。
该计算机可读指令被处理器4001执行时实现上述各实施例中的设备控制方法。
此外，本公开实施例中提供了一种存储介质，该存储介质上存储有计算机可读指令，所述计算机可读指令被处理器加载并执行，以实现如如上所述的设备控制方法。
本公开实施例中提供了一种计算机程序产品，计算机程序产品包括计算机可读指令，计算机可读指令存储在存储介质中，设备的处理器从存储介质读取计算机可读指令，加载并执行该计算机可读指令，使得设备实现如上所述的设备控制方法。其中，该计算机程序产品可以使用任何编程语言，并采用源代码、目标代码或者在源代码和目标代码之间的中间代码的形式，诸如部分编译的形式或者任何其它所需的形式。
与相关技术相比，以场景动作记录的方式，对场景中至少一个设备对应执行的场景动作进行记录，并配置给该场景中的该至少一个设备，在设备控制过程中，通过组播方式向该些设备发送场景控制指令，该些设备便能够按照已配置的场景动作记录中为该些设备记录的场景动作，同时执行对应的场景动作，避免基于多条指令逐一控制多个设备，也即是避免了多个设备顺序执行对应的场景动作，进而减小了多设备执行多动作的网络延迟，从而能够有效的解决相关技术中存在的多设备执行多动作网络延迟较大的问题。
应该理解的是，虽然附图的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，其可以以其他的顺序执行。而且，附图的流程图中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，其执行顺序也不必然是依次进行，而是可以与其他步骤或者其他步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
以上所述仅是本公开的部分实施方式，应当指出，对于本技术领域的普通技术人员来 说，在不脱离本公开原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (15)

  1. 一种设备控制方法，由服务端执行，所述方法包括：
    获取针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；
    识别各所述设备中的第一设备；所述第一设备为已配置有场景动作记录的设备；
    若识别到至少一个所述第一设备，则按照组播传输方式，向各所述第一设备发送所述场景控制指令，以指示各所述第一设备响应于所述场景控制指令，同步执行所述场景动作记录中为所述第一设备记录的场景动作。
  2. 如权利要求1所述的方法，其中，所述获取针对多个设备的场景控制指令，包括：
    接收用户终端发送的针对多个所述设备的场景控制指令，所述场景控制指令用于指示所述用户终端中构建的目标场景被执行，所述目标场景中为多个所述设备配置了对应的场景动作。
  3. 如权利要求1所述的方法，其中，所述获取针对多个设备的场景控制指令，包括：
    接收多个所述设备发送的设备状态数据，所述设备状态数据用于指示所述设备的设备状态；
    根据接收到的设备状态数据，若确定设备联动数据中的触发条件满足，则根据所述设备联动数据中多个所述设备对应执行的场景动作，生成针对多个所述设备的场景控制指令。
  4. 如权利要求1所述的方法，其中，所述识别各所述设备中的第一设备，包括：
    基于所述场景控制指令，对各所述设备进行场景动作记录的配置检测，确定完成配置的至少一个所述第一设备，和/或，未进行配置的至少一个第二设备；
    所述按照组播传输方式，向各所述第一设备发送所述场景控制指令，包括：
    以至少一个所述第一设备作为组播成员，向所述组播成员发送所述场景控制指令。
  5. 如权利要求4所述的方法，其中，所述识别各所述设备中的第一设备之后，所述方法还包括：
    若识别到至少一个所述第二设备，则按照单播传输方式，分别向各所述第二设备发送所述场景控制指令对应的设备控制指令，使得各所述第二设备分别响应于所述设备控制指令，执行对应的场景动作。
  6. 如权利要求1所述的方法，其中，所述按照组播传输方式，向各所述第一设备发送所述场景控制指令之后，所述方法还包括：
    针对各所述第一设备，接收所述第一设备发送的设备状态数据，所述设备状态数据用于指示所述第一设备执行场景动作后的设备状态；
    若检测到所述第一设备的设备状态数据接收超时，则按照组播传输方式，向各所述第一设备重新发送所述场景控制指令。
  7. 如权利要求1至6任一项所述的方法，其中，所述方法还包括：
    接收场景配置数据，所述场景配置数据至少指示了多个所述设备被配置允许执行的场景动作；
    根据所述场景配置数据，请求对多个所述设备中的第三设备进行场景动作记录的配置；所述第三设备为支持场景动作记录配置的设备。
  8. 如权利要求7所述的方法，其中，所述根据所述场景配置数据，请求对多个所述设备中的所述第一设备进行场景动作记录的配置，包括：
    基于所述场景配置数据指示的多个所述设备，确定多个所述设备中的所述第三设备；
    从所述场景配置数据中，得到与所确定的第三设备关联的快照配置数据，所述快照配置数据用于指示所述第三设备被配置允许执行的场景动作；
    将所述快照配置数据发送至关联的所述第三设备，使得所述第三设备根据所述快照配置数据进行场景动作记录的配置，在完成场景动作记录配置的情况下，所述第三设备转化为完成配置的所述第一设备。
  9. 一种设备控制方法，由智能设备执行，所述方法包括：
    接收针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；
    基于已配置的场景动作记录，响应于所述场景控制指令，执行所述场景动作记录中与自身有关的场景动作。
  10. 一种设备控制方法，由设备控制系统执行，所述设备控制系统包括服务端和智能设备，所述方法包括：
    所述服务端获取针对多个智能设备的场景控制指令，并在各所述智能设备中识别到至少一个第一设备的情况下，按照组播传输方式，向各所述第一设备发送所述场景控制指令；所述场景控制指令用于指示各所述智能设备分别执行对应的场景动作，所述第一设备为已配置有场景动作记录的智能设备；
    各所述第一设备响应于接收到的所述场景控制指令，基于已配置的场景动作记录，执行所述场景动作记录中与自身有关的场景动作。
  11. 一种设备控制装置，部署于服务端，所述装置包括：
    指令获取器，配置为获取针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；
    设备识别器，配置为识别各所述设备中的第一设备；所述第一设备为已配置有场景动作记录的设备；
    指令发送器，配置为若识别到至少一个所述第一设备，则按照组播传输方式，向各所述第一设备发送所述场景控制指令，以指示各所述第一设备响应于所述场景控制指令，同步执行所述场景动作记录中为所述第一设备记录的场景动作。
  12. 一种设备控制装置，部署于智能设备，所述装置包括：
    指令接收器，配置为接收针对多个设备的场景控制指令；所述场景控制指令用于指示各所述设备分别执行对应的场景动作；
    动作执行器，配置为基于已配置的场景动作记录，响应于所述场景控制指令，执行所述场景动作记录中与自身有关的场景动作。
  13. 一种设备控制系统，所述系统包括：
    服务端，配置为获取针对多个智能设备的场景控制指令，并在各所述智能设备中识别到至少一个第一设备的情况下，按照组播传输方式，向各所述第一设备发送所述场景控制指令；所述场景控制指令用于指示各所述智能设备分别执行对应的场景动作，所述第一设备为已配置有场景动作记录的智能设备；
    各所述智能设备，配置为响应于接收到的所述场景控制指令，基于已配置的场景动作记录，执行所述场景动作记录中与自身有关的场景动作。
  14. 一种电子设备，包括：至少一个处理器以及至少一个存储器，其中，
    所述存储器上存储有计算机可读指令；
    所述计算机可读指令被一个或多个所述处理器执行，使得电子设备实现如权利要求1至10中任一项所述的设备控制方法。
  15. 一种存储介质，其上存储有计算机可读指令，所述计算机可读指令被一个或多个处理器执行，以实现如权利要求1至10中任一项所述的设备控制方法。
PCT/CN2023/093300 2022-04-21 2023-05-10 设备控制方法、装置、设备及存储介质 Ceased WO2023226768A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23810841.9A EP4530761A4 (en) 2022-05-23 2023-05-10 METHOD AND APPARATUS FOR CONTROLLING DEVICE, DEVICE AND STORAGE MEDIUM
US18/920,955 US20250060714A1 (en) 2022-04-21 2024-10-20 Device control method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210565411.X 2022-05-23
CN202210565411.XA CN115016302B (zh) 2022-05-23 2022-05-23 设备控制方法、装置、设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/920,955 Continuation-In-Part US20250060714A1 (en) 2022-04-21 2024-10-20 Device control method

Publications (1)

Publication Number Publication Date
WO2023226768A1 true WO2023226768A1 (zh) 2023-11-30

Family

ID=83068302

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/093300 Ceased WO2023226768A1 (zh) 2022-04-21 2023-05-10 设备控制方法、装置、设备及存储介质

Country Status (3)

Country Link
EP (1) EP4530761A4 (zh)
CN (1) CN115016302B (zh)
WO (1) WO2023226768A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115016302B (zh) * 2022-05-23 2025-07-11 深圳绿米联创科技有限公司 设备控制方法、装置、设备及存储介质
CN116112538A (zh) * 2022-12-26 2023-05-12 珠海格力电器股份有限公司 一种联动场景的指令下发方法、装置、介质及电子设备

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170357425A1 (en) * 2016-06-12 2017-12-14 Apple Inc. Generating Scenes Based On Accessory State
CN108037675A (zh) * 2018-02-01 2018-05-15 苏州创爵智能科技有限公司 一种基于ZigBee Group的智能家居场景控制方法
CN111650845A (zh) * 2020-06-05 2020-09-11 杭州鸿雁电器有限公司 家居组播控制方法、系统和计算机可读存储介质
CN112034726A (zh) * 2020-09-15 2020-12-04 百度在线网络技术（北京）有限公司 基于场景的控制方法、装置、设备以及存储介质
CN112925219A (zh) * 2021-02-03 2021-06-08 青岛海尔科技有限公司 用于智能家居场景执行的方法及装置
CN113485129A (zh) * 2021-06-11 2021-10-08 杭州控客信息技术有限公司 全屋智能系统的情景模式下设备控制及上报方法
CN114280949A (zh) * 2021-12-10 2022-04-05 深圳市欧瑞博科技股份有限公司 设备智能控制方法、智能控制装置、智能设备及存储介质
CN115016302A (zh) * 2022-05-23 2022-09-06 深圳绿米联创科技有限公司 设备控制方法、装置、设备及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109634251A (zh) * 2019-01-31 2019-04-16 广东美的制冷设备有限公司 智能家居设备联动控制方法、装置及智能家居设备
CN110347054A (zh) * 2019-08-12 2019-10-18 珠海格力电器股份有限公司 控制方法、控制设备及控制系统
CN110716438B (zh) * 2019-10-11 2022-06-07 青岛海信智慧生活科技股份有限公司 一种联动场景执行的方法及装置
CN112114527B (zh) * 2020-09-22 2024-03-01 深圳绿米联创科技有限公司 设备控制装置、方法和计算机可读存储介质
CN114326420A (zh) * 2021-12-10 2022-04-12 深圳市欧瑞博科技股份有限公司 设备智能分组方法、智能分组装置、智能设备及存储介质

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170357425A1 (en) * 2016-06-12 2017-12-14 Apple Inc. Generating Scenes Based On Accessory State
CN108037675A (zh) * 2018-02-01 2018-05-15 苏州创爵智能科技有限公司 一种基于ZigBee Group的智能家居场景控制方法
CN111650845A (zh) * 2020-06-05 2020-09-11 杭州鸿雁电器有限公司 家居组播控制方法、系统和计算机可读存储介质
CN112034726A (zh) * 2020-09-15 2020-12-04 百度在线网络技术（北京）有限公司 基于场景的控制方法、装置、设备以及存储介质
CN112925219A (zh) * 2021-02-03 2021-06-08 青岛海尔科技有限公司 用于智能家居场景执行的方法及装置
CN113485129A (zh) * 2021-06-11 2021-10-08 杭州控客信息技术有限公司 全屋智能系统的情景模式下设备控制及上报方法
CN114280949A (zh) * 2021-12-10 2022-04-05 深圳市欧瑞博科技股份有限公司 设备智能控制方法、智能控制装置、智能设备及存储介质
CN115016302A (zh) * 2022-05-23 2022-09-06 深圳绿米联创科技有限公司 设备控制方法、装置、设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4530761A4 *

Also Published As

Publication number Publication date
EP4530761A4 (en) 2025-09-03
CN115016302B (zh) 2025-07-11
CN115016302A (zh) 2022-09-06
EP4530761A1 (en) 2025-04-02

Similar Documents

Publication Publication Date Title
US11782590B2 (en) Scene-operation method, electronic device, and non-transitory computer readable medium
CN108092861A (zh) 实现设备联动的配置方法、设备联动控制方法及装置
CN110471845B (zh) 智能设备在线调试方法、装置及系统、电子设备
CN109660387B (zh) 设备配置数据的管理方法、装置、服务器及存储介质
CN114125005B (zh) 一种基于智慧楼宇系统的数据处理方法及装置
WO2023226768A1 (zh) 设备控制方法、装置、设备及存储介质
WO2020228033A1 (zh) Sdk插件的加载方法、装置、移动终端以及存储介质
CN111464402A (zh) 一种智能家居设备的控制方法、终端设备及介质
CN109617963B (zh) 设备控制方法、装置以及物联网系统
WO2022105558A1 (zh) 场景配置方法、存储介质及边缘网关
WO2020168568A1 (zh) 数据处理方法、装置、电子设备及可读存储介质
CN109753034A (zh) 一种控制方法、装置、电子设备及存储介质
CN115793481A (zh) 设备控制方法、装置、电子设备及存储介质
CN111399459A (zh) 智能家居设备控制方法、装置、设备及存储介质
CN108836093A (zh) 智能窗帘控制方法、装置及计算机可读存储介质
CN112751734A (zh) 基于清洁机器人的家电控制方法、清洁机器人及芯片
WO2023202678A1 (zh) 设备控制方法、装置、电子设备及存储介质
WO2023216995A1 (zh) 设备控制方法、装置、电子设备及存储介质
CN115356937A (zh) 设备控制方法、装置和存储介质及电子装置
WO2023024752A1 (zh) 网络优化方法、装置及电子设备
CN108259281A (zh) 基于ZigBee和Raspberry Pi的智能家居系统
CN114326420A (zh) 设备智能分组方法、智能分组装置、智能设备及存储介质
CN109981424A (zh) 联动方案处理的方法、装置、电子设备以及存储介质
US20250060714A1 (en) Device control method
WO2024016539A1 (zh) 设备的控制方法、装置、存储介质及电子装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23810841

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023810841

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023810841

Country of ref document: EP

Effective date: 20241223

WWP Wipo information: published in national office

Ref document number: 2023810841

Country of ref document: EP