A device control method and apparatus

Abstract

The application provides a device control method and device, in which a scene rule is defined according to a device type and a device action, the scene rule is not bound to a specific device, and the scene rule is executed when a device control event is received, and associated devices are searched and matched by using the scene rule, so that in a linkage use scene of intelligent devices, a user does not need to manually select and bind in multiple devices, and user operation can be reduced. Furthermore, the scene rule can solve the inconvenience of scene application and device binding, supports reverse rule execution, and can improve user experience.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a device control method and apparatus. Background Technology

[0002] With the development of smart terminals, there are more and more smart devices in homes. The interconnected use of these smart devices has brought many conveniences to people's daily lives. As a result, the interconnected use scenarios of smart devices are becoming more and more widespread, such as performing the closing operation of the window closer when the air conditioner is turned on.

[0003] Currently, the process of associating smart devices with specific scenarios usually involves users manually selecting devices from downloaded scenario templates and then binding them. However, when there are many devices involved in the associated scenario, users need to select multiple devices, which is cumbersome and results in a poor user experience. Summary of the Invention

[0004] This application provides a device control method and apparatus to reduce user operations and improve user experience in smart device-related usage scenarios.

[0005] In a first aspect, this application provides a device control method, the method comprising: receiving a first control instruction from a control device, the control device being a device for executing the first control instruction; then determining a first scenario rule based on the first control instruction, and determining an associated device based on the first scenario rule, the associated device being a device associated with the control device and used to execute a second control instruction; sending the first control instruction to the control device, and sending the second control instruction to the associated device.

[0006] It should be noted that the subject executing this method can be a central device, or it can be the control center in the embodiments described below.

[0007] The above technical solution, upon receiving the first control command, firstly determines the first scene rule based on the first control command, then identifies the associated device based on the first scene rule, and finally sends the first control command to the control device to execute the corresponding operation. Simultaneously, it sends the second control command from the scene rule to the associated device to execute the corresponding operation. Compared to the existing technology that searches for the associated device after the control device executes the operation and then sends the control command, the above solution can find the associated device before the control device executes the operation and can automatically match the corresponding associated device according to the scene rule. This solves the problems of inconvenient binding of scene applications to devices and inflexible execution of scene rules, eliminating the need for users to bind devices multiple times, reducing user operations, and improving the user experience.

[0008] In one possible design, determining the first scene rule based on the first control instruction includes:

[0009] Obtain multiple pre-stored scene rules; determine a first scene rule among the multiple scene rules that uses the first control command as the operating condition.

[0010] The above technical solution allows for the selection of scenario rules with the first control command as the operating condition from a pre-stored set of scenario rules. This facilitates the subsequent identification of associated devices from the selected scenario rules.

[0011] In one possible design, determining the associated device based on the first scenario rule includes:

[0012] A second scenario rule is determined in the first scenario rule, wherein the second scenario rule is a scenario rule in which the associated action related to the first control command is allowed to be executed; the device type of the associated device is determined in the second scenario rule; and the associated devices included under the device type of the associated device are determined according to the rule scope of the second scenario rule.

[0013] For example, the first scenario rule can be rule 1 and rule 3 in the embodiments shown below, and the second scenario rule can be rule 1, that is, when the [air conditioner] is turned on, the [window closer] in the same room will automatically close the window. This scenario rule is a allowed scenario rule.

[0014] Using the above technical solution, after filtering out the allowed scenario rules, the associated devices can be determined according to the effective scope of the rules. The location information of the devices can be obtained using the effective scope of the rules, and then a list of associated devices of the same type can be determined based on the location relationship between the devices.

[0015] In one possible design, the method further includes: acquiring family status information; determining a third scenario rule based on the family status information in the first scenario rule, the third scenario rule including the family status information; and determining a second scenario rule in the third scenario rule.

[0016] It should be understood that family status information may include whether the user is in a home or away scenario, whether anyone is at home, and whether anyone is sleeping. For example, a scenario rule that includes family status information could be Rule 2 in the embodiments described below. It should be understood that Rule 2 is only for illustrative purposes to show that a scenario rule may include family status information.

[0017] The above technical solution can filter out scene rules containing family status information from the first scene rules based on family status information. This makes the filtered scene rules more compatible with the family status information, making the subsequent identification of associated devices more accurate and improving the user experience.

[0018] In one possible design, the method further includes:

[0019] When the first scenario rule includes a fourth scenario rule, the sending of the second control command to the associated device included in the fourth scenario rule is interrupted. The fourth scenario rule is a scenario rule in which the associated action related to the first control command is prohibited from execution.

