Device data processing method and apparatus, electronic device, and readable storage medium

Abstract

The application provides a device data processing method and device, electronic equipment and readable storage medium, and applies to the technical field of device data processing. The method comprises the following steps: when the communication state between a management device and an 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 acquires 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; the device type of the to-be-deleted device carried by the data deletion instruction is acquired; the data deletion strategy corresponding to the device type is acquired, and the local data of the to-be-deleted device is deleted according to the data deletion strategy. The method of the embodiment can delete the local data of the to-be-deleted device at the same time when deleting the device, so that the leakage of device data is prevented.

Description

Technical Field

[0001] This application belongs to the field of equipment data processing technology, and specifically relates to an equipment data processing method, apparatus, electronic device and readable storage medium. Background Technology

[0002] An Internet of Things (IoT) system includes at least one device, such as home appliances that are connected to the IoT system, like air conditioners, fans, and refrigerators. The data related to these home appliances can be stored in the cloud.

[0003] In related technologies, deleting a device typically requires deleting the device's data from the cloud. However, this method can lead to incomplete data deletion, potentially resulting in the leakage of user information. Summary of the Invention

[0004] This application aims to provide a device data processing method, apparatus, electronic device, and readable storage medium, which at least solves the problem that prior art device data processing methods are difficult to completely delete data when deleting the device, which can easily lead to the leakage of user information.

[0005] In a first aspect, embodiments of this application disclose a device data processing method applied to device management, the method comprising:

[0006] When the communication state between the management device and the instruction sending device changes from disconnected to reconnected, a management device identifier is sent to the instruction sending device so that the instruction sending device can retrieve the data deletion instruction corresponding to the management device identifier from the data deletion instruction list based on the management device identifier, and send the data deletion instruction to the management device.

[0007] Obtain the device type of the device to be deleted carried in the data deletion instruction;

[0008] 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.

[0009] Secondly, embodiments of this application disclose a device data processing method applied to an instruction sending device, the method comprising:

[0010] The system receives a management device identifier sent by the management device; the management device identifier is sent when the communication state between the management device and the instruction sending device switches from disconnection to reconnection.

[0011] Based on the management device identifier, a data deletion instruction corresponding to the management device identifier is retrieved from the data deletion instruction list, and the data deletion instruction is sent to the management device. The management device then retrieves the device type of the device to be deleted carried in 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] Thirdly, embodiments of this application disclose a device data processing apparatus for managing devices, the apparatus comprising:

[0013] The first sending module is 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 the data deletion instruction list based on the management device identifier, and send the data deletion instruction to the management device.

[0014] The first acquisition module is used to acquire the device type of the device to be deleted carried in 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] Fourthly, embodiments of this application also disclose a device data processing apparatus, applied to an instruction sending device, the method comprising:

[0017] The first receiving module is used to receive a management device identifier sent by the management device; the management device identifier is sent when the communication state between the management device and the instruction sending device switches from disconnection to reconnection;

[0018] The third acquisition module is used to acquire a data deletion instruction corresponding to the management device identifier from the data deletion instruction list based on the management device identifier, and send the data deletion instruction to the management device so that the management device can acquire the device type of the device to be deleted carried by the data deletion instruction, acquire 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] Fifthly, embodiments of this application also disclose an electronic device, including a processor and a memory, wherein the memory stores a program or instructions executable on the processor, and the program or instructions, when executed by the processor, implement the steps of the method described in the first or second aspect.

[0020] In a sixth aspect, embodiments of this application also disclose a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the method described in the first or second aspect.

[0021] In summary, in this embodiment, the management device obtains a data deletion command sent by the command sending device and acquires the device type of the device to be deleted carried in the data deletion command. Based on the data deletion policy corresponding to the device type, the local data of the device to be deleted is deleted. This achieves the deletion of the local data of the device to be deleted when deleting the device, preventing the leakage of user data on the device and protecting user privacy. Furthermore, when the communication state between the management device and the command sending device switches from disconnected to reconnected, a management device identifier is sent to the command sending device. The command sending device then retrieves the data deletion command corresponding to the management device identifier from the data deletion command list and sends the data deletion command to the management device. Therefore, even after the communication connection between the management device and the command sending device is broken, the data deletion command sent by the command sending device can be obtained promptly after reconnection. Based on the data deletion command, the local data of the device to be deleted can be deleted promptly, thus preventing user information leakage and protecting user privacy. Attached Figure Description

[0022] In the attached diagram:

[0023] Figure 1 This is a flowchart illustrating the steps of a device data processing method provided in an embodiment of this application;

[0024] Figure 2 This is a schematic diagram of the structure of a device data processing system provided in an embodiment of this application;

[0025] Figure 3 This is a flowchart illustrating the steps of a device data processing method provided in an embodiment of this application;

[0026] Figure 4 This is a flowchart illustrating the steps of a device data processing method provided in an embodiment of this application;

[0027] Figure 5 This is a flowchart of the interactive steps of another device data processing method provided in this application embodiment;

[0028] Figure 6 This is a block diagram of another device data processing apparatus provided in the embodiments of this application;

[0029] Figure 7This is a block diagram of another device data processing apparatus provided in the embodiments of this application;

[0030] Figure 8 This is a block diagram of an electronic device provided in one embodiment of this application;

[0031] Figure 9 This is a block diagram of an electronic device according to another embodiment of the present application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0033] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0034] Figure 1 This embodiment provides a device data processing method, which can be referred to as follows: 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 changes from disconnected to reconnected, 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 based on the management device identifier, and send the data deletion instruction to the management device.

[0036] Furthermore, if the communication status between the management device and the command sending device remains unchanged, and the communication connection with the command sending device remains unbroken, the management device directly receives the data deletion command sent by the command sending device.

[0037] For example, if a command sending device sends a device data deletion command to a management device, and no response is received from the management device within a preset time period, the communication status between the management device and the command sending device is determined to be disconnected. If, after determining that the communication is disconnected, device information reported by the management device is received, the communication status between the management device and the command sending device is determined to switch from disconnected to reconnected. The device information may include the management device's network information and its management device identifier.

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

[0039] A management device is a device that communicates with and is connected to a command-sending device, and is also connected to at least one device to be deleted. The management device is used to manage the devices to be deleted, which are registered in the IoT system to which the management device resides. For example, the management device can be a host device capable of connecting to various protocols and performing local data storage and processing.

[0040] For example, refer to Figure 2 The management device is the host, and the command sending device is the server. The device to be deleted can be a CAN device or a 485 device connected to the host via the Controller Area Network (CAN) bus or 485 bus, a Mesh device connected to the host via Mesh, or a WiFi or BLE device connected to the host via WiFi / Bluetooth Low Energy (WiFi BLE). Additionally, the device to be deleted can also be a third-party Bluetooth device (not shown in the diagram), or other devices that can communicate with the host. Among these, 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] Furthermore, refer to Figure 2 The client sends a device deletion command (Delete command) to the server through the application (APP). Based on the Delete command, the server forwards the Delete command to the host. Based on the received Delete command, the host sends a Reset command 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] In the event that a WiFi or BLE device does not receive a Reset command from the host and reconnects to the host after being disconnected, the host can resend the Reset command to it, or the server can resend the Reset command to it.

[0043] The data deletion instruction list is a list generated by the instruction sending device to store data deletion instructions that the instruction sending device has sent, but has not received a notification from the management device that the instruction has been executed within a preset time period.

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

[0045] In the event of a power outage or network outage on the management device, the communication between the management device and the command sending device will be disconnected. A network outage can include the management device disconnecting from the external network or from the router; for example, if the router loses power, the management device will experience a network outage.

[0046] When the management device experiences a power outage or network disconnection, it cannot receive data deletion commands sent by the command sending device. After the management device is powered on and restarted or reconnected to the network, it can proactively send its own identifier to the command sending device to trigger the command sending device to reissue the data deletion command.

[0047] For example, the command 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 command to the MQTT server through its application to delete the device data to be deleted. The MQTT server then forwards the device data deletion command to the host.

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

[0049] If the MQTT server does not receive a received response from the host within a preset time period, it determines that the communication connection between the host and the MQTT server is broken. After the host reconnects to the network, it will report the network status information. Upon receiving this information, the MQTT server determines whether the host has switched from a broken communication connection state to a connected state. The MQTT server checks its data deletion command list for a data deletion command corresponding to the host's management device identifier. If a data deletion command is found, it indicates that the previous data deletion command was not successfully sent. In this case, the data deletion command is resent to ensure that the host can receive and execute the data deletion command.

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

[0051] The equipment type can be either wired communication equipment or wireless communication equipment.

[0052] Furthermore, wired communication devices can include CAN devices or 485 devices. CAN devices or 485 devices are devices that connect to management devices via a CAN bus or 485 bus, such as central air conditioning or underfloor heating systems. These wired communication devices do not record data; they only execute received commands.

[0053] Wireless communication devices can include Wi-Fi and Bluetooth devices that connect to the management device via Wi-Fi and BLE. Specifically, these devices connect to the management device (e.g., a home control unit) via Wi-Fi, while BLE devices send and receive Bluetooth scene commands. These devices can be air purifiers, fans, refrigerators, washing machines, etc. These devices can receive specific control commands, and can also record and set commands, triggering actions by executing those commands.

[0054] Wireless communication devices can also include individual smart devices that access management devices via GMESH. These devices connect to management devices (such as home hubs) via GMESH and typically include smart switches, scene switches, sensors, and other similar devices.

[0055] Wireless communication devices can also include third-party devices that access the management device via Wi-Fi and IP. These devices connect to the management device (e.g., a home console) via Wi-Fi and IP, and are typically Bluetooth Mesh devices connected to a third-party gateway, such as lighting devices. The control protocols of these third-party devices differ; they do not record the management device's setting commands, but rather the management device translates the control commands and sends them to the third-party gateway, which then forwards them to the third-party device.

[0056] Step 103: 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.

[0057] For example, the system retrieves the data deletion policy corresponding to the device type, sends a device reset (Reset) command to the device under test according to the data deletion policy, the device under test receives the Reset command and responds to the home host, and then performs a device reset according to the Reset command. After receiving the device's response, the management device removes the device to be deleted from the device registration list. This completes the deletion of local data on the device under test.

[0058] For example, if the device type of the device under test is a wireless communication device, the data deletion strategy is to broadcast a data deletion instruction so that the device to be deleted can delete its local data. Alternatively, the deletion strategy may also include deleting the device information of the device under test from the device registration list.

[0059] For example, if the device type of the device to be tested is a wired communication device, then the data deletion strategy is: delete 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 command sending device is the MQTT server. The MQTT server receives the client's command to delete the device under the host and sends a device data deletion (Delete) command to the host. If the communication connection between the host and the MQTT server is broken, the host will not receive the device data deletion command. After the host reconnects to the network, it refreshes its subscription and sends the host's management device identifier to the MQTT server, triggering the MQTT server to resend the data deletion command. After receiving the data deletion command, the host determines the data deletion strategy based on the device type in the command and sends the data deletion command to the device to be deleted according to the command distribution logic described in the data deletion strategy.

[0061] With the continuous development of the Internet of Things (IoT), the number of smart home appliances that can be connected to the IoT in the home is also increasing. In related technologies, when a home appliance is removed from the IoT, only the cloud data of the device is deleted, while the data inside the device is still retained, which may lead to the leakage of user privacy.

[0062] In this embodiment, the management device receives a data deletion command sent by the command sending device and obtains the device type of the device to be deleted carried in the data deletion command. Based on the data deletion policy corresponding to the device type, the management device deletes the local data of the device to be deleted. This achieves the deletion of the local data of the device to be deleted when deleting the device, preventing the leakage of user data on the device and protecting user privacy. Furthermore, when the communication state between the management device and the command sending device switches from disconnected to reconnected, a management device identifier is sent to the command sending device. The command sending device then retrieves the data deletion command corresponding to the management device identifier from the data deletion command list and sends the data deletion command to the management device. Therefore, even after the communication connection between the management device and the command sending device is broken, the management device can promptly receive the data deletion command sent by the command sending device after reconnection, and delete the local data of the device to be deleted in a timely manner based on the data deletion command, thus preventing user information leakage and protecting user privacy.

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

