WO2021203848A1 - 设备状态标识方法、装置及智能终端 - Google Patents

设备状态标识方法、装置及智能终端 Download PDF

Info

Publication number
WO2021203848A1
WO2021203848A1 PCT/CN2021/077095 CN2021077095W WO2021203848A1 WO 2021203848 A1 WO2021203848 A1 WO 2021203848A1 CN 2021077095 W CN2021077095 W CN 2021077095W WO 2021203848 A1 WO2021203848 A1 WO 2021203848A1
Authority
WO
WIPO (PCT)
Prior art keywords
scene
list page
information
identification
state information
Prior art date
Application number
PCT/CN2021/077095
Other languages
English (en)
French (fr)
Inventor
钟浩华
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP21784253.3A priority Critical patent/EP4130953A4/en
Publication of WO2021203848A1 publication Critical patent/WO2021203848A1/zh
Priority to US17/956,657 priority patent/US20230017725A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2823—Reporting information sensed by appliance or service execution status of appliance services in a home automation network
    • 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/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72415—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories for remote control of appliances

Definitions

  • This application belongs to the field of smart home technology, and in particular relates to a device state identification method, device, smart terminal, and computer-readable storage medium.
  • the device display page is used to display device identifiers of devices that can be connected to the smart home
  • the scene list page is used to display device identifiers of devices in different scenarios.
  • the devices that can be connected to the smart home include air purifiers, light bulbs, and speakers
  • the "away from home” scenario includes air purifiers and light bulbs.
  • the air purifier logo and light bulb will be displayed on the device display page.
  • logo and speaker logo, and the scene "Leaving Home” will be displayed on the scene list page, and this scene includes the air purifier logo and the light bulb logo.
  • the scene list page also displays the scene "Leaving Home”
  • the corresponding execution button is shown in Figure 1. In this way, when the user clicks the "execute” button, each device in the "away from home” scenario will be started according to the preset parameters, and the execution result will be fed back after the execution ends.
  • the embodiment of the present application provides a device status identification method, which can solve the problem in the prior art that it is difficult for users to obtain more effective information according to the feedback execution result.
  • an embodiment of the present application provides a device state identification method, which is applied to a smart terminal, and includes:
  • the device identification corresponding to the device is marked according to the state information of the device.
  • the status information of the device can indicate whether the device is in an abnormal state, such as whether the device has been deleted or whether the device has been offline, the corresponding device identification is marked according to the device status information, so that the user receives the "Partially successful execution" "As a result of this execution, it is also possible to know in time from the scene list page which devices have been deleted by the device display page and which devices are offline, thereby improving the user’s good experience.
  • an embodiment of the present application provides a device status identification device, which is applied to a smart terminal and includes:
  • the status information acquiring unit is configured to acquire the status information of the device corresponding to the device identifier displayed on the scene list page, and the scene list page is used to display the device identifiers contained in different scenes;
  • the marking unit is configured to mark the device identification corresponding to the device according to the state information of the device if the state information of the device indicates that the device is in an abnormal state.
  • an embodiment of the present application provides an intelligent terminal, including a memory, a processor, and a computer program stored in the memory and running on the processor.
  • the processor executes the computer program, Implement the method as described in the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium that stores a computer program that implements the method described in the first aspect when the computer program is executed by a processor.
  • the embodiments of the present application provide a computer program product, which when the computer program product runs on a terminal device, causes the smart terminal to execute the method described in the first aspect.
  • FIG. 1 is a schematic diagram of a scene list page provided by the prior art
  • FIG. 2 is a flowchart of a method for identifying device status according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of identifying a device identifier through an icon provided by an embodiment of the present application
  • FIG. 4 is a schematic diagram of displaying generated prompt information on a scene list page according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of a device status identification device provided by an embodiment of the present application.
  • Fig. 6 is a schematic structural diagram of a smart terminal provided by an embodiment of the present application.
  • the term “if” can be construed as “when” or “once” or “in response to determination” or “in response to detecting “.
  • the phrase “if determined” or “if detected [described condition or event]” can be interpreted as meaning “once determined” or “in response to determination” or “once detected [described condition or event]” depending on the context ]” or “in response to detection of [condition or event described]”.
  • Equipment status identification methods include:
  • S21 Obtain the status information of the device corresponding to the device identifier displayed on the scene list page, and the scene list page is used to display the device identifiers contained in different scenes;
  • step S22 if the state information of the device indicates that the device is in an abnormal state, marking the device identification corresponding to the device according to the state information of the device, including: if the state information of the device indicates that the device is in an abnormal state, then The status information of the device marks the device identification corresponding to the device with an icon, and/or the text mark is applied to the device identification corresponding to the device according to the state information of the device.
  • the device status identification method further includes: if the status information of the device indicates that the device is in an abnormal state, detecting whether other devices in the same scene have a device that is linked with the device in the abnormal state; If the device is linked with the device, the existing device is marked.
  • the device state identification method further includes: if the state information of the device indicates that the device is in an abnormal state, generating prompt information according to the state information of the device, and the prompt information includes an entry for re-editing the scene.
  • acquiring the status information of the device corresponding to the device identification displayed on the scene list page includes: if an access instruction to the scene list page is detected, acquiring the status information of the device corresponding to the device identification displayed on the scene list page status information.
  • obtaining the status information of the device corresponding to the device identifier displayed on the scene list page includes: if it is detected that the location of the smart terminal and/or the current time meets the execution of any scene in the scene list page
  • the trigger condition is to obtain the status information of the device corresponding to the device identifier displayed on the scene list page.
  • the device state identification method further includes: if a manual execution instruction is detected, controlling each device in the corresponding scene according to the manual execution instruction, and The execution result is fed back according to the first feedback method; if the automatic execution instruction issued by the smart terminal is detected, each device in the corresponding scene is controlled according to the automatic execution instruction, and the execution result is fed back according to the second feedback method.
  • the second feedback method is the same as the first feedback method. The feedback method is different.
  • the embodiment of the present application also provides a device status identification device 5 applied to an intelligent terminal 6 (shown in FIG. 6 ), including a status information acquiring unit 51 and a marking unit 52.
  • the obtaining unit 51 is used to obtain the status information of the equipment corresponding to the equipment identification displayed on the scene list page, and the scene list page is used to display the equipment identifications contained in different scenes;
  • the marking unit 52 is used to obtain if the equipment status information indicates that the equipment is abnormal Status, the device identification corresponding to the device is marked according to the status information of the device.
  • the smart terminal 6 includes a memory 61, a processor 60, and a computer program 62 stored in the memory 61 and running on the processor 60.
  • the processor 60 executes the computer program 62, it realizes: obtain the status information of the device corresponding to the device ID displayed on the scene list page, the scene list page is used to display the device ID contained in different scenes; if the status information of the device indicates that the device is abnormal Status, the device identification corresponding to the device is marked according to the status information of the device.
  • the processor 60 when the processor 60 executes the computer program 62, it also implements: if the status information of the device indicates that the device is in an abnormal state, the device identification corresponding to the device is marked according to the status information of the device, and/or, according to the device The status information of the device marks the device identification corresponding to the device.
  • the processor 60 when the processor 60 executes the computer program 62, it also implements: if the state information of the device indicates that the device is in an abnormal state, it detects whether there are other devices in the same scene that are linked with the device in the abnormal state; if there is The equipment linked with the equipment in the abnormal state will mark the existing equipment.
  • the processor 60 executes the computer program 62, it is also realized: if the state information of the device indicates that the device is in an abnormal state, prompt information is generated according to the state information of the device, and the prompt information includes an entry for re-editing the scene.
  • the processor 60 executes the computer program 62, it is also implemented: if an access instruction of the scene list page is detected, the status information of the device corresponding to the device identifier displayed on the scene list page is obtained.
  • the processor 60 executes the computer program 62, it is also implemented: if it is detected that the location and/or current time of the smart terminal meets the scene execution trigger condition of any scene in the scene list page, then the scene list page is acquired. The status information of the device corresponding to the device ID displayed in.
  • the processor 60 when the processor 60 executes the computer program 62, it also implements: if a manual execution instruction is detected, each device in the corresponding scene is controlled according to the manual execution instruction, and the execution result is fed back according to the first feedback mode; The automatic execution instruction issued by the smart terminal controls each device in the corresponding scene according to the automatic execution instruction, and feeds back the execution result according to the second feedback mode, which is different from the first feedback mode.
  • the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the computer program When the computer program is executed by a processor, the computer program realizes: obtaining the status information of the device corresponding to the device identifier displayed on the scene list page, and the scene list The page is used to display the device identification contained in different scenes; if the status information of the device indicates that the device is in an abnormal state, the device identification corresponding to the device is marked according to the status information of the device.
  • the computer program when executed by the processor, it is also realized: if the state information of the device indicates that the device is in an abnormal state, the device identification corresponding to the device is marked with an icon according to the state information of the device, and/or, according to the status information of the device The status information marks the device identification corresponding to the device in text.
  • the computer program when executed by the processor, it is also realized: if the status information of the device indicates that the device is in an abnormal state, it is detected whether other devices in the same scene have a device linked with the device in the abnormal state; The equipment linked with the equipment in the abnormal state will mark the existing equipment.
  • the computer program when executed by the processor, it is also realized: if the state information of the device indicates that the device is in an abnormal state, prompt information is generated according to the state information of the device, and the prompt information includes an entry for re-editing the scene.
  • the computer program when executed by the processor, it is also implemented: if an access instruction of the scene list page is detected, the status information of the device corresponding to the device identifier displayed on the scene list page is obtained.
  • the computer program when executed by the processor, it is also realized: if it is detected that the location and/or current time of the smart terminal meets the scene execution trigger condition of any scene in the scene list page, the scene list page is acquired The status information of the device corresponding to the displayed device ID.
  • the computer program when executed by the processor, it is also realized: if a manual execution instruction is detected, each device in the corresponding scene is controlled according to the manual execution instruction, and the execution result is fed back according to the first feedback mode;
  • each device in the corresponding scene is controlled according to the automatic execution instruction, and the execution result is fed back according to the second feedback mode, which is different from the first feedback mode.
  • “Scene” is a function in smart home applications. In a scene, multiple devices can be combined to control tasks specified by the user to realize the intelligent linkage of the whole house. Among them, the device here refers to a device that can connect to the network through various protocols such as Wi-Fi or Bluetooth, so as to realize its own data and status online in real time.
  • Wi-Fi Wireless Fidelity
  • Bluetooth Wireless Fidelity
  • the applicant knows through analysis that the execution result of "partially successful execution" is that some devices in the executed scenario no longer belong to the devices in the smart home that can be controlled by the smart terminal, that is, the certain devices The device ID corresponding to the device has been deleted on the device display page. Or, because some devices in the executed scenario are disconnected from the network, that is, some devices are offline.
  • the scene that includes the device identification in the scene list page still retains the certain device identification, instead of following the device display page
  • the corresponding device ID in the scene list page will be deleted. This is because if the corresponding device identification in the scene list page is deleted in linkage, it may cause some confusion to the user. For example, suppose that the device A logo in scene 1 has been deleted from the device display page, and the user may remember that he added the device A logo in scene 1. At this time, if the device A logo in scene 1 on the scene list page is deleted by linkage , The user may doubt his own memory, which will cause some trouble to the user.
  • the device identification is already displayed on the device When the page is deleted, or the device is offline, the corresponding device ID is identified on the scene list page. In this way, even if the feedback execution result is "partially successful", the user can learn that the deleted device was unsuccessful in execution, or that the device in an offline state was unsuccessful in execution.
  • FIG. 2 shows a flowchart of a device state identification method provided by an embodiment of the present application.
  • the device state identification method is applied to a smart terminal, and the details are as follows:
  • Step S21 Obtain the status information of the device corresponding to the device identifier displayed on the scene list page, where the scene list page is used to display the device identifiers contained in different scenes;
  • the scene list page displays the different scenes set by the user and the device identifiers contained in the scene, and the device identifiers have a one-to-one correspondence with the devices.
  • a scene can include one device identifier, or two or more device identifiers, which is specifically related to the number of devices actually included in the scene.
  • the scene list page has only one scene "Leaving Home” set by the user, and the "Leaving Home” scene includes the air purifier logo and the light bulb logo.
  • the device identification (such as the air purifier identification) may be represented by text (such as the air purifier) in addition to the icon shown in FIG. 1.
  • the status information of the device includes information about whether the device is abnormal, and the information about whether the device is abnormal includes information about whether the device is deleted and information about whether the device is offline.
  • the device status information is acquired only when the user visits the scene list page.
  • the step S21 includes:
  • the access instruction of the scene list page is detected, the status information of the device corresponding to the device identification displayed on the scene list page is obtained.
  • each device identifier here refers to the device identifier corresponding to each different device, that is, the status information of the device corresponding to each device identifier is acquired only once.
  • scene 1 contains an air purifier identifier
  • scene 2 also contains an air purifier identifier
  • the status information of the air purifier corresponding to the air purifier identifier contained in scene 1 has been obtained, then in scene 2, you can directly use The status information of the air purifier is obtained without obtaining it from other places.
  • the device status information is acquired before the scene is executed.
  • the step S21 includes:
  • the status information of the device corresponding to the device identifier displayed on the scene list page is acquired.
  • the user can set the scene to automatically execute the corresponding scene when the scene execution trigger condition is met.
  • the scene execution trigger condition may be that the location meets the requirement, or the time meets the requirement, or both the location and time meet the requirement, and so on. For example, assuming that scenario 1 is automatically triggered when the location of the smart terminal is B, when it is detected that the location of the smart terminal is B, the status information of the device corresponding to the device identifier displayed on the scenario list page is obtained, Otherwise, the status information of the device will not be obtained even if the device is deleted or offline. Through this setting, the frequency of obtaining the status information of the device is reduced.
  • the execution of the scene can be automatically triggered, and the user does not necessarily need to know the status information of the device when the scene is automatically triggered to execute, therefore, in order to further reduce the frequency of acquiring the status information of the device.
  • the application start instruction issued by the user is detected, then the status information of the device is obtained. If the scene execution trigger condition of any scene in the list page is acquired, the status information of the device corresponding to the device identifier displayed on the scene list page is acquired, including:
  • the corresponding scene is triggered to be automatically executed, and the execution result is obtained;
  • the application start instruction issued by the user is detected within the preset time period for obtaining the execution result, the status information of the device corresponding to the device identification displayed on the scene list page is obtained, wherein the application start instruction is used to start the obtained The smart home application of the execution result.
  • an execution result A is obtained after a certain scene in the scene list page of the smart home application A is automatically executed, and the execution result A is obtained within a preset time (for example, within 5 minutes), if If it is detected that the user starts the smart home application A (for example, double-clicking the smart home application A), the status information of the device corresponding to the device identification displayed on the scene list page is obtained. Since the user does not need to open the scene list page when the scene is automatically executed, that is, it is impossible to know the status of each device identification from the scene list page.
  • the smart terminal obtains the status information of the device, which can ensure the timeliness of subsequent identification of the corresponding device.
  • Step S22 If the state information of the device indicates that the device is in an abnormal state, mark the device identifier corresponding to the device according to the state information of the device.
  • the corresponding device identification is identified by the preset deletion identification ; If the device is offline, the corresponding device identification is identified by the preset offline identification, and the preset deletion identification is different from the preset offline identification.
  • the step S22 includes:
  • the device identification corresponding to the device is marked with an icon according to the state information of the device, and/or the device is marked according to the state information of the device.
  • the corresponding device identification is marked with text.
  • the preset deletion flag is an icon of a "trash can”
  • the preset offline flag is an icon of a "broken chain”.
  • Figure 3 shows a schematic diagram of identifying the equipment identification by icons.
  • the "Leaving Home” scene has a delete icon of "trash can” next to the air purifier icon, indicating that the air purifier has been deleted.
  • Deleted there is a "broken chain” offline icon next to the light bulb logo, indicating that the light bulb is offline.
  • the status information of the device corresponding to the device identifier displayed on the scene list page is obtained, and if the status information of the device indicates that the device is in an abnormal state, the device is checked according to the status information of the device.
  • the corresponding device identification is marked. Since the status information of the device can indicate whether the device is in an abnormal state (such as whether it has been deleted or whether it is offline), the corresponding device identification is marked according to the status information of the device, so that the user gets the "partial execution success" When the result is executed, it can also be timely learned from the scene list page which devices have been deleted by the device display page and which devices are offline, thereby improving the user's good experience.
  • the device status identification method further includes:
  • the status information of the device indicates that the device is in an abnormal state, check whether other devices in the same scene have a device that is linked to the device in the abnormal state; if there is a device that is linked to the device in the abnormal state, it is Equipment for identification.
  • a linkage failure indicator can be preset to mark the corresponding device identity.
  • the “away from home” scenario includes three devices: air purifier, light bulb, and speaker, and there is the following linkage relationship between air purifier and light bulb: turn on the air purifier, and after the PM2.5 value of the air meets the requirements Turn on the light bulb. If the air purifier is deleted, the execution of the "away from home” scenario will cause the air purifier and the light bulb to fail to execute. Therefore, in order to enable the user to determine all unsuccessful devices and unsuccessful executions when they get "partially successful” The reason is that, in the embodiment, a preset deletion flag is used to mark the air purifier identification, and a preset linkage failure flag is used to mark the light bulb identification.
  • the device status identification method when the device is deleted or offline, if the scene in which it is located is executed, the device will execute successfully, and this may cause the function of the executed scene to fail to meet the needs of the user. Therefore, in order to facilitate the user Quickly setting a scene with a new function, and the device status identification method further includes:
  • prompt information is generated according to the state information of the device, and the prompt information includes an entry for re-editing the scene.
  • the display mode of the setting scene editing entry is different from the display mode of other information of the prompt information.
  • the generated prompt message is "The air purifier has been deleted, you can re-edit the scene", where "Edit Scene” is the entrance to the scene to be re-edited.
  • the "Edit Scene” The display mode is different from the display mode of other information of the prompt message.
  • the generated prompt information also includes the device name and the scene name, and the order of the device name is before the scene name. For example, suppose the device "air purifier” is deleted and the scene “away from home” is deleted, the generated prompt message is: the device “air purifier” is deleted, and the scene “away from home” is deleted, you can edit the scene again. After the scene is deleted, the user can no longer see the corresponding scene, and after the device is deleted, the corresponding device identification can be seen in the scene. Therefore, prioritizing the display of the device name will help users get more from the prompt information. The amount of information.
  • the execution result is fed back in a different feedback manner, that is, after the device identifier corresponding to the device is marked according to the state information of the device, the The device status identification method also includes:
  • each device in the corresponding scene is controlled according to the automatic execution instruction, and the execution result is fed back according to the second feedback mode, which is the same as the first feedback The way is different.
  • the execution result is fed back according to the first feedback mode; if the location and/or When the current time meets the scene execution trigger condition of any scene in the scene list page, the scene is automatically executed through the smart terminal, and at this time, the execution result is fed back according to the second feedback mode.
  • the first feedback method may be text feedback, that is, the execution result in text form is displayed on the scene list page.
  • the second feedback method can be voice feedback, that is, the user does not need to open the scene list page of the smart home application, but can also be realized through the voice broadcast by the smart terminal . Since different feedback methods are selected to feed back the execution results in combination with different scene execution methods, the way for users to obtain the execution results is more flexible, and the execution results are guaranteed to be obtained in a more timely manner.
  • FIG. 5 shows a structural block diagram of the device status identification device provided in an embodiment of the present application. For ease of description, only the parts related to the embodiment of the present application are shown.
  • the device status identification device 5 is applied to a smart terminal, and includes:
  • the status information acquiring unit is configured to acquire the status information of the device corresponding to the device identifier displayed on the scene list page, and the scene list page is used to display the device identifiers contained in different scenes;
  • the marking unit is configured to mark the device identification corresponding to the device according to the state information of the device if the state information of the device indicates that the device is in an abnormal state.
  • the status information of the device corresponding to the device identifier displayed on the scene list page is obtained, and if the status information of the device indicates that the device is in an abnormal state, the device is checked according to the status information of the device.
  • the corresponding device identification is marked. Since the status information of the device can indicate whether the device has been deleted or whether the device is offline, the corresponding device identification is marked according to the status information of the device, so that when the user gets the execution result of "partial execution success", It can learn from the scene list page in time which devices have been deleted by the device display page and which devices are offline, thereby improving a good user experience.
  • the marking unit is specifically used for:
  • the device identification corresponding to the device is marked with an icon according to the state information of the device, and/or the device is marked according to the state information of the device.
  • the corresponding device identification is marked with text.
  • the device status identification device 5 further includes:
  • the linkage device detection unit is configured to, if the state information of the device indicates that the device is in an abnormal state, detect whether other devices in the same scene have a device that is linked with the device in the abnormal state;
  • the linked device marking unit is used to mark the existing device if there is a device linked with a device in an abnormal state.
  • the device status identification device further includes:
  • the prompt information generating unit is configured to generate prompt information according to the state information of the device if the state information of the device indicates that the device is in an abnormal state, and the prompt information includes an entry for re-editing the scene.
  • the display mode of the setting scene editing entry is different from the display mode of other information of the prompt information.
  • the generated prompt information also includes the device name and the scene name, and the order of the device name is before the scene name.
  • the device status information in order to ensure that more accurate device status information is acquired, and to reduce the frequency of acquiring device status information, the device status information is only acquired when the user visits the scene list page.
  • the status Information acquisition unit specifically used for:
  • the access instruction of the scene list page is detected, the status information of the device corresponding to the device identification displayed on the scene list page is obtained.
  • each device identifier here refers to the device identifier corresponding to each different device, that is, the status information of the device corresponding to each device identifier is acquired only once.
  • the device state information in order to be able to obtain accurate device state information in time, and to reduce the frequency of obtaining device state information, the device state information is obtained before the scene is executed.
  • the state information obtaining unit Specifically used for:
  • the status information of the device corresponding to the device identifier displayed on the scene list page is acquired.
  • the user can set the scene to automatically execute the corresponding scene when the scene execution trigger condition is met.
  • the scene execution trigger condition may be that the location meets the requirement, or the time meets the requirement, or both the location and time meet the requirement, and so on.
  • the state information acquiring unit is specifically configured to:
  • the corresponding scene is triggered to automatically execute and the execution result is obtained; if the preset duration of the execution result is obtained. If the application start instruction issued by the user is detected in the application, the status information of the device corresponding to the device identification displayed on the scene list page is obtained, wherein the application start instruction is used to start the smart home application that obtains the execution result .
  • the device status identification device 5 further includes:
  • the first execution result feedback unit is configured to, if a manual execution instruction is detected, control each device in the corresponding scene according to the manual execution instruction, and feed back the execution result according to the first feedback mode;
  • the second execution result feedback unit is configured to, if an automatic execution instruction issued by the smart terminal is detected, control each device in the corresponding scene according to the automatic execution instruction, and feed back the execution result according to the second feedback mode.
  • the second feedback mode is different from the first feedback mode.
  • Fig. 6 is a schematic structural diagram of a smart terminal provided by an embodiment of the application.
  • the smart terminal 6 of this embodiment includes: at least one processor 60 (only one processor is shown in FIG. 6), a memory 61, and a memory 61 that is stored in the memory 61 and can be processed in the at least one processor.
  • the computer program 62 running on the processor 60 implements the steps in any of the foregoing method embodiments when the processor 60 executes the computer program 62:
  • the device identification corresponding to the device is marked according to the state information of the device.
  • the smart terminal 6 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the smart terminal may include, but is not limited to, a processor 60 and a memory 61.
  • FIG. 6 is only an example of the smart terminal 6 and does not constitute a limitation on the smart terminal 6. It may include more or less components than those shown in the figure, or a combination of certain components, or different components. , For example, can also include input and output devices, network access devices, and so on.
  • the so-called processor 60 may be a central processing unit (Central Processing Unit, CPU), and the processor 60 may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), and application specific integrated circuits (Application Specific Integrated Circuits). , ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory 61 may be an internal storage unit of the smart terminal 6 in some embodiments, such as a hard disk or a memory of the smart terminal 6. In other embodiments, the memory 61 may also be an external storage device of the smart terminal 6, such as a plug-in hard disk equipped on the smart terminal 6, a smart media card (SMC), a secure digital (Secure Digital, SD) card, Flash Card, etc. Further, the memory 61 may also include both an internal storage unit of the smart terminal 6 and an external storage device.
  • the memory 61 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory 61 can also be used to temporarily store data that has been output or will be output.
  • An embodiment of the present application also provides a network device, which includes: at least one processor, a memory, and a computer program stored in the memory and running on the at least one processor, and the processor executes The computer program implements the steps in any of the foregoing method embodiments.
  • the embodiments of the present application also provide a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in each of the foregoing method embodiments can be realized.
  • the embodiments of the present application provide a computer program product.
  • the steps in the foregoing method embodiments can be realized when the mobile terminal is executed.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the computer program can be stored in a computer-readable storage medium. When executed by the processor, the steps of the foregoing method embodiments can be implemented.
  • the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file, or some intermediate forms.
  • the computer-readable medium may at least include: any entity or device capable of carrying the computer program code to the photographing device/terminal device, recording medium, computer memory, read-only memory (ROM, Read-Only Memory), and random access memory (RAM, Random Access Memory), electric carrier signal, telecommunications signal and software distribution medium.
  • ROM read-only memory
  • RAM random access memory
  • electric carrier signal telecommunications signal and software distribution medium.
  • U disk mobile hard disk, floppy disk or CD-ROM, etc.
  • computer-readable media cannot be electrical carrier signals and telecommunication signals.
  • the disclosed apparatus/network equipment and method may be implemented in other ways.
  • the device/network device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units.
  • components can be combined or integrated into another system, or some features can be omitted or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

