Equipment data processing method and device, electronic equipment and readable storage medium

Abstract

The invention provides an equipment data processing method and device, electronic equipment and a readable storage medium, and is applied to the technical field of equipment data processing. The method comprises the following steps: when a communication state between management equipment and instruction sending equipment is switched from disconnection to reconnection, sending a management equipment identifier to the instruction sending equipment, so that the instruction sending equipment obtains a data deletion instruction corresponding to the management equipment identifier from a data deletion instruction list according to the management equipment identifier, and sends the data deletion instruction to the management equipment; the data deletion instruction is sent to the management equipment; obtaining a device type of a to-be-deleted device carried by the data deletion instruction; and acquiring a data deletion strategy corresponding to the equipment type, and deleting local data of the to-be-deleted equipment according to the data deletion strategy. According to the method, the local data of the to-be-deleted equipment can be deleted while the equipment is deleted, and equipment data leakage is prevented.

Description

Technical Field

[0001] The present application belongs to the technical field of device data processing, and specifically relates to a device data processing method, apparatus, electronic device and readable storage medium. Background Art

[0002] The Internet of Things system includes at least one device, for example, it may include home appliances such as air conditioners, fans, refrigerators, etc. that are connected to the Internet of Things system. The relevant data of these home appliances can be stored in the cloud.

[0003] In the related art, when deleting a device, it is usually necessary to delete the relevant data of the device from the cloud. However, this processing method may cause incomplete data deletion, resulting in the leakage of user information. Summary of the invention

[0004] The present application aims to provide a device data processing method, apparatus, electronic device and readable storage medium, which at least solves the problem that the device data processing method in the prior art is difficult to completely delete data when deleting the device, which easily leads to user information leakage.

[0005] In a first aspect, an embodiment of the present application discloses a device data processing method, which is applied to manage devices, and the method includes:

[0006] When the communication state between the management device and the instruction sending device switches from disconnection to reconnection, sending a management device identifier to the instruction sending device, so that the instruction sending device obtains a data deletion instruction corresponding to the management device identifier from a data deletion instruction list according to the management device identifier, and sends the data deletion instruction to the management device;

[0007] Obtaining the device type of the device to be deleted carried by the data deletion instruction;

[0008] A data deletion policy corresponding to the device type is obtained, and local data of the device to be deleted is deleted according to the data deletion policy.

[0009] In a second aspect, an embodiment of the present application discloses a device data processing method, which is applied to an instruction sending device, and the method includes:

[0010] receiving a management device identifier sent by a management device; the management device identifier is sent when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection;

[0011] According to the management device identifier, a data deletion instruction corresponding to the management device identifier is obtained from the data deletion instruction list, and the data deletion instruction is sent to the management device, so that the management device obtains the device type of the device to be deleted carried by the data deletion instruction, obtains the data deletion policy corresponding to the device type, and deletes the local data of the device to be deleted according to the data deletion policy.

[0012] In a third aspect, an embodiment of the present application discloses a device data processing apparatus, which is applied to manage devices, and the apparatus includes:

[0013] A first sending module, configured to send a management device identifier to the instruction sending device when the communication state between the management device and the instruction sending device switches from disconnection to reconnection, so that the instruction sending device can obtain a data deletion instruction corresponding to the management device identifier from a data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device;

[0014] A first acquisition module, used to acquire the device type of the device to be deleted carried by the data deletion instruction;

[0015] The second acquisition module is used to acquire a data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

[0016] In a fourth aspect, an embodiment of the present application further discloses a device data processing apparatus, which is applied to an instruction sending device, and the method includes:

[0017] A first receiving module, configured to receive a management device identifier sent by a management device; the management device identifier is sent when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection;

[0018] The third acquisition module is used to obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device, so that the management device can obtain the device type of the device to be deleted carried by the data deletion instruction, obtain the data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

[0019] In a fifth aspect, an embodiment of the present application further discloses an electronic device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0020] In a sixth aspect, an embodiment of the present application further discloses a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0021] In summary, in this embodiment, the management device obtains the data deletion instruction sent by the instruction sending device, and obtains the device type of the device to be deleted carried in the data deletion instruction, and deletes the local data of the device to be deleted according to the data deletion policy corresponding to the device type and according to the data deletion policy, thereby achieving the effect of deleting the local data of the device to be deleted when deleting the device to be deleted, avoiding the leakage of user data in the device, and achieving the effect of protecting user privacy and security. In addition, when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection, the management device identifier is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device. Therefore, even after the communication connection between the management device and the instruction sending device is disconnected, the data deletion instruction sent by the instruction sending device can be obtained in time after reconnection, so as to delete the local data of the device to be deleted in time based on the data deletion instruction, so as to avoid the leakage of user information and protect the privacy and security of users. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In the attached picture:

[0023] Figure 1 is a flowchart of a method for processing device data provided by an embodiment of the present application;

[0024] Figure 2 It is a structural diagram of a device data processing system provided in an embodiment of the present application;

[0025] Figure 3 is a flowchart of a method for processing device data provided by an embodiment of the present application;