[0064] Step 201: When the communication state between the management device and the instruction sending device changes from disconnected to reconnected, 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 based on the management device identifier, and send the data deletion instruction to the management device.

[0065] Furthermore, if the communication status between the management device and the command sending device remains unchanged, and the communication connection with the command sending device remains unbroken, the management device directly receives the data deletion command sent by the command sending device.

[0066] The method for this step has been explained in step 101 above, 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, the data deletion strategy is determined based on the device type. If the device type of the device under test is a wireless communication device, the data deletion strategy is: broadcast a data deletion command so that the device to be deleted can delete the local data of the device under test.

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

[0070] Step 203: Broadcast device reset command, so that the device to be deleted can receive and execute the broadcast device reset command.

[0071] For example, when the wireless communication device is a WiFi or BLE device, the management device broadcasts the device reset command via Open Systems Interconnection (UDP); when the wireless communication device is a GMESH device, the management device broadcasts the device reset command via Mesh broadcast.

[0072] For example, consider a scenario where the management device is the host, the command sending device is the MQTT server, and the client deletes a WiFi device under the host. The MQTT server sends a Delete command to both the host and the WiFi device. If the device fails to receive the command due to an malfunction, and the host receives the command, it will synchronously broadcast a Reset command to the device via UDP. Simultaneously, when the device reconnects to the network and refreshes its subscription, it triggers the server to resend the Reset command. If the device receives a parseable command, it enters a reset state; otherwise, it does not execute the command. The parseability of the command refers to whether the device under test can parse the encrypted device data deletion command, which is encrypted using the management device manufacturer's proprietary protocol.

[0073] The process involves generating a public-private key pair during network registration for the device to be deleted. The public key is recorded in the embedded software of the management device and is used to parse peripheral information for device data deletion commands; the public key cannot be deleted. The private key, on the other hand, is generated during network registration and stored locally on the device to be deleted. It is used to parse specific action commands for the device to be deleted. After the device is deleted, the stored private key is also deleted. Therefore, if a previous device data deletion command is received after the private key has been deleted, the device to be deleted will not be able to parse the command.

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

[0075] Sub-step 2031: Obtain the encryption device reset command through the public key encryption device reset command.

[0076] When a device to be deleted registers with 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 stores it locally on the device.

[0077] Sub-step 2032: Broadcast the encrypted device reset command so that the device to be deleted can receive the encrypted device reset command, decrypt the encrypted device reset command using the private key, obtain the decrypted device reset command and execute it.

[0078] The private key is generated and stored locally on the device to be deleted during network registration, and is deleted from the device after the device is deleted.

[0079] Specifically, the device to be deleted acquires and stores its private key during network registration. Based on this stored private key, it can decrypt the encrypted device data deletion command sent by the management device, thus enabling the parsing of the device data deletion command. After the device to be deleted is deleted, the old private key stored within it is also deleted. When the device to be deleted re-registers with the network, it will receive a new private key. If, after the device to be deleted and re-registers with the network, it receives an encrypted device data deletion command generated by the management device before the device deletion, the new key stored in the device under test will prevent the parsing and execution of the encrypted device data deletion command.

[0080] Based on the method of this embodiment, the device to be deleted needs to decrypt the encrypted device data deletion command using the private key generated during network registration. After deletion and re-registration, the private key will be updated. If the device to be deleted has executed a device data deletion command and re-registered, the management device will still broadcast the previously generated device data deletion command. Since the device to be deleted cannot parse the old device data deletion command using the new private key, it will not execute the previously executed device data deletion command again, thus avoiding accidental deletion of the device to be deleted.

[0081] For example, a wireless communication device can also be a Bluetooth mesh device. When the power is 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 via the mesh.

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

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

[0084] Specifically, when a device to be deleted registers with the network, its device information is stored in the registered device list. When the device is deleted, its device information is removed from the registered device list. This prevents the device's information from remaining in the registered device list after deletion, thus avoiding information leakage.

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

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

[0087] After receiving the device reset command, the device to be deleted will send a reset command reception response to the management device. If the management device receives the device reset command reception response from the device to be deleted within a 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 successfully received the device data deletion command.