[0020] For example, the fourth scenario rule can be rule 3 in the embodiments described below, that is, when the [air conditioner] is turned on, the action of prohibiting the [humidifier] in the same room from turning off is automatically executed. The associated action in this scenario rule is a rule that prohibits execution. In this way, the transmission of the associated instruction can be interrupted before the control device performs the operation, realizing the support capability of reverse rules.

[0021] In one possible design, the first control command of the control device is triggered by the user through an application or the device's control panel.

[0022] Using the above technical solution, users can trigger control commands for the device on the application or control panel, so that the central device can then send the control commands to the corresponding control device.

[0023] Secondly, this application provides a device control apparatus, the apparatus comprising a memory, a transceiver, and a processor. The transceiver is used to receive and transmit signals, and the processor is configured to support the apparatus in performing the corresponding functions described in the first aspect or any possible implementation thereof. The memory is coupled to the processor and stores necessary program instructions and data for the apparatus.

[0024] Thirdly, this application also provides a device control apparatus, which includes modules / units for executing the first aspect or any possible design method of the first aspect; these modules / units can be implemented in hardware or by hardware executing corresponding software.

[0025] Fourthly, this application also provides a computer-readable storage medium storing instructions that, when executed on a device control device, cause the device control device to perform the first aspect and any possible design of the first aspect.

[0026] Fifthly, an embodiment of this application provides a computer program product that, when run on a device control device, causes the device control device to execute the first aspect of the present application and any possible design of the first aspect.

[0027] For the various aspects of the second to fifth aspects mentioned above, and the technical effects that each aspect may achieve, please refer to the above description of the technical effects that the various possible solutions for the first aspect may achieve, which will not be repeated here. Attached Figure Description

[0028] Figure 1A This is a schematic diagram of a scene template;

[0029] Figure 1B This is a schematic diagram illustrating the instantiation of a scene template;

[0030] Figure 1C This is a schematic diagram of a user interface for an intelligent linkage scenario;

[0031] Figure 1D This is a flowchart of a device control method;

[0032] Figure 2 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0033] Figure 3 This is a schematic diagram of a device control method provided in an embodiment of this application;

[0034] Figure 4 A flowchart of a device control method provided in an embodiment of this application;

[0035] Figure 5 A flowchart of a rule execution method provided in an embodiment of this application;

[0036] Figure 6 This is a schematic diagram of the structure of a device control apparatus provided in an embodiment of this application;

[0037] Figure 7 This is a schematic diagram of another device control device provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0039] The following embodiments involve at least one, including one or more; wherein, multiple means two or more. Furthermore, it should be understood that in the description of this application, terms such as "first" and "second" are used only for descriptive purposes.

[0040] First, we will introduce the specific implementation process of current intelligent scenarios. Specifically, it may include the following steps:

[0041] Step 1: Define the scene template

[0042] During the template definition phase, Internet of Things (IoT) scenario designers can define the scenario templates. These designers create templates outlining the execution conditions and actions for each scenario, and then upload the designed templates to the IoT scenario application marketplace. For example, such as... Figure 1A As shown, scene designers can define scene templates, such as a scene template for automatically closing windows: when {Air Conditioner 01} is turned on, {Window Closer 001} automatically performs the window-closing action. The {} brackets can be used to fill in relevant smart devices in the home. It should be understood that the air conditioner and window closer brackets used in the {} brackets are merely illustrative examples, and this application is not limited thereto. Then, scene designers can upload multiple designed templates, such as Template 1, Template 2, etc., to the scene application marketplace.

[0043] Step 2: Scene Instantiation

[0044] Currently, the application of interconnected smart devices is becoming increasingly common, and intelligent interconnected scenarios can support the following methods:

[0045] Method 1: Timed linkage, that is, operation 1 is executed at a specified time.

[0046] Method 2: Device status linkage, that is, when a device status event occurs, operation 2 is executed.

[0047] Method 3: External event linkage, that is, to execute operation 3 based on environmental information (such as temperature, humidity, weather, PM2.5, sunrise and sunset, wind speed, etc.).

[0048] It should be understood that the above three methods can be used individually or in combination to achieve intelligent linkage scenarios.

[0049] As an example, users can browse the scene marketplace through a smart living application (App) and then download scenes of interest to their homes. Next, users need to instantiate a template based on the device information managed by their family account, and then associate and bind specific device operations within the scene template. For example, such as... Figure 1BAs shown, users can download the template they need from multiple templates, and then select the device in the device information section of the template. It should be understood that the dotted rectangle in the figure represents the device information; users can select and bind devices within this section. Taking the template "When {} enters 'away mode' from 9:00 AM to 6:00 PM every day, turn on {} to start panoramic cruise" as an example, users can select a device, such as a smart door lock, in the box after "9:00 AM to 6:00 PM every day," and then select a camera device, such as the Haique Smart Camera Pro, in the box after "Turn on." In other words, after instantiating this template, it means: When the smart door lock enters 'away mode' from 9:00 AM to 6:00 PM every day, turn on the Haique Smart Camera Pro to start panoramic cruise.

[0050] Another example, such as Figure 1C As shown, taking a mobile phone as an example, users can... Figure 1C As shown in (a), a smart linkage scenario is created. For example, when a user clicks "weather change", the mobile phone can respond to the user's click operation and display... Figure 1C The diagram shown in (b) allows users to select and set up smart scenes according to their needs on the interface.

[0051] Step 3: Scenario Execution

[0052] like Figure 1D As shown, the process is described using the scenario where the window closer automatically closes when the air conditioner is turned on as an example.

[0053] 1. User triggers device control operation

[0054] Typically, a device control management center is set up in a home for managing home control, multi-device interaction, and capability interoperability. This control management center can be a cloud-based control center (such as an IoT home cloud) or an edge-based control center (such as a home hub or edge cloud). Users can trigger device control operations through control terminals (such as a smart home app or a whole-house control panel), and then the control terminal can send device control commands to the device control management center. For example, a user can trigger a control command to turn on the air conditioner on the smart home app, and the control terminal can send this command to the device control management center.

[0055] 2. The equipment control and management center issues instructions to the controlled equipment.

[0056] The equipment control and management center can send the control command to turn on the air conditioner to the controlled equipment through the control channel, and the controlled equipment can then execute the command to turn on the air conditioner.

[0057] 3. The controlled equipment executes equipment operations according to the control commands.

[0058] In this scenario example, the controlled device is an air conditioner. Therefore, when the air conditioner receives the turn-on command, it can perform the operation of turning on the air conditioner.

[0059] 4. The controlled equipment reports its status to the control center.

[0060] After the controlled device completes its operation, it can report its control status to the device event matching module in the control center. For example, an air conditioner can report its on / off status to the device event matching module.

[0061] 5. The control center matches the scene based on the equipment status and decides which linked devices are triggered by the scene's linkage action.

[0062] Based on the control status of the devices and the association rules defined in the scene, the control center finds the devices that trigger the linkage action and issues the device linkage operation through the control management module. For example, it can find the associated device, the window closer, based on the air conditioner's on / off status.

[0063] 6. The control center issues linkage control commands through the equipment control management module.

[0064] In this scenario example, the associated device is a window closer, meaning the control center can send a command to the window closer to close the window.

[0065] 7. Associated devices perform equipment operations.

[0066] The window closer can execute window closing commands.

[0067] In other words, current scene-based linkage requires users to manually select devices for template instantiation. For complex scenarios, this may require selecting numerous devices, making the process cumbersome. Furthermore, device binding occurs during template instantiation. Changes in device configuration, location information, or even just reconfiguration of devices within the home can invalidate the rules, necessitating re-instantiation and reducing flexibility. Secondly, current device association control rules can only configure which actions a device is allowed to perform, not which actions are prohibited, resulting in a poor user experience. For example, a scenario rule might state that a user turns on the room lights when they return home. However, if someone is resting in the room, the rule cannot be disabled to turn on the lights; doing so could negatively impact the user experience.

[0068] In summary, the current device linkage scenario configuration is relatively complicated, the degree of automation is not high, and the user experience is poor.

[0069] In view of this, embodiments of this application provide a device control method. This method defines scene rules and then changes the rule execution matching process from binding to devices during scene template application to dynamically searching for devices during scene rule execution, thus solving the problem of inflexible scene rule execution. Furthermore, during scene rule execution, device tag information and the scope of linkage are used to match associated devices, addressing the inconvenience of binding scene applications to devices and simplifying the configuration of device linkage scenes. Finally, by changing the scene matching rule process from matching device status events to analyzing device control event triggering processes at the control front end, it provides support for reverse rule adaptation for whole-house device control.

[0070] like Figure 2 The diagram shown is an application scenario illustration provided by an embodiment of this application. (See attached image.) Figure 2 As shown, this scenario may include terminal device 20, central device 21, and smart device 22. Terminal device 20 may be an electronic device such as a mobile phone or tablet; central device 21 may also be called a control device or control center, which may be a central device in a home or a home cloud located on the cloud side; smart device 22 may include control device 221 and associated devices 222.

[0071] In some embodiments, a user can trigger a device control command via a terminal device 20 and send the command to a central device 21. The device control command may include operation instructions to be executed by the control device 221. Upon receiving the device control command, the central device 21 can find a rule based on the device control command as a condition, and then locate the associated device 222 associated with the control device 221. Thus, the corresponding operation instructions can be executed according to the rule.

[0072] In some embodiments, the communication method between the terminal device 20, the smart device 22 and the central device 21 can be a local area network-based wireless communication method, such as Bluetooth communication, wireless-fidelity (Wi-Fi) communication, ZigBee communication and other short-range wireless communication methods; or it can be a wireless communication method based on a cellular network (such as cellular networks established by 2G, 3G, 4G, 5G and subsequent standard protocols).

[0073] The device control method in the embodiments of this application is described in detail below. For example... Figure 3 As shown, this method can specifically include two parts: rule definition and rule execution.

[0074] I. Rule Definition

[0075] In this embodiment, scene designers can first define scene rules, and then upload these rules to an IoT scene application marketplace, allowing users to download the corresponding rules according to their needs. The definition process of scene rules is described in detail below.

[0076] In some embodiments, a scenario rule may include the following five parts of content definition:

[0077] 1. Conditions

[0078] a. Device behavior: Only device type and device behavior are defined in device behavior, without being bound to a specific device.

[0079] b. Room status, the status of the people in the room, such as whether there is anyone in the room (including whether there is someone or not), the number of people (e.g., one or more), and their behavior, such as whether they are sleeping.

[0080] c. Family status: The status of users within a family, such as whether a user is away from home or has returned home.

[0081] d. Time range, i.e. the time range during which the scene rules take effect.

[0082] It should be understood that when defining scenario rules, at least one of the above four conditions can be used.

[0083] 2. Associated Actions: These refer to device behaviors that are automatically executed under certain conditions. When defining associated actions, only the device type and device behavior are defined; they are not bound to specific devices.

[0084] 3. Preventing Action: This refers to equipment behavior that is automatically prohibited under certain conditions. That is, if the equipment behavior occurs under these conditions, the operation of the equipment will be stopped.

[0085] 4. Scope of Application: The scope of application for scene rules is divided into the same household and the same room. This scope of application can affect the range of devices searched by scene rules. By limiting the scope of scene rules, devices associated with scene rules can be matched.

[0086] 5. Activation Method: The notification method for the scenario rule to take effect can include three types: confirmation notification, notification only, and no notification. Confirmation notification means informing the user and requiring their confirmation. For example, a notification message can be displayed on the user's phone, allowing them to confirm whether the rule has taken effect. Notification only means informing the user that the scenario rule has taken effect, without requiring further confirmation. No notification means the scenario rule takes effect automatically, without reminding or requiring user confirmation.

[0087] For example, the above five parts are used to define scene rules, as shown in the following code example:

[0088] define.rule

[0089] rule name: <name>

[0090] conditions:

[0091] device action:{device type,service}

[0092] room status:one / sleeping / no one / multi

[0093] house status:leave home / back home

[0094] time range:{time start:time end}

[0095] auto actions:

[0096] device action:{device type,service}

[0097] prevent actions:

[0098] device action:{device type,service}

[0099] effect range:

[0100] same room / same house

[0101] Effect way:

[0102] notify with confirm / notify without confirm / auto

[0103] It should be understood that the above code is merely illustrative and is not specifically limited in this embodiment. Based on the above definition, scene designers can define different rules, as shown in the following examples:

[0104] In the automatic window closing scenario, rule 1: When the [air conditioner] is turned on, the [window closer] will automatically close the window. This rule applies to the same room / same label.

[0105] Sleep Do Not Disturb scenario, rule 2: When someone is sleeping in the [Bedroom], automatically disable the [Main Light] from being turned on. This rule applies to the same room / same tag.

[0106] In other words, scenario designers can define multiple rules based on different scenarios, and then upload these defined scenario rules, such as Rule 1, Rule 2, ... Rule n, to the scenario marketplace of the Smart Living App. Compared to binding specific devices in templates, defining device types and actions in scenario rules, without binding to specific devices, saves users' steps and improves user experience. Furthermore, if users add, move, or change devices in their homes, the rules automatically adapt and take effect without requiring modification of rule configurations or rebinding of devices, thus increasing flexibility.