[0026] Figure 4 is a flowchart of a method for processing device data provided by an embodiment of the present application;

[0027] Figure 5 is a flow chart of interaction steps of another device data processing method provided in an embodiment of the present application;

[0028] Figure 6 is a block diagram of another device data processing apparatus provided in an embodiment of the present application;

[0029] Figure 7is a block diagram of another device data processing apparatus provided in an embodiment of the present application;

[0030] Figure 8 is a block diagram of an electronic device according to an embodiment of the present application;

[0031] Fig. 9 It is a block diagram of an electronic device of another embodiment provided by the embodiments of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0033] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0034] Figure 1 This is a device data processing method provided by this embodiment, refer to Figure 1 , the method may include the following steps:

[0035] Step 101, when the communication state between the management device and the instruction sending device switches from disconnection to reconnection, the management device identifier is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device.

[0036] Furthermore, when the communication state between the management device and the instruction sending device has not changed and the communication connection with the instruction sending device has not been disconnected, the management device directly receives the data deletion instruction sent by the instruction sending device.

[0037] For example, if the instruction sending device sends a device data deletion instruction to the management device, and within a preset time period, no response to the device data deletion instruction fed back by the management device is received, it is determined that the communication state between the management device and the instruction sending device is disconnected. If after determining that the communication is disconnected, the device information reported by the management device is received, it is determined that the communication state between the management device and the instruction sending device is switched from disconnected to reconnected. The device information may include the networking information of the management device and the management device identifier of the management device.

[0038] The instruction sending device is a device that is connected to the terminal device in communication and can receive the device data deletion instruction sent by the terminal device. The instruction sending device can be a physical server, a cloud server, or other devices.

[0039] The management device is a device that is connected to the instruction sending device and is connected to at least one device to be deleted, and is used to manage the device to be deleted. The device to be deleted is a device registered in the IoT system where the management device is located. For example, the management device can be a host device that has devices that can connect to various protocols and has the ability to store and calculate data locally.

[0040] For example, refer to Figure 2 , the management device is the host, the instruction sending device is the server, the device to be deleted can be a CAN device or 485 device connected to the host through the Controller Area Network bus (CAN, Controller Area Network) and 485 bus, a Mesh device connected to the host through the Mesh mode, and a WiFi and BLE device connected to the host through WiFi Bluetooth (Wireless Fidelity Bluetooth Low Energy, WiFi BLE). In addition, the device to be deleted can also be a third-party Bluetooth device (not shown in the figure), or other devices that can communicate with the host. Among them, the WiFI Bluetooth device can be a device equipped with a WiFi Bluetooth module, such as an air conditioner equipped with a WiFi Bluetooth module.

[0041] Further, see Figure 2 The client sends a device deletion instruction (Delete instruction) to the server through the application (Application, APP). Based on the Delete instruction, the server forwards the Delete instruction to the host. Based on the received Delete instruction, the host sends a Reset instruction to the Mesh device, WiFi and BLE device, and removes the device information of the CAN device or 485 device from the registration list.

[0042] Among them, when the WiFi and BLE devices do not receive the Reset command sent by the host and recover from the state of being disconnected from the host to the state of being reconnected to the host, the host can resend the Reset command to them, or the server can resend the Reset command to them.

[0043] The data deletion instruction list is a list generated by the instruction sending device, and is used to store a list of instruction execution completion instructions that have been sent by the instruction sending device but have not been received from the management device within a preset time period.

[0044] Furthermore, the data deletion instruction list includes the data deletion instruction and the management device identifier of the management device that needs to receive the data deletion instruction.

[0045] When the management device is powered off or disconnected from the network, the communication state between the management device and the instruction sending device is disconnected. The disconnection may include the management device disconnecting from the external network or disconnecting from the router. For example, when the router is powered off, the management device will be disconnected from the network.

[0046] When the management device is powered off or disconnected from the network, it cannot accept the data deletion command sent by the command sending device. After the management device is powered on and restarted or reconnected to the network, the management device can actively send the management device identifier to the command sending device to trigger the command sending device to re-send the device data deletion command.

[0047] For example, the instruction sending device is a message queuing telemetry transport (MQTT) server, the terminal device is a client device, and the management device is a host. The client device sends a device data deletion instruction to delete the device to be deleted to the MQTT server through an application, and the MQTT server sends the device data deletion instruction to the host.

[0048] If the host receives the device data deletion instruction, it returns a response of receiving the device data deletion instruction to the MQTT server and executes the device data deletion instruction.

[0049] If the MQTT server does not receive a response from the host within the preset time period, it is determined that the communication connection between the host and the MQTT server is disconnected. After the host is reconnected to the network, it will report the network status information. After receiving the information, the MQTT server determines that the host has switched from the disconnected state to the connected state. The MQTT server searches the data deletion instruction list to see if there is a data deletion instruction corresponding to the host's management device identifier. If so, it means that the data deletion instruction was not sent successfully. In this case, the data deletion instruction is resent to ensure that the host can receive and execute the data deletion instruction.

[0050] Step 102: Obtain the device type of the device to be deleted carried in the data deletion instruction.

