CN112163125A - Device management method and apparatus, storage medium, and electronic device - Google Patents
Device management method and apparatus, storage medium, and electronic device Download PDFInfo
- Publication number
- CN112163125A CN112163125A CN202011003602.4A CN202011003602A CN112163125A CN 112163125 A CN112163125 A CN 112163125A CN 202011003602 A CN202011003602 A CN 202011003602A CN 112163125 A CN112163125 A CN 112163125A
- Authority
- CN
- China
- Prior art keywords
- scene management
- management map
- scene
- map
- management
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 406
- 238000000034 method Methods 0.000 claims abstract description 23
- 230000015654 memory Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 13
- 230000004044 response Effects 0.000 claims description 12
- 238000010586 diagram Methods 0.000 description 11
- 230000009849 deactivation Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/904—Browsing; Visualisation therefor
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a device management method and device, a storage medium and an electronic device. Wherein, the method comprises the following steps: obtaining a removal instruction initiated by a target client, wherein the removal instruction is used for indicating that target equipment is removed from a target equipment group; responding to the removal instruction, and determining scene management maps corresponding to a plurality of application scenes where the target equipment is located; hiding the device identifier of the target device in each scene management map and updating the scene management map to obtain an updated scene management map under the condition that the management state of each scene management map is a non-use state, wherein the updated scene management map comprises a first-class scene management map and a second-class scene management map; and adjusting the management state of the first-class scene management map to be an enabling state. The invention solves the technical problem of complex application management operation of the equipment.
Description
Technical Field
The invention relates to the field of smart home, in particular to a device management method and device, a storage medium and electronic equipment.
Background
The use of smart homes at home is becoming more and more popular at present. After the intelligent home devices are bound to the intelligent home established by the user, the user can configure corresponding application scenes for the intelligent devices through the cloud of the intelligent home, and therefore linkage application between at least two intelligent home devices is achieved.
In the related art, after a certain smart home device is unbound from a smart home, the smart scene related to the smart home device is automatically closed and deleted. Under the condition that the intelligent scene after the intelligent household equipment is removed can be applied, the user needs to perform corresponding intelligent scene configuration for the rest intelligent household equipment again, so that the management operation for the application of the intelligent household equipment is complex and tedious. When the smart home device binds the smart home of the user again, since the previously configured smart scene is deleted, the smart scene needs to be configured for the smart home device again, thereby increasing the complexity of the management operation applied to the smart home device.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides a device management method and device, a storage medium and electronic equipment, and aims to at least solve the technical problem that application management operation of the equipment is complex.
According to an aspect of an embodiment of the present invention, there is provided a device management method, including: obtaining a removal instruction initiated by a target client, wherein the removal instruction is used for indicating that target equipment is removed from a target equipment group; responding to the removal instruction, and determining scene management maps corresponding to a plurality of application scenes where the target equipment is located; hiding the device identifier of the target device in each scene management map and updating the scene management map to obtain an updated scene management map when the management state of each scene management map is a disabled state, wherein the updated scene management map comprises a first-class scene management map and a second-class scene management map, the first-class scene management map comprises a management control relationship of which the relationship label is indicated as an effective label, and the relationship labels of the management control relationship in the second-class scene management map are all indicated as invalid labels; and adjusting the management state of the first-class scene management map to be an enabling state.
According to another aspect of the embodiments of the present invention, there is also provided an apparatus for device management, including: the system comprises an acquisition module, a sending module and a receiving module, wherein the acquisition module is used for acquiring a removal instruction initiated by a target client, and the removal instruction is used for indicating that target equipment is removed from a target equipment group; a determining module, configured to determine, in response to the removal instruction, a scene management map corresponding to each of a plurality of application scenes where the target device is located; a processing module, configured to hide an equipment identifier of the target equipment in each scene management map and update the scene management map to obtain an updated scene management map when a management state of each scene management map is a disabled state, where the updated scene management map includes a first-class scene management map and a second-class scene management map, the first-class scene management map includes a management control relationship in which a relationship tag indicates an effective tag, and relationship tags in the management control relationship in the second-class scene management map all indicate failed tags; and the adjusting module is used for adjusting the management state of the first-class scene management map into a starting state.
According to still another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned device management method when running.
According to still another aspect of the embodiments of the present invention, there is also provided an electronic device, including a memory and a processor, where the memory stores therein a computer program, and the processor is configured to execute the device management method described above through the computer program.
In the embodiment of the invention, the device identifier of the target device in the scene management map containing the target device is hidden, the judgment is carried out through the validity of the management control relation label in the updated scene management map, the management state of the first type of scene management map is adjusted to the starting state, and the purpose of starting the application scene which can still be used after the target device is removed is achieved, so that the technical effect that the application scene of the device can be continuously used without reconfiguring the application scene for the rest devices is achieved, and the technical problem that the application management operation of the device is complex is further solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a schematic diagram of an application environment of an alternative device management method according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating an alternative device management method according to an embodiment of the present invention;
FIG. 3 is a flow chart illustrating an alternative device management method according to an embodiment of the present invention;
FIG. 4 is a flow chart illustrating an alternative device management method according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a flow of an alternative device management method according to an embodiment of the invention;
FIG. 6 is a schematic diagram of a flow of an alternative device management method according to an embodiment of the invention;
FIG. 7 is a schematic diagram of the flow of an alternative device management method according to an embodiment of the invention;
fig. 8 is a schematic structural diagram of an alternative device management apparatus according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of an alternative electronic device according to an embodiment of the invention;
fig. 10 is a schematic structural diagram of an alternative electronic device according to an embodiment of the invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, 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.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
According to an aspect of the embodiments of the present invention, there is provided a device management method, which may be applied to, but not limited to, the environment shown in fig. 1. The terminal device 102 performs data interaction with the server 112 through the network 110.
Optionally, in this embodiment, the terminal device 102 may be a terminal device configured with a target client, and may include but is not limited to at least one of the following: mobile phones (such as Android phones, iOS phones, etc.), notebook computers, tablet computers, palm computers, MID (Mobile Internet Devices), PAD, desktop computers, smart televisions, etc. The target client may be a client with management of linkage relationships between smart devices, such as "hai keepers. The network 110 may include, but is not limited to: a wired network, a wireless network, wherein the wired network comprises: a local area network, a metropolitan area network, and a wide area network, the wireless network comprising: bluetooth, WIFI, and other networks that enable wireless communication. The server 112 may be a single server, a server cluster composed of a plurality of servers, or a cloud server. The above is merely an example, and this is not limited in this embodiment.
As an optional implementation, as shown in fig. 2, the device management method includes:
s202, a removing instruction initiated by the target client is obtained, wherein the removing instruction is used for indicating that the target equipment is removed from the target equipment group;
s204, responding to the removal instruction, and determining scene management maps corresponding to a plurality of application scenes where the target equipment is located;
s206, under the condition that the management state of each scene management map is a non-use state, hiding the equipment identifier of the target equipment in each scene management map, updating the scene management map, and obtaining an updated scene management map, wherein the updated scene management map comprises a first-class scene management map and a second-class scene management map;
and S208, adjusting the management state of the first-class scene management map to be an enabling state.
It should be noted that: in step S206, the first-type scene management map includes management control relationships whose relationship labels are indicated as valid labels, and the relationship labels of the management control relationships in the second-type scene management map are all indicated as invalid labels.
Alternatively, the target device group may be a group of at least two smart devices including the target device. At least one set of management control relationships exist between the intelligent devices in the device group for forming a specific device group. The management control relationship between the intelligent devices refers to a response relationship in which the state of the intelligent devices changes under a set condition. For example, between the intelligent entrance and the intelligent socket installed in the entrance, and the intelligent small night lamp installed on the intelligent socket, the management control relationship means that the user is configured for the intelligent entrance, the intelligent socket, and the intelligent small night lamp: under the condition that the door was opened in the response of intelligence entrance, the smart jack response was started, and the little night-light of intelligence is then the concrete work cooperation relation that lights under the condition that smart jack started.
Alternatively, the scenario may be a specific application scenario formed by one or more sets of management control relationships. For example, the application scenarios formed by specific application conditions and state transitions among the intelligent hallway, the intelligent socket and the intelligent small night lamp.
Optionally, the scene management map may be a concrete representation of a management control relationship of a certain application scene in the device group. The scenario management map is used to represent the management control relationship of the determined state change of a specific smart device. For example, the specific working conditions among the intelligent hallway, the intelligent socket and the intelligent small night lamp can be represented by a scene management map. Alternatively, the representation of the scene management graph may be, but is not limited to: a connection relation diagram, a circuit control diagram and a control relation diagram.
Alternatively, the management state of the scene management graph may be the current application state of the scene management graph. Alternatively, the management state may include, but is not limited to: enabled, disabled. The scene management map being in the enabled state indicates that the management control relationship represented in the scene management map is in the application state. Disabled means that all the management control relations represented in the scene management graph are in the state of being disabled. The non-use state indicates that the management control relationship represented in the scene management map is in a state of temporarily non-use.
Alternatively, the management state of the scene management map needs to be adjusted to a deactivated state when the scene management map is managed. If the management state of the scene management map is the disabled state before the management operation, the management state adjustment is not required, and the management operation can be directly performed on the scene management map. If the management state of the scene management map is an enabled state before the management operation, the management state needs to be adjusted to a disabled state in order to enable the management operation on the scene management map.
Optionally, the device identification is an identification for identifying a specific device in the scene management atlas. The device identifiers correspond to the smart devices one to one, and are used for representing the smart devices in the scene management map. Optionally, the device identifier includes at least one of the following forms: image identification, symbol identification, character identification and number identification.
Optionally, the relationship label is a label for indicating a specific certain management control relationship state in the scene management map. Alternatively, the relationship label may indicate, but is not limited to: a valid tag, a stale tag.
Optionally, after the management state of the first type of scene management graph is adjusted to the enabled state, an enabling message is sent to the target client to notify the target client that the application scene corresponding to the target client is successfully enabled.
Optionally, a message that cannot be enabled by the second type of scene management graph is pushed to the target client. Optionally, the disable notification message may indicate that the reason for the disable is the lack of a primary device, i.e., a target device.
In the embodiment of the application, the device identifier of the target device in the scene management map containing the target device is hidden, the judgment is performed through the validity of the management control relation label in the updated scene management map, the management state of the first-class scene management map is adjusted to the starting state, and the purpose of starting the application scene which can still be used after the target device is removed is achieved, so that the technical effect that the application scene of the device can be continuously used without reconfiguring the application scene for the rest devices is achieved, and the technical problem that the application management operation of the device is complex is solved.
As an optional implementation manner, when the management state of the first class scene management graph is adjusted to the enabled state, the method further includes:
determining the original management state of each scene management map in the first class of scene management maps;
and keeping the shutdown state of the scene management map with the original management state as the shutdown state.
It should be noted that the original management state of the scene management map may be a management state of the scene management map before a series of operations of the present apparatus management, that is, before the removal instruction is acquired.
Optionally, the management state of the scenario management graph is one of a deactivated state and an activated state.
Optionally, the target client is provided with an application client that adjusts the original management state of the scene management graph. The management state of the scene management graph is adjusted by using the target client, so that the corresponding management control relation between the intelligent devices indicated by the scene management graph is disabled or enabled.
Optionally, as shown in fig. 3, when the first type of scene management map is enabled, step S302 is executed to determine whether an original management state of the corresponding scene management map is an enabled state, if the determination result is yes, that is, the scene management map is in an enabled state before the current device management operation, step S304 is executed to adjust the management state of the scene management map to be the enabled state, and if the determination result of S302 is no, step S306 is executed to maintain the disabled state of the scene management map.
In the embodiment of the application, when the state of the first-class scene management map is adjusted, the original state of the scene management picture is judged, and when the original state is the disabled state, the disabled state is maintained, that is, the first-class scene management map whose original state is the disabled state is not enabled, so that the management state of the scene management map is ensured to be consistent with the original management state before the current device management operation.
As an optional implementation manner, updating the scene management map, and obtaining the updated scene management map includes:
acquiring a relationship label of a management control relationship among devices in a scene management map;
adjusting a relation label of a management control relation directly associated with the target equipment in the scene management map to be a failure label so as to obtain an updated scene management map;
determining the scene management map as a first class of scene management map under the condition that the scene management map comprises a management control relation indicated as an effective label by a relation label aiming at the updated scene management map; and under the condition that the relationship labels of the management control relationship in the scene management map are all indicated as failure labels, determining the scene management map as a second type of scene management map.
It should be noted that, when a management control relationship indicated as a valid relationship label exists in the scene management map, the scene management map is determined as the first type scene management map. The number of valid tags is not limited.
Alternatively, the directly associated management control relationship may be a management control relationship between the target device and the directly connected related device. Alternatively, the direct association may be, but is not limited to: the device identification of the target device is associated with the device identification of the connected associated device.
Alternatively, as shown in fig. 4, when the scene management map is updated, step S402 is executed to obtain the relationship labels of the management control relationships existing in the scene management map. In the case where the relationship labels of all the management control relationships are acquired, step S404 is executed to determine the position of the device identifier of the target device in the scene management map and the relationship label of the management control relationship directly connected to the device identifier of the target device. If the target device and the directly associated relationship tag are determined, step S406 is executed to adjust the directly associated relationship tag to be a failure tag. In the case where the adjustment of the indication state of the relation label is completed, step S408 is performed to determine whether a valid label exists in the scene management map. In the case that the judgment result is yes, step S410 is performed to determine that the scene management map is the first-type scene management map. In the case where the determination result is no, step S412 is performed to determine that the scene management map is the second-type scene management map.
In the embodiment of the application, whether an effective label exists in the updated scene management map is judged, and if the effective label exists, the first type of scene management map can be started, so that the first type of scene management map is started, waste of an effective equipment management control relation is avoided, and meanwhile, the operation of reconfiguring the equipment management control relation is saved, so that the equipment application management operation is simplified.
As an optional implementation manner, before obtaining the release instruction initiated by the target client, the method further includes:
receiving a dismissal operation in the target client;
and generating a release instruction in response to the release operation, wherein the release instruction is used for indicating to delete the binding relationship between the target device and the target device group.
Alternatively, the disarming operation may be a specific operation to remove the target device out of the group of target devices. Alternatively, the specific operation form of the release operation may be, but is not limited to: sliding plus click, long pressing plus click, dragging to a set position, and clicking plus click.
As an optional implementation manner, in response to the removing instruction, determining the scene management graph corresponding to each of the plurality of application scenes where the target device is located includes:
responding to the removal instruction, and acquiring the equipment identifier of the target equipment;
and determining a scene management map corresponding to each of the plurality of application scenes matched with the equipment identifier from the scene management map set corresponding to the target equipment group.
Alternatively, the scene management profile set may include all scene management profiles to which the target device group is set. Optionally, the presentation form of each scene management map in the scene management map set may be, but is not limited to: brief information list, icon list, thumbnail list, name list, code list. It should be noted that the display information in the display form is matched and corresponds to each scene management map, so that a plurality of scene management maps are distinguished.
In the embodiment of the application, the target device in the device group is removed from the device group by performing the removal operation on the target client and correspondingly generating the removal instruction, and the management control relationships of the other related devices are reserved in a manner of hiding the device identifier of the target device, so that the operation of reconfiguring the application management relationships of the other related devices is saved, and the effect of simplifying the application management operation of the device is realized.
As an alternative implementation, as shown in fig. 5, after the updating the scene management map to obtain the updated scene management map, the method further includes:
s502, acquiring a binding instruction initiated by the target client, wherein the binding instruction is used for indicating target equipment to be added again in the target equipment group;
s504, responding to the binding instruction, and determining scene management maps corresponding to a plurality of application scenes where the target equipment is located;
and S506, under the condition that the management state of each scene management map is a non-use state, displaying the equipment identifier of the target equipment in each hidden scene management map, and recovering the scene management map to obtain the recovered scene management map.
Alternatively, the binding instruction may be to re-add the target device to the group of target devices.
Optionally, displaying the device identification of the target device in each scene management graph that has been hidden includes:
determining a location of a device identification of a target device in a scene management atlas;
the device identification is adjusted from a hidden state to a displayed state.
Optionally, as shown in fig. 6, restoring the scene management map to obtain a restored scene management map includes:
s602, determining the position of the equipment identifier of the target equipment in the scene management map;
s604, obtaining a relation label of a management control relation directly connected with the equipment identifier of the target equipment;
and S606, recovering the relation label from the invalid label to an effective label to obtain a recovered scene management map.
Note that the instruction content of the scene management map after the restoration is identical to the instruction content of the scene management map before the removal target apparatus operates.
Optionally, after obtaining the recovered scene management map, the method further includes:
and adjusting the state of the recovered scene management map to be an enabled state.
Optionally, adjusting the state of the recovered scene management graph to an enabled state includes:
judging the management state of the scene management map before management operation;
under the condition that the management state before the management operation is the starting state, adjusting the state of the recovered scene management map into the starting state;
and under the condition that the management state before the management operation is a deactivation state, pushing activation selection information to the target client so that the target client selects whether to activate the corresponding scene management map.
Alternatively, the management state of the scene management map before the management operation may be a management state before the binding instruction is acquired.
Optionally, the enabling selection information may include, but is not limited to: identification information of the scene management map, a reason for the deactivation, and a deactivation time.
Optionally, the reason for the deactivation of the scene management map adjusted to the deactivation state may be, but is not limited to: temporary absence, regulatory tuning, lack of critical equipment.
Alternatively, the flow of adjusting the state of the recovered scene management graph to the enabled state may be, but is not limited to, as shown in fig. 7. In the case of obtaining the recovered scene management map, step S702 is executed to determine whether the management state of the scene management map before the binding instruction is obtained is the enabled state. If it is determined that the scene is in the enabled state, step S704 is executed to adjust the state of the recovered scene management map to the enabled state. If the client is not in the enabled state, step S706 is executed, and the enabled selection information is sent to the target client, and the selection instruction returned by the target client is received. The enabling selection information comprises identification information of the scene management map, a disabling reason and disabling time.
And the user judges whether the management state of the scene management map is adjusted currently or not based on the starting selection information received by the target client. In the event that the scene management graph is disabled due to the lack of critical and target devices, the user may select whether this application scenario is still needed based on the target device's rebinding. In the case where the deactivation of the scene management graph is not needed for a while, the user may select whether this application scene is needed based on the target device's rebinding.
The selection instruction returned by the target client may be, but is not limited to: keeping the deactivation state and adjusting the deactivation state to the activation state. In the case of receiving the selection instruction returned by the target client, step S708 is executed to determine whether the selection instruction indicates to adjust to the enabled state. If yes, step S710 is executed to adjust the state of the recovered scene management map to the enabled state. If the determination is no, step S712 is executed to maintain the deactivated state of the recovered scene management map.
In the embodiment of the present application, the recovery of the management control relationship related to the target device is achieved by adjusting the state of the device identifier of the target device and the state of the relationship tag of the management control relationship.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
According to another aspect of the embodiment of the present invention, there is also provided a device management apparatus for implementing the device management method. As shown in fig. 8, the apparatus includes:
an obtaining module 802, configured to obtain a removal instruction initiated by a target client, where the removal instruction is used to instruct to remove a target device from a target device group;
a determining module 804, configured to determine, in response to the removal instruction, a scene management map corresponding to each of the multiple application scenes where the target device is located;
a processing module 806, configured to hide the device identifier of the target device in each scene management map and update the scene management map to obtain an updated scene management map when the management state of each scene management map is a disabled state, where the updated scene management map includes a first-class scene management map and a second-class scene management map, the first-class scene management map includes a management control relationship in which a relationship tag indicates an effective tag, and relationship tags in the management control relationship in the second-class scene management map both indicate a failed tag;
an adjusting module 808, configured to adjust the management state of the first class of scene management graph to an enabled state.
In the embodiment of the application, the device identifier of the target device in the scene management map containing the target device is hidden, the judgment is performed through the validity of the management control relation label in the updated scene management map, the management state of the first-class scene management map is adjusted to the starting state, and the purpose of starting the application scene which can still be used after the target device is removed is achieved, so that the technical effect that the application scene of the device can be continuously used without reconfiguring the application scene for the rest devices is achieved, and the technical problem that the application management operation of the device is complex is solved.
As an optional implementation, the apparatus further includes:
the obtaining module is further configured to obtain a binding instruction initiated by the target client, where the binding instruction is used to indicate that the target device is newly added to the target device group;
the determining module is further configured to determine, in response to the binding instruction, a scene management map corresponding to each of the plurality of application scenes where the target device is located;
the processing module is further configured to display the device identifier of the target device in each hidden scene management map and restore the scene management map to obtain a restored scene management map when the management state of each scene management map is the disabled state.
In the embodiment of the application, the recovered scene management map is obtained by restoring the device identifier of the target device in the scene management map containing the target device to display, so that when the target device is added to the target device group again, the tag validity of the management control relationship in the scene management map can be adjusted, the application scene of the target device can be started, the purpose of restarting the management control relationship configured before the target device is added again is achieved, the application scene does not need to be configured for the target device again, and the technical problem that the application management operation of the device is complex is solved.
According to another aspect of the embodiment of the present invention, there is also provided an electronic device for implementing the device management method, where the electronic device may be the terminal device or the server shown in fig. 1. The present embodiment takes the electronic device as a server as an example for explanation. As shown in fig. 9, the electronic device comprises a memory 902 and a processor 904, the memory 902 having stored therein a computer program, the processor 904 being arranged to perform the steps of any of the above-described method embodiments by means of the computer program.
Optionally, in this embodiment, the electronic device may be located in at least one network device of a plurality of network devices of a computer network.
Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:
s1, obtaining a removal instruction initiated by the target client, wherein the removal instruction is used for indicating that the target device is removed from the target device group;
s2, responding to the removal instruction, and determining scene management maps corresponding to the application scenes where the target equipment is located;
s3, under the condition that the management state of each scene management map is a non-use state, hiding the equipment identification of the target equipment in each scene management map, updating the scene management map to obtain an updated scene management map, wherein the updated scene management map comprises a first-class scene management map and a second-class scene management map;
and S4, adjusting the management state of the first-class scene management map to be an enabling state.
Alternatively, it can be understood by those skilled in the art that the structure shown in fig. 9 is only an illustration, and the electronic device may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palmtop computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 9 is a diagram illustrating a structure of the electronic device. For example, the electronics may also include more or fewer components (e.g., network interfaces, etc.) than shown in FIG. 9, or have a different configuration than shown in FIG. 9.
The memory 902 may be used to store software programs and modules, such as program instructions/modules corresponding to the device management method and apparatus in the embodiments of the present invention, and the processor 904 executes various functional applications and data processing by running the software programs and modules stored in the memory 902, so as to implement the device management method described above. The memory 902 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 902 may further include memory located remotely from the processor 904, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. The storage 902 may be specifically, but not limited to, used for storing information such as sample characteristics of the item and the target virtual resource account number. As an example, the electronic device may be configured as shown in FIG. 10, which includes a memory 1002, a processor 1004, a transmission 1006, a display 1008, and a connection bus 1010.
Optionally, the memory 1002 may include, but is not limited to, the obtaining module 802, the determining module 804, the processing module 806, and the adjusting module 808 in the device management apparatus. In addition, the device management apparatus may further include, but is not limited to, other module units in the device management apparatus, which is not described in this example again.
Optionally, the above-mentioned transmission device 1006 is used for receiving or sending data via a network. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 1006 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices so as to communicate with the internet or a local area Network. In one example, the transmission device 1006 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
In addition, the electronic device further includes: a display 1008 for displaying the information of the order to be processed; and a connection bus 1010 for connecting the respective module parts in the above-described electronic apparatus.
In other embodiments, the terminal device or the server may be a node in a distributed system, where the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting a plurality of nodes through a network communication. Nodes can form a Peer-To-Peer (P2P, Peer To Peer) network, and any type of computing device, such as a server, a terminal, and other electronic devices, can become a node in the blockchain system by joining the Peer-To-Peer network.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the device management method provided in the various alternative implementations of the device management aspect described above. Wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
Alternatively, in the present embodiment, the above-mentioned computer-readable storage medium may be configured to store a computer program for executing the steps of:
s1, obtaining a removal instruction initiated by the target client, wherein the removal instruction is used for indicating that the target device is removed from the target device group;
s2, responding to the removal instruction, and determining scene management maps corresponding to the application scenes where the target equipment is located;
s3, under the condition that the management state of each scene management map is a non-use state, hiding the equipment identification of the target equipment in each scene management map, updating the scene management map to obtain an updated scene management map, wherein the updated scene management map comprises a first-class scene management map and a second-class scene management map;
and S4, adjusting the management state of the first-class scene management map to be an enabling state.
Alternatively, in this embodiment, a person skilled in the art may understand that all or part of the steps in the methods of the foregoing embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.
In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and 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 units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A device management method, comprising:
obtaining a removal instruction initiated by a target client, wherein the removal instruction is used for indicating that a target device is removed from a target device group;
responding to the removal instruction, and determining scene management maps corresponding to a plurality of application scenes where the target equipment is located;
hiding the equipment identifier of the target equipment in each scene management map and updating the scene management map to obtain an updated scene management map under the condition that the management state of each scene management map is a non-use state, wherein the updated scene management map comprises a first class of scene management map and a second class of scene management map, the first class of scene management map comprises a management control relationship of which the relationship label is indicated as an effective label, and the relationship labels of the management control relationship in the second class of scene management map are indicated as failure labels;
and adjusting the management state of the first-class scene management map to be an enabling state.
2. The method of claim 1, wherein the updating the scene management map, and obtaining the updated scene management map comprises:
acquiring a relationship label of a management control relationship among devices in the scene management map;
adjusting a relationship label of a management control relationship directly associated with the target device in the scene management map to be a failure label so as to obtain an updated scene management map;
for the updated scene management map, determining the scene management map as the first class scene management map under the condition that the scene management map comprises the management control relationship of which the relationship label indicates the effective label; determining the scene management map as the second type scene management map when the relationship labels of the management control relationship in the scene management map are all indicated as failure labels.
3. The method according to claim 1, wherein the determining, in response to the removal instruction, a scene management map corresponding to each of a plurality of application scenes in which the target device is located comprises:
responding to the removal instruction, and acquiring the equipment identifier of the target equipment;
and determining scene management maps corresponding to the application scenes matched with the equipment identifications from the scene management map set corresponding to the target equipment group.
4. The method of claim 1, wherein prior to obtaining the target client initiated release instruction, the method further comprises:
receiving a dismissal operation in the target client;
and generating the release instruction in response to the release operation, wherein the release instruction is used for indicating to delete the binding relationship between the target device and the target device group.
5. The method according to claim 1, wherein when the management status of the first class of scene management graph is adjusted to an enabled status, the method further comprises:
determining the original management state of each scene management map in the first class of scene management maps;
and keeping the shutdown state of the scene management map with the original management state as the shutdown state.
6. The method according to claim 1, further comprising, after said updating the scene management map to obtain the updated scene management map:
acquiring a binding instruction initiated by the target client, wherein the binding instruction is used for indicating that the target equipment is added again in the target equipment group;
responding to the binding instruction, and determining scene management maps corresponding to a plurality of application scenes where the target equipment is located;
and under the condition that the management state of each scene management map is a non-use state, displaying the equipment identification of the target equipment in each hidden scene management map, and recovering the scene management map to obtain the recovered scene management map.
7. An apparatus for managing devices, comprising:
the device comprises an acquisition module, a sending module and a processing module, wherein the acquisition module is used for acquiring a removal instruction initiated by a target client, and the removal instruction is used for indicating that target equipment is removed from a target equipment group;
a determining module, configured to determine, in response to the removal instruction, a scene management map corresponding to each of a plurality of application scenes where the target device is located;
the processing module is configured to hide the device identifier of the target device in each scene management map and update the scene management map to obtain an updated scene management map when the management state of each scene management map is a disabled state, where the updated scene management map includes a first-class scene management map and a second-class scene management map, the first-class scene management map includes a management control relationship in which a relationship label is indicated as an effective label, and the relationship labels of the management control relationship in the second-class scene management map are all indicated as failed labels;
and the adjusting module is used for adjusting the management state of the first type of scene management map into an enabling state.
8. The apparatus of claim 7, further comprising:
the obtaining module is further configured to obtain a binding instruction initiated by the target client, where the binding instruction is used to instruct to add the target device in the target device group again;
the determining module is further configured to determine, in response to the binding instruction, a scene management map corresponding to each of the plurality of application scenes where the target device is located;
the processing module is further configured to, when the management state of each scene management map is a disabled state, display the device identifier of the target device in each hidden scene management map, and recover the scene management map to obtain the recovered scene management map.
9. A computer-readable storage medium, comprising a stored program, wherein the program when executed performs the method of any of claims 1 to 6.
10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 6 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003602.4A CN112163125A (en) | 2020-09-22 | 2020-09-22 | Device management method and apparatus, storage medium, and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003602.4A CN112163125A (en) | 2020-09-22 | 2020-09-22 | Device management method and apparatus, storage medium, and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112163125A true CN112163125A (en) | 2021-01-01 |
Family
ID=73862645
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011003602.4A Pending CN112163125A (en) | 2020-09-22 | 2020-09-22 | Device management method and apparatus, storage medium, and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112163125A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115913806A (en) * | 2021-08-17 | 2023-04-04 | 青岛海尔科技有限公司 | Edge scene adjusting method and device, storage medium and electronic device |
Citations (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040110530A1 (en) * | 2002-08-21 | 2004-06-10 | Alone Vijay B. | Wireless network connection system and method |
| CN1881917A (en) * | 2005-06-13 | 2006-12-20 | 海尔集团公司 | Household network wireless netting and communication method |
| CN102891786A (en) * | 2012-09-21 | 2013-01-23 | 兴泓昇(福州)智能科技有限公司 | Automatically-correlated scene control networking method of intelligent home system |
| US20140068089A1 (en) * | 2012-08-31 | 2014-03-06 | Nxp B.V. | Method of establishing control relationships, configuration device, networked device and computer program product |
| CN104808501A (en) * | 2015-03-31 | 2015-07-29 | 小米科技有限责任公司 | Intelligent scene deleting method and device |
| CN104932456A (en) * | 2015-04-27 | 2015-09-23 | 小米科技有限责任公司 | Intelligent scene realizing method and device, intelligent terminal and controller |
| CN104992542A (en) * | 2015-07-01 | 2015-10-21 | 慧锐通智能科技股份有限公司 | Configuration method and system for intelligent home equipment |
| US20160285644A1 (en) * | 2015-03-24 | 2016-09-29 | Lenovo (Beijing) Co., Ltd. | Device and Method for Smart Home |
| US20170085499A1 (en) * | 2015-09-17 | 2017-03-23 | Xiaomi Inc. | Method and device for removing a control relationship between a user account and a device |
| CN106789488A (en) * | 2017-03-29 | 2017-05-31 | 海信集团有限公司 | Intelligent home device management method and device |
| CN106972958A (en) * | 2017-03-13 | 2017-07-21 | 海信集团有限公司 | Gateway device collocation method, apparatus and system |
| CN107341389A (en) * | 2017-06-26 | 2017-11-10 | 北京洋浦伟业科技发展有限公司 | The method and device for preventing equipment to be multiplexed |
| CN108923969A (en) * | 2018-06-29 | 2018-11-30 | 海尔优家智能科技（北京）有限公司 | A kind of method, apparatus of equipment linkage, equipment and computer readable storage medium |
| CN109587018A (en) * | 2018-12-06 | 2019-04-05 | 深圳绿米联创科技有限公司 | Method, apparatus, network system and the mobile terminal of device configuration |
| CN110401583A (en) * | 2019-06-21 | 2019-11-01 | 深圳绿米联创科技有限公司 | Method, apparatus, system, mobile terminal and the storage medium of equipment replacement |
| CN110868719A (en) * | 2018-08-27 | 2020-03-06 | 中国电信股份有限公司 | Access management system, device and method |
| US20200084117A1 (en) * | 2018-09-11 | 2020-03-12 | Apple Inc. | User interfaces for controlling or presenting information about multiple cellular identifiers on an electronic device |
| CN111176517A (en) * | 2019-12-31 | 2020-05-19 | 青岛海尔科技有限公司 | Method and device for setting scene and mobile phone |
| US20200186985A1 (en) * | 2018-12-07 | 2020-06-11 | Samsung Electronics Co., Ltd. | Method and apparatus for pairing iot devices and iot service in heterogeneous iot ecosystem |
| US20200228536A1 (en) * | 2017-09-30 | 2020-07-16 | Gree Electric Appliances(Wuhan) Co.,Ltd | Method and Device for Sharing Control Rights of Appliances, Storage Medium, and Server |
| CN111474860A (en) * | 2020-04-07 | 2020-07-31 | 广东科徕尼智能科技有限公司 | Processing method and device based on failure intelligent scene and storage medium |
| CN111541593A (en) * | 2020-04-16 | 2020-08-14 | 杭州鸿雁电器有限公司 | Home management method, home management system and computer readable storage medium |
-
2020
- 2020-09-22 CN CN202011003602.4A patent/CN112163125A/en active Pending
Patent Citations (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040110530A1 (en) * | 2002-08-21 | 2004-06-10 | Alone Vijay B. | Wireless network connection system and method |
| CN1881917A (en) * | 2005-06-13 | 2006-12-20 | 海尔集团公司 | Household network wireless netting and communication method |
| US20140068089A1 (en) * | 2012-08-31 | 2014-03-06 | Nxp B.V. | Method of establishing control relationships, configuration device, networked device and computer program product |
| CN102891786A (en) * | 2012-09-21 | 2013-01-23 | 兴泓昇(福州)智能科技有限公司 | Automatically-correlated scene control networking method of intelligent home system |
| US20160285644A1 (en) * | 2015-03-24 | 2016-09-29 | Lenovo (Beijing) Co., Ltd. | Device and Method for Smart Home |
| CN104808501A (en) * | 2015-03-31 | 2015-07-29 | 小米科技有限责任公司 | Intelligent scene deleting method and device |
| US20160294574A1 (en) * | 2015-03-31 | 2016-10-06 | Xiaomi Inc. | Method and device for deleting smart scene |
| CN104932456A (en) * | 2015-04-27 | 2015-09-23 | 小米科技有限责任公司 | Intelligent scene realizing method and device, intelligent terminal and controller |
| CN104992542A (en) * | 2015-07-01 | 2015-10-21 | 慧锐通智能科技股份有限公司 | Configuration method and system for intelligent home equipment |
| US20170085499A1 (en) * | 2015-09-17 | 2017-03-23 | Xiaomi Inc. | Method and device for removing a control relationship between a user account and a device |
| CN106972958A (en) * | 2017-03-13 | 2017-07-21 | 海信集团有限公司 | Gateway device collocation method, apparatus and system |
| CN106789488A (en) * | 2017-03-29 | 2017-05-31 | 海信集团有限公司 | Intelligent home device management method and device |
| CN107341389A (en) * | 2017-06-26 | 2017-11-10 | 北京洋浦伟业科技发展有限公司 | The method and device for preventing equipment to be multiplexed |
| US20200228536A1 (en) * | 2017-09-30 | 2020-07-16 | Gree Electric Appliances(Wuhan) Co.,Ltd | Method and Device for Sharing Control Rights of Appliances, Storage Medium, and Server |
| CN108923969A (en) * | 2018-06-29 | 2018-11-30 | 海尔优家智能科技（北京）有限公司 | A kind of method, apparatus of equipment linkage, equipment and computer readable storage medium |
| CN110868719A (en) * | 2018-08-27 | 2020-03-06 | 中国电信股份有限公司 | Access management system, device and method |
| US20200084117A1 (en) * | 2018-09-11 | 2020-03-12 | Apple Inc. | User interfaces for controlling or presenting information about multiple cellular identifiers on an electronic device |
| CN109587018A (en) * | 2018-12-06 | 2019-04-05 | 深圳绿米联创科技有限公司 | Method, apparatus, network system and the mobile terminal of device configuration |
| US20200186985A1 (en) * | 2018-12-07 | 2020-06-11 | Samsung Electronics Co., Ltd. | Method and apparatus for pairing iot devices and iot service in heterogeneous iot ecosystem |
| CN110401583A (en) * | 2019-06-21 | 2019-11-01 | 深圳绿米联创科技有限公司 | Method, apparatus, system, mobile terminal and the storage medium of equipment replacement |
| CN111176517A (en) * | 2019-12-31 | 2020-05-19 | 青岛海尔科技有限公司 | Method and device for setting scene and mobile phone |
| CN111474860A (en) * | 2020-04-07 | 2020-07-31 | 广东科徕尼智能科技有限公司 | Processing method and device based on failure intelligent scene and storage medium |
| CN111541593A (en) * | 2020-04-16 | 2020-08-14 | 杭州鸿雁电器有限公司 | Home management method, home management system and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115913806A (en) * | 2021-08-17 | 2023-04-04 | 青岛海尔科技有限公司 | Edge scene adjusting method and device, storage medium and electronic device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108040108B (en) | Communication switching method, device, coordination server and readable storage medium | |
| CN108038114B (en) | Path query method, terminal and computer readable storage medium | |
| CN112737899B (en) | Intelligent device management method and device, storage medium and electronic device | |
| CN103678319B (en) | Resource file update method, device and system and server | |
| CN102129378B (en) | A kind of software menu updating method and device | |
| KR102288521B1 (en) | Apparatus and method for storing data based on blockchain | |
| EP2575322B1 (en) | Method, user equipment, server, and device for sharing information | |
| CN103152398A (en) | Method and system for file synchronization among multiple terminal files | |
| CN103312489A (en) | Method and device for synchronizing terminal and server | |
| CN102646041A (en) | Software installation method and system | |
| CN102521390B (en) | Database management and monitoring system based on pin function | |
| CN107632872B (en) | Desktop layout processing method, user data processing method and device and computer storage medium | |
| CN111142885B (en) | eSIM equipment management method, device, equipment and storage medium | |
| CN102752215A (en) | Processing method for VDP (vertical data processing) request messages and edge switch | |
| CN111930565A (en) | Process fault self-healing method, device and equipment for components in distributed management system | |
| CN103701653A (en) | Processing method for interface hot plugging and unplugging configuration data and network configuration server | |
| CN104468947A (en) | Information processing method and electronic equipment | |
| WO2021087892A1 (en) | Resource subscription method and device, and storage medium | |
| CN112163125A (en) | Device management method and apparatus, storage medium, and electronic device | |
| CN110958287B (en) | Operation object data synchronization method, device and system | |
| CN105577734A (en) | Information backup method, device, server and terminal | |
| CN114281555A (en) | Application state synchronization method and device, electronic equipment and storage medium | |
| CN104426918A (en) | Device setting method and electronic device | |
| CN113434190B (en) | Data processing method and device, storage medium and electronic equipment | |
| CN114390485A (en) | Data transmission method and electronic equipment |
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 |