[0107] II. Rule Enforcement

[0108] Once the scene rules are defined and uploaded to the app store, users can download them to their home scene for subsequent execution within the corresponding scenario. Execution of scene rules may include the following steps:

[0109] 1. The user triggers a device control command and sends the device control command to the control center.

[0110] 2. Pre-matching management. The control center performs rule filtering and matches scenario rules before issuing device control commands.

[0111] 3. Prevent matching; control commands are aborted.

[0112] 4. Automatic matching, with linkage commands and control commands issued synchronously.

[0113] The steps described above will be explained in detail below. Figure 4 The diagram shown is a flowchart of a device control method provided in an embodiment of this application. (See attached diagram.) Figure 4 As shown, the method may include the following steps:

[0114] For ease of description, the device control command triggered by the user will be referred to as the "first control command," and the device control command executed by the associated device will be referred to as the "second control command." It should be understood that the control center in the following text can be understood as... Figure 2 The central equipment shown.

[0115] S401: The control center receives the first control command from the control equipment.

[0116] As one possible implementation, users can trigger device control commands via an app or control panel, and then send these commands to a control center. For example, a user can trigger a control device, such as a command to turn on the air conditioner, through the air conditioner's control panel. Here, the control device is the device that executes the first control command.

[0117] S402: The control center determines the first scenario rule based on the first control command, with the first control command as a condition.

[0118] In scene rules, the instructions executed by the controlled device can be used as conditions, and the instructions executed by associated devices can be used as associated instructions. For example, the scene rule could be: When the [air conditioner] is turned on, automatically execute the window-closing action of the [window closer] in the same room. In this scene rule, "turn on the air conditioner" can be understood as the condition, and "close the window closer" can be understood as the associated instruction.

[0119] In some embodiments, a user can download multiple scene rules according to their needs. The control center can then filter the downloaded scene rules to select those that use the first device control command as a condition. For example, assuming the first device control command is "turn on the air conditioner," the control center can filter the multiple scene rules to select those that use "turn on the air conditioner" (or "the air conditioner" is turned on) as a condition. Assuming the user downloads three scene rules, an example is shown below:

[0120] Rule 1: When the [air conditioner] is turned on, the [window closer] in the same room will automatically close the window.

[0121] Rule 2: When someone is sleeping in the [bedroom], automatically prevent the [main light] in the same room from being turned on.

[0122] Rule 3: When the [air conditioner] is turned on, the [humidifier] in the same room will be automatically prevented from turning off.

[0123] According to the above rules, the control center can select rule 1 and rule 3 from the above 3 scenario rules as the first scenario rule with "[Air Conditioner] Execute Turn On" as the condition.

[0124] It should be noted that the first scenario rule with the first control instruction as a condition can be one or more, and this application does not limit this.

[0125] S403: The control center determines the associated devices according to the rules of the first scenario.

[0126] Among them, the associated device is the device that is associated with the control device and executes the second control command.

[0127] For scenario rules that are "prohibited" from execution in the first scenario rules, the control center can directly prevent the execution of such scenario rules. Subsequently, the control center does not need to send device execution commands to the associated devices corresponding to the "prohibited" scenario rules. For example, assuming the first scenario rules are rules 1 and 3 above, and rule 3 is a "prohibited" scenario rule, then the control center does not need to send a shutdown command to the humidifier. In other words, this embodiment supports reverse rule control, i.e., it supports automatically preventing devices from doing something they shouldn't. Compared to existing methods that only support forward rule control, this improves the user experience.

[0128] Taking the scenario rule definition code introduced earlier as an example, for a rule whose action is defined as prevent, the prevent execution instruction is executed directly, and the control center interrupts the issuance of the device instruction to the corresponding device.

[0129] For the "automatically" executed scenario rules included in the first scenario rules, the control center can determine the associated devices based on these rules. Taking the scenario rule definition code described above as an example, for rules whose action is defined as automatic (auto), automatic matching of associated devices is required. It should be understood that since the scenario rules defined in this application embodiment are not bound to specific devices, but are defined based on device type and device action, the associated devices corresponding to the "automatically" executed scenario rules may include at least one.

[0130] In some embodiments, the control center can determine associated devices based on the effective scope defined in the scenario rules. Specifically, the control center can query a list of devices that meet the effective scope from the whole-house device relationship database, and then identify the devices that meet the conditions as associated devices. The whole-house device relationship database is a location relationship database of whole-house devices constructed based on room information and label information. The control center can query a list of related devices in the same room and a list of devices under the same label / specified label from this relationship database. For example, the device location relationships are shown in Table 1.