一种设备状态标识方法、装置(5)及智能终端(6)，方法包括：(S21)获取场景列表页中显示的设备标识所对应的设备的状态信息，场景列表页用于显示不同场景中包含的设备标识；(S22)若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行标记。

Description

设备状态标识方法、装置及智能终端
优先权信息
本申请请求2020年4月7日向中国国家知识产权局提交的、专利申请号为202010263868.6的专利申请的优先权和权益，并且通过参照将其全文并入此处。
技术领域
本申请属于智能家居技术领域，尤其涉及设备状态标识方法、装置、智能终端及计算机可读存储介质。
背景技术
目前，用户可以使用智能终端上安装的智能家居类应用来控制对应的设备。
在智能家居类应用中，包括设备显示页和场景列表页。其中，设备显示页用于显示能够接入智能家居的设备的设备标识，而场景列表页用于显示不同场景下的设备的设备标识。比如，假设能够接入智能家居的设备包括空气净化器、灯泡和音箱，“离家”这一场景包括的设备是空气净化器和灯泡，那么，在设备显示页将显示空气净化器标识、灯泡标识和音箱标识，而在场景列表页将显示“离家”这一场景，且显示这一场景下包括空气净化器标识和灯泡标识，此外，场景列表页还显示与“离家”这一场景对应的执行按钮，如图1所示。这样，当用户点击“执行”按钮时，将根据预设的参数启动该“离家”场景下各个设备，并在执行结束后，反馈执行结果。
发明内容
本申请实施例提供了设备状态标识方法，可以解决现有技术中用户根据反馈的执行结果难以获取更有效的信息的问题。
第一方面，本申请实施例提供了一种设备状态标识方法，所述设备状态标识方法应用于智能终端，包括：
获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
本申请实施例与现有技术相比存在的有益效果是：
由于设备的状态信息能够指示设备是否处于异常状态，如指示设备是否被删除或指示设备是否已离线，因此，根据该设备的状态信息对对应的设备标识进行标记，使得用户在得到“部分执行成功”这一执行结果时，也能够从场景列表页中及时获知哪些设备是已被设备显示页删除的，哪些设备是处于离线状态的，从而提高用户的良好体验。
第二方面，本申请实施例提供了一种设备状态标识装置，所述设备状态标识装置应用于智能终端，包括：
状态信息获取单元，用于获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
标记单元，用于若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
第三方面，本申请实施例提供了一种智能终端，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如第一方面所述的方法。
第四方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如第一方面所述的方法。
第五方面，本申请实施例提供了一种计算机程序产品，当计算机程序产品在终端设备上运行时，使得智能终端执行上述第一方面所述的方法。
可以理解的是，上述第二方面至第五方面的有益效果可以参见上述第一方面中的相关描述，在此不再赘述。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1是现有技术提供的一种场景列表页的示意图；
图2是本申请实施例提供的一种设备状态标识方法的流程图；
图3是本申请实施例提供的一种通过图标对设备标识进行标识的示意图；
图4是本申请实施例提供的一种在场景列表页显示生成的提示信息的示意图；
图5是本申请实施例提供的一种设备状态标识装置的结构示意图；
图6是本申请实施例提供的一种智能终端的结构示意图。
具体实施方式
以下描述中，为了说明而不是为了限定，提出了诸如特定系统结构、技术之类的具体细节，以便透彻理解本申请实施例。然而，本领域的技术人员应当清楚，在没有这些具体细节的其它实施例中也可以实现本申请。在其它情况中，省略对众所周知的系统、装置、电路以及方法的详细说明，以免不必要的细节妨碍本申请的描述。
应当理解，当在本申请说明书和所附权利要求书中使用时，术语“包括”指示所描述特征、整体、步骤、操作、元素和/或组件的存在，但并不排除一个或多个其它特征、整体、步骤、操作、元素、组件和/或其集合的存在或添加。
还应当理解，在本申请说明书和所附权利要求书中使用的术语“和/或”是指相关联列出的项中的一个或多个的任何组合以及所有可能组合，并且包括这些组合。
如在本申请说明书和所附权利要求书中所使用的那样，术语“如果”可以依据上下文被解释为“当...时”或“一旦”或“响应于确定”或“响应于检测到”。类似地，短语“如果确定”或“如果检测到[所描述条件或事件]”可以依据上下文被解释为意指“一旦确定”或“响应于确定”或“一旦检测到[所描述条件或事件]”或“响应于检测到[所描述条件或事件]”。
另外，在本申请说明书和所附权利要求书的描述中，术语“第一”、“第二”等仅用于区分描述，而不能理解为指示或暗示相对重要性。
在本申请说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其他一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其他方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
请参阅图2，本申请实施方式提供一种用于智能终端6(图6所示)的设备状态标识方法。设备状态标识方法包括：
S21：获取场景列表页中显示的设备标识所对应的设备的状态信息，场景列表页用于显示不同场景中包含的设备标识；
S22：若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行标记。
在一些实施例中，步骤S22：若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行标记，包括：若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行图标标记，和/或，根据设备的状态信息对设备对应的设备标识进行文字标记。
在一些实施例中，设备状态标识方法还包括：若设备的状态信息指示设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；若存在与处于异常状态的设备联动的设备，则对存在的设备进行标记。
在一些实施例中，设备状态标识方法还包括：若设备的状态信息指示设备处于异常状态，根据设备的状态信息生成提示信息，提示信息包括场景重新编辑的入口。
在一些实施例中，获取场景列表页中显示的设备标识所对应的设备的状态信息，包括：若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
在一些实施例中，获取场景列表页中显示的设备标识所对应的设备的状态信息，包括：若检测到智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
在一些实施例中，在根据设备的状态信息对设备对应的设备标识进行标记之后，设备状态标识方法还包括：若检测到手动执行指令，则根据手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；若检测到智能终端发出的自动执行指令，则根据自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，第二反馈方式与第一反馈方式不同。
请参阅图5，本申请实施方式还提供一种应用于智能终端6(图6所示)的设备状态标识装置5包括状态信息获取单元51及标记单元52。获取单元51用于获取场景列表页中显示的设备标识所对应的设备的状态信息，场景列表页用于显示不同场景中包含的设备标识；标记单元52用于若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行标记。
请参阅图6，本申请还提供一种智能终端6。智能终端6包括存储器61、处理器60以及存储在存储器61中并可在处理器60上运行的计算机程序62。处理器60执行计算机程序62时实现：获取场景列表页中显示的设备标识所对应的设备的状态信息，场景列表页用于显示不同场景中包含的设备标识；若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行标记。
在一些实施例中，处理器60执行计算机程序62时还实现：若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行图标标记，和/或，根据设备的状态信息对设备对应的设备标识进行文字标记。
在一些实施例中，处理器60执行计算机程序62时还实现：若设备的状态信息指示设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；若存在与处于异常状态的设备联动的设备，则对存在的设备进行标记。
在一些实施例中，处理器60执行计算机程序62时还实现：若设备的状态信息指示设备处于异常状态，根据设备的状态信息生成提示信息，提示信息包括场景重新编辑的入口。
在一些实施例中，处理器60执行计算机程序62时还实现：若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
在一些实施例中，处理器60执行计算机程序62时还实现：若检测到智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
在一些实施例中，处理器60执行计算机程序62时还实现：若检测到手动执行指令，则根据手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；若检测到智能终端发出的自动执行指令，则根据自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，第二反馈方式与第一反馈方式不同。
本申请还提供一种计算机可读存储介质，计算机可读存储介质存储有计算机程序，计算机程序被处理器执行时实现：获取场景列表页中显示的设备标识所对应的设备的状态信息，场景列表页用于显示不同场景中包含的设备标识；若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行标记。
在一些实施例中，计算机程序被处理器执行时还实现：若设备的状态信息指示设备处于异常状态，则根据设备的状态信息对设备对应的设备标识进行图标标记，和/或，根据设备的状态信息对设备对应的设备标识进行文字标记。
在一些实施例中，计算机程序被处理器执行时还实现：若设备的状态信息指示设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；若存在与处于异常状态的设备联动的设备，则对存在的设备进行标记。
在一些实施例中，计算机程序被处理器执行时还实现：若设备的状态信息指示设备处于异常状态，根据设备的状态信息生成提示信息，提示信息包括场景重新编辑的入口。
在一些实施例中，计算机程序被处理器执行时还实现：若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
在一些实施例中，计算机程序被处理器执行时还实现：若检测到智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
在一些实施例中，计算机程序被处理器执行时还实现：若检测到手动执行指令，则根据手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；
若检测到智能终端发出的自动执行指令，则根据自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，第二反馈方式与第一反馈方式不同。实施例一：
“场景”是智能家居类应用里的一个功能，在一个场景中，可以组合控制多台设备执行用户指定的任务，实现全屋的智能联动。其中，这里的设备是指能够通过Wi-Fi或蓝牙等多种协议方式连接上网络，从而实现自身数据、状态实时在线化的设备。当用户执行某个场景时，可能得到的执行结果是“部分执行成功”，用户根据该执行结果不能确定哪个部分执行成功，哪个部分执行不成功。即不能从上述执行结果中获取更有效的信息。为了解决该技术问题，本申请人通过分析可知，出现“部分执行成功”的执行结果是被执行的场景下的某些设备不再属于智能家居中能够被智能终端控制的设备，即该某些设备所对应的设备标识已在设备显示页中被删除。或者，由于被执行的场景下的某些设备与网络断开连接，即该某些设备处于离线状态。
由于在实际应用中，当用户在设备显示页中删除了某个设备标识后，在场景列表页中包括该某个设备标识的场景仍保留该某个设备标识，而不会随着设备显示页删除了该某个设备标识就联动删除场景列表页中对应的设备标识。这是因为，如果联动删除场景列表页中对应的设备标识，可能给用户带来一定的困扰。比如，假设场景1中的设备A标识已在设备显示页中删除，而用户可能记得其在场景1中添加了设备A标识，此时，若场景列表页中场景1的设备A标识被联动删除，则用户可能会怀疑自己的记忆，即给用户带来一定的困扰。在本申请中，为了避免直接在场景列表页中联动删除对应的设备标识，也为了保证用户在反馈的执行结果为“部分执行成功”时获取更有效的信息，则在设备标识已在设备显示页删除，或设备处于离线状态时，在场景列表页中将对应的设备标识进行标识。这样，即使反馈的执行结果是“部分执行成功”，用户也能获知是被删除的设备执行不成功，或，处于离线状态的设备执行不成功。
下面将详细介绍本申请实施例提供的设备状态标识方法：
图2示出了本申请实施例提供的一种设备状态标识方法的流程图，该设备状态标识方法应用于智能终端，详述如下：
步骤S21，获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
其中，场景列表页显示了用户设置的不同场景以及该场景下所包含的设备标识，设备标识与设备是一一对应的关系。需要指出的是，一个场景可以包含1个设备标识，也可以包含2个及2个以上的设备标识，具体与该场景实际包含的设备数量有关。参见图1的场景列表页示意图，在图1中，该场景列表页只有用户设置的一个场景“离家”，在该“离家”场景下包含了空气净化器标识和灯泡标识。需要指出的是，在本申请中，设备标识(如空气净化器标识)除了如图1所示采用图标表示，也可以用文字(如空气净化器)表示。
其中，设备的状态信息包括设备是否异常的信息，其中，设备是否异常的信息包括该 设备是否被删除的信息和该设备是否离线的信息。
在一些实施例中，为了保证获取更准确的设备的状态信息，以及，为了减少获取设备的状态信息的频率，则只在用户访问场景列表页才获取设备的状态信息，此时，所述步骤S21，包括：
若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
本实施例中，若检测到用户点击场景列表页，发出访问指令之后，才获取该场景列表页中显示的各个设备标识对应的设备的状态信息，在用户发出访问指令之前，即使设备处于异常状态，例如该设备被删除或离线都不获取该设备的状态信息。需要指出的是，这里的各个设备标识是指各个不同设备所对应的设备标识，即每个设备标识对应的设备的状态信息都只获取一次。例如，若场景1包含空气净化器标识，场景2同样包含空气净化器标识，若已获取场景1包含的空气净化器标识对应的空气净化器的状态信息，则在场景2中，可直接使用已获取的空气净化器的状态信息，而无需再从其他地方获取。
在一些实施例中，为了能够及时获取准确的设备的状态信息，以及，为了减少获取设备的状态信息的频率，则在执行场景之前获取设备的状态信息，此时，所述步骤S21，包括：
若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息。
本实施例中，用户可设置场景在满足场景执行触发条件时自动执行对应的场景，该场景执行触发条件可以为位置满足要求，或者时间满足要求，或者位置和时间都满足要求等。例如，假设场景1是在智能终端所处的位置为B时自动触发，则在检测到智能终端所处的位置为B时，获取场景列表页中显示的设备标识所对应的设备的状态信息，否则，即使设备被删除或离线都不获取设备的状态信息。通过这样设置，减少了获取设备的状态信息的频率。
在一些实施例中，由于可以自动触发场景的执行，而用户在场景被自动触发执行时也不一定存在获知设备的状态信息的需求，因此，为了进一步减少获取设备的状态信息的频率，则在得到执行结果后的预设时长内，若检测到用户发出的应用启动指令，再获取设备的状态信息，此时，所述若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息，包括：
若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则触发相应场景自动执行，获得执行结果；
若在获得执行结果的预设时长内检测到用户发出的应用启动指令，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息，其中，所述应用启动指令用于启动得到所述执行结果的智能家居类应用。
本实施例中，假设智能家居类应用A中的场景列表页中某个场景自动执行后得到一个执行结果A，在得到该执行结果A内的预设时间内(比如在5分钟内)，若检测到用户启动该智能家居类应用A(比如双击该智能家居类应用A)，则获取场景列表页中显示的设备标识所对应的设备的状态信息。由于场景自动执行时用户无需打开场景列表页，即无法从场景列表页中获知各个设备标识被标识的情况，因此，若执行结果为“部分执行成功”，且用户在获得执行结果后的预设时间内启动智能家居类应用，则表明用户希望获知是哪部分设备没有被执行成功，此时，智能终端获取设备的状态信息，能够保证后续对相应设备标识进行标识的及时性。
步骤S22，若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
具体地，若设备已被删除(具体地，若在设备显示页显示的设备标识被删除，则表示所述设备标识对应的设备被删除)，则通过预设的删除标识对相应设备标识进行标识；若设备已离线，则通过预设的离线标识对对应的设备标识进行标识，且预设的删除标识和预设的离线标识不同。
在一些实施例中，所述步骤S22包括：
若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行图标标记，和/或，根据所述设备的状态信息对所述设备对应的设备标识进行文字标记。
具体地，假设预设的删除标识为一个“垃圾桶”的图标，预设的离线标识为一个“断开的链条”的图标。参见图3，图3示出了通过图标对设备标识进行标识的示意图，在图3中，“离家”场景在空气净化器标识旁边有一个“垃圾桶”的删除标识，表示空气净化器已被删除；在灯泡标识旁边有一个“断开的链条”的离线图标，表示灯泡处于离线状态。
本申请实施例中，获取场景列表页中显示的设备标识所对应的设备的状态信息，若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。由于设备的状态信息能够指示设备是否处于异常状态(如是否被删除或是否已离线)，因此，根据该设备的状态信息对对应的设备标识进行标记，使得用户在得到“部分执行成功”这一执行结果时，也能够从场景列表页中及时获知哪些设备是已被设备显示页删除的，哪些设备是处于离线状态的，从而提高用户的良好体验。
在一些实施例中，由于同一场景下的各个设备之间可能存在联动关系，而若存在联动 关系中的某个设备被删除或离线，将影响联动关系的另一方，即在执行场景时，存在联动关系的另一方同样是执行失败的，因此，为了使得用户获知存在联动关系的另一方也会在场景执行时失败，则对该存在联动关系的另一方也进行标识。即，所述设备状态标识方法还包括：
若所述设备的状态信息指示所述设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；若存在与处于异常状态的设备联动的设备，则对存在的设备进行标识。
本实施例中，可预设一个联动失败标识对相应的设备标识进行标记。比如，假设“离家”场景包括空气净化器、灯泡和音箱这3个设备，且空气净化器和灯泡之间存在以下联动关系：开启空气净化器，且在空气的PM2.5值满足要求后打开灯泡。若空气净化器被删除，则执行“离家”场景时将导致空气净化器和灯泡执行失败，因此，为了使得用户在获得“部分执行成功”时确定所有执行不成功的设备及执行不成功的原因，则在实施例中，采用预设的删除标识对空气净化器标识进行标记，以及，采用预设的联动失败标识对灯泡标识进行标记。
在一些实施例中，当设备被删除或离线时，若其所在的场景被执行时，该设备将执行成功，而这可能导致被执行的场景的功能不能达到用户的需求，因此，为了便于用户快速设置具有新的功能的场景，所述设备状态标识方法还包括：
若所述设备的状态信息指示所述设备处于异常状态，根据所述设备的状态信息生成提示信息，所述提示信息包括场景重新编辑的入口。
本实施例中，若提示信息除了包括场景重新编辑的入口，还包括其他信息，则设置场景编辑的入口的显示方式与提示信息的其他信息的显示方式不同。如图4所示，生成的提示信息为“空气净化器已被删除，你可以重新编辑场景”，其中，“编辑场景”为场景重新编辑的入口，根据图4可知，该“编辑场景”的显示方式与提示信息的其他信息的显示方式不同。当用户点击“编辑场景”后，将进入场景的编辑界面。
在一些实施例中，若被删除的除了设备，还有场景，则生成的提示信息还包括设备名称和场景名称，且设备名称的顺序在场景名称之前。例如，假设设备“空气净化器”被删除，场景“离家”被删除，则生成的提示信息为：设备“空气净化器”被删除，场景“离家”被删除，你可以重新编辑场景。由于场景被删除后，用户不能再看到对应的场景，而设备被删除后，还能在场景中看到对应的设备标识，因此，优先显示设备名称有助于增加用户从提示信息获取更多的信息量。
在一些实施例中，若通过不同的方式执行场景，则通过不同的反馈方式反馈执行结果，即，在所述根据所述设备的状态信息对所述设备对应的设备标识进行标记之后，所述设备 状态标识方法还包括：
若检测到手动执行指令，则根据所述手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；
若检测到所述智能终端发出的自动执行指令，则根据所述自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，所述第二反馈方式与所述第一反馈方式不同。
本实施例中，若通过用户手动执行场景(即用户通过点击图1中的“执行按钮”实现手动执行场景)，则根据第一反馈方式反馈执行结果；若智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则通过智能终端自动执行场景，此时，根据第二反馈方式反馈执行结果。例如，由于用户通过场景列表页实现手动执行场景，所以第一反馈方式可以为文字反馈，即在场景列表页中显示文字形式的执行结果。又例如，由于智能终端自动执行场景时，用户无需进入场景列表页，所以第二反馈方式可以为语音反馈，即用户无需打开智能家居类应用的场景列表页，也能通过智能终端播报的语音实现。由于结合不同的场景执行方式选择不同的反馈方式反馈执行结果，因此，使得用户获取执行结果的方式更灵活，且保证执行结果的获取更及时。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
对应于上文实施例所述的设备状态标识方法，图5示出了本申请实施例提供的设备状态标识装置的结构框图，为了便于说明，仅示出了与本申请实施例相关的部分。
参照图5，该设备状态标识装置5应用于智能终端，包括：
状态信息获取单元，用于获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
标记单元，用于若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
本申请实施例中，获取场景列表页中显示的设备标识所对应的设备的状态信息，若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。由于设备的状态信息能够指示设备是否被删除或指示设备是否已离线，因此，根据该设备的状态信息对对应的设备标识进行标记，使得用户在得到“部分执行成功”这一执行结果时，也能够从场景列表页中及时获知哪些设备是已被设备显示页删除的，哪些设备是处于离线状态的，从而提高用户的良好体验。
在一些实施例中，所述标记单元具体用于：
若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行图标标记，和/或，根据所述设备的状态信息对所述设备对应的设备标识进行文字标记。
在一些实施例中，由于同一场景下的各个设备之间可能存在联动关系，而若存在联动关系中的某个设备被删除或离线，将影响联动关系的另一方，即在执行场景时，存在联动关系的另一方同样是执行失败的，因此，为了使得用户获知存在联动关系的另一方也会在场景执行时失败，则对该存在联动关系的另一方也进行标记。此时，所述设备状态标识装置5还包括：
联动设备检测单元，用于若所述设备的状态信息指示所述设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；
联动设备标记单元，用于若存在与处于异常状态的设备联动的设备，则对存在的设备进行标记。
在一些实施例中，所述设备状态标识装置还包括：
提示信息生成单元，用于若所述设备的状态信息指示所述设备处于异常状态，根据所述设备的状态信息生成提示信息，所述提示信息包括场景重新编辑的入口。
本实施例中，若提示信息除了包括场景重新编辑的入口，还包括其他信息，则设置场景编辑的入口的显示方式与提示信息的其他信息的显示方式不同。
在一些实施例中，若被删除的除了设备，还有场景，则生成的提示信息还包括设备名称和场景名称，且设备名称的顺序在场景名称之前。
在一些实施例中，为了保证获取更准确的设备的状态信息，以及，为了减少获取设备的状态信息的频率，则只在用户访问场景列表页才获取设备的状态信息，此时，所述状态信息获取单元，具体用于：
若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
本实施例中，若检测到用户点击场景列表页，发出访问指令之后，才获取该场景列表页中显示的各个设备标识对应的设备的状态信息，在用户发出访问指令之前，即使设备被删除或离线都不获取设备的状态信息。需要指出的是，这里的各个设备标识是指各个不同设备所对应的设备标识，即每个设备标识对应的设备的状态信息都只获取一次。
在一些实施例中，为了能够及时获取准确的设备的状态信息，以及，为了减少获取设备的状态信息的频率，则在执行场景之前获取设备的状态信息，此时，所述状态信息获取单元，具体用于：
若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景 执行触发条件，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息。
本实施例中，用户可设置场景在满足场景执行触发条件时自动执行对应的场景，该场景执行触发条件可以为位置满足要求，或者时间满足要求，或者位置和时间都满足要求等。
在一些实施例中，所述状态信息获取单元，具体用于：
若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则触发相应场景自动执行，获得执行结果；若在获得执行结果的预设时长内检测到用户发出的应用启动指令，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息，其中，所述应用启动指令用于启动得到所述执行结果的智能家居类应用。
在一些实施例中，若通过不同的方式执行场景，则通过不同的反馈方式反馈执行结果，即所述设备状态标识装置5还包括：
第一执行结果反馈单元，用于若检测到手动执行指令，则根据所述手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；
第二执行结果反馈单元，用于若检测到所述智能终端发出的自动执行指令，则根据所述自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，所述第二反馈方式与所述第一反馈方式不同。
需要说明的是，上述装置/单元之间的信息交互、执行过程等内容，由于与本申请方法实施例基于同一构思，其具体功能及带来的技术效果，具体可参见方法实施例部分，此处不再赘述。
图6为本申请一实施例提供的智能终端的结构示意图。如图6所示，该实施例的智能终端6包括：至少一个处理器60(图6中仅示出一个处理器)、存储器61以及存储在所述存储器61中并可在所述至少一个处理器60上运行的计算机程序62，所述处理器60执行所述计算机程序62时实现上述任意各个方法实施例中的步骤：
获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
所述智能终端6可以是桌上型计算机、笔记本、掌上电脑及云端服务器等计算设备。该智能终端可包括，但不仅限于，处理器60、存储器61。本领域技术人员可以理解，图6仅仅是智能终端6的举例，并不构成对智能终端6的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，例如还可以包括输入输出设备、网络接入设备等。
所称处理器60可以是中央处理单元(Central Processing Unit，CPU)，该处理器60还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
所述存储器61在一些实施例中可以是所述智能终端6的内部存储单元，例如智能终端6的硬盘或内存。所述存储器61在另一些实施例中也可以是所述智能终端6的外部存储设备，例如所述智能终端6上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。进一步地，所述存储器61还可以既包括所述智能终端6的内部存储单元也包括外部存储设备。所述存储器61用于存储操作系统、应用程序、引导装载程序(BootLoader)、数据以及其他程序等，例如所述计算机程序的程序代码等。所述存储器61还可以用于暂时地存储已经输出或者将要输出的数据。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。实施例中的各功能单元、模块可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中，上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。另外，各功能单元、模块的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。上述系统中单元、模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本申请实施例还提供了一种网络设备，该网络设备包括：至少一个处理器、存储器以及存储在所述存储器中并可在所述至少一个处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现上述任意各个方法实施例中的步骤。
本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时实现可实现上述各个方法实施例中的步骤。
本申请实施例提供了一种计算机程序产品，当计算机程序产品在移动终端上运行时，使得移动终端执行时实现可实现上述各个方法实施例中的步骤。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可 存储于一计算机可读存储介质中，该计算机程序在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机程序包括计算机程序代码，所述计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质至少可以包括：能够将计算机程序代码携带到拍照装置/终端设备的任何实体或装置、记录介质、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质。例如U盘、移动硬盘、磁碟或者光盘等。在某些司法管辖区，根据立法和专利实践，计算机可读介质不可以是电载波信号和电信信号。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的实施例中，应该理解到，所揭露的装置/网络设备和方法，可以通过其它的方式实现。例如，以上所描述的装置/网络设备实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通讯连接可以是通过一些接口，装置或单元的间接耦合或通讯连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (22)

  1. 一种设备状态标识方法，其特征在于，所述设备状态标识方法应用于智能终端，包括：
    获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
    若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
  2. 如权利要求1所述的设备状态标识方法，其特征在于，所述若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记，包括：
    若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行图标标记，和/或，根据所述设备的状态信息对所述设备对应的设备标识进行文字标记。
  3. 如权利要求1所述的设备状态标识方法，其特征在于，所述设备状态标识方法还包括：
    若所述设备的状态信息指示所述设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；
    若存在与处于异常状态的设备联动的设备，则对存在的设备进行标记。
  4. 如权利要求1所述的设备状态标识方法，其特征在于，所述设备状态标识方法还包括：
    若所述设备的状态信息指示所述设备处于异常状态，根据所述设备的状态信息生成提示信息，所述提示信息包括场景重新编辑的入口。
  5. 如权利要求1至4任一项所述的设备状态标识方法，其特征在于，所述获取场景列表页中显示的设备标识所对应的设备的状态信息，包括：
    若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
  6. 如权利要求1至4任一项所述的设备状态标识方法，其特征在于，所述获取场景列表页中显示的设备标识所对应的设备的状态信息，包括：
    若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息。
  7. 如权利要求6所述的设备状态标识方法，其特征在于，在所述根据所述设备的状态信息对所述设备对应的设备标识进行标记之后，所述设备状态标识方法还包括：
    若检测到手动执行指令，则根据所述手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；
    若检测到所述智能终端发出的自动执行指令，则根据所述自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，所述第二反馈方式与所述第一反馈方式不同。
  8. 一种设备状态标识装置，其特征在于，所述设备状态标识装置应用于智能终端，包括：
    状态信息获取单元，用于获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
    标记单元，用于若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
  9. 一种智能终端，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序，其特征在于，所述处理器执行所述计算机程序时实现：
    获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
    若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
  10. 如权利要求9所述的智能终端，其特征在于，所述处理器执行所述计算机程序时还实现：
    若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行图标标记，和/或，根据所述设备的状态信息对所述设备对应的设备标识进行文字标记。
  11. 如权利要求9所述的智能终端，其特征在于，所述处理器执行所述计算机程序时还实现：
    若所述设备的状态信息指示所述设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；
    若存在与处于异常状态的设备联动的设备，则对存在的设备进行标记。
  12. 如权利要求9所述的智能终端，其特征在于，所述处理器执行所述计算机程序时还实现：
    若所述设备的状态信息指示所述设备处于异常状态，根据所述设备的状态信息生成提示信息，所述提示信息包括场景重新编辑的入口。
  13. 如权利要求9至12任一项所述的智能终端，其特征在于，所述处理器执行所述计 算机程序时还实现：
    若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
  14. 如权利要求9至12任一项所述的智能终端，其特征在于，若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息。
  15. 如权利要求14所述的智能终端，其特征在于，所述处理器执行所述计算机程序时还实现：
    若检测到手动执行指令，则根据所述手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；
    若检测到所述智能终端发出的自动执行指令，则根据所述自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，所述第二反馈方式与所述第一反馈方式不同。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现：
    获取场景列表页中显示的设备标识所对应的设备的状态信息，所述场景列表页用于显示不同场景中包含的设备标识；
    若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行标记。
  17. 如权利要求16所述的计算机可读存储介质，其特征在于，所述计算机程序被处理器执行时还实现：
    若所述设备的状态信息指示所述设备处于异常状态，则根据所述设备的状态信息对所述设备对应的设备标识进行图标标记，和/或，根据所述设备的状态信息对所述设备对应的设备标识进行文字标记。
  18. 如权利要求16所述的计算机可读存储介质，其特征在于，所述计算机程序被处理器执行时还实现：
    若所述设备的状态信息指示所述设备处于异常状态，则检测同一场景下的其他设备是否存在与处于异常状态的设备联动的设备；
    若存在与处于异常状态的设备联动的设备，则对存在的设备进行标记。
  19. 如权利要求16所述的计算机可读存储介质，其特征在于，所述计算机程序被处理器执行时还实现：
    若所述设备的状态信息指示所述设备处于异常状态，根据所述设备的状态信息生成提 示信息，所述提示信息包括场景重新编辑的入口。
  20. 如权利要求16至19任一项所述的计算机可读存储介质，其特征在于，所述计算机程序被处理器执行时还实现：
    若检测到场景列表页的访问指令，则获取场景列表页中显示的设备标识所对应的设备的状态信息。
  21. 如权利要求16至19任一项所述的计算机可读存储介质，其特征在于，所述计算机程序被处理器执行时还实现：
    若检测到所述智能终端所处的位置和/或当前时间满足场景列表页中任一场景的场景执行触发条件，则获取所述场景列表页中显示的设备标识所对应的设备的状态信息。
  22. 如权利要求21所述的计算机可读存储介质，其特征在于，所述计算机程序被处理器执行时还实现：
    若检测到手动执行指令，则根据所述手动执行指令控制对应场景下的各个设备，并根据第一反馈方式反馈执行结果；
    若检测到所述智能终端发出的自动执行指令，则根据所述自动执行指令控制对应场景下的各个设备，并根据第二反馈方式反馈执行结果，所述第二反馈方式与所述第一反馈方式不同。
PCT/CN2021/077095 2020-04-07 2021-02-20 设备状态标识方法、装置及智能终端 WO2021203848A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21784253.3A EP4130953A4 (en) 2020-04-07 2021-02-20 DEVICE STATE IDENTIFICATION PROCESSING METHOD AND APPARATUS, AND INTELLIGENT TERMINAL
US17/956,657 US20230017725A1 (en) 2020-04-07 2022-09-29 Device state identification method and apparatus, and intelligent terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010263868.6A CN111488088B (zh) 2020-04-07 2020-04-07 设备状态标识方法、装置及智能终端
CN202010263868.6 2020-04-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/956,657 Continuation US20230017725A1 (en) 2020-04-07 2022-09-29 Device state identification method and apparatus, and intelligent terminal

Publications (1)

Publication Number Publication Date
WO2021203848A1 true WO2021203848A1 (zh) 2021-10-14

Family

ID=71798197

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/077095 WO2021203848A1 (zh) 2020-04-07 2021-02-20 设备状态标识方法、装置及智能终端

Country Status (4)

Country Link
US (1) US20230017725A1 (zh)
EP (1) EP4130953A4 (zh)
CN (1) CN111488088B (zh)
WO (1) WO2021203848A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125147A (zh) * 2021-11-15 2022-03-01 青岛海尔科技有限公司 设备场景功能的校验方法、场景引擎及场景平台

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111488088B (zh) * 2020-04-07 2022-05-06 Oppo广东移动通信有限公司 设备状态标识方法、装置及智能终端
CN112147910B (zh) * 2020-09-14 2023-02-03 青岛海尔科技有限公司 执行能力的确定方法、装置、存储介质及电子装置
CN113098944A (zh) * 2021-03-26 2021-07-09 广东好太太智能家居有限公司 一种智能设备离线实时提醒方法、系统及存储介质
CN113904924A (zh) * 2021-10-19 2022-01-07 吴枚兰 一种物联网的局域网系统高效运维方法
CN117892015A (zh) * 2024-01-16 2024-04-16 山东智慧燃气物联网技术有限公司 一种用户端燃气使用状态监控方法、系统、设备和介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020158910A1 (en) * 2000-02-17 2002-10-31 Sharrow John Anthony Adaptive menu appliance control with user interface options
CN105809881A (zh) * 2016-05-10 2016-07-27 北京小米移动软件有限公司 报警方法及装置、控制设备及传感设备
CN106919060A (zh) * 2016-08-23 2017-07-04 广州零号软件科技有限公司 圆形气泡显示的智能家居产品人机交互界面
CN107765555A (zh) * 2016-08-23 2018-03-06 广州零号软件科技有限公司 实物图标显示的智能家居产品人机交互界面
CN111488088A (zh) * 2020-04-07 2020-08-04 Oppo广东移动通信有限公司 设备状态标识方法、装置及智能终端