[0088] Sub-step 2042: If no device reset command 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 if the device status information is that it has switched from the state of disconnected and connected to the management device to the state of restored and connected to the management device, the device reset command is resent.

[0089] If no device reset command response is received from the device to be deleted within the preset time period, it indicates an abnormal communication between the device to be deleted and the management device. The device reset command needs to be resent after the device to be deleted switches from the state of disconnection from the management device to the state of reconnection to the management device. Based on this command, the successful deletion of the device to be deleted can be ensured.

[0090] For example, after a wireless device to be deleted disconnects from 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 its network status and device identifier. If the management device receives the information reported by the wireless device, it determines that the wireless device has switched from the state of disconnecting from the management device to the state of resuming communication with the management device.

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

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

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

[0094] For example, a wired communication device can be a device that connects to the host via CAN or 485.

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

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

[0097] CAN or 485 devices have limited communication bandwidth and internal data storage space, making them unable to receive and parse large data packets. They also lack a private key mechanism. Therefore, if a device to be deleted is a CAN or 485 device, it needs to be removed from the device registration list.

[0098] For example, if the device to be deleted is a wireless device, after the wireless device is reset, it can be deleted from the device registry or left undeleted.

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

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

[0101] The management device identifier is sent when the communication status between the management device and the command sending device changes from disconnection to reconnection.

[0102] The identification of managed equipment can be the name, number, or other identifier of the managed equipment.

[0103] Step 302: Based on the management device identifier, retrieve 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 in 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 receives data deletion commands from the command sending device and obtains the device type of the device to be deleted carried in the data deletion command. Based on the data deletion policy corresponding to the device type, it deletes the local data of the device to be deleted. This achieves the deletion of local data of the device to be deleted when deleting the device, preventing the leakage of user data on the device and protecting user privacy. Furthermore, when the communication state between the management device and the command sending device switches from disconnected to reconnected, the management device sends a management device identifier to the command sending device. The command sending device then retrieves the data deletion command corresponding to the management device identifier from the data deletion command list and sends the data deletion command to the management device. Therefore, even after the communication connection between the management device and the command sending device is broken, the data deletion command sent by the command sending device can be obtained promptly after reconnection. Based on the data deletion command, the local data of the device to be deleted can be deleted in a timely manner, thus preventing user information leakage and protecting user privacy.

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

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

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

[0108] Furthermore, the client's APP interface can include the device identifier of the device to be deleted. The user identifies the device to be deleted based on the device identifier and selects the deletion operation for the device to be deleted. The APP generates a device data deletion command and sends it to the command sending device.

[0109] Step 304: If no response to the device data deletion instruction is received from the management device within the preset time period, it is determined that the communication between the management device and the instruction sending device is disconnected.

[0110] For example, in the event of a power outage or network outage, the management device cannot receive the device data deletion command sent by the command sending device, nor can it provide feedback to the command sending device indicating that the data deletion command has been received.

[0111] Step 305: Store the data deletion instruction in the data deletion instruction list.

[0112] The data deletion instruction list obtained through this method is used to store device data deletion instructions that were not successfully sent to the management device. In subsequent processing, when the management device switches from a state of interrupted communication with the instruction sending device to a state of re-establishing communication and sends its management device identifier to the instruction sending device, the instruction sending device can retrieve the data deletion instruction from this list based on the management device identifier 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 (e.g., a user terminal device), stores the received device data deletion instruction in a data deletion instruction list, sends the data deletion instruction to a management device, and deletes the instruction from the data deletion instruction list after receiving a response from the management device confirming receipt of the data deletion instruction; if no response is received from the management device, the corresponding device data deletion instruction is not deleted and is retained in the data deletion instruction list.

[0114] The resulting list of data deletion instructions contains only those device data deletion instructions that were not successfully sent. Subsequently, when the management device sends a device identifier to the instruction sending device after the communication connection has been broken and then restored, the instruction sending device can retrieve the unsuccessfully sent data deletion instructions from this list based on the management device identifier and resend them to the management device.

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

[0116] Step 401: When the communication state between the management device and the command sending device changes from disconnected to reconnected, the management device sends a management device identifier to the command sending device.

