CN114125147A - Equipment scene function checking method, scene engine and scene platform - Google Patents
Equipment scene function checking method, scene engine and scene platform Download PDFInfo
- Publication number
- CN114125147A CN114125147A CN202111348522.7A CN202111348522A CN114125147A CN 114125147 A CN114125147 A CN 114125147A CN 202111348522 A CN202111348522 A CN 202111348522A CN 114125147 A CN114125147 A CN 114125147A
- Authority
- CN
- China
- Prior art keywords
- scene
- target
- function
- equipment
- action
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000009471 action Effects 0.000 claims abstract description 128
- 238000012545 processing Methods 0.000 claims description 12
- 238000012795 verification Methods 0.000 claims description 10
- 230000008569 process Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
- H04M1/72454—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to context-related or environment-related conditions
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y10/00—Economic sectors
- G16Y10/75—Information technology; Communication
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y40/00—IoT characterised by the purpose of the information processing
- G16Y40/30—Control
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Environmental & Geological Engineering (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Combined Controls Of Internal Combustion Engines (AREA)
Abstract
The invention provides a method for verifying the scene function of equipment, a scene engine and a scene platform, wherein the method comprises the following steps: when the attribute state of the target equipment meets the execution condition of the target scene, acquiring an equipment scene function of the target equipment for supporting the action of the target scene from an equipment scene management module; judging whether the device scene function is matched with the configuration rule of the target scene action; if not, adding a first failure identifier for the device scene function, and feeding back the first failure identifier to the target device; if so, executing the target scene action, and judging whether the target equipment has the equipment scene function; if not, adding a second failure identifier for the device scene function, and feeding back the second failure identifier to the target device; and if so, issuing a control command corresponding to the target scene action to the target equipment. Before the control instruction corresponding to the scene action is issued to the intelligent equipment, the scene function of the equipment is checked for the second time, so that the normal use of the intelligent equipment is ensured.
Description
Technical Field
The invention relates to the technical field of interconnection and intercommunication, in particular to a method for verifying a scene function of equipment, a scene engine and a scene platform.
Background
Along with the development of the internet of things, the intelligent device can support various device scene functions so as to provide rich and diverse use experiences for users. When the scene function of the device changes, the normal use of the intelligent device is affected, and therefore how to use the intelligent device normally is a problem to be solved urgently today.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method for checking a device scene function, a scene engine, and a scene platform, so as to ensure normal use of an intelligent device.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
the first aspect of the embodiment of the present invention discloses a method for checking a device scene function, which is applied to a scene engine, and the method includes:
when the attribute state uploaded by the target device meets the execution condition of the target scene, acquiring a device scene function used by the target device to support a target scene action from a device scene management module, wherein the target scene action is any scene action contained in the target scene;
judging whether the device scene function is matched with a configuration rule corresponding to the target scene action;
if the configuration rule corresponding to the equipment scene function and the target scene action is not matched, adding a first failure identifier for the equipment scene function, and feeding back the first failure identifier to the target equipment, wherein the first failure identifier indicates that the equipment scene function does not support the target scene action;
if the device scene function is matched with the configuration rule corresponding to the target scene action, executing the target scene action, and judging whether the target device has the device scene function;
if the target device does not have the device scene function, adding a second failure identifier for the device scene function, and feeding back the second failure identifier to the target device, wherein the second failure identifier indicates that the target device does not have the device scene function;
and if the target equipment has the equipment scene function, issuing a control instruction corresponding to the target scene action to the target equipment.
Preferably, the determining whether the target device has the device context function includes:
acquiring a device model corresponding to the target device;
if the device scene function is contained in the device model, determining that the target device has the device scene function;
and if the equipment scene function is not contained in the equipment model, determining that the target equipment does not have the equipment scene function.
Preferably, after the control instruction corresponding to the target scene action is issued to the target device, the method further includes:
if receiving an invalid identifier fed back by the target device, acquiring specific failure description information corresponding to the invalid identifier from the device scene management module, wherein the invalid identifier indicates that the target device fails to execute the control instruction;
and feeding back the specific failure description information to the target equipment.
Preferably, the executing the target scene action includes:
and calling a device management module arranged in the scene engine to execute the target scene action.
A second aspect of the present invention discloses a scene engine, including:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a device scene function used by a target device for supporting a target scene action from a device scene management module when an attribute state uploaded by the target device meets an execution condition of a target scene, and the target scene action is any scene action contained in the target scene;
the judging unit is used for judging whether the equipment scene function is matched with a configuration rule corresponding to the target scene action;
a first adding unit, configured to add a first failure identifier to the device scenario function and feed the first failure identifier back to the target device if the device scenario function does not match the configuration rule corresponding to the target scenario action, where the first failure identifier indicates that the device scenario function does not support the target scenario action;
the processing unit is used for executing the target scene action and judging whether the target equipment has the equipment scene function or not if the equipment scene function is matched with the configuration rule corresponding to the target scene action;
a second adding unit, configured to add a second failure identifier to the device scenario function and feed back the second failure identifier to the target device if the target device does not have the device scenario function, where the second failure identifier indicates that the target device does not have the device scenario function;
and the issuing unit is used for issuing a control instruction corresponding to the target scene action to the target equipment if the target equipment has the equipment scene function.
Preferably, the processing unit configured to determine whether the target device has the device context function is specifically configured to: acquiring a device model corresponding to the target device; if the device scene function is contained in the device model, determining that the target device has the device scene function; and if the equipment scene function is not contained in the equipment model, determining that the target equipment does not have the equipment scene function.
Preferably, the scene engine further includes:
a feedback unit, configured to, if an invalid identifier fed back by the target device is received, obtain, from the device scene management module, specific failure description information corresponding to the invalid identifier, where the invalid identifier indicates that the target device fails to execute the control instruction; and feeding back the specific failure description information to the target equipment.
A third aspect of the embodiments of the present invention discloses a scene platform, where the scene platform at least includes: an equipment scene management module and a scene engine disclosed in the second aspect of the embodiment of the invention.
The fourth aspect of the present invention discloses an electronic device, where the electronic device is configured to run a program, and the program executes the method for checking the device context function disclosed in the first aspect of the present invention when running.
The fifth aspect of the embodiment of the present invention discloses a computer storage medium, where the storage medium includes a storage program, and when the program runs, the device where the storage medium is located is controlled to execute the method for checking the device context function disclosed in the first aspect of the embodiment of the present invention.
Based on the verification method for the device scene function, the scene engine and the scene platform provided by the embodiment of the invention, the method comprises the following steps: when the attribute state uploaded by the target equipment meets the execution condition of the target scene, acquiring an equipment scene function of the target equipment for supporting the action of the target scene from an equipment scene management module; judging whether the device scene function is matched with a configuration rule corresponding to the target scene action; if not, adding a first failure identifier for the device scene function, and feeding back the first failure identifier to the target device; if the device scene function is matched with the configuration rule corresponding to the target scene action, executing the target scene action, and judging whether the target device has the device scene function; if not, adding a second failure identifier for the device scene function, and feeding back the second failure identifier to the target device; and if so, issuing a control command corresponding to the target scene action to the target equipment. Before the control instruction corresponding to the scene action is issued to the intelligent equipment, the scene function of the equipment is checked for the second time, so that the normal use of the intelligent equipment is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for verifying a device scene function according to an embodiment of the present invention;
fig. 2 is another flowchart of a method for checking a device context function according to an embodiment of the present invention;
fig. 3 is a block diagram of a scene engine according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
As can be seen from the background art, smart devices generally support a variety of device scene functions, thereby providing users with a rich variety of user experiences. However, when the scene function of the device changes, the normal use of the smart device is affected, and therefore how to use the smart device normally is a problem to be solved urgently today.
The embodiment of the invention provides a method for verifying a device scene function, a scene engine and a scene platform, wherein before a control instruction corresponding to a scene action is issued to an intelligent device, the device scene function is verified for the second time to ensure the normal use of the intelligent device, and the method for verifying the device scene function is described in detail through various embodiments below.
Referring to fig. 1, a flowchart of a method for checking a device context function according to an embodiment of the present invention is shown, where the method for checking is applied to a context engine, and the method for checking includes:
step S101: and when the attribute state uploaded by the target device meets the execution condition of the target scene, acquiring a device scene function of the target device for supporting the action of the target scene from the device scene management module.
It should be noted that a scene at least includes a corresponding scene action (which may be multiple) and an execution condition, and for a certain scene, the subsequent scene action execution flow can be continued only when the attribute state of the device satisfies the execution condition of the scene. The target scene action is any scene action contained in the target scene.
It can be understood that the device context management module at least includes a device context function for supporting a context of a device, that is, a device context function for supporting a context of a certain device can be obtained from the device context management module.
In the process of implementing step S101 specifically, when receiving the attribute state uploaded by the target device (attribute state of the target device), determining whether the attribute state satisfies the execution condition of the target scene; when the attribute state meets the execution condition of the target scene, acquiring a plurality of device scene functions (the number of the device scene functions to be verified is not limited) of the target device for supporting the target scene action from the device scene management module, that is, acquiring the device scene functions of the target device for supporting the target scene action.
Specifically, the corresponding query instruction may be sent to the device context management module, and the device context function definition returned by the device context management module is received, where the device context function definition includes: the target device is used to support device scene functions of the target scene actions.
Step S102: and judging whether the device scene function is matched with the configuration rule corresponding to the target scene action. If the device scene function does not match the configuration rule corresponding to the target scene action, executing step S103; if the device scene function matches the configuration rule corresponding to the target scene action, step S104 is executed.
It should be noted that, the scene engine has a configuration rule corresponding to the scene action, and it can be determined whether the device scene function supports the scene action according to the configuration rule.
In the process of specifically implementing step S102, for a device scenario function (that is, a device scenario function to be verified) of a target device for supporting a target scenario action, the device scenario function needs to be primarily verified, where a specific verification manner of the primary verification is as follows: judging whether the scene function of the equipment is matched with a configuration rule corresponding to the target scene action; if the device scene function of the target device for supporting the target scene action does not match the configuration rule, it indicates that the device scene function acquired from the device scene management module does not support the target scene action, and step S103 is executed; if the device scene function of the target device for supporting the target scene action matches with the configuration rule, continuing to perform a second verification on the device scene function, where the specific content of the second verification is described in step S104.
It is understood that the above-mentioned determination of whether the device context function matches the configuration rule corresponding to the target context action may be considered as determining whether a device context function definition (including a device context function for supporting the target context action by the target device) still exists in the context engine.
Step S103: and adding a first failure identifier for the device scene function, and feeding back the first failure identifier to the target device.
It should be noted that the first failure flag indicates: the device context function (i.e., the device context function to be verified) acquired from the device context management module does not support the target context action.
In the process of specifically implementing step S103, if the device context function used by the target device to support the target context action does not match the configuration rule, it indicates that the device context function acquired from the device context management module does not support the target context action, that is, the device context function used to support the target context action has changed. At this time, a first failure identifier is added to the device scenario function which does not support the target scenario action, and the first failure identifier may also be used to indicate a failure in executing the target scenario action and a failure reason, where the failure reason is that the device scenario function does not support the target scenario action.
After the first failure identifier is added to the device context function that does not support the target context action, the first failure identifier is fed back to the target device, and specifically, the first failure identifier may be fed back to an APP corresponding to the target device. And the user can be guided to modify or delete the device scene function added with the first failure identifier through the first failure identifier displayed by the target device.
Step S104: and executing the target scene action and judging whether the target equipment has the equipment scene function. If the target device does not have the device scene function, executing step S105; if the target device has the device scene function, step S106 is executed.
In the process of specifically implementing step S104, if the device scene function of the target device for supporting the target scene action matches with the configuration rule of the target scene action, it indicates that the device scene function acquired from the device scene management module supports the target scene action, at this time, the target scene action is executed, and the device scene function acquired from the device scene management module is further subjected to second verification.
In some embodiments, in performing the target scene action, a device management module disposed in the scene engine may be invoked to perform the target scene action.
The above mentioned second verification method is: and judging whether the target equipment has the equipment scene function (namely the equipment scene function to be verified) acquired from the equipment scene management module. Specifically, an equipment model corresponding to the target equipment is obtained, and it should be noted that the equipment model includes an equipment scene function of the target equipment; if the device model includes the device scene function acquired from the device scene management module, determining that the target device has the device scene function acquired from the device scene management module, and executing step S106; if the device model does not include the device context function acquired from the device context management module, it is determined that the target device does not have the device context function acquired from the device context management module, and step S105 is executed.
Step S105: and adding a second failure identifier for the device scene function, and feeding back the second failure identifier to the target device.
It should be noted that the second failure flag indicates: the target device does not have the device scene function obtained from the device scene management module.
In the process of specifically implementing step S105, if it is determined that the target device does not have the device context function acquired from the device context management module, a second failure identifier is added to the device context function that the target device does not have, and the second failure identifier may also be used to indicate a failure in executing the target context action and a failure reason, where the failure reason is that the target device does not have the device context function acquired from the device context management module. At this time, the second failure identifier is fed back to the target device, and the user can learn the related information through the second failure identifier.
Step S106: and issuing the control instruction corresponding to the target scene action to the target equipment.
In the process of implementing step S106 specifically, if it is determined that the target device has the device scene function obtained from the device scene management module, which indicates that the device scene function obtained from the device scene management module passes two checks, a control instruction corresponding to the target scene action may be issued to the target device, so that the target device executes the control instruction (i.e., executes the target scene action).
It should be noted that, when the target device receives a control instruction corresponding to the target scene action, the control instruction is executed; if the target device successfully executes the control command, the target scene action is successfully executed; if the target device fails to execute the control instruction, the target device feeds back the invalid identifier to the scene engine.
In some specific embodiments, if an invalid identifier fed back by a target device is received, specific failure description information corresponding to the invalid identifier is acquired from a device scene management module, and the invalid identifier indicates that the target device fails to execute a control instruction; the specific failure description information is fed back to the target device, and the target device displays (for example, displays through APP) the specific failure description information, so that the user knows the specific reason for the failure in executing the control instruction according to the specific failure description information, that is, the specific failure description information is used as the specific reason for the execution failure, and the specific reason is displayed in the target device.
For each scene action of the target scene (or other scenes), the verification of the device scene function can be performed by using the contents shown in the above steps S101 to S106, so as to ensure the normal use of the intelligent device.
In the embodiment of the invention, when the attribute state of the target device meets the execution condition of the target scene, the device scene function of the target device for supporting the action of the target scene is acquired from the device scene management module. And judging whether the device scene function is matched with the configuration rule of the target scene action. And if not, adding a first failure identifier for the device scene function, and feeding back the first failure identifier to the target device. And if so, executing the target scene action and judging whether the target equipment has the equipment scene function. And if not, adding a second failure identifier for the device scene function, and feeding back the second failure identifier to the target device. And if so, issuing a control command corresponding to the target scene action to the target equipment. Before the control instruction corresponding to the scene action is issued to the intelligent equipment, the scene function of the equipment is checked for the second time, so that the normal use of the intelligent equipment is ensured.
To better explain the content of each step in fig. 1 in the above embodiment of the present invention, an interaction flow between the scenario engine and the device scenario management module is taken as an example for illustration, and referring to fig. 2, another flow chart of a verification method for a device scenario function is shown, which includes the following steps:
step S201: and when the attribute state uploaded by the target device meets the execution condition of the target scene, the scene engine requests to acquire a device scene function used by the target device for supporting the action of the target scene from the device scene management module.
Step S202: the scene engine determines whether the acquired device scene function exists. And if the target scene action does not exist, determining that the target scene action fails to be executed, and adding a first failure identifier for the device scene function. If yes, go to step S203.
It should be noted that the first failure flag indicates that the acquired device context function does not support the target context action.
In the process of implementing step S202 specifically, the scene engine determines whether the acquired device scene function exists, that is, determines whether the device scene function matches the configuration rule corresponding to the target scene action.
Step S203: and the scene engine calls the equipment management module to execute the target scene action.
Step S204: the scene engine judges whether the target device has a device scene function. And if not, determining that the target scene action fails to be executed, and adding a second failure identifier for the device scene function. If yes, go to step S205.
It should be noted that the second failure flag indicates that the target device does not have the device context function.
Step S205: and the scene engine issues the control command corresponding to the target scene action to the target equipment.
Step S206: the scene engine determines whether an invalid identifier fed back by the target device is received. And if not, determining that the target device successfully executes the target scene action. And if the failure information is received, determining that the target device fails to execute the target scene action, and requesting to acquire specific failure description information corresponding to the invalid identifier from the device scene management module.
It should be noted that, the execution principle in step S201 to step S206 can refer to the content in fig. 1 of the above embodiment of the present invention, and is not described herein again.
Corresponding to the method for verifying the device scene function provided in the embodiment of the present invention, referring to fig. 3, an embodiment of the present invention further provides a structural block diagram of a scene engine, where the scene engine includes: an acquisition unit 301, a judgment unit 302, a first adding unit 303, a processing unit 304, a second adding unit 305 and a sending unit 306;
an obtaining unit 301, configured to obtain, from the device scene management module, a device scene function that is used by the target device to support a target scene action when the attribute state uploaded by the target device satisfies an execution condition of the target scene, where the target scene action is any scene action included in the target scene.
A determining unit 302, configured to determine whether the device scene function matches a configuration rule corresponding to the target scene action.
The first adding unit 303 is configured to add a first failure identifier to the device scenario function if the configuration rule corresponding to the device scenario function does not match the configuration rule corresponding to the target scenario action, and feed back the first failure identifier to the target device, where the first failure identifier indicates that the device scenario function does not support the target scenario action.
The processing unit 304 is configured to execute the target scene action and determine whether the target device has the device scene function if the device scene function matches the configuration rule corresponding to the target scene action.
In a specific implementation, the processing unit 304, configured to determine whether the target device has a device context function, is specifically configured to: acquiring a device model corresponding to target devices; if the equipment model comprises the equipment scene function, determining that the target equipment has the equipment scene function; and if the equipment scene function is not contained in the equipment model, determining that the target equipment does not have the equipment scene function.
In a specific implementation, the processing unit 304 for executing the target scene action is specifically configured to: and calling a device management module arranged in the scene engine to execute the target scene action.
A second adding unit 305, configured to add a second failure flag to the device context function if the target device does not have the device context function, and feed back the second failure flag to the target device, where the second failure flag indicates that the target device does not have the device context function.
The issuing unit 306 is configured to issue a control instruction corresponding to the target scene action to the target device if the target device has the device scene function.
Preferably, in conjunction with the content shown in fig. 3, the scene engine further includes:
the feedback unit is used for acquiring specific failure description information corresponding to an invalid identifier from the equipment scene management module if the invalid identifier fed back by the target equipment is received, wherein the invalid identifier indicates that the target equipment fails to execute the control instruction; and feeding back the specific failure description information to the target equipment.
In the embodiment of the invention, when the attribute state of the target device meets the execution condition of the target scene, the device scene function of the target device for supporting the action of the target scene is acquired from the device scene management module. And judging whether the device scene function is matched with the configuration rule of the target scene action. And if not, adding a first failure identifier for the device scene function, and feeding back the first failure identifier to the target device. And if so, executing the target scene action and judging whether the target equipment has the equipment scene function. And if not, adding a second failure identifier for the device scene function, and feeding back the second failure identifier to the target device. And if so, issuing a control command corresponding to the target scene action to the target equipment. Before the control instruction corresponding to the scene action is issued to the intelligent equipment, the scene function of the equipment is checked for the second time, so that the normal use of the intelligent equipment is ensured.
Corresponding to the method for verifying the device scene function provided by the embodiment of the present invention, an embodiment of the present invention further provides a scene platform, where the scene platform at least includes: the device context management module and the context engine, wherein the execution principle of the device context management module and the context engine may refer to the content in the foregoing embodiments, and details are not repeated here.
Preferably, an embodiment of the present invention further provides an electronic device, where the electronic device is configured to run a program, and the program executes the method for verifying the device scene function disclosed in the foregoing embodiment when running.
Preferably, an embodiment of the present invention further provides a computer storage medium, where the storage medium includes a storage program, and when the program runs, the device on which the storage medium is located is controlled to execute the method for verifying the device scene function disclosed in the foregoing embodiment.
In summary, embodiments of the present invention provide a method, a scene engine, and a scene platform for verifying a device scene function, where before a control instruction corresponding to a scene action is issued to an intelligent device, the device scene function is verified for the second time, so as to ensure normal use of the intelligent device.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed 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 modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for checking the scene function of a device is applied to a scene engine, and comprises the following steps:
when the attribute state uploaded by the target device meets the execution condition of the target scene, acquiring a device scene function used by the target device to support a target scene action from a device scene management module, wherein the target scene action is any scene action contained in the target scene;
judging whether the device scene function is matched with a configuration rule corresponding to the target scene action;
if the configuration rule corresponding to the equipment scene function and the target scene action is not matched, adding a first failure identifier for the equipment scene function, and feeding back the first failure identifier to the target equipment, wherein the first failure identifier indicates that the equipment scene function does not support the target scene action;
if the device scene function is matched with the configuration rule corresponding to the target scene action, executing the target scene action, and judging whether the target device has the device scene function;
if the target device does not have the device scene function, adding a second failure identifier for the device scene function, and feeding back the second failure identifier to the target device, wherein the second failure identifier indicates that the target device does not have the device scene function;
and if the target equipment has the equipment scene function, issuing a control instruction corresponding to the target scene action to the target equipment.
2. The method of claim 1, wherein the determining whether the target device is capable of the device context comprises:
acquiring a device model corresponding to the target device;
if the device scene function is contained in the device model, determining that the target device has the device scene function;
and if the equipment scene function is not contained in the equipment model, determining that the target equipment does not have the equipment scene function.
3. The method of claim 1, wherein after issuing the control command corresponding to the target scene action to the target device, further comprising:
if receiving an invalid identifier fed back by the target device, acquiring specific failure description information corresponding to the invalid identifier from the device scene management module, wherein the invalid identifier indicates that the target device fails to execute the control instruction;
and feeding back the specific failure description information to the target equipment.
4. The method of claim 1, wherein the performing the target scene action comprises:
and calling a device management module arranged in the scene engine to execute the target scene action.
5. A scene engine, comprising:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a device scene function used by a target device for supporting a target scene action from a device scene management module when an attribute state uploaded by the target device meets an execution condition of a target scene, and the target scene action is any scene action contained in the target scene;
the judging unit is used for judging whether the equipment scene function is matched with a configuration rule corresponding to the target scene action;
a first adding unit, configured to add a first failure identifier to the device scenario function and feed the first failure identifier back to the target device if the device scenario function does not match the configuration rule corresponding to the target scenario action, where the first failure identifier indicates that the device scenario function does not support the target scenario action;
the processing unit is used for executing the target scene action and judging whether the target equipment has the equipment scene function or not if the equipment scene function is matched with the configuration rule corresponding to the target scene action;
a second adding unit, configured to add a second failure identifier to the device scenario function and feed back the second failure identifier to the target device if the target device does not have the device scenario function, where the second failure identifier indicates that the target device does not have the device scenario function;
and the issuing unit is used for issuing a control instruction corresponding to the target scene action to the target equipment if the target equipment has the equipment scene function.
6. The context engine of claim 5, wherein the processing unit configured to determine whether the target device has the device context function is specifically configured to: acquiring a device model corresponding to the target device; if the device scene function is contained in the device model, determining that the target device has the device scene function; and if the equipment scene function is not contained in the equipment model, determining that the target equipment does not have the equipment scene function.
7. The scene engine of claim 5, further comprising:
a feedback unit, configured to, if an invalid identifier fed back by the target device is received, obtain, from the device scene management module, specific failure description information corresponding to the invalid identifier, where the invalid identifier indicates that the target device fails to execute the control instruction; and feeding back the specific failure description information to the target equipment.
8. A scenario platform, characterized in that the scenario platform comprises at least: a device scenario management module and a scenario engine of any of claims 5 to 7.
9. An electronic device, characterized in that the electronic device is configured to run a program, wherein the program is configured to execute the method for verifying the device context function according to any one of claims 1 to 4 when running.
10. A computer storage medium, characterized in that the storage medium comprises a storage program, wherein when the program runs, a device on which the storage medium is located is controlled to execute the verification method of the device scenario function according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111348522.7A CN114125147B (en) | 2021-11-15 | 2021-11-15 | Verification method for equipment scene function, scene engine and scene platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111348522.7A CN114125147B (en) | 2021-11-15 | 2021-11-15 | Verification method for equipment scene function, scene engine and scene platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114125147A true CN114125147A (en) | 2022-03-01 |
| CN114125147B CN114125147B (en) | 2023-05-30 |
Family
ID=80395546
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111348522.7A Active CN114125147B (en) | 2021-11-15 | 2021-11-15 | Verification method for equipment scene function, scene engine and scene platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114125147B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110687812A (en) * | 2019-10-28 | 2020-01-14 | 星络智能科技有限公司 | Household equipment linkage control method, system and storage medium |
| CN110808961A (en) * | 2019-10-16 | 2020-02-18 | 上海易点时空网络有限公司 | Data processing method and device for security verification |
| CN111474860A (en) * | 2020-04-07 | 2020-07-31 | 广东科徕尼智能科技有限公司 | Processing method and device based on failure intelligent scene and storage medium |
| WO2020181599A1 (en) * | 2019-03-08 | 2020-09-17 | 网宿科技股份有限公司 | Model application method and system, and model management method and server |
| WO2020228032A1 (en) * | 2019-05-16 | 2020-11-19 | 深圳市欢太科技有限公司 | Scene pushing method, apparatus and system, and electronic device and storage medium |
| CN112327763A (en) * | 2020-09-08 | 2021-02-05 | 深圳Tcl新技术有限公司 | Intelligent scene control method, device, gateway and storage medium |
| CN112422380A (en) * | 2020-11-18 | 2021-02-26 | 青岛海尔科技有限公司 | Target device control method and device, storage medium and electronic device |
| CN113433869A (en) * | 2021-07-14 | 2021-09-24 | 青岛海尔科技有限公司 | Control method, control device and control system of intelligent equipment |
| WO2021196591A1 (en) * | 2020-04-02 | 2021-10-07 | 深圳创维－Rgb电子有限公司 | Display switching method and device for smart display terminal, equipment, and storage medium |
| WO2021203848A1 (en) * | 2020-04-07 | 2021-10-14 | Oppo广东移动通信有限公司 | Device state identification method and apparatus, and smart terminal |
| WO2021218069A1 (en) * | 2020-04-27 | 2021-11-04 | 平安科技（深圳）有限公司 | Dynamic scenario configuration-based interactive processing method and apparatus, and computer device |
| US20210377355A1 (en) * | 2019-07-02 | 2021-12-02 | Tencent Technology (Shenzhen) Company Limited | Message pushing method, storage medium, and server |
-
2021
- 2021-11-15 CN CN202111348522.7A patent/CN114125147B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020181599A1 (en) * | 2019-03-08 | 2020-09-17 | 网宿科技股份有限公司 | Model application method and system, and model management method and server |
| WO2020228032A1 (en) * | 2019-05-16 | 2020-11-19 | 深圳市欢太科技有限公司 | Scene pushing method, apparatus and system, and electronic device and storage medium |
| US20210377355A1 (en) * | 2019-07-02 | 2021-12-02 | Tencent Technology (Shenzhen) Company Limited | Message pushing method, storage medium, and server |
| CN110808961A (en) * | 2019-10-16 | 2020-02-18 | 上海易点时空网络有限公司 | Data processing method and device for security verification |
| CN110687812A (en) * | 2019-10-28 | 2020-01-14 | 星络智能科技有限公司 | Household equipment linkage control method, system and storage medium |
| WO2021196591A1 (en) * | 2020-04-02 | 2021-10-07 | 深圳创维－Rgb电子有限公司 | Display switching method and device for smart display terminal, equipment, and storage medium |
| CN111474860A (en) * | 2020-04-07 | 2020-07-31 | 广东科徕尼智能科技有限公司 | Processing method and device based on failure intelligent scene and storage medium |
| WO2021203848A1 (en) * | 2020-04-07 | 2021-10-14 | Oppo广东移动通信有限公司 | Device state identification method and apparatus, and smart terminal |
| WO2021218069A1 (en) * | 2020-04-27 | 2021-11-04 | 平安科技（深圳）有限公司 | Dynamic scenario configuration-based interactive processing method and apparatus, and computer device |
| CN112327763A (en) * | 2020-09-08 | 2021-02-05 | 深圳Tcl新技术有限公司 | Intelligent scene control method, device, gateway and storage medium |
| CN112422380A (en) * | 2020-11-18 | 2021-02-26 | 青岛海尔科技有限公司 | Target device control method and device, storage medium and electronic device |
| CN113433869A (en) * | 2021-07-14 | 2021-09-24 | 青岛海尔科技有限公司 | Control method, control device and control system of intelligent equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114125147B (en) | 2023-05-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111988337B (en) | Authority management method and system | |
| CN103841134B (en) | Based on API transmission, the method for receive information, apparatus and system | |
| CN110557284B (en) | Data aggregation method and device based on client gateway | |
| CN108804399B (en) | Form verification method and device | |
| CN111651140B (en) | Service method and device based on workflow | |
| CN111124544A (en) | Interface display method and device, electronic equipment and storage medium | |
| CN107798064A (en) | Page processing method, electronic equipment and computer-readable recording medium | |
| US20240220449A1 (en) | Method and apparatus for managing accounts, and server and storage medium thereof | |
| CN105635124A (en) | Flow control method and device | |
| CN112860398A (en) | Data processing method, device, equipment and medium based on rule engine | |
| CN115599728B (en) | Slot position determining method, device and equipment of FRU equipment and readable storage medium | |
| CN111090442B (en) | Application updating method, device and storage medium | |
| CN114125147A (en) | Equipment scene function checking method, scene engine and scene platform | |
| CN112417402B (en) | Authority control method, authority control device, authority control equipment and storage medium | |
| US20150143333A1 (en) | Native Application Variation | |
| CN113485870A (en) | Method for executing multi-type data sharing service | |
| CN113746918A (en) | Hypertext transfer protocol proxy method and system | |
| CN111506846B (en) | Web page generation method and device, electronic equipment and storage medium | |
| CN109582680B (en) | Business processing method based on new product development, electronic device and readable storage medium | |
| CN111858833A (en) | Asynchronous indexing method and device, computer equipment and storage medium | |
| CN110851287A (en) | Data processing method, device and computer readable storage medium | |
| CN111131205B (en) | Authority management method and device based on Restful interface | |
| CN113890872B (en) | Data set uploading method and device, electronic equipment and storage medium | |
| CN113986279A (en) | Intelligent equipment upgrading method and device, storage medium and electronic equipment | |
| CN115134613A (en) | Method and related device for acquiring information of live broadcast room |
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 | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Tian Yunlong Inventor after: Wang Bo Inventor before: Wang Bo |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |