[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN111880426B - Method, system, device and equipment for finding scene execution conflict - Google Patents

Method, system, device and equipment for finding scene execution conflict Download PDF

Info

Publication number
CN111880426B
CN111880426B CN202010737989.XA CN202010737989A CN111880426B CN 111880426 B CN111880426 B CN 111880426B CN 202010737989 A CN202010737989 A CN 202010737989A CN 111880426 B CN111880426 B CN 111880426B
Authority
CN
China
Prior art keywords
logic control
scene
control list
attribute
attribute change
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.)
Active
Application number
CN202010737989.XA
Other languages
Chinese (zh)
Other versions
CN111880426A (en
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.)
Qingdao Haier Technology Co Ltd
Original Assignee
Qingdao Haier 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 Qingdao Haier Technology Co Ltd filed Critical Qingdao Haier Technology Co Ltd
Priority to CN202010737989.XA priority Critical patent/CN111880426B/en
Publication of CN111880426A publication Critical patent/CN111880426A/en
Application granted granted Critical
Publication of CN111880426B publication Critical patent/CN111880426B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B15/00Systems controlled by a computer
    • G05B15/02Systems controlled by a computer electric
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/418Total 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]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/26Pc applications
    • G05B2219/2642Domotique, domestic, home control, automation, smart house
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Manufacturing & Machinery (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)
  • Selective Calling Equipment (AREA)

Abstract

The application relates to the technical field of the Internet of things, and discloses a method for finding scene execution conflict. Comprising the following steps: detecting the attribute change condition of the equipment; generating a device attribute change structure when the attribute of the device is changed; triggering a scene execution module of the monitoring equipment to perform scene execution conflict detection, and feeding back a third logic control list under the condition that the detection result is that no scene execution conflict exists; combining the third logic control list with the first logic control list in the corresponding equipment attribute change structure body to obtain a fourth logic control list; determining whether the logic control information in the fourth logic control list has scene execution conflict. The method can enable the scene orchestration module to interact with the plurality of scene execution modules concurrently, and can realize detection of scene execution conflicts among the plurality of scene execution modules. The application also discloses a system, a device and equipment for finding the scene execution conflict.

Description