[0131] Table 1

[0132]

[0133] It should be understood that the above table is merely an example, and Table 1 can be understood as a portion of the whole-house equipment relationship database. Furthermore, equipment location relationships can be stored in the whole-house equipment relationship database in tabular form, or in other forms, such as relationship diagrams; this application does not limit this. In the above table, the same equipment type can be understood as the same label. For example, when the label is "window closer," the devices under the same label may include window closer 001 and window closer 002.

[0134] For example, suppose the associated device in the "automatic" execution scenario rule included in the first scenario rule is a window closer. The effective scope defined in this scenario rule is the same room. Therefore, the control center can search for the list of window closers in the same room. For example, the list of window closers in bedroom 1 may include window closer 001 and window closer 002. Then window closer 001 and window closer 002 are associated devices.

[0135] One possible implementation is that the control center can obtain household status information (e.g., whether anyone is home / whether anyone is sleeping), and then further filter the first scenario rules based on this information to select a second scenario rule. For example, assuming rules 1 and 3 in the above rules are the first scenario rules, since neither of these rules defines household status information, the second scenario rule is the same as the first scenario rule. In other words, if household status information is defined in the scenario rules, the second scenario rule corresponding to that household status information can be filtered from the first scenario rules.

[0136] The home status information can be obtained from a home status database, which provides real-time maintenance of home status information, including home status (away, home), room activity status (occupied, empty, asleep), etc. This status information can be acquired through sensors throughout the house, collected and maintained by the home control center, and updated in real time when information changes.

[0137] S404: The control center sends a first control command to the control equipment and a second control command to the associated equipment.

[0138] In some embodiments, after the control center identifies the control device and the associated device, it can send a first control command to the control device and a second control command to the associated device. For example, assuming the associated devices corresponding to the "automatically" executed scenario rules included in the first scenario rule are window closer 001 and window closer 002, and the control device is air conditioner 01, the control center can send an air conditioner-on command to air conditioner 01 and a window-closing command to window closer 001 and window closer 002. Correspondingly, air conditioner 01 can receive the air conditioner-on command, and window closer 001 and window closer 002 can receive the window-closing command sent by the control center.

[0139] S405: The control device and associated device perform corresponding operations according to the first control command and the second control command.

[0140] After the control device and associated device receive the first control command and the second control command, they can perform the corresponding operations according to the first control command and the second control command. For example, if the first control command is an air conditioner turn-on command, then air conditioner 01 can perform the operation of turning on the air conditioner; if the second control command is a window close command, then window closer 001 and window closer 002 can perform the window close action according to the window close command.

[0141] Through the above embodiments, in device linkage scenarios, the solution of automatically matching related home devices by proposing home-wide device tag information and linkage effective range can solve the problem of inconvenient scene application and device binding. This eliminates the need for users to bind devices multiple times to complete scene configuration, making the operation more convenient. Secondly, by changing the rule execution matching from binding to devices during scene template application to dynamically searching for devices during scene execution, the problem of inflexible scene rule execution can be solved. Furthermore, it can prevent devices from performing certain operations, improving the user experience.

[0142] Furthermore, such as Figure 5 The diagram shown is a flowchart of a rule execution method provided in an embodiment of this application. (See attached diagram.) Figure 5 As shown, the method may include the following steps:

[0143] Step 1: The control center receives equipment operation events.

[0144] Step 2: Query family status information.

[0145] In some embodiments, the control center may query household status information from a household status database. It should be understood that this step is optional, and whether it is executed depends on whether household status information is defined in the scenario rules.

[0146] Step 3: Match the prevent operation rules according to the device type.

[0147] Step 4: Match the auto linkage rule according to the device type.

[0148] In some examples, the control center can match operation rules based on a rules database. Specifically, after starting up, the whole-house control center can scan all active control rule files in the home from a specified loading location, then parse the rule information and load it into the rules database. Simultaneously, the control center also supports real-time dynamic updates of whole-house active control rule files. When a user downloads a new active control rule file via the cloud, the whole-house control center will scan the rule file information again, update and load the changed rule files, and synchronize them to the rules database.

[0149] Step 5: Match the associated target devices based on the device location relationship.

[0150] In some examples, the control center can find the associated target device based on the device location relationships in the device relationship database.

[0151] It should be noted that, Figure 5 For details on the implementation of each step in the illustrated embodiment, please refer to [link / reference needed]. Figure 4 The detailed descriptions of S401 to S403 in the embodiments described herein will not be repeated here.