[0051] The device type may be a wired communication device or a wireless communication device.

[0052] Furthermore, the wired communication device may include a CAN device or a 485 device, which is a device connected to the management device via a CAN bus or a 485 bus, such as a central air conditioner, floor heating, etc. The wired communication device does not record data, but only executes received instructions.

[0053] Wireless communication devices may include WiFI Bluetooth devices that access management devices via WiFI and BLE. Specifically, such devices connect to management devices (e.g., home hosts) via WiFI, and BLE devices send and receive Bluetooth scene commands. Such devices may be air purifiers, fans, refrigerators, washing machines, and other devices. Such devices may receive specific control commands, record and set commands, and trigger execution and setting actions by executing commands.

[0054] Wireless communication devices may also include smart device items that access management devices through GMesh. Such devices are connected to management devices (e.g., home hosts) through GMesh, and typically include smart switches, scenario switches, sensors and other devices.

[0055] Wireless communication devices may also include third-party devices that access management devices via WiFI and IP. Such devices connect to management devices (e.g., home hosts) via WiFi and IP. They are usually Bluetooth Mesh devices with third-party gateways attached. For example, they may be lighting devices. The control protocols of third-party devices are different. They do not record the setting instructions of management devices. Instead, they convert control instructions through management devices and then send them to third-party gateways, which then send them to such devices.

[0056] Step 103: Obtain a data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

[0057] For example, the data deletion policy corresponding to the device type is obtained, and a device reset (Reset) instruction is sent to the device under test according to the data deletion policy. The device under test receives the Reset instruction and replies to the home host, and then resets the device according to the Reset instruction. After receiving the device reply, the management device removes the device to be deleted from the device registration list. In this way, the local data of the device under test is deleted.

[0058] For example, if the device type of the device to be tested is a wireless communication device, the data deletion strategy is: broadcasting a data deletion instruction for the device to be deleted to delete the local data of the device to be tested. In addition, the deletion strategy may also include: deleting the device information of the device to be tested from the device registration list.

[0059] For example, if the device type of the device to be tested is a wired communication device, the data deletion policy is: deleting the device information of the device to be tested from the device registration list.

[0060] For example, the management device is the host, and the instruction sending device is the MQTT server. The MQTT server receives the client's instruction to delete the device to be deleted from the host, and sends the device data deletion (Delete) instruction to the host. If the communication connection between the host and the MQTT server is disconnected, the host cannot receive the device data deletion instruction. After the host is reconnected to the network, the subscription is refreshed, and the host's management device identifier is sent to the MQTT server, triggering the MQTT server to re-issue the data deletion instruction. After receiving the data deletion instruction, the host determines the data deletion policy based on the device type in the instruction, and sends the data deletion instruction to the device to be deleted according to the instruction distribution logic described by the data deletion policy.

[0061] With the continuous development of the Internet of Things, the number of smart home appliances that can be connected to the Internet of Things in the home has also increased. In related technologies, when deleting a home appliance from the Internet of Things, only the cloud data of the device is deleted, while the data in the entire device is still retained, which will lead to user privacy leakage.

[0062] In this embodiment, the management device obtains the data deletion instruction sent by the instruction sending device, and obtains the device type of the device to be deleted carried in the data deletion instruction, and deletes the local data of the device to be deleted according to the data deletion policy corresponding to the device type and the data deletion policy, thereby achieving the effect of deleting the local data of the device to be deleted when deleting the device to be deleted, avoiding the leakage of user data in the device, and achieving the effect of protecting user privacy and security. In addition, when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection, the management device identifier is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device. Therefore, even after the communication connection between the management device and the instruction sending device is disconnected, the data deletion instruction sent by the instruction sending device can be obtained in time after reconnection, so as to delete the local data of the device to be deleted in time based on the data deletion instruction, so as to avoid the leakage of user information and protect the privacy and security of the user.

[0063] Reference Figure 3 The device data processing method of the present application may include the following steps:

[0064] Step 201, when the communication state between the management device and the instruction sending device switches from disconnection to reconnection, the management device identifier is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device.

[0065] Furthermore, when the communication state between the management device and the instruction sending device has not changed and the communication connection with the instruction sending device has not been disconnected, the management device directly receives the data deletion instruction sent by the instruction sending device.

[0066] The method of this step has been described in the aforementioned step 101 and will not be repeated here.

[0067] Step 202: Obtain the device type of the device to be deleted carried in the data deletion instruction.

[0068] After obtaining the device type, a data deletion policy is determined according to the device type. If the device type of the device to be tested is a wireless communication device, the data deletion policy is: broadcast a data deletion instruction so that the device to be deleted can delete the local data of the device to be tested.

[0069] Specifically, when the device type is a wireless communication device, after step 202, the following steps may also be included:

[0070] Step 203: broadcast a device reset instruction, so that the device to be deleted receives and executes the broadcasted device reset instruction.

[0071] For example, when the wireless communication device is a WiFi and BLE device, the management device broadcasts the device reset instruction through the Open Systems Interconnection Protocol (UDP) broadcast; when the wireless communication device is a GMesh device, the management device broadcasts the device reset instruction through the Mesh broadcast.

[0072] For example, the management device is the host, the command sending device is the MQTT server, the client deletes the WiFi device under the host, and the MQTT server sends the Delete command to the host and the WiFi device. Due to the abnormality of the device, the command cannot be received. If the host receives the command at this time, the host synchronizes the UDP broadcast device Reset command. At the same time, when the device reconnects to the network and refreshes the subscription, it triggers the server to resend the Reset command. If the device receives a resolvable command, it enters the reset state. If it receives an unresolvable command, it will not execute it. Among them, whether the command is resolvable refers to whether the device under test can parse the encrypted device data deletion command after receiving it encrypted by the private protocol of the management device manufacturer.

[0073] Among them, the device to be deleted generates a public-private key pair when it registers on the network. The public key is recorded in the embedded software of the management device and is used to parse the peripheral information of the device data deletion instruction. The public key cannot be deleted. The private key is generated when the device to be deleted is connected to the network and stored locally on the device to be deleted. It is used to parse the specific action instructions of the device to be deleted. After the device to be deleted is deleted, the private key stored in it will also be deleted. After the private key is deleted, if the device to be deleted receives the previous device data deletion instruction again, the device to be deleted cannot parse the instruction.

[0074] For example, step 203 may include the following sub-steps:

[0075] Sub-step 2031, encrypting the device reset instruction through the public key to obtain the encryption device reset instruction.

[0076] When the device to be deleted is registered on the network, the management device generates a public-private key pair, records the public key in the embedded software of the management device, and sends the private key to the device to be deleted, which is stored locally on the device.

[0077] Sub-step 2032, broadcasting the encrypted device reset instruction so that the device to be deleted receives the encrypted device reset instruction, decrypts the encrypted device reset instruction using the private key, obtains the decrypted device reset instruction and executes it.

[0078] Among them, the private key is generated and stored locally on the device to be deleted when the device to be deleted is registered on the network, and is deleted locally from the device to be deleted after the device to be deleted is deleted.

[0079] Specifically, the device to be deleted obtains and stores a private key when registering on the network. Based on the stored private key, the encrypted device data deletion instruction sent by the management device can be decrypted, thereby realizing the parsing of the device data deletion instruction. After the device to be deleted is deleted, the old private key stored therein will be deleted together. After the device to be deleted is registered on the network again, it will receive a new private key. After the device to be deleted is deleted and re-registered on the network, if it receives an encrypted device data deletion instruction generated by the management device before the device is deleted, because the device to be deleted has deleted the previous old key, the new key is now stored in the device to be tested. The encrypted device data deletion instruction cannot be parsed based on the new key, and the device data deletion instruction cannot be executed.

[0080] Based on the method of this embodiment, the device to be deleted needs to decrypt the encrypted device data deletion instruction based on the private key generated when registering with the network, and the private key will be updated after the device is deleted and re-enters the network. If the device to be deleted has executed the device data deletion instruction and re-enters the network, the management device is still broadcasting the previously generated device data deletion instruction. The device to be deleted cannot parse the old device data deletion instruction based on the new private key, so it will not execute the executed device data deletion instruction again, avoiding the accidental deletion of the device to be deleted.

[0081] For example, the wireless communication device may be a Bluetooth Mesh device that is powered off, the client deletes the Bluetooth Mesh device under the host, the MQTT server sends a Delete command to the host, and the host broadcasts a Reset command to the device through the Mesh broadcast.

[0082] Step 204: Obtain a list of registered devices stored locally on the management device, and delete device information of the device to be deleted from the list of registered devices.

[0083] The registered device list is used to store the device information of the registered devices.

[0084] When the device to be deleted is registered in the network, its device information is stored in the registered device list. When the device to be deleted is deleted, the device information of the device to be deleted is deleted from the registered device list. In this way, the device information of the device to be deleted can be prevented from being retained in the registered device list after the device is deleted, thereby avoiding device information leakage.

[0085] For example, step 204 may include the following sub-steps:

[0086] Sub-step 2041: if a device reset instruction reception response is received from the device to be deleted within a preset time period, the device information of the device to be deleted is deleted from the registered device list.

[0087] After receiving the device reset instruction, the device to be deleted will send a reset instruction reception response to the management device. If the device reset instruction reception response is received from the device to be deleted within the preset time period, it means that the communication between the management device and the device to be deleted is normal, and the device to be deleted has received the device data deletion instruction normally.

[0088] In sub-step 2042, if no device reset instruction reception response is received from the device to be deleted within a preset time period, the device status information of the device to be deleted is obtained, and when the device status information switches from a state of disconnection and device connection management to a state of restoration and device connection management, the device reset instruction is resent.

[0089] If no response to the device reset instruction is received from the device to be deleted within the preset time period, it indicates that there is an abnormality in the communication between the device to be deleted and the management device. It is necessary to resend the device reset instruction when the device to be deleted is switched from a disconnected state to a restored state to a connected state. Thus, the successful deletion of the device to be deleted can be ensured based on this instruction.

[0090] For example, after the wireless device to be deleted disconnects the communication connection with the management device, the management device can send an information reporting instruction to the wireless device to be deleted at a set time interval, notifying the wireless device to report the networking status and device identification. If the information reported by the wireless device is received, it is determined that the wireless device is in a state of disconnecting the communication connection with the management device, and switches to a state of restoring the communication connection with the management device.

[0091] In the case where the device type is a wired communication device, after step 202, the following steps may also be included:

[0092] Step 205: Obtain a list of registered devices stored locally on the management device.

[0093] The registered device list is used to store device information of registered devices.

[0094] For example, the wired communication device may be a device connected to the host via CAN or 485.

[0095] Step 206: Delete the device information of the device to be deleted from the registered device list.

[0096] For example, the wired communication device can be a device connected to the host through CAN or 485, the management device is the host, and the instruction sending device is the MQTT server. After the client sends a Delete command to delete the CAN or 485 device under the host to the server, the MQTT server forwards the Delete command to the host, and the host responds to the command and removes the CAN or 485 device from the registered device list.

[0097] The communication bandwidth of CAN or 485 devices is small, the internal data storage space of the whole device is small, it is unable to receive and parse large data packets, and there is no private key mechanism. Therefore, after the device to be deleted is a CAN or 485 device, the device needs to be removed from the device registration list.

[0098] For example, when the device to be deleted is a wireless device, after the wireless device is reset, the wireless device may be deleted from the device registration list, or may not be deleted.

[0099] For example, the method of this embodiment can be applied to an instruction sending device. Figure 4 , the method may include the following steps:

[0100] Step 301: Receive a management device identifier sent by a management device.

[0101] The management device identifier is sent when the communication state between the management device and the instruction sending device switches from disconnection to reconnection.

[0102] The management device identifier may be a name, number, or other identifier of the management device.

[0103] Step 302, according to the management device identifier, obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list, and send the data deletion instruction to the management device, so that the management device can obtain the device type of the device to be deleted carried by the data deletion instruction, obtain the data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

[0104] The management device obtains the data deletion instruction sent by the instruction sending device, and obtains the device type of the device to be deleted carried in the data deletion instruction, and deletes the local data of the device to be deleted according to the data deletion policy corresponding to the device type and the data deletion policy, thereby achieving the effect of deleting the local data of the device to be deleted when deleting the device to be deleted, avoiding the leakage of user data in the device, and achieving the effect of protecting the privacy and security of the user. In addition, when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection, the management device identification is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identification from the data deletion instruction list according to the management device identification, and send the data deletion instruction to the management device. Therefore, even after the communication connection between the management device and the instruction sending device is disconnected, the data deletion instruction sent by the instruction sending device can be obtained in time after reconnection, so as to delete the local data of the device to be deleted in time based on the data deletion instruction, so as to avoid the leakage of user information and protect the privacy and security of the user.

[0105] For example, before step 301, the following steps may also be included:

[0106] Step 303: Send a data deletion instruction to the management device.

[0107] Specifically, the instruction sending device receives the data deletion instruction sent by the client through the APP, and sends the instruction to the management device.

[0108] Furthermore, the APP interface of the client may include a device identification of the device to be deleted. The user determines the device to be deleted based on the device identification and selects a deletion operation for the device to be deleted. The APP generates a device data deletion instruction and sends it to the instruction sending device.

[0109] Step 304: If no device data deletion instruction reception response fed back by the management device is received within a preset time period, it is determined that the communication state between the management device and the instruction sending device is disconnected.

[0110] For example, when the management device is powered off or disconnected from the network, the management device cannot receive the device data deletion instruction sent by the instruction sending device, and cannot feedback a response of receiving the data deletion instruction to the instruction sending device.

[0111] Step 305: store the data deletion instruction into a data deletion instruction list.

[0112] The data deletion instruction list obtained by this method is a list for storing device data deletion instructions that have not been successfully sent to the management device. In the subsequent processing process, when the management device is disconnected from the communication connection with the instruction sending device, switches to a state of reconnecting the communication, and sends the management device identification to the instruction sending device, the instruction sending device can search for the data deletion instruction from the data deletion instruction list according to the management device identification of the management device and resend it to the management device.

[0113] In one embodiment, the instruction sending device receives a device data deletion instruction sent by a terminal device (for example, a user terminal device), saves the received device data deletion instruction in a data deletion instruction list, sends the data deletion instruction to the management device, and deletes the instruction from the data deletion instruction list after receiving a response from the management device indicating that the data deletion instruction has been received; if no response is received from the management device, the corresponding device data deletion instruction is not deleted and remains in the data deletion instruction list.

[0114] The data deletion instructions recorded in the data deletion instruction list thus obtained are all device data deletion instructions that were not successfully sent. When the management device that has disconnected the communication connection subsequently sends the device identification to the instruction sending device, the instruction sending device can search for the data deletion instruction that was not successfully sent from the data deletion instruction list based on the management device identification of the management device, and resend it to the management device.

[0115] Reference Figure 5 The method may further include the following steps:

[0116] Step 401: When the communication state between the management device and the instruction sending device switches from disconnection to reconnection, the management device sends a management device identifier to the instruction sending device.