Method, system, device and equipment for finding scene execution conflict
Technical Field
The application relates to the technical field of the internet of things, for example, to a method, a system, a device and equipment for finding scene execution conflict.
Background
With the vigorous development of the internet of things, more and more intelligent household appliances and household equipment move into thousands of households, unprecedented intelligent living experience is brought to users, the household appliances are not machines for ice, but can actively understand the needs and the favorites of the users, and automatically provide the service agents for the users, so long as the users bring out the experience effect which is expected to be achieved, namely, the use scene, specific control commands are not required to be issued, and all the equipment in the intelligent household network can cooperate to complete the effect expected by the users. However, no matter how intelligent the scene system effect is, the scene system effect needs to be translated into a machine language, namely, according to the scene description, the existing equipment is coordinated, and the target effect of the scene is achieved through a certain control logic.
In the process of implementing the embodiments of the present disclosure, it is found that at least the following problems exist in the related art:
in actual operation, there are often some conflicts in executing scenes, so that the scenes cannot be executed normally.
Disclosure of Invention
The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed embodiments. This summary is not an extensive overview, and is intended to neither identify key/critical elements nor delineate the scope of such embodiments, but is intended as a prelude to the more detailed description that follows.
The embodiment of the disclosure provides a method, a system, a device and equipment for finding scene execution conflict.
In some embodiments, the method for discovering a scenario execution conflict is used for a scenario orchestration module, and includes:
detecting the attribute change condition of the equipment;
Generating a device attribute changing structure body under the condition that the attribute of the device is changed, wherein the device attribute changing structure body comprises a first logic control list stored with logic control information;
triggering a scene execution module for monitoring the equipment to perform scene execution conflict detection, and feeding back a third logic control list stored with logic control information under the condition that the detection result is that no scene execution conflict exists;
Receiving the third logic control list, and merging the third logic control list with the first logic control list in the corresponding equipment attribute change structure body to obtain a fourth logic control list;
Determining whether the logic control information in the fourth logic control list has scene execution conflict.
In some embodiments, the device attribute change structure further includes attribute change information corresponding to the first logical control list; generating a device attribute change structure when the attribute of the device is changed, the device attribute change structure comprising:
Caching attribute change information of the equipment under the condition that the attribute of the equipment is changed;
And establishing an empty first logic control list, and forming the attribute change information and the first logic control list into a device attribute change structure body.
In some embodiments, the device attribute change structure further includes attribute change information and an attribute change number corresponding to the first logical control list; generating a device attribute change structure when the attribute of the device is changed, the device attribute change structure comprising:
Caching attribute change information of the equipment and establishing a unique identifier as an attribute change number of the attribute change information under the condition that the attribute of the equipment is changed;
And establishing an empty first logic control list, and forming the attribute change number, the attribute change information and the first logic control list into an equipment attribute change structure body.
The device attribute change structure is stored in a preset attribute change dictionary,
And determining the attribute change number as a key in the dictionary.
In some embodiments, triggering a scene execution module listening to the device to perform scene execution conflict detection includes:
And sending the attribute change information and the detection instruction to a scene execution module of the monitoring equipment, and triggering the scene execution module to detect whether a scene execution conflict exists in a corresponding second logic control list.
In some embodiments, determining whether the logic control information in the fourth logic control list has a scene execution conflict includes:
And determining whether the logic control information in the fourth logic control list has mutual exclusion conflict.
In some embodiments, the logic control information includes a scene condition and a corresponding operation, and determining whether the logic control information in the fourth logic control list has a mutual exclusion conflict includes:
determining whether a scene condition exists in the fourth logic control list to trigger two or more than three mutually exclusive operations;
In the case that there is one scene condition in the fourth logic control list that triggers two or more mutually exclusive operations, the logic control information in the fourth logic control list has mutually exclusive conflicts.
In some embodiments, the method for discovering a scene execution conflict is used for a scene execution module, and includes:
receiving attribute change information and detection instructions sent by a scene overall module;
Detecting whether scene execution conflict exists in logic control information in a second logic control list according to the attribute change information and the detection instruction;
And under the condition that the logic control information in the second logic control list has scene execution conflict, feeding back a third logic control list to the scene overall module so as to trigger the scene overall module to acquire a fourth logic control list stored with the logic control information and determine whether the logic control information in the fourth logic control list has scene execution conflict.
In some embodiments, detecting whether the scene execution conflict exists in the logic control information in the second logic control list according to the attribute change information and the detection instruction includes:
and under the condition that the detection instruction is received, detecting whether the logic control information in the second logic control list corresponding to the attribute change information has scene execution conflict or not.
In some embodiments, detecting whether the scene execution conflict exists in the logic control information in the second logic control list according to the attribute change information and the detection instruction includes:
And detecting whether the logic control information in the second logic control list has mutual exclusion conflict or not according to the attribute change information and the detection instruction.
In some embodiments, the logic control information includes scene conditions and corresponding operations, and detecting whether the logic control information in the second logic control list has mutual exclusion conflict according to the attribute change information and the detection instruction includes:
Detecting whether a scene condition exists in a second logic control list according to the attribute change information and the detection instruction to trigger two or more than three mutually exclusive operations;
And under the condition that one scene condition triggers two or more mutually exclusive operations in the second logic control list, determining that the logic control information in the second logic control list has mutually exclusive conflict.
In some embodiments, the system for finding scene execution conflicts includes a scene orchestration module and a scene execution module;
The scene overall module is used for detecting the attribute change condition of the equipment; generating a device attribute changing structure body under the condition that the attribute of the device is changed, wherein the device attribute changing structure body comprises a first logic control list stored with logic control information; triggering a scene execution module for monitoring the equipment to perform scene execution conflict detection, and feeding back a third logic control list stored with logic control information under the condition that the detection result is that no scene execution conflict exists; receiving the third logic control list, and merging the third logic control list with the first logic control list in the corresponding equipment attribute change structure body to obtain a fourth logic control list; determining whether scene execution conflict exists in logic control information in the fourth logic control list;
The scene execution module is used for receiving the attribute change information and the detection instruction sent by the scene overall module; detecting whether a scene execution conflict exists in the second logic control list according to the attribute change information and the detection instruction; and under the condition that the second logic control list has scene execution conflict, feeding back a third logic control list to the scene overall module so as to trigger the scene overall module to acquire a fourth logic control list stored with logic control information and determine whether the logic control information in the fourth logic control list has scene execution conflict.
In some embodiments, the apparatus for discovering a scenario execution conflict includes a processor and a memory storing program instructions, the processor configured to perform the method for discovering a scenario execution conflict described above when executing the program instructions.
In some embodiments, the apparatus includes the above-described means for discovering a scene execution conflict.
The method, the device and the equipment for finding the scene execution conflict provided by the embodiment of the disclosure can realize the following technical effects: by generating the equipment attribute changing structure body under the condition that the attribute of the equipment is changed, merging the logic control list with the logic control list in the corresponding equipment attribute changing structure body according to the logic control list obtained by the scene execution module, and determining whether the merged logic control list has scene execution conflict, the scene overall module and the scene execution modules can be interacted concurrently, the detection of the scene execution conflict among the scene execution modules can be realized, and the user can find the scene execution conflict in time conveniently.
The foregoing general description and the following description are exemplary and explanatory only and are not restrictive of the application.
Drawings
One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which like reference numerals refer to similar elements, and in which:
FIG. 1 is a schematic diagram of a method for discovering scene execution conflicts provided by an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of another method for discovering scenario execution conflicts provided by an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of another method for discovering scenario execution conflicts provided by an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a method for a scenario execution module to find a scenario execution conflict provided by an embodiment of the present disclosure;
FIG. 5 is a schematic diagram of a system for scene instantiation provided by an embodiment of the present disclosure;
Fig. 6 is a schematic diagram of an apparatus for discovering a scenario execution conflict provided by an embodiment of the present disclosure.
Detailed Description
So that the manner in which the features and techniques of the disclosed embodiments can be understood in more detail, a more particular description of the embodiments of the disclosure, briefly summarized below, may be had by reference to the appended drawings, which are not intended to be limiting of the embodiments of the disclosure. In the following description of the technology, for purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the disclosed embodiments. However, one or more embodiments may still be practiced without these details. In other instances, well-known structures and devices may be shown simplified in order to simplify the drawing.
The terms first, second and the like in the description and in the claims of the embodiments of the disclosure and in the above-described figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe embodiments of the present disclosure. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion.
The term "plurality" means two or more, unless otherwise indicated.
In the embodiment of the present disclosure, the character "/" indicates that the front and rear objects are an or relationship. For example, A/B represents: a or B.
The term "and/or" is an associative relationship that describes an object, meaning that there may be three relationships. For example, a and/or B, represent: a or B, or, A and B.
As shown in conjunction with fig. 1, an embodiment of the present disclosure provides a method for discovering a scenario execution conflict, for a scenario orchestration module, including:
step S101, detecting the attribute change condition of equipment;
Step S102, generating a device attribute changing structure body when the attribute of the device is changed, wherein the device attribute changing structure body comprises a first logic control list stored with logic control information;
Step S103, triggering a scene execution module of the monitoring equipment to perform scene execution conflict detection, and feeding back a third logic control list stored with logic control information under the condition that the detection result is that no scene execution conflict exists;
step S104, receiving a third logic control list, and combining the third logic control list with the first logic control list in the corresponding equipment attribute change structure body to obtain a fourth logic control list;
Step S105, determining whether there is a scene execution conflict in the logic control information in the fourth logic control list.
By adopting the method for finding the scene execution conflict provided by the embodiment of the disclosure, the device attribute change structure body is generated under the condition that the attribute of the device is changed, the logic control list is combined with the logic control list in the corresponding device attribute change structure body according to the logic control list obtained by the scene execution module, and whether the combined logic control list has the scene execution conflict or not is determined, so that the scene overall module and the scene execution modules can perform concurrent interaction, the detection of the scene execution conflict among the scene execution modules can be realized, and the user can find the scene execution conflict in time.
Optionally, the device attribute changing structure further includes attribute changing information corresponding to the first logical control list; generating a device attribute change structure when a change occurs in an attribute of a device, the device attribute change structure comprising: caching attribute change information of the equipment under the condition that the attribute of the equipment is changed; and establishing an empty first logic control list, and forming the attribute change information and the first logic control list into an equipment attribute change structure body.
Optionally, the device attribute changing structure further includes attribute changing information and an attribute changing number corresponding to the first logical control list; generating a device attribute change structure when a change occurs in an attribute of a device, the device attribute change structure comprising: caching attribute change information of the equipment and establishing a unique identifier as an attribute change number of the attribute change information under the condition that the attribute of the equipment is changed; establishing an empty first logic control list, and forming an equipment attribute change structure body from the attribute change number, the attribute change information and the first logic control list; the equipment attribute changing structure body is stored in a preset attribute changing dictionary; the attribute change number is determined as a key in the attribute change dictionary.
According to the scheme, the device attribute change information and the logic control list are stored through the structure body, and the retrieval can be realized through the dictionary storage form, so that the concurrent interaction of the multi-scene execution modules can be realized.
Optionally, triggering a scene execution module of the monitoring device to perform scene execution conflict detection includes: and sending the attribute change information and the detection instruction to a scene execution module of the monitoring equipment, and triggering the scene execution module to detect whether the logic control information in the corresponding second logic control list has scene execution conflict.
Under the condition that a plurality of scene execution modules exist, the scheme judges whether the corresponding scene execution modules have scene execution conflict or not by triggering the scene execution modules to detect whether the corresponding second logic control list has conflict logic control information, so that the respective scene execution conflict detection of the multiple scene execution modules is realized. Optionally, a scenario execution conflict refers to the existence of some logical conflict within a single scenario, or between scenarios. Optionally, the scene execution conflict is a mutually exclusive conflict.
Optionally, determining whether the logic control information in the fourth logic control list has a scene execution conflict includes: and determining whether the logic control information in the fourth logic control list has mutual exclusion conflict.
Optionally, a mutex conflict triggers multiple mutex operations for one condition.
Optionally, the logic control information includes a scene condition and a corresponding operation, and determining whether the logic control information in the fourth logic control list has a mutual exclusion conflict includes: determining whether a scene condition exists in the fourth logic control list to trigger two or more than three mutually exclusive operations; in the case that there is one scene condition in the fourth logical control list that triggers two or more mutually exclusive operations, the logical control information in the fourth logical control list has mutually exclusive conflicts.
As shown in connection with fig. 2, an embodiment of the present disclosure provides a method for discovering a scenario execution conflict, for a scenario execution module, including:
step S201, receiving attribute change information and a detection instruction sent by a scene orchestration module;
step S202, detecting whether the logic control information in the second logic control list has scene execution conflict according to the attribute change information and the detection instruction;
in step S203, when the logic control information in the second logic control list has a scenario execution conflict, the third logic control list is fed back to the scenario overall module to trigger the scenario overall module to acquire a fourth logic control list storing the logic control information, and determine whether the logic control information in the fourth logic control list has the scenario execution conflict.
By adopting the method for finding the scene execution conflict provided by the embodiment of the disclosure, the device attribute change structure body is generated under the condition that the attribute of the device is changed, the logic control list is combined with the logic control list in the corresponding device attribute change structure body according to the logic control list obtained by the scene execution module, and whether the combined logic control list has the scene execution conflict or not is determined, so that the scene overall module and the scene execution modules can perform concurrent interaction, the detection of the scene execution conflict among the scene execution modules can be realized, and the user can find the scene execution conflict in time.
Optionally, detecting whether the logic control information in the second logic control list has a scene execution conflict according to the attribute change information and the detection instruction includes: and detecting whether the logic control information in the second logic control list corresponding to the attribute change information has scene execution conflict or not under the condition that the detection instruction is received.
Optionally, a scenario execution conflict refers to a logical conflict within a single scenario, or between scenarios. According to the scheme, whether the corresponding scene execution modules have scene execution conflicts or not is judged by detecting whether the corresponding second logic control list has the conflicted logic control information, so that the scene execution conflict detection of each of the multiple scene execution modules can be realized under the condition that the multiple scene execution modules exist.
Optionally, detecting whether the logic control information in the second logic control list has a scene execution conflict according to the attribute change information and the detection instruction includes: and detecting whether the logic control information in the second logic control list has mutual exclusion conflict according to the attribute change information and the detection instruction.
Optionally, the logic control information includes a scene condition and a corresponding operation, and detecting whether the logic control information in the second logic control list has a mutual exclusion conflict according to the attribute change information and the detection instruction includes: detecting whether a scene condition exists in the second logic control list according to the attribute change information and the detection instruction to trigger two or more than three mutually exclusive operations; and under the condition that one scene condition triggers two or more than three mutually exclusive operations in the second logic control list, determining that the logic control information in the second logic control list has mutually exclusive conflict.
Optionally, the first logic control list, the second logic control list, the third logic control list and the fourth logic control list respectively include logic control information corresponding to the respective attribute change information. The logic control information is operation information for the device.
In practical application, for a system of multiple scenario execution modules, a scenario orchestration module is required to monitor the change of equipment attributes, and find out whether execution conflicts exist between different scenario execution modules. When a scene execution module starts a scene task, informing the scene overall module of the equipment attribute to be monitored; meanwhile, the scene orchestration module needs to record which scene execution modules monitor the device attribute. Optionally, the process of finding a scene execution conflict includes:
In the first stage, initiating attribute change detection:
The scene overall module discovers that the monitored equipment attribute changes; caching the attribute change information, and establishing a unique identifier as the serial number of the attribute change; establishing an empty logic control list, namely, what operation is performed on the equipment by logic control; forming a structure body by the attribute change number, the attribute change information and the logic control list; the structure is put into an attribute change dictionary storage which is initialized in advance, and the change number is used as a retrieval key in the dictionary; traversing all scene execution modules monitoring the attribute change of the equipment, concurrently sending attribute change information, informing the scene execution modules of detection purpose, and waiting for feedback of each scene execution module.
In the second stage, the scene execution module performs conflict judgment:
The scene execution module receives the device attribute change and detects according to a scene execution module discovery method; the scene execution module finds no conflict and sends all logic control information to the scene overall module; the scene execution module finds that there is conflict; the scene execution module returns the conflict information to the scene overall module; after the scene overall module receives the scene overall module, the corresponding structure body is taken out from the dictionary; removing the structure from the dictionary if the structure exists, and determining that a conflict exists; if the structure is not present, this property change is indicated as having been previously determined to be conflicting.
In the third stage, the scene orchestration module judges the conflict:
The scene overall module receives a device logic control list fed back by a certain scene execution module; the scene overall module takes out the corresponding structure body from the dictionary; if the structure is not present, indicating that the attribute change has previously been determined to be conflicting; merging the received logical control list into a logical control list of the structure; grouping the logic control according to the controlled equipment; traversing all the groups, and judging whether mutual exclusion operation exists or not; if the mutual exclusion exists, removing the structure from the dictionary and determining that a conflict exists; if the mutual exclusion does not exist, further judging whether all scene execution modules are fed back, and if the mutual exclusion does not exist, determining that the conflict does not exist.
Optionally, because the scene execution module may have a fault, the scene overall module cannot timely feed back data to the scene overall module, and the scene overall module sets a timeout threshold for each device attribute change, and considers that no scene execution conflict exists if no scene execution conflict exists in a specified time.
As shown in connection with fig. 3, the method for finding a scene execution conflict in some embodiments specifically includes the following steps:
step S301, detecting the attribute change condition of the equipment by a scene orchestration module;
step S302, a scene orchestration module establishes a unique identifier as an attribute change number of attribute change information;
step S303, a scene orchestration module establishes an empty first logic control list;
step S304, the scene orchestration module forms an equipment attribute change structure body from the attribute change number, the attribute change information and the first logic control list;
Step S305, the scene orchestration module stores the equipment attribute change structure body in a preset attribute change dictionary; the attribute change number is used as a key in an attribute change dictionary;
Step S306, the scene orchestration module traverses all scene execution modules monitoring the attribute of the equipment and sends attribute change information and detection instructions to the scene execution modules;
step S307, the scene execution module receives the attribute change information and the detection instruction;
Step S308, traversing all scene tasks by the scene execution module and summarizing logic control triggered by all scene tasks;
Step S309, the scene execution module groups the logic control according to the devices;
step S310, the scene execution module traverses all the groups to judge whether a scene execution conflict exists in a second logic control list corresponding to the scene execution module, and the step S311 is executed when the scene execution conflict exists; executing step S321 in the absence of a scene execution conflict;
Step S311, the scene execution module returns a third logic control list to the scene overall module;
step S312, the scene orchestration module takes out the device attribute change structure from the attribute change dictionary;
Step S313, the scenario orchestration module merges the received third logical control list into the extracted first logical control list when a structure corresponding to the third logical control list exists in the extracted device attribute change structure, thereby obtaining a fourth logical control list;
step S314, the scene orchestration module groups the logic controls in the fourth logic control list according to the devices;
Step S315, the scene orchestration module traverses all the groups to judge whether scene execution conflicts exist in the fourth logic control list; step S316 is performed in the case where there is a conflict, and step S318 is performed in the case where there is no conflict;
step S316, the scene orchestration module removes the device attribute change structure body with scene execution conflict from the attribute change dictionary;
Step S317, the scene orchestration module determines that a conflict exists, and executes the scene execution conflict processing flow and then ends;
Step S318, the scene orchestration module judges whether the device attribute changes all relevant scene execution modules to feed back the detection result; determining that no scene execution conflict exists under the condition that all relevant scene execution modules feed back detection results;
Step S319, the scene orchestration module traverses all scene execution modules monitoring the equipment attribute and sends attribute change information and execution instructions to the scene execution modules;
step S320, the scene execution module executes scene task trigger and then ends;
Step S321, the scene execution module feeds back conflict information to the scene orchestration module, namely, the detection result is that scene execution conflicts exist;
in step S322, the scenario orchestration module extracts the device attribute change structure from the attribute change dictionary, and when there is a structure corresponding to the conflict information in the extracted device attribute change structure, the scenario orchestration module executes step S316.
The method can find scene execution conflicts existing between the single scene execution module and the multi-scene execution module, and can find scene execution conflicts of single scene tasks and multi-scene tasks. The scene overall module judges whether scene execution conflict exists according to equipment groups by means of collecting the triggered logic execution information from the multi-scene execution module to the scene overall module. The scene overall module caches the equipment attribute change, and realizes retrieval in a dictionary storage mode, so that concurrent interaction of the multi-scene execution module is realized.
Optionally, in the actual application, the scene execution module finds whether a scene execution conflict exists by finding all triggered device controls, grouping the device control operations according to the controlled devices, then judging whether the control of each group has a conflict, and if so, determining that the scene execution conflict exists. Referring to fig. 4, in some embodiments, the method for the scenario execution module to find a scenario execution conflict specifically includes the following steps:
step S401, monitoring equipment attribute change;
step S402, traversing all tasks to summarize all triggered logic controls;
step S403, grouping logic control according to devices;
step S404, traversing all the groups, judging whether a scene execution conflict exists, if yes, executing step S405, and if not, executing step S406;
step S405, a conflict flow is executed by a processing scene;
Step S406, executing all triggered logic control.
From a colloquial perspective, a scene can be said to be the user's intent, which may be more definite, but more often ambiguous, as illustrated by defining two scene examples:
scene a: if the door is opened from the outside, the corridor wall lamp is lit.
Scene B: if the door is opened from the outside, the corridor is illuminated.
In general, a scene may be understood as "after a certain condition is met" to achieve a certain effect ".
The scene task can be regarded as the actual operation of the scene, and the whole scene system needs to comprehensively integrate the existing equipment ends to meet the scene requirement, taking two scenes as examples:
Scene a task: the intelligent door lock X of the entrance door is monitored, and if the intelligent door lock X is opened from outside, the corridor wall lamp Y is opened.
Scene B task: and monitoring the intelligent door lock X of the entrance door, if the intelligent door lock X is opened from outside, detecting the brightness information of the corridor light sensor Z, and if the brightness is smaller than K, opening the corridor wall lamp Y.
In general, a scene task may be understood as "after a certain device side satisfies a certain condition" performing a certain operation on a certain device side ".
The scene has the descriptions of 'conditions', 'effects', 'logic', for example, the 'door is opened from the open air' in the scene B is a trigger condition, and the subsequent 'illumination corridor' is a trigger effect; the series of "if, then" is logic. For example, "outdoor" is a constraint and "door open" is a trigger condition; "illumination" is a trigger and "corridor" is an effect constraint. The scene task consists of a device end condition, a device end execution condition and a logic condition, and is the scene task B, and the corridor door lock is opened and is the device end condition; the 'turning on corridor wall lamp' is implemented by the equipment end; if, then is logic. For example, "door entry" is a device-side condition constraint, and "door lock open" is a device-side condition; the "corridor" is the constraint of the executing equipment end, and the "turn on wall lamp" is the execution of one equipment end. Thus scene tasks are aligned with scenes.
The equipment side provides all information except logic in the scene task, such as a position attribute of a door lock of an 'entrance door', an operation of a door lock of an 'opening door', a position attribute of a wall lamp of a 'corridor', and an operation of a wall lamp of an 'turning on lamp', and then the equipment model can be regarded as: attribute + operation.
Except logic, the scene model can be regarded as a capability, and when the device model is defined, a mapping relation between the attribute, the operation and the known capability is required to be defined. After the mapping relation is established, the capabilities of one equipment model can be obtained.
The process of converting a scene into a scene task is the instantiation of the scene. According to the above examples of the scene and the scene task, it can be regarded as an instantiation that "what conditions are satisfied" is converted into "what conditions are satisfied by what device side", "what effects are realized" is converted into "what operations are performed on what device side". For example, in the scene B, an intelligent door lock is matched from the outdoor opening door to the corridor, the intelligent door lock has the capability of detecting the opening from the outdoor, the illumination corridor is matched to the corridor, the wall lamp has the illumination capability, the photoreceptor is an optional equipment end, the problem of whether the problem needs to be illuminated is solved, an implicit and optional additional judging condition is that whether the problem of whether the illumination is needed is matched to the corridor, the photoreceptor can detect the brightness of the current corridor, and if the integral scene effect is not affected, the necessary capability in the scene is called as 'necessary capability', and the optional capability is called as 'optional capability'. Optionally, the optional capability is the capability of the sensing device, i.e. the capability of enabling detection of various scenes, such as temperature detection, illumination detection, humidity detection, etc.
Scene task conflicts refer to the existence of some logical conflict within a single scene, or between scenes. Wherein a mutually exclusive conflict triggers multiple mutually exclusive operations for one condition. Such as: the starting and the closing of the air conditioner are mutually exclusive, and the scene task A monitors that the temperature is higher than 25 ℃ and controls the air conditioner to refrigerate; the scene task B monitors that the temperature is lower than 27 ℃, and controls the air conditioner to heat; if the room temperature becomes 26 degrees, the triggering operations of the two scenes are mutually exclusive.
The embodiment of the disclosure provides a system for finding scene execution conflicts, which comprises a scene orchestration module and a scene execution module;
The scene overall module is used for detecting the attribute change condition of the equipment; generating a device attribute changing structure body under the condition that the attribute of the device is changed, wherein the device attribute changing structure body comprises a first logic control list stored with logic control information; triggering a scene execution module of the monitoring equipment to detect scene execution conflict, and feeding back a third logic control list stored with logic control information under the condition that the detection result shows that the scene execution conflict exists; receiving a third logic control list, and combining the third logic control list with the first logic control list in the corresponding equipment attribute change structure body to obtain a fourth logic control list; determining whether scene execution conflict exists in logic control information in a fourth logic control list;
The scene execution module is used for receiving the attribute change information and the detection instruction sent by the scene overall module; detecting whether scene execution conflict exists in the second logic control list according to the attribute change information and the detection instruction; and under the condition that the second logic control list has scene execution conflict, feeding back the third logic control list to the scene overall module so as to trigger the scene overall module to acquire a fourth logic control list stored with logic control information and determine whether the logic control information in the fourth logic control list has scene execution conflict.
By adopting the system for finding the scene execution conflict provided by the embodiment of the disclosure, the scene overall module and the scene execution modules can be interacted concurrently, the detection of the scene execution conflict among the scene execution modules can be realized, and the user can find the scene execution conflict in time.
As shown in fig. 5, in some embodiments, the system for scenario instantiation includes a scenario orchestration module 1, a scenario instantiation module 2, a scenario execution module 3, and a device end 4, where the scenario orchestration module 1 is connected to the scenario instantiation module 2, the scenario execution module 3, and the device end 4, respectively, the scenario orchestration module 1 scans the execution module and issues a scenario task to the scenario execution module 3, the scenario orchestration module 1 scans a device end list, and the scenario orchestration module 1 requests the scenario instantiation module 2 for an instantiated scenario fed back by the scenario Jing Shili instantiation module 2. The scene execution module 3 is connected with the equipment end 4, and the scene execution module 3 performs data interaction with the equipment end 4 so that the equipment end 4 executes scene tasks.
The scene overall module is responsible for overall planning of scene execution, and can be a server deployed on a cloud end or an intelligent gateway deployed on equipment such as a home. In the invention, the method is particularly responsible for maintaining a device end list and a scene execution module list, maintaining a scene model, initiating the instantiation of a scene, pushing the instantiated scene tasks to the scene execution module, initiating the merging of a plurality of selectable scene tasks and the like.
The scenario instantiation module is responsible for instantiating a scenario as a scenario task. Similar to the scenario orchestration module, the instantiation module may be a server deployed at the cloud, or may be an intelligent gateway deployed on a device, such as a home. In some embodiments, the scenario instantiation module is deployed on the same device as the scenario orchestration module.
The scene execution module is responsible for executing scene tasks, and one scene execution module can execute a plurality of scene tasks. The scene execution module can be a server deployed at the cloud end or an intelligent gateway deployed on equipment, such as a home. The system can also be a master control device with certain operation and storage capacity.
As shown in connection with fig. 6, an embodiment of the present disclosure provides an apparatus for discovering a scene execution conflict, including a processor (processor) 100 and a memory (memory) 101 storing program instructions. Optionally, the apparatus may further comprise a communication interface (Communication Interface) 102 and a bus 103. The processor 100, the communication interface 102, and the memory 101 may communicate with each other via the bus 103. The communication interface 102 may be used for information transfer. The processor 100 may call program instructions in the memory 101 to perform the method for finding scene execution conflicts of the above-described embodiments.
Further, the program instructions in the memory 101 described above may be implemented in the form of software functional units and sold or used as a separate product, and may be stored in a computer-readable storage medium.
The memory 101 is a computer readable storage medium that can be used to store a software program, a computer executable program, such as program instructions/modules corresponding to the methods in the embodiments of the present disclosure. The processor 100 executes functional applications and data processing by running program instructions/modules stored in the memory 101, i.e. implements the method for finding scene execution conflicts in the above-described embodiments.
The memory 101 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for a function; the storage data area may store data created according to the use of the terminal device, etc. Further, the memory 101 may include a high-speed random access memory, and may also include a nonvolatile memory.
By adopting the device for finding the scene execution conflict provided by the embodiment of the disclosure, the device attribute change structure body is generated under the condition that the attribute of the device is changed, the logic control list is combined with the logic control list in the corresponding device attribute change structure body according to the logic control list obtained by the scene execution module, and whether the combined logic control list has the scene execution conflict or not is determined, so that the scene overall module and the scene execution modules can perform concurrent interaction, the detection of the scene execution conflict among the scene execution modules can be realized, and the user can find the scene execution conflict in time.
The embodiment of the disclosure provides equipment comprising the device for finding scene execution conflict.
Optionally, the device includes a computer, a server, and intelligent user terminals such as a smart phone, a tablet computer, an intelligent gateway, and an intelligent sound box.
According to the device, the device attribute changing structure body is generated under the condition that the attribute of the device is changed, the logic control list is combined with the logic control list in the corresponding device attribute changing structure body according to the logic control list obtained by the scene execution module, and whether scene execution conflict exists in the combined logic control list or not is determined, so that the scene overall module and the scene execution modules can be interacted concurrently, detection of scene execution conflict among the scene execution modules can be achieved, and a user can find the scene execution conflict in time conveniently.
The disclosed embodiments provide a computer readable storage medium storing computer executable instructions configured to perform the above-described method for discovering a scenario execution conflict.
The disclosed embodiments provide a computer program product comprising a computer program stored on a computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform the above-described method for discovering a scenario execution conflict.
The computer readable storage medium may be a transitory computer readable storage medium or a non-transitory computer readable storage medium.
Embodiments of the present disclosure may be embodied in a software product stored on a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of a method according to embodiments of the present disclosure. And the aforementioned storage medium may be a non-transitory storage medium including: a plurality of media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or a transitory storage medium.
The above description and the drawings illustrate embodiments of the disclosure sufficiently to enable those skilled in the art to practice them. Other embodiments may involve structural, logical, electrical, process, and other changes. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some embodiments may be included in, or substituted for, those of others. Moreover, the terminology used in the present application is for the purpose of describing embodiments only and is not intended to limit the claims. As used in the description of the embodiments and the claims, the singular forms "a," "an," and "the" (the) are intended to include the plural forms as well, unless the context clearly indicates otherwise. Similarly, the term "and/or" as used in this disclosure is meant to encompass any and all possible combinations of one or more of the associated listed. Furthermore, when used in the present disclosure, the terms "comprises," "comprising," and/or variations thereof, mean that the recited features, integers, steps, operations, elements, and/or components are present, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Without further limitation, an element defined by the phrase "comprising one …" does not exclude the presence of other like elements in a process, method or apparatus that includes the element. In this context, each embodiment may be described with emphasis on the differences from the other embodiments, and the same similar parts between the various embodiments may be referred to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method sections disclosed in the embodiments, the description of the method sections may be referred to for relevance.
Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. The skilled artisan may use different methods for each particular application to achieve the described functionality, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the embodiments disclosed herein, the disclosed methods, articles of manufacture (including but not limited to devices, apparatuses, etc.) may be practiced in other ways. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the units may be merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form. The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to implement the present embodiment. In addition, each functional unit in the embodiments of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. In the description corresponding to the flowcharts and block diagrams in the figures, operations or steps corresponding to different blocks may also occur in different orders than that disclosed in the description, and sometimes no specific order exists between different operations or steps. For example, two consecutive operations or steps may actually be performed substantially in parallel, they may sometimes be performed in reverse order, which may be dependent on the functions involved. Each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Claims (12)