[0152] It should be noted that all or part of the embodiments provided in this application can be freely and arbitrarily combined with each other. The combined technical solutions are also within the protection scope of this application.

[0153] The methods provided in the embodiments of this application above are described from the perspective of an electronic device as the executing entity. To implement the functions of the methods provided in the embodiments of this application above, the electronic device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0154] Based on the above embodiments, this application also provides a device control apparatus 600, which can be the central device or control center in the foregoing embodiments. See also... Figure 6 As shown, the device may include a receiving unit 601, a processing unit 602, and a transmitting unit 603.

[0155] The receiving unit 601 is used to receive a first control instruction from a control device, wherein the control device is a device used to execute the first control instruction; the processing unit 602 is used to determine a first scene rule based on the first control instruction received by the receiving unit 601, and to determine an associated device based on the first scene rule, wherein the associated device is the device associated with the control device and used to execute a second control instruction; the sending unit 603 is used to send the first control instruction to the control device and to send the second control instruction to the associated device.

[0156] In one possible implementation, the processing unit 602 is specifically configured to determine the first scene rule according to the first control instruction in the following manner:

[0157] Obtain multiple pre-stored scene rules; determine a first scene rule among the multiple scene rules that uses the first control command as the operating condition.

[0158] In one possible implementation, the processing unit 602 is specifically configured to determine the associated device according to the first scenario rule in the following manner:

[0159] A second scenario rule is determined in the first scenario rule, wherein the second scenario rule is a scenario rule in which the associated action related to the first control command is allowed to be executed; the device type of the associated device is determined in the second scenario rule; and the associated devices included under the device type of the associated device are determined according to the rule scope of the second scenario rule.

[0160] In one possible implementation, the device further includes an acquisition unit 604 for acquiring household status information.

[0161] The processing unit 602 is further configured to: determine a third scenario rule in the first scenario rule based on the family status information, the third scenario rule including the family status information; and determine the second scenario rule in the third scenario rule.

[0162] In one possible implementation, the processing unit 602 is further configured to: interrupt the sending of the second control command to the associated device included in the fourth scene rule when the first scene rule includes a fourth scene rule, wherein the fourth scene rule is a scene rule in which the associated action related to the first control command is prohibited from execution.

[0163] In one possible implementation, the first control command of the control device is triggered by the user through an application or the device's control panel.

[0164] Based on the above embodiments, this application also provides a device control apparatus, which is used to implement the device control methods shown in the above figures. (See also...) Figure 7 As shown, the device 700 includes a transceiver 701, a processor 702, and a memory 703. The transceiver 701, the processor 702, and the memory 703 are interconnected.

[0165] It should be understood that transceiver 701 is used to perform... Figure 6 The steps performed by the receiving unit 601, sending unit 603, and acquiring unit 604 in the illustrated embodiment. The processor 702 is used to execute... Figure 6 The steps performed by the processing unit 602 in the illustrated embodiment are as follows: For example, the transceiver 701 is used to receive a first control command from the control device; the processor 702 is used to determine a first scene rule based on the first control command, and to determine an associated device based on the first scene rule, wherein the associated device is the device associated with the control device for executing the second control command.

[0166] Optionally, the transceiver 701, the processor 702, and the memory 703 are interconnected via a bus 704. The bus 704 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0167] Memory 703 is used to store program instructions and data. Specifically, program instructions may include program code, which includes computer operation instructions. Memory 703 may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Processor 702 executes the program instructions and data stored in memory 703 to implement the above functions, thereby implementing the device control method provided in the above embodiments.

[0168] In this embodiment, the processor 702 can be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this embodiment. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this embodiment can be directly implemented by the hardware processor, or implemented by a combination of hardware and software modules within the processor. The software modules can be located in the memory 703. The processor 702 reads the program instructions from the memory 703 and, in conjunction with its hardware, completes the steps of the aforementioned methods.

[0169] In this embodiment, the memory 703 can be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as RAM. The memory can also be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in this embodiment can also be a circuit or any other device capable of implementing storage functions, used to store instructions and / or data.

[0170] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described apparatus and unit can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0171] Based on the above embodiments, this application also provides a computer storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the device control method provided in the above embodiments.

[0172] This application also provides a computer program product, including instructions that, when run on a computer, cause the computer to execute the device control method provided in the above embodiments.

[0173] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by instructions. These instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0174] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0175] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.< / name>

Claims

1. A device control method, characterized in that, Applied to central nervous system equipment, including: Receive a first control instruction from a control device, wherein the control device is a device for executing the first control instruction; A first scenario rule is determined based on the first control instruction, and an associated device is determined based on the first scenario rule. The associated device is a device associated with the control device and used to execute the second control instruction. The first scenario rule defines a device type and is a rule decoupled from a specific device identifier. Send the first control command to the control device and send the second control command to the associated device; The step of determining the associated device according to the first scenario rule includes: Based on the first scenario rule, determine the target device type; From a pre-stored device relationship database, devices whose device types match the target device type are identified as the associated devices.

2. The method as described in claim 1, characterized in that, The first scene rules are determined according to the first control command, including: Retrieve multiple pre-stored scene rules; Among the multiple scenario rules, a first scenario rule is determined that uses the first control command as the operating condition.

3. The method as described in claim 1, characterized in that, The associated devices are determined according to the first scenario rules, including: A second scenario rule is determined from the first scenario rule, wherein the second scenario rule is a scenario rule in which the associated action related to the first control command is allowed to be executed; The device type of the associated device is determined in the second scenario rule; The associated devices included under the device type of the associated device are determined according to the scope of the rules in the second scenario rules.

4. The method as described in claim 3, characterized in that, The method further includes: Obtain family status information; A third scenario rule is determined from the first scenario rule based on the family status information, wherein the third scenario rule includes the family status information; The second scenario rule is determined in the third scenario rule.

5. The method as described in claim 3, characterized in that, The method further includes: When the first scenario rule includes a fourth scenario rule, the sending of the second control command to the associated device included in the fourth scenario rule is interrupted. The fourth scenario rule is a scenario rule in which the associated action related to the first control command is prohibited from execution.

6. The method according to any one of claims 1-5, characterized in that, The first control command of the control device is triggered by the user through an application or the device's control panel.

7. A device control apparatus, characterized in that, The device control unit includes one or more processors; one or more memories; and one or more computer programs; The one or more computer programs are stored in the one or more memories, and the one or more computer programs include instructions that, when executed by the one or more processors, cause the device control device to perform the following steps: Receive a first control instruction from a control device, wherein the control device is a device for executing the first control instruction; A first scenario rule is determined based on the first control instruction, and an associated device is determined based on the first scenario rule. The associated device is a device associated with the control device and used to execute the second control instruction. The first scenario rule defines a device type and is a rule decoupled from a specific device identifier. Send the first control command to the control device and send the second control command to the associated device; The step of determining the associated device according to the first scenario rule includes: Based on the first scenario rule, determine the target device type; From a pre-stored device relationship database, devices whose device types match the target device type are identified as the associated devices.

8. The apparatus as claimed in claim 7, characterized in that, When the instruction is invoked and executed by the one or more processors, the device control device performs the following steps: Retrieve multiple pre-stored scene rules; Among the multiple scenario rules, a first scenario rule is determined that uses the first control command as the operating condition.

9. The apparatus as claimed in claim 7, characterized in that, When the instruction is invoked and executed by the one or more processors, the device control device performs the following steps: A second scenario rule is determined from the first scenario rule, wherein the second scenario rule is a scenario rule in which the associated action related to the first control command is allowed to be executed; The device type of the associated device is determined in the second scenario rule; The associated devices included under the device type of the associated device are determined according to the scope of the rules in the second scenario rules.

10. The apparatus as claimed in claim 9, characterized in that, When the instruction is invoked and executed by the one or more processors, the device control device further performs the following steps: Obtain family status information; A third scenario rule is determined from the first scenario rule based on the family status information, wherein the third scenario rule includes the family status information; The second scenario rule is determined in the third scenario rule.

11. The apparatus as claimed in claim 9, characterized in that, When the instruction is invoked and executed by the one or more processors, the device control device further performs the following steps: When the first scenario rule includes a fourth scenario rule, the sending of the second control command to the associated device included in the fourth scenario rule is interrupted. The fourth scenario rule is a scenario rule in which the associated action related to the first control command is prohibited from execution.

12. The apparatus according to any one of claims 7-11, characterized in that, The first control command of the control device is triggered by the user through an application or the device's control panel.

13. A computer-readable storage medium storing instructions, characterized in that, When the instruction is executed on the device control device, it causes the device control device to perform the method as described in any one of claims 1 to 6.

14. A computer program product, characterized in that, When the computer program product is run on the device control device, it causes the device control device to perform the method as described in any one of claims 1 to 6.

Images