[0117] The method of this step has been described in the aforementioned step 101 and will not be repeated here.

[0118] Step 402: The instruction sending device receives the management device identifier sent by the management device.

[0119] The method of this step has been described in the aforementioned step 301 and will not be repeated here.

[0120] Step 403: the instruction sending device obtains the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and sends the data deletion instruction to the management device.

[0121] The method of this step has been described in the aforementioned step 302 and will not be repeated here.

[0122] Step 404, the management device obtains the device type of the device to be deleted carried in the data deletion instruction;

[0123] The method of this step has been described in the aforementioned step 102 and will not be repeated here.

[0124] Step 405: The management device obtains a data deletion policy corresponding to the device type, and deletes the local data of the device to be deleted according to the data deletion policy.

[0125] The method of this step has been described in the aforementioned step 103 and will not be repeated here.

[0126] For example, for home hosts with various types of devices such as central air conditioners connected to the host through CAN or 485, home appliances connected to the host through WiFi and BLE, and smart products connected to the host through GMesh, when various types of devices under the home host are deleted in the connected or disconnected state, the device data can be cleared and the device can enter the reset state.

[0127] Specifically, in the aforementioned embodiment, the management device is a home host, and the instruction sending device is a server. Based on the method of the embodiment of the present application, the user terminal can be sent to the server, and then the device data deletion instruction sent by the server to the home host is sent to the following devices: central air conditioners connected to the home host through CAN or 485, home appliances connected to the host through WiFi+BLE, and smart items connected to the host through GMesh. And based on the method of the embodiment of the present application, it can be compatible with abnormal situations such as power failure of the device, disconnection from the external network, or power failure of the router. And in various situations where the device to be deleted is normally connected to the Internet, powered off, disconnected from the external network, or the router is powered off, when it is necessary to delete the device to be deleted under multiple types of home hosts, the device data deletion instruction can be executed through the aforementioned method to clear the local data of the device to be deleted.

[0128] In this embodiment, when the communication connection between the management device and the instruction sending device switches from interruption to reconnection, the management device sends a device identification to the instruction sending device, the instruction sending device receives the management device identification sent by the management device, obtains the device data deletion instruction corresponding to the management device identification, and sends it to the management device, the management device obtains the device type of the device to be deleted carried in the data deletion instruction, and deletes the local data of the device to be deleted according to the data deletion policy corresponding to the device type and the data deletion policy, thereby achieving the effect of deleting the local data of the device to be deleted when deleting the device to be deleted, avoiding the leakage of user data in the device, and achieving the effect of protecting user privacy and security. In addition, when the communication state between the management device and the instruction sending device switches from disconnection to reconnection, the management device identification is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identification from the data deletion instruction list according to the management device identification, and send the data deletion instruction to the management device. Therefore, even after the communication connection between the management device and the instruction sending device is disconnected, the data deletion instruction sent by the instruction sending device can be obtained in time after reconnection, so as to delete the local data of the device to be deleted in time based on the data deletion instruction, so as to avoid user information leakage and protect user privacy and security.

[0129] refer to Figure 6 , which shows a device data processing device 50 provided in an embodiment of the present application, which is applied to manage devices, and the device data processing device 50 includes:

[0130] The first sending module 501 is used to send the management device identifier to the instruction sending device when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device;

[0131] A first acquisition module 502 is used to acquire the device type of the device to be deleted carried by the data deletion instruction;

[0132] The second acquisition module 503 is used to acquire a data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

[0133] Optionally, when the device type is a wireless communication device, the second acquisition module 503 may include:

[0134] A first instruction broadcasting submodule, used for broadcasting a device reset instruction, so that the device to be deleted receives and executes the broadcasted device reset instruction;

[0135] The first acquisition submodule is used to acquire a registered device list stored locally on the management device, and delete device information of the device to be deleted from the registered device list.

[0136] Optionally, the first acquisition submodule may include:

[0137] The first deleting unit is configured to delete the device information of the device to be deleted from the registered device list if a device reset instruction reception response fed back by the device to be deleted is received within a preset time period.

[0138] The first sending unit is used to obtain the device status information of the device to be deleted if no device reset instruction reception response is received from the device to be deleted within a preset time period, and resend the device reset instruction when the device status information switches from a state of disconnecting and managing the device connection to a state of restoring and managing the device connection.

[0139] Optionally, the first instruction broadcast submodule includes:

[0140] An acquisition unit, used to encrypt the device reset instruction through a public key to obtain the encrypted device reset instruction;

[0141] The first instruction broadcasting unit is used to broadcast an encrypted device reset instruction so that the device to be deleted receives the encrypted device reset instruction, and uses a private key to decrypt the encrypted device reset instruction, obtains the decrypted device reset instruction and executes it; wherein the public key and private key are generated when the device to be deleted is registered on the network, the private key is stored locally on the device to be deleted, and after the device to be deleted is deleted, the private key is deleted locally from the device to be deleted.

[0142] Optionally, when the device type is a wired communication device, the second acquisition module 503 includes:

[0143] The second acquisition submodule is used to acquire the registered device list stored locally in the management device; the registered device list is used to store device information of the registered device;

[0144] The first deleting submodule is used to delete the device information of the device to be deleted from the registered device list.

[0145] Based on this implementation, when deleting a device to be deleted, the local data of the device to be deleted is deleted, thereby avoiding leakage of user data in the device and achieving the effect of protecting user privacy and security. In addition, when the communication state between the management device and the instruction sending device switches from disconnection to reconnection, the management device identification is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identification from the data deletion instruction list according to the management device identification, and send the data deletion instruction to the management device. Therefore, even after the communication connection between the management device and the instruction sending device is disconnected, the data deletion instruction sent by the instruction sending device can be obtained in time after reconnection, so as to timely delete the local data of the device to be deleted based on the data deletion instruction, so as to avoid leakage of user information and protect user privacy and security.

[0146] Reference Figure 7 , which shows a device data processing device 60 provided in an embodiment of the present application, applied to an instruction sending device, and the device data processing device 60 includes:

[0147] The first receiving module 601 is used to receive a management device identifier sent by a management device; the management device identifier is sent when the communication state between the management device and the instruction sending device is switched from disconnected to reconnected;

[0148] The third acquisition module 602 is used to obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device so that the management device can obtain the device type of the device to be deleted carried by the data deletion instruction, obtain the data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

[0149] Optionally, the device 60 further includes:

[0150] A sending module, used for sending a data deletion instruction to the management device before receiving the management device identifier sent by the management device;

[0151] A determination module, configured to determine that the communication state between the management device and the instruction sending device is disconnected if no device data deletion instruction reception response fed back by the management device is received within a preset time period;

[0152] The deletion module is used to store the data deletion instruction into the data deletion instruction list.

[0153] In this embodiment, the instruction sending device receives the management device identification sent by the management device, obtains the device data deletion instruction corresponding to the management device identification, and sends it to the management device. The management device obtains the device type of the device to be deleted carried in the data deletion instruction, and deletes the local data of the device to be deleted according to the data deletion policy corresponding to the device type and the data deletion policy. Thus, when deleting the device to be deleted, the local data of the device to be deleted is deleted, avoiding the leakage of user data in the device, and achieving the effect of protecting user privacy and security. In addition, when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection, the management device identification is sent to the instruction sending device, so that the instruction sending device can obtain the data deletion instruction corresponding to the management device identification from the data deletion instruction list according to the management device identification, and send the data deletion instruction to the management device. Thus, even after the communication connection between the management device and the instruction sending device is disconnected, the data deletion instruction sent by the instruction sending device can be obtained in time after reconnection, so as to delete the local data of the device to be deleted in time based on the data deletion instruction, so as to avoid the leakage of user information and protect the privacy and security of users.

[0154] Reference Figure 8 , the electronic device 700 may include one or more of the following components: a processing component 702 , a memory 704 , a power component 706 , a multimedia component 708 , an audio component 710 , an input / output (I / O) interface 712 , a sensor component 714 , and a communication component 716 .

[0155] The processing component 702 generally controls the overall operation of the electronic device 700, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 702 may include one or more modules to facilitate the interaction between the processing component 702 and other components. For example, the processing component 702 may include a multimedia module to facilitate the interaction between the multimedia component 708 and the processing component 702.

[0156] The memory 704 is used to store various types of data to support operations on the electronic device 700. Examples of such data include instructions for any application or method operating on the electronic device 700, contact data, phone book data, messages, pictures, multimedia, etc. The memory 704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0157] The power supply component 706 provides power to the various components of the electronic device 700. The power supply component 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 700.

[0158] The multimedia component 708 includes an interface that provides an output interface between the electronic device 700 and the user. In some embodiments, the interface may include a liquid crystal display (LCD) and a touch panel (TP). If the interface includes a touch panel, the interface may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 708 includes a front camera and / or a rear camera. When the electronic device 700 is in an operating mode, such as a shooting mode or a multimedia mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0159] The audio component 710 is used to output and / or input audio signals. For example, the audio component 710 includes a microphone (MIC), and when the electronic device 700 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is used to receive an external audio signal. The received audio signal can be further stored in the memory 704 or sent via the communication component 716. In some embodiments, the audio component 710 also includes a speaker for outputting audio signals.

[0160] The input / output I / O interface 712 provides an interface between the processing component 702 and the peripheral interface module, which may be a keyboard, a click wheel, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0161] The sensor assembly 714 includes one or more sensors for providing various aspects of status assessment for the electronic device 700. For example, the sensor assembly 714 can detect the open / closed state of the electronic device 700, the relative positioning of components, such as the display and keypad of the electronic device 700, and the sensor assembly 714 can also detect the position change of the electronic device 700 or a component of the electronic device 700, the presence or absence of user contact with the electronic device 700, the orientation or acceleration / deceleration of the electronic device 700, and the temperature change of the electronic device 700. The sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 714 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 714 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0162] The communication component 716 is used to facilitate wired or wireless communication between the electronic device 700 and other devices. The electronic device 700 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 716 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 716 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0163] In an exemplary embodiment, the electronic device 700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to implement a device data processing method provided in an embodiment of the present application.