1. A method for discovering a scenario execution conflict for a scenario orchestration module, comprising:
detecting the attribute change condition of the equipment;
Generating a device attribute changing structure body under the condition that the attribute of the device is changed, wherein the device attribute changing structure body comprises a first logic control list stored with logic control information;
triggering a scene execution module for monitoring the equipment to perform scene execution conflict detection, and feeding back a third logic control list stored with logic control information under the condition that the detection result is that no scene execution conflict exists;
Receiving the third logic control list, and merging the third logic control list with the first logic control list in the corresponding equipment attribute change structure body to obtain a fourth logic control list;
determining whether scene execution conflict exists in logic control information in the fourth logic control list;
the device attribute changing structure further comprises attribute changing information and an attribute changing number corresponding to the first logic control list; generating a device attribute change structure when the attribute of the device is changed, the device attribute change structure comprising: caching attribute change information of the equipment and establishing a unique identifier as an attribute change number of the attribute change information under the condition that the attribute of the equipment is changed; establishing an empty first logic control list, and forming an equipment attribute change structure body from the attribute change number, the attribute change information and the first logic control list; the equipment attribute changing structure body is stored in a preset attribute changing dictionary; and determining the attribute change number as a key in the attribute change dictionary.
2. The method of claim 1, wherein the device attribute change structure further comprises attribute change information corresponding to the first logical control list; generating a device attribute change structure when the attribute of the device is changed, the device attribute change structure comprising:
Caching attribute change information of the equipment under the condition that the attribute of the equipment is changed;
And establishing an empty first logic control list, and forming the attribute change information and the first logic control list into a device attribute change structure body.
3. The method according to claim 1 or 2, wherein triggering a scenario execution module listening to the device for scenario execution conflict detection comprises:
And sending the attribute change information and the detection instruction to a scene execution module of the monitoring equipment, and triggering the scene execution module to detect whether a scene execution conflict exists in a corresponding second logic control list.
4. The method according to any one of claims 1 to 2, wherein determining whether there is a scenario execution conflict with the logical control information in the fourth logical control list comprises:
And determining whether the logic control information in the fourth logic control list has mutual exclusion conflict.
5. The method of claim 4, wherein the logical control information includes a scene condition and a corresponding operation, and determining whether the logical control information in the fourth logical control list has a mutual exclusion conflict comprises:
determining whether a scene condition exists in the fourth logic control list to trigger two or more than three mutually exclusive operations;
In the case that there is one scene condition in the fourth logic control list that triggers two or more mutually exclusive operations, the logic control information in the fourth logic control list has mutually exclusive conflicts.
6. A method for discovering a scene execution conflict for a scene execution module, comprising:
receiving attribute change information and detection instructions sent by a scene overall module;
Detecting whether scene execution conflict exists in logic control information in a second logic control list according to the attribute change information and the detection instruction;
Under the condition that the logic control information in the second logic control list has no scene execution conflict, feeding back a third logic control list to the scene overall module so as to trigger the scene overall module to acquire a fourth logic control list stored with the logic control information and determine whether the logic control information in the fourth logic control list has scene execution conflict;
The fourth logic control list is obtained by combining the third logic control list with the first logic control list in the equipment attribute change structure body; the device attribute change structure is generated by a scene orchestration module under the condition that the attribute of the device is changed;
the device attribute changing structure further comprises attribute changing information and an attribute changing number corresponding to the first logic control list; generating a device attribute change structure when the attribute of the device is changed, the device attribute change structure comprising: caching attribute change information of the equipment and establishing a unique identifier as an attribute change number of the attribute change information under the condition that the attribute of the equipment is changed; establishing an empty first logic control list, and forming an equipment attribute change structure body from the attribute change number, the attribute change information and the first logic control list; the equipment attribute changing structure body is stored in a preset attribute changing dictionary; and determining the attribute change number as a key in the attribute change dictionary.
7. The method of claim 6, wherein detecting whether a scene execution conflict exists in the logic control information in the second logic control list according to the attribute change information and the detection instruction, comprising:
and under the condition that the detection instruction is received, detecting whether the logic control information in the second logic control list corresponding to the attribute change information has scene execution conflict or not.
8. The method of claim 6, wherein detecting whether a scene execution conflict exists in the logic control information in the second logic control list according to the attribute change information and the detection instruction, comprising:
And detecting whether the logic control information in the second logic control list has mutual exclusion conflict or not according to the attribute change information and the detection instruction.
9. The method of claim 8, wherein the logic control information includes a scene condition and a corresponding operation, and detecting whether the logic control information in the second logic control list has a mutual exclusion conflict according to the attribute change information and the detection instruction includes:
Detecting whether a scene condition exists in a second logic control list according to the attribute change information and the detection instruction to trigger two or more than three mutually exclusive operations;
And under the condition that one scene condition triggers two or more mutually exclusive operations in the second logic control list, determining that the logic control information in the second logic control list has mutually exclusive conflict.
10. A system for finding scene execution conflicts, which is characterized by comprising a scene orchestration module and a scene execution module;
The scene overall module is used for detecting the attribute change condition of the equipment; generating a device attribute changing structure body under the condition that the attribute of the device is changed, wherein the device attribute changing structure body comprises a first logic control list stored with logic control information; triggering a scene execution module for monitoring the equipment to perform scene execution conflict detection, and feeding back a third logic control list stored with logic control information under the condition that the detection result is that no scene execution conflict exists; receiving the third logic control list, and merging the third logic control list with the first logic control list in the corresponding equipment attribute change structure body to obtain a fourth logic control list; determining whether scene execution conflict exists in logic control information in the fourth logic control list;
the scene execution module is used for receiving the attribute change information and the detection instruction sent by the scene overall module; detecting whether a scene execution conflict exists in the second logic control list according to the attribute change information and the detection instruction; under the condition that the logic control information in the second logic control list has no scene execution conflict, feeding back a third logic control list to the scene overall module so as to trigger the scene overall module to acquire a fourth logic control list stored with the logic control information and determine whether the logic control information in the fourth logic control list has scene execution conflict;
the device attribute changing structure further comprises attribute changing information and an attribute changing number corresponding to the first logic control list; generating a device attribute change structure when the attribute of the device is changed, the device attribute change structure comprising: caching attribute change information of the equipment and establishing a unique identifier as an attribute change number of the attribute change information under the condition that the attribute of the equipment is changed; establishing an empty first logic control list, and forming an equipment attribute change structure body from the attribute change number, the attribute change information and the first logic control list; the equipment attribute changing structure body is stored in a preset attribute changing dictionary; and determining the attribute change number as a key in the attribute change dictionary.
11. An apparatus for discovering a scenario execution conflict, comprising a processor and a memory storing program instructions, wherein the processor is configured to, when executing the program instructions, perform the method for discovering a scenario execution conflict of any one of claims 1 to 9.
12. An electronic device comprising the apparatus for discovering a scene execution conflict as recited in claim 11.
CN202010737989.XA 2020-07-28 2020-07-28 Method, system, device and equipment for finding scene execution conflict Active CN111880426B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010737989.XA CN111880426B (en) 2020-07-28 2020-07-28 Method, system, device and equipment for finding scene execution conflict

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010737989.XA CN111880426B (en) 2020-07-28 2020-07-28 Method, system, device and equipment for finding scene execution conflict

Publications (2)

Publication Number Publication Date
CN111880426A CN111880426A (en) 2020-11-03
CN111880426B true CN111880426B (en) 2024-09-27

Family

ID=73200853

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010737989.XA Active CN111880426B (en) 2020-07-28 2020-07-28 Method, system, device and equipment for finding scene execution conflict

Country Status (1)

Country Link
CN (1) CN111880426B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105159079A (en) * 2015-08-31 2015-12-16 青岛海尔智能家电科技有限公司 Method and apparatus for eliminating concurrency control conflict of household appliances
CN108111378A (en) * 2017-12-22 2018-06-01 南京物联传感技术有限公司 The conflict coordination system and method for work of a kind of scene settings of smart home

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120044816A (en) * 2010-10-28 2012-05-08 중앙대학교 산학협력단 A method and device for preventing home network device confliction
JP2014222868A (en) * 2013-05-14 2014-11-27 富士通株式会社 Device control apparatus, device control method and device control system
CN110839175A (en) * 2018-08-15 2020-02-25 Tcl集团股份有限公司 Interaction method based on smart television, storage medium and smart television
CN110471300B (en) * 2019-08-23 2022-12-06 杭州行至云起科技有限公司 Conflict coordination method and system for multiple intelligent scenes
CN110597075B (en) * 2019-09-09 2020-11-03 珠海格力电器股份有限公司 Method and device for detecting control conflict, electronic equipment and storage medium
CN111427316A (en) * 2020-03-19 2020-07-17 海尔优家智能科技(北京)有限公司 Scene triggering method and device, storage medium and electronic device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105159079A (en) * 2015-08-31 2015-12-16 青岛海尔智能家电科技有限公司 Method and apparatus for eliminating concurrency control conflict of household appliances
CN108111378A (en) * 2017-12-22 2018-06-01 南京物联传感技术有限公司 The conflict coordination system and method for work of a kind of scene settings of smart home