Family Cites Families (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6456306B1 (en) * 1995-06-08 2002-09-24 Nortel Networks Limited Method and apparatus for displaying health status of network devices
US5870559A (en) * 1996-10-15 1999-02-09 Mercury Interactive Software system and associated methods for facilitating the analysis and management of web sites
ATE315861T1 (de) * 1997-02-18 2006-02-15 Cit Alcatel Leitwegumlenkungsverfahren in hierarchischen strukturierten netzwerken
US7197561B1 (en) * 2001-03-28 2007-03-27 Shoregroup, Inc. Method and apparatus for maintaining the status of objects in computer networks using virtual state machines
US7519909B2 (en) * 2001-08-10 2009-04-14 American Power Conversion Corporation Uninterruptible power supply (UPS) devices monitoring system
JP2003244151A (ja) * 2002-02-15 2003-08-29 Fujitsu Ltd ネットワーク装置及びネットワーク管理装置
US7617073B2 (en) * 2002-03-01 2009-11-10 Bmc Software, Inc. System and method for assessing and indicating the health of components
US7272564B2 (en) * 2002-03-22 2007-09-18 Motorola, Inc. Method and apparatus for multimodal communication with user control of delivery modality
US20030233660A1 (en) * 2002-06-18 2003-12-18 Bellsouth Intellectual Property Corporation Device interaction
US10048681B2 (en) * 2004-09-29 2018-08-14 Rockwell Automation Technologies, Inc. System status visualization method and system
US8117290B2 (en) * 2005-07-25 2012-02-14 Cisco Technology, Inc. Simple home networking
US7702487B2 (en) * 2006-04-11 2010-04-20 Invensys Systems, Inc. System management user interface providing user access to status information for process control system equipment including displayed propagated status in a navigation pane
US9357052B2 (en) * 2008-06-09 2016-05-31 Immersion Corporation Developing a notification framework for electronic device events
US8943551B2 (en) * 2008-08-14 2015-01-27 Microsoft Corporation Cloud-based device information storage
US9978365B2 (en) * 2008-10-31 2018-05-22 Nokia Technologies Oy Method and system for providing a voice interface
US11487347B1 (en) * 2008-11-10 2022-11-01 Verint Americas Inc. Enhanced multi-modal communication
US8769085B2 (en) * 2009-11-16 2014-07-01 Cox Communications, Inc. Systems and methods for analyzing the health of networks and identifying points of interest in networks
US20120251016A1 (en) * 2011-04-01 2012-10-04 Kenton Lyons Techniques for style transformation
US20120306620A1 (en) * 2011-05-31 2012-12-06 General Electric Company Systems and methods for alert visualization
US9183163B2 (en) * 2012-06-27 2015-11-10 Ubiquiti Networks, Inc. Method and apparatus for distributed control of an interfacing-device network
CN102833108B (zh) * 2012-08-30 2016-03-30 华为技术有限公司 故障点位置信息处理方法及设备
US8490006B1 (en) * 2012-09-04 2013-07-16 State Farm Mutual Automobile Insurance Company Scene creation for building automation systems
CN102891786B (zh) * 2012-09-21 2015-05-13 兴泓昇(福州)智能科技有限公司 自动进行关联的智能家居系统的场景控制组网方法
CN103869761B (zh) * 2012-12-14 2017-03-08 海尔集团公司 家电控制方法及控制系统
US20140191856A1 (en) * 2013-01-07 2014-07-10 Lg Electronics Inc. Home Appliance and Mobile Device
US10025463B2 (en) * 2013-09-18 2018-07-17 Vivint, Inc. Systems and methods for home automation scene control
KR102088526B1 (ko) * 2013-11-04 2020-04-14 삼성전자주식회사 스마트 홈 시스템을 제어하기 위한 방법 및 그 전자 장치
US10454783B2 (en) * 2014-02-05 2019-10-22 Apple Inc. Accessory management system using environment model
EP2890223B1 (en) * 2013-12-27 2020-05-27 Panasonic Intellectual Property Corporation of America Method for controlling mobile terminal and program for controlling mobile terminal
US9952750B2 (en) * 2014-02-13 2018-04-24 International Business Machines Corporation Managing a drop-down menu having a set of items corresponding with a set of data
US20170097621A1 (en) * 2014-09-10 2017-04-06 Crestron Electronics, Inc. Configuring a control sysem
US20160124403A1 (en) * 2014-10-29 2016-05-05 Xiaomi Inc. Method and server of customizing scenario mode for smart devices
CN110067971B (zh) * 2014-12-26 2021-08-27 麦克赛尔株式会社 照明装置
CN104808501B (zh) * 2015-03-31 2018-02-02 小米科技有限责任公司 智能场景删除方法和装置
US10133443B2 (en) * 2015-06-14 2018-11-20 Google Llc Systems and methods for smart home automation using a multifunction status and entry point icon
CN105182777A (zh) * 2015-09-18 2015-12-23 小米科技有限责任公司 设备控制方法及装置
JP6572737B2 (ja) * 2015-10-30 2019-09-11 ヤマハ株式会社 オーディオシステム制御プログラムおよび制御端末装置
CN105897522A (zh) * 2015-12-23 2016-08-24 乐视网信息技术（北京）股份有限公司 智能家居设备的控制方法及装置
US20170187809A1 (en) * 2015-12-23 2017-06-29 Le Holdings (Beijing) Co., Ltd. Method and electronic apparatus for controlling smart home device
US20170289766A1 (en) * 2016-03-29 2017-10-05 Microsoft Technology Licensing, Llc Digital Assistant Experience based on Presence Detection
CN106452989B (zh) * 2016-08-31 2019-12-13 北京小米移动软件有限公司 建立智能场景的方法及装置
US10516589B2 (en) * 2016-08-31 2019-12-24 At&T Intellectual Property I, L.P. Sensor web management system for internet of things sensor devices with physically imprinted unique frequency keys
CN108804299B (zh) * 2017-04-26 2023-04-07 腾讯科技（深圳）有限公司 应用程序异常处理方法及装置
US10619882B2 (en) * 2017-07-27 2020-04-14 Johnson Controls Technology Company Building management system with scorecard for building energy and equipment performance
CN108449241B (zh) * 2018-02-09 2021-10-08 深圳绿米联创科技有限公司 智能家居场景的配置方法及装置、终端
CN108594771A (zh) * 2018-03-20 2018-09-28 深圳华龙讯达信息技术股份有限公司 运行状态报警呈现方法和装置
CN110609759B (zh) * 2018-06-15 2021-09-14 华为技术有限公司 一种故障根因分析的方法及装置
CN116055323A (zh) * 2018-08-20 2023-05-02 Oppo广东移动通信有限公司 一种场景恢复方法、云平台及计算机存储介质
CN109245308A (zh) * 2018-11-01 2019-01-18 常州思贝尔电能科技有限公司 一种基于变电站综合监控系统的联动告警方法
CN109460172B (zh) * 2018-11-02 2020-10-02 珠海格力电器股份有限公司 对象显示方法和装置、存储介质及电子装置
CN110134020A (zh) * 2019-03-13 2019-08-16 佛山市云米电器科技有限公司 智能门锁自动控制全屋家电设备的方法
CN114500137A (zh) * 2019-05-31 2022-05-13 华为技术有限公司 一种控制设备服务的方法、云服务器和智能家居系统
US20230029568A1 (en) * 2020-01-16 2023-02-02 Honeywell International Inc. Root cause analytics of hvac faults
CN113452542A (zh) * 2020-03-27 2021-09-28 华为技术有限公司 故障检测方法及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020158910A1 (en) * 2000-02-17 2002-10-31 Sharrow John Anthony Adaptive menu appliance control with user interface options
CN105809881A (zh) * 2016-05-10 2016-07-27 北京小米移动软件有限公司 报警方法及装置、控制设备及传感设备
CN106919060A (zh) * 2016-08-23 2017-07-04 广州零号软件科技有限公司 圆形气泡显示的智能家居产品人机交互界面
CN107765555A (zh) * 2016-08-23 2018-03-06 广州零号软件科技有限公司 实物图标显示的智能家居产品人机交互界面
CN111488088A (zh) * 2020-04-07 2020-08-04 Oppo广东移动通信有限公司 设备状态标识方法、装置及智能终端

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125147A (zh) * 2021-11-15 2022-03-01 青岛海尔科技有限公司 设备场景功能的校验方法、场景引擎及场景平台

Also Published As

Publication number Publication date
EP4130953A1 (en) 2023-02-08
EP4130953A4 (en) 2023-11-01
CN111488088A (zh) 2020-08-04
CN111488088B (zh) 2022-05-06
US20230017725A1 (en) 2023-01-19

Similar Documents

Publication Publication Date Title
WO2021203848A1 (zh) 设备状态标识方法、装置及智能终端
WO2021027365A1 (zh) 事件监控方法、装置、计算机设备和存储介质
CN102946343B (zh) 访问音视频社区虚拟房间的方法和系统
WO2018120721A1 (zh) 用户界面的测试方法、系统、电子装置及计算机可读存储介质
CN109995805B (zh) 一种智能机器人的管理方法、终端设备及介质
EP3901843A2 (en) Screen projection method and apparatus, and storage medium
CN107645546B (zh) 基于安卓系统的文件监听方法、智能设备及存储介质
CN110287696B (zh) 一种反弹shell进程的检测方法、装置和设备
CN112269799A (zh) 一种数据查询方法、装置、设备和介质
WO2022135276A1 (zh) 测试用例的处理方法、装置和存储介质
CN110688305B (zh) 测试环境同步方法、装置、介质、电子设备
CN113872951B (zh) 混合云安全策略下发方法、装置、电子设备和存储介质
CN115001967B (zh) 一种数据采集方法、装置、电子设备及存储介质
CN112380170A (zh) 一种文件更新操作的关联方法、装置及计算机设备
WO2021164179A1 (zh) 一种数据监控方法及装置
CN114417282A (zh) 一种用户权限确定方法、装置、电子设备及存储介质
CN113010587B (zh) 数据源配置方法、装置、终端、服务器及介质
CN115079885A (zh) 双窗口显示的系统操控方法、装置、电子设备及存储介质
CN115208671A (zh) 防火墙配置方法、装置、电子设备和存储介质
WO2019056545A1 (zh) 测试机自动化管理方法、装置、设备及存储介质
WO2016173136A1 (zh) 一种终端应用处理方法及其装置
CN112256820A (zh) 一种文档定位方法及装置
CN113626409B (zh) 一种测试资料处理方法、装置、设备及存储介质
CN109271398B (zh) 数据库事务处理方法、装置、设备和计算机可读存储介质
CN114841648B (zh) 物料分发方法、装置、电子设备和介质

Legal Events

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

Ref document number: 21784253

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021784253

Country of ref document: EP

Effective date: 20221104