[0164] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 704 including instructions, and the instructions can be executed by a processor 720 of an electronic device 700 to perform the above method. For example, the non-transitory storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0165] Fig. 98 is a block diagram of an electronic device 800 according to another embodiment of the present invention. For example, the electronic device 800 may be provided as a server. Fig. 9 The electronic device 800 includes a processing component 822, which further includes one or more processors, and a memory resource represented by a memory 832 for storing instructions executable by the processing component 822, such as an application. The application stored in the memory 832 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 822 is configured to execute instructions to perform a device data processing method provided in an embodiment of the present application.

[0166] The electronic device 800 may also include a power supply component 826 configured to perform power management of the electronic device 800, a wired or wireless network interface 850 configured to connect the electronic device 800 to a network, and an input / output (I / O) interface 858. The electronic device 800 may operate based on an operating system stored in the memory 832, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

[0167] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0168] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A device data processing method, characterized in that: Applied to managing equipment, the method comprises: When the communication state between the management device and the instruction sending device switches from disconnection to reconnection, sending a management device identifier to the instruction sending device, so that the instruction sending device obtains a data deletion instruction corresponding to the management device identifier from a data deletion instruction list according to the management device identifier, and sends the data deletion instruction to the management device; Obtaining the device type of the device to be deleted carried by the data deletion instruction; A data deletion policy corresponding to the device type is obtained, and local data of the device to be deleted is deleted according to the data deletion policy.

2. The method according to claim 1, characterized in that In the case where the device type is a wireless communication device, the acquiring a data deletion policy corresponding to the device type and deleting the local data of the device to be deleted according to the data deletion policy includes: Broadcasting a device reset instruction, so that the device to be deleted receives and executes the broadcasted device reset instruction; Obtaining a registered device list stored locally on the management device; the registered device list is used to store device information of registered devices; Delete the device information of the device to be deleted from the registered device list.

3. The method according to claim 2, characterized in that The deleting the device information of the device to be deleted from the registered device list includes: If a device reset instruction reception response is received from the device to be deleted within a preset time period, deleting the device information of the device to be deleted from the registered device list; If no response to the device reset instruction is received from the device to be deleted within a preset time period, the device status information of the device to be deleted is obtained, and when the device status information switches from a state of disconnection from the management device to a state of restoration of connection with the management device, the device reset instruction is resent.

4. The method according to claim 2, characterized in that: The broadcasting device reset instruction, so that the device to be deleted receives and executes the broadcasted device reset instruction, includes: Encrypt the device reset instruction by using a public key to obtain an encrypted device reset instruction; Broadcasting the encryption device reset instruction so that the device to be deleted receives the encryption device reset instruction, decrypts the encryption device reset instruction using a private key, obtains the decrypted device reset instruction, and executes it; The private key is generated and stored locally on the device to be deleted when the device to be deleted is registered on the network, and is deleted locally from the device to be deleted after the device to be deleted is deleted.

5. The method according to claim 1, characterized in that In the case where the device type is a wired communication device, the acquiring a data deletion policy corresponding to the device type and deleting the local data of the device to be deleted according to the data deletion policy includes: Obtaining a registered device list stored locally on the management device; the registered device list is used to store device information of registered devices; Delete the device information of the device to be deleted from the registered device list.

6. A device data processing method, characterized in that: Applied to an instruction sending device, the method comprises: receiving a management device identifier sent by a management device; the management device identifier is sent when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection; According to the management device identifier, a data deletion instruction corresponding to the management device identifier is obtained from a data deletion instruction list, and the data deletion instruction is sent to the management device, so that the management device can obtain the device type of the device to be deleted carried by the data deletion instruction, obtain the data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

7. The method according to claim 6, characterized in that Before receiving the management device identifier sent by the management device, the method further includes: Sending a data deletion instruction to the management device; If no device data deletion instruction reception response fed back by the management device is received within a preset time period, it is determined that the communication state between the management device and the instruction sending device is disconnected; The data deletion instruction is stored in the data deletion instruction list.

8. A device data processing apparatus, characterized in that: The device is applied to manage equipment, and the device comprises: A first sending module, configured to send a management device identifier to the instruction sending device when the communication state between the management device and the instruction sending device switches from disconnection to reconnection, so that the instruction sending device can obtain a data deletion instruction corresponding to the management device identifier from a data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device; A first acquisition module, used to acquire the device type of the device to be deleted carried by the data deletion instruction; The second acquisition module is used to acquire a data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

9. A device data processing apparatus, characterized in that: The device is applied to a command sending device, and the device comprises: A first receiving module, configured to receive a management device identifier sent by a management device; the management device identifier is sent when the communication state between the management device and the instruction sending device is switched from disconnection to reconnection; The third acquisition module is used to obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list according to the management device identifier, and send the data deletion instruction to the management device, so that the management device can obtain the device type of the device to be deleted carried by the data deletion instruction, obtain the data deletion policy corresponding to the device type, and delete the local data of the device to be deleted according to the data deletion policy.

10. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images