[0117] The method for this step has been explained in step 101 above, 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 for this step has been explained in step 301 above, and will not be repeated here.

[0120] Step 403: The instruction sending device retrieves the data deletion instruction corresponding to the management device identifier from the data deletion instruction list based on the management device identifier, and sends the data deletion instruction to the management device.

[0121] The method for this step has been explained in step 302 above, 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 for this step has been explained in step 102 above, and will not be repeated here.

[0124] Step 405: The management device 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.

[0125] The method for this step has been explained in step 103 above, and will not be repeated here.

[0126] For example, a home host system can be used to clear device data and put the devices into a reset state when deleting various types of devices under the home host system, such as central air conditioners connected to the host system via CAN or 485, home appliances connected to the host system via WiFi and BLE, and smart devices connected to the host system via GMESH, whether the network is connected or disconnected.

[0127] Specifically, in the aforementioned embodiments, the management device is a home host, and the instruction sending device is a server. Based on the method of this application embodiment, a device data deletion instruction can be sent from the user terminal to the server, and then from the server to the home host, which will then distribute the instruction to the following devices: central air conditioning units connected to the home host via CAN or 485; home appliances connected to the host via WiFi+BLE; and smart devices connected to the host via GMash. Furthermore, the method of this application embodiment is compatible with abnormal situations such as device power outages, internet outages, or router power outages. Moreover, when multiple types of devices under a home host need to be deleted under various circumstances, including normal network connectivity, power outages, internet outages, or router power outages, the aforementioned method can be used to execute the device data deletion instruction to clear the local data of the devices to be deleted.

[0128] In this embodiment, when the communication connection between the management device and the command sending device switches from interrupted to reconnected, the management device sends a device identifier to the command sending device. The command sending device receives the management device identifier sent by the management device, obtains the device data deletion instruction corresponding to the management device identifier, 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. 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 on the device and achieving the effect of protecting user privacy and security. Furthermore, when the communication state between the management device and the command sending device switches from disconnected to reconnected, the management device sends a management device identifier to the command sending device. This allows the command sending device to obtain the data deletion instruction corresponding to the management device identifier from the data deletion instruction list based on the management device identifier and send the data deletion instruction to the management device. Therefore, even if the communication connection between the management device and the command sending device is lost, the data deletion command sent by the command sending device can be obtained in a timely manner after reconnection. Based on the data deletion command, the local data of the device to be deleted can be deleted in a timely manner, thereby avoiding the leakage of user information and protecting user privacy and security.

[0129] refer to Figure 6 This application illustrates a device data processing apparatus 50 provided in an embodiment of the present application, used for managing devices. The device data processing apparatus 50 includes:

[0130] The first sending module 501 is used 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 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] The first acquisition module 502 is used to acquire the device type of the device to be deleted carried in the data deletion instruction;

[0132] The second acquisition module 503 is used to acquire 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.

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

[0134] The first instruction broadcast submodule is used to broadcast device reset instructions so that the device to be deleted can receive and execute the broadcast device reset instructions;

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

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

[0137] The first deletion unit is used to delete the device information of the device to be deleted from the registered device list if a device reset command response is received from the device to be deleted within a preset time period.

[0138] The first sending unit is configured to, if no device reset command response is received from the device to be deleted within a preset time period, obtain the device status information of the device to be deleted, and resend the device reset command if the device status information changes from a state of disconnection and management device connection to a state of restoration of management device connection.

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

[0140] The acquisition unit is used to obtain the device reset command through the public key encryption device reset command;

[0141] The first instruction broadcasting unit is used to broadcast the encryption device reset instruction, so that the device to be deleted can receive the encryption device reset instruction, decrypt the encryption device reset instruction using the private key, obtain the decrypted device reset instruction, and execute it; wherein, the public key and private key are generated when the device to be deleted registers with the network, the private key is stored locally on the device to be deleted, and the private key is deleted from the local storage of the device to be deleted after the device to be deleted is 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 list of registered devices stored locally on the management device; the list of registered devices is used to store device information of the registered devices;

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

[0145] Based on this implementation, local data on the device to be deleted is also deleted when deleting the device, preventing the leakage of user data and protecting user privacy. Furthermore, when the communication state between the management device and the command sending device switches from disconnected to reconnected, a management device identifier is sent to the command sending device. This allows the command sending device to retrieve the corresponding data deletion instruction from the data deletion instruction list based on the management device identifier and send it to the management device. Therefore, even after the communication connection between the management device and the command sending device is broken, the data deletion instruction sent by the command sending device can be obtained promptly after reconnection. Based on this instruction, the local data on the device to be deleted can be deleted in a timely manner, thus preventing user information leakage and protecting user privacy.

[0146] Reference Figure 7 This illustration shows a device data processing apparatus 60 provided in an embodiment of this application, applied to an instruction sending device. The device data processing apparatus 60 includes:

[0147] The first receiving module 601 is used to receive the management device identifier sent by the management device; the management device identifier is sent when the communication state between the management device and the instruction sending device changes from disconnection to reconnection;

[0148] The third acquisition module 602 is used to acquire 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 acquire the device type of the device to be deleted carried in the data deletion instruction, acquire 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, device 60 further includes:

[0150] The sending module is used to send a data deletion command to the management device before receiving the management device identifier sent by the management device;

[0151] The determination module is used to determine that the communication status between the management device and the instruction sending device is disconnected if no response to the device data deletion instruction is received from the management device within a preset time period.

[0152] The deletion module is used to store data deletion commands in a data deletion command list.

[0153] In this embodiment, the instruction sending device receives a management device identifier from the management device, obtains the device data deletion instruction corresponding to the management device identifier, 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. This achieves the deletion of the local data of the device to be deleted when deleting the device, preventing the leakage of user data on the device and protecting user privacy. Furthermore, when the communication state between the management device and the instruction sending device switches from disconnected to reconnected, the management device identifier is sent to the instruction sending device. The instruction sending device then retrieves the data deletion instruction corresponding to the management device identifier from the data deletion instruction list based on the management device identifier and sends the data deletion instruction to the management device. Therefore, even after the communication connection between the management device and the instruction sending device is broken, the data deletion instruction sent by the instruction sending device can be obtained promptly after reconnection, allowing for timely deletion of the local data of the device to be deleted, thus preventing user information leakage and protecting user privacy.

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

[0155] Processing component 702 typically controls the overall operation of electronic device 700, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 702 may include one or more modules to facilitate interaction between processing component 702 and other components. For example, processing component 702 may include a multimedia module to facilitate interaction between multimedia component 708 and processing component 702.

[0156] Memory 704 is used to store various types of data to support the operation of electronic device 700. Examples of this data include instructions for any application or method operating on electronic device 700, contact data, phonebook data, messages, pictures, multimedia, etc. 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 storage, flash memory, magnetic disk, or optical disk.

[0157] Power supply component 706 provides power to various components of electronic device 700. 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 electronic device 700.

[0158] Multimedia component 708 includes an interface that provides an output interface between electronic device 700 and a 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 touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may not only sense the boundaries of touch or swipe actions but also detect the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 708 includes a front-facing camera and / or a rear-facing camera. When electronic device 700 is in an operating mode, such as a shooting mode or a multimedia mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

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

[0160] Input / output (I / O) interface 712 provides an interface between processing component 702 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

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

[0162] Communication component 716 facilitates wired or wireless communication between electronic device 700 and other devices. Electronic device 700 can access wireless networks based on communication standards, such as WiFi, carrier networks (such as 2G, 3G, 4G, or 5G), or combinations thereof. In one exemplary embodiment, communication component 716 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 716 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may 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 the embodiments of this 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, which can be executed by a processor 720 of an electronic device 700 to perform the above-described method. For example, the non-transitory storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0165] Figure 9This 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. (See also...) Figure 9 The electronic device 800 includes a processing component 822, which further includes one or more processors, and memory resources represented by a memory 832 for storing instructions, such as application programs, that can be executed by the processing component 822. The application programs stored in the memory 832 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 822 is configured to execute instructions to perform a device data processing method provided in embodiments of this application.

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

[0167] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0168] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A device data processing method, characterized by, The method is applied to a management device and comprises the following steps: When a communication state between the management device and an instruction sending device switches from disconnection to reconnection, sending a management device identifier to the instruction sending device, so that the instruction sending device acquires 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; Acquiring a device type of a to-be-deleted device carried by the data deletion instruction; Acquiring a data deletion strategy corresponding to the device type, and deleting local data of the to-be-deleted device according to the data deletion strategy.

2. The method of claim 1, wherein, In the case where the device type is a wireless communication device, the acquiring of the data deletion strategy corresponding to the device type and the deleting of the local data of the to-be-deleted device according to the data deletion strategy comprise the following steps: Broadcasting a device reset instruction, so that the to-be-deleted device receives and executes the broadcasted device reset instruction; Acquiring a registered device list stored locally by the management device; the registered device list is used for storing device information of registered devices; Deleting device information of the to-be-deleted device from the registered device list.

3. The method of claim 2, wherein, The deleting of the device information of the to-be-deleted device from the registered device list comprises the following steps: If a device reset instruction receiving response fed back by the to-be-deleted device is received within a preset time period, deleting the device information of the to-be-deleted device from the registered device list; If the device reset instruction receiving response fed back by the to-be-deleted device is not received within the preset time period, acquiring device state information of the to-be-deleted device, and in the case where the device state information switches from a state of being disconnected from the management device to a state of resuming connection with the management device, re-sending the device reset instruction.

4. The method of claim 2, wherein, The broadcasting of the device reset instruction, so that the to-be-deleted device receives and executes the broadcasted device reset instruction, comprises the following steps: Encrypting the device reset instruction by using a public key to obtain an encrypted device reset instruction; Broadcasting the encrypted device reset instruction, so that the to-be-deleted device receives the encrypted device reset instruction, decrypts the encrypted device reset instruction by using a private key, acquires a decrypted device reset instruction, and executes the decrypted device reset instruction; The private key is generated when the to-be-deleted device is registered in a network and is stored locally in the to-be-deleted device, and is deleted from the to-be-deleted device after the to-be-deleted device is deleted.

5. The method of claim 1, wherein, In the case where the device type is a wired communication device, the acquiring of the data deletion strategy corresponding to the device type and the deleting of the local data of the to-be-deleted device according to the data deletion strategy comprise the following steps: Acquiring a registered device list stored locally by the management device; the registered device list is used for storing device information of registered devices; Deleting device information of the to-be-deleted device from the registered device list.

6. A device data processing method, characterized by, The method is applied to an instruction sending device and comprises the following steps: The management device identifier is sent by the management device 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 obtains a device type of a to-be-deleted device carried by the data deletion instruction, obtains a data deletion strategy corresponding to the device type, and deletes local data of the to-be-deleted device according to the data deletion strategy.

7. The method of claim 6, wherein, 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 a device data deletion instruction receiving response fed back by the management device is not 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. An apparatus data processing device, characterized by The device is applied to a management device, and the device includes: a first sending module configured to send a management device identifier to an instruction sending device when a communication state between the management device and the instruction sending device is switched from disconnection to reconnection, 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; a first obtaining module configured to obtain a device type of a to-be-deleted device carried by the data deletion instruction; a second obtaining module configured to obtain a data deletion strategy corresponding to the device type, and delete local data of the to-be-deleted device according to the data deletion strategy.

9. An apparatus data processing device, characterized by The device is applied to an instruction sending device, and the device includes: a first receiving module configured to receive a management device identifier sent by a management device; the management device identifier is sent by the management device when a communication state between the management device and the instruction sending device is switched from disconnection to reconnection; a third obtaining module configured to 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, so that the management device obtains a device type of a to-be-deleted device carried by the data deletion instruction, obtains a data deletion strategy corresponding to the device type, and deletes local data of the to-be-deleted device according to the data deletion strategy.

10. An electronic device, comprising: The device includes a processor and a memory, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the method in any one of claims 1 to 7.

11. A readable storage medium, characterized by, The readable storage medium stores programs or instructions, and the programs or instructions are executed by the processor to implement the steps of the method in any one of claims 1 to 7.

Images