Also Published As

Publication number Publication date
CN111880426A (en) 2020-11-03

Similar Documents

Publication Publication Date Title
CN109587018A (en) Method, apparatus, network system and the mobile terminal of device configuration
CN110383274A (en) Identify method, apparatus, system, storage medium, processor and the terminal of equipment
WO2007052886A1 (en) Sensing information management apparatus and method of sensor based home network system
CN102156707A (en) Video abstract forming and searching method and system
CN109240876A (en) Example monitoring method, computer readable storage medium and terminal device
CN106034112B (en) Access control, strategy acquisition, attribute acquisition methods and relevant apparatus
CN112199249B (en) Method, device, equipment and medium for processing monitoring data
CN102929613A (en) Adjusting and optimizing device and method for operating system
CN103716384A (en) Method and device for realizing cloud storage data synchronization in cross-data-center manner
CN110968553A (en) Method and device for sorting elements in directory tree
US20120095986A1 (en) Runtime optimization of spatiotemporal events processing background
CN112313637A (en) Semantic search method for distributed data system with numerical time series data
CN108156018B (en) Power network device topology identification method, electronic device and computer storage medium
CN111880426B (en) Method, system, device and equipment for finding scene execution conflict
CN111418187A (en) Scalable statistics and analysis mechanism in cloud networks
CN115981804A (en) Industrial big data calculation task scheduling management system
CN110945497A (en) Semantic search and rule method for distributed data system
CN113452763B (en) Smart home business registration method and device and smart home system
CN103530369A (en) De-weight method and system
CN117093465B (en) Server log collection method, device, communication equipment and storage medium
CN104731659A (en) Apparatus and method for mapping position information of virtual resources
CN115756472B (en) Cloud-edge cooperative industrial equipment digital twin operation monitoring method and system
CN111602412B (en) Device selection apparatus, data set selection apparatus, device selection method, and storage medium
CN114564854B (en) Operation method and equipment of data node supporting FMEA bidirectional relationship tree
CN115695073A (en) Communication method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant