Factory reset method, device, system and storage medium
By issuing factory reset instructions to IoT devices, setting flags and configuring network binding data, the problem of factory settings is solved between the device and the server, the normal distribution network and control of IoT devices is realized, and the configuration is improved Accuracy and reliability of the network process.
Patent Information
- Application Number
- CN202211627768.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-16
- Publication Date
- 2024-12-17
- Estimated Expiration
- 2042-12-16
AI Technical Summary
After the soft wireless access point distribution is completed, the service set identification or key modification of the IoT device causes the device to redistribute the network, and the factory settings between the device and the server are out of synchronized, causing the application to not be able to control the IoT device normally. .
By issuing factory reset instructions to IoT devices, setting their flag bits to preset values, entering the network mode to be distributed, and when the flag bits are detected as preset values, configure network binding data to realize the device and server The synchronization between the network ensures the accuracy and integrity of the distribution network process.
It solves the problem of factory settings that are out of synchronization between the device and the server, ensures that the Internet of Things devices can be properly distributed and controlled, and improves the accuracy and reliability of the distribution process.
Smart Images

Figure CN115766456B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to but is not limited to the field of display technology, and in particular to a voltage conversion circuit, a driving method, a device and a storage medium. Background Art
[0002] After the softAP network configuration is completed, the device that has already been configured needs to be configured again, considering that the wireless access point has changed the service set identifier (SSID) or modified the key (password). At this time, it is necessary to delete the original network configuration data in the application and then configure the network. However, due to the unsynchronized factory settings between the IoT device and the server, the application displays the device abnormally and cannot control the IoT device normally. Summary of the invention
[0003] In view of this, embodiments of the present application at least provide a method, device, system and storage medium for restoring factory settings.
[0004] The technical solution of the embodiment of the present application is implemented as follows:
[0005] In a first aspect, an embodiment of the present application provides a method for restoring factory settings, the method comprising:
[0006] When receiving the information to be restored to factory, a factory restore instruction is issued to the IoT device, so that the IoT device sets the flag bit to a preset value and enters a waiting network configuration mode;
[0007] When it is detected that the flag bit is the preset value, configure the network binding data of the Internet of Things device in the waiting network configuration mode;
[0008] In response to completing the configuration of the network binding data, prompt information is output.
[0009] In a second aspect, an embodiment of the present application provides a method for restoring factory settings, the method comprising:
[0010] When receiving the factory reset command sent by the server, the flag is set to the preset value and the network configuration waiting mode is entered;
[0011] Storing the flag bit in a preset storage repository so that the server can detect the flag bit;
[0012] Receive the prompt information fed back by the server; wherein the prompt information is used to prompt that the network binding data of the Internet of Things device in the waiting network configuration mode has been configured.
[0013] In a third aspect, an embodiment of the present application provides a device for restoring factory settings, the device comprising:
[0014] A first sending module is used to send a factory restore instruction to the IoT device when receiving the information to be restored to factory, so that the IoT device sets the flag bit to a preset value and enters a waiting network configuration mode;
[0015] A first configuration module is used to configure the network binding data of the Internet of Things device in the waiting network configuration mode when it is detected that the flag bit is the preset value;
[0016] A first output module is used to output prompt information in response to completing the configuration of the network binding data.
[0017] In a fourth aspect, an embodiment of the present application provides a device for restoring factory settings, the device for restoring factory settings comprising:
[0018] The first setting module is used to set the flag bit to a preset value and enter a waiting network configuration mode when receiving a factory reset instruction sent by the server;
[0019] A first storage module, used for storing the flag bit in a preset storage repository so that the server can detect the flag bit;
[0020] The first receiving module is used to receive the prompt information fed back by the server; wherein the prompt information is used to prompt that the network binding data of the Internet of Things device in the waiting network configuration mode has been configured.
[0021] In a fifth aspect, an embodiment of the present application provides a factory reset system, characterized in that the factory reset system includes a server and an Internet of Things device; wherein the server is used to execute the method described in the first aspect above; and the Internet of Things device is used to execute the method described in the second aspect above.
[0022] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which implements some or all of the steps in the above method when executed by a processor.
[0023] An embodiment of the present application provides a computer program, including a computer-readable code. When the computer-readable code is executed in a computer device, a processor in the computer device executes some or all of the steps for implementing the above method.
[0024] An embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and when the computer program is read and executed by a computer, implements some or all of the steps in the above method.
[0025] In an embodiment of the present application, upon receiving the factory information to be restored, the server sends a factory restore instruction to the IoT device, so that the IoT device sets the flag to a preset value and enters the waiting network configuration mode; in this way, the server and the IoT device can synchronously learn that the Internet device needs to restore factory settings. The server detects the flag of the IoT device, and if it detects that the flag is a preset value, it configures the network binding data for the IoT device in the waiting network configuration mode to achieve the network configuration of the IoT device; and if the configuration of the network binding data is completed, the server outputs a prompt message so that the IoT device and the application that controls the IoT device can both know that the IoT device has completed the network configuration. In this way, upon receiving the factory information to be restored, the server sends a factory restore instruction to the IoT device, and when it detects that the flag is a preset value, it configures the IoT device, thereby achieving synchronization between the server and the IoT device, and then more accurately completing the network configuration of the IoT device, so as to facilitate the control of the IoT device.
[0026] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and are used together with the specification to illustrate the technical solution of the present application.
[0028] Figure 1 A schematic diagram of a method for restoring factory settings according to an embodiment of the present invention;
[0029] Figure 2 A schematic diagram of another implementation flow of a method for restoring factory settings provided in an embodiment of the present application;
[0030] Figure 3 A schematic diagram of an interactive process of restoring factory settings provided in an embodiment of the present application;
[0031] Figure 4 A schematic diagram of another implementation flow of a method for restoring factory settings provided in an embodiment of the present application;
[0032] Figure 5 A schematic diagram of the structure of a device for restoring factory settings provided in an embodiment of the present application;
[0033] Figure 6 A schematic diagram of the structure of a device for restoring factory settings provided in an embodiment of the present application;
[0034] Figure 7 A schematic diagram of a hardware entity of an electronic device that restores factory settings in an embodiment of the present application. DETAILED DESCRIPTION
[0035] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application are further elaborated in detail below in conjunction with the drawings and embodiments. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.
[0036] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.
[0037] The terms "first / second / third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that "first / second / third" can be interchanged with a specific order or sequence where permitted so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.
[0038] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing this application and are not intended to limit this application.
[0039] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are described first. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.
[0040] 1) IoT devices are non-standard computing devices that can be wirelessly connected to a network and have the ability to transmit data. IoT involves extending the scope of Internet connectivity from standard devices such as desktops, laptops, smartphones and tablets to any range of traditional "dumb" or non-Internet-enabled physical devices and everyday objects. They can communicate and interact over the Internet. They can also be remotely controlled.
[0041] 2) Message Queuing Telemetry Transport (MQTT) is a message protocol based on the publish / subscribe paradigm under the International Organization for Standardization (ISO). It works on the Transmission Control Protocol / Internet Protocol (TCP / IP) protocol family and is a publish / subscribe messaging protocol designed for remote devices with low hardware performance and poor network conditions.
[0042] Based on this, the embodiment of the present application provides a method for restoring factory settings, which is applicable to IoT devices. When the server receives the factory restoration information that meets the preset conditions, it sends a factory restoration instruction to the IoT device, and when the flag bit is detected to be a preset value, the IoT device is configured for networking, thereby achieving synchronization between the server and the IoT device, and then more accurately completing the networking of the IoT device, so as to facilitate the control of the IoT device. In the embodiment of the present application, the method for restoring factory settings can be executed by a server, an application, an IoT device, and a processor. Figure 1 A schematic diagram of a method for restoring factory settings provided in an embodiment of the present application is provided. The method can be implemented by a server, such as Figure 1 As shown, the method includes the following steps S101 to S103:
[0043] Step S101, when receiving information that satisfies the factory restoration, a factory restoration instruction is issued to the IoT device, so that the IoT device sets the flag bit to a preset value and enters a waiting network configuration mode.
[0044] Here, IoT devices can include smart TVs, smart speakers, toys, wearables, and smart appliances, among others. For example, in a smart home, IoT devices are designed to sense and respond to human presence. When a person arrives home, the car communicates with the garage door to unlock it. Once inside, the thermostat is adjusted to its preferred temperature and the lighting is set to a lower intensity and color because the user's smartwatch data indicates that it is a stressful day. Other smart home devices include sprinklers that adjust their watering based on the weather forecast and robotic vacuum cleaners that learn which areas of the house are cleaned most often.
[0045] In some possible implementations, when the server receives the information to be restored to factory, it sends a factory restore instruction to the IoT device; after the IoT device receives the factory restore instruction, it sets the flag to a preset value and enters the waiting network configuration mode. The information to be restored to factory is used to indicate that the IoT device needs to be restored to factory settings, so as to trigger the server to send a factory restore instruction to the IoT device. The information to be restored to factory can be triggered by an application that controls the IoT device, or the IoT device can call a preset function interface through a case or command line interface to send a factory restore request to the server. After receiving the request, the server sends a factory restore instruction to the application to inform the user that the IoT device needs to be restored to factory settings; in response to the instruction, the application deletes the relevant data of the IoT device, such as the function card used to enter the IoT device, and feeds back a deleted message to the server to inform the server that the relevant data has been deleted. In this case, it is determined that the server receives the information to be restored to factory, which triggers the server to send a factory restore instruction to the IoT device.
[0046] In some possible implementations, after receiving the factory restore command, the IoT device sets the flag to a preset value. For example, the preset value can be set to 1, indicating that the IoT device has received the factory restore command. At the same time, the IoT device clears the key and identification data between the device and the server, and enters the waiting network configuration mode. The waiting network configuration mode is a wireless access point mode. The IoT device in the waiting network configuration mode is equivalent to a bridge connecting the wired network and the wireless network. It can connect various wireless network clients together and then connect the wireless network to the Ethernet. In this way, after the IoT device enters the waiting network configuration mode, it can establish a connection with the application and the server, that is, the IoT device is waiting for network configuration.
[0047] Step S102: when it is detected that the flag bit is the preset value, configure the network binding data of the Internet of Things device in the waiting network configuration mode.
[0048] Here, when the server detects that the flag bit of the IoT device is a preset value, the server is informed that the IoT device has received the factory reset instruction, and then the IoT device in the waiting network configuration mode configures the network binding data to realize the network configuration of the IoT device. The network binding data is used to represent the communication data of the IoT device interacting with the server and the application in the network, and the network binding data includes: network authentication data for authenticating the IoT device, configuration data for the IoT device (for example, the name and serial number of the IoT device), authentication protocol, and function cards in the application to control the IoT device.
[0049] In some possible implementations, the network binding data of the IoT device in the waiting network configuration mode is configured to establish a communication relationship between the IoT device, the server, and the application. The server first unbinds the IoT device and deletes the binding data of the IoT device under the unbinding relationship, and then rebinds the IoT device to configure the network authentication data of the IoT device, the configuration data of the IoT device (e.g., the name and serial number of the IoT device), the authentication protocol, and other network binding data.
[0050] Step S103: in response to completing the configuration of the network binding data, outputting prompt information.
[0051] Here, the configuration process of the network binding data of the IoT device is completed, indicating that the IoT device is successfully configured, that is, the IoT device is successfully connected to the network controlled by the server and the application, and can interact with the server and the application. The server feeds back prompt information to the application and the IoT device, and the prompt information is used to prompt the IoT device that the network configuration is successful.
[0052] In an embodiment of the present application, when the server receives the information to be restored to factory settings, it sends a factory restore instruction to the IoT device, and when it detects that the flag bit is a preset value, it configures the IoT device for networking, thereby enabling the server and the IoT device to synchronously learn that the IoT device needs to be restored to factory settings, and thus more accurately complete the networking of the IoT device to facilitate control of the IoT device.
[0053] In some embodiments, after the IoT device receives the factory reset instruction and sets the flag bit to a preset value to enter the waiting network configuration mode, the current network binding relationship of the IoT device is first released, and then the IoT device is re-bound to achieve the re-network configuration of the IoT device, that is, the above step S102 can be performed by Figure 2 The steps shown are implemented, Figure 2 Another implementation flow diagram of a method for restoring factory settings provided in an embodiment of the present application, combined with Figure 2 The steps shown are explained below:
[0054] Step S201, when it is detected that the flag bit is the preset value, the current network binding relationship of the IoT device is untied, the network configuration data between the IoT device and the server is deleted, and a data deletion instruction is sent to the application associated with the IoT device, so that the application deletes the associated data between the IoT device and the application.
[0055] Here, when the server detects that the flag of the IoT device is set to a preset value, it is informed that the IoT device has received a factory reset instruction. The server unbinds the current network binding relationship of the IoT device; in this way, the IoT device is unbound from the server and the application. The server deletes the network configuration data between the IoT device and the server, and sends a data deletion instruction to the application to notify the application to delete the function card that controls the IoT device, the network authentication data of the IoT device in the application, the authentication protocol of the IoT device in the application, and other related data; the network configuration data between the IoT device and the server is used to represent the data required for communication between the IoT device and the server, including: the communication protocol between the IoT device and the server, the configuration data of the server for the IoT device (for example, the name and serial number of the IoT device identified in the server), and the authentication protocol between the IoT device and the server. In this way, both the server and the application are unbound from the IoT device, which facilitates the reconfiguration of the network of the IoT device.
[0056] In some possible implementations, the application associated with the IoT device may be an application installed on a terminal that controls the IoT device. For example, the IoT device is a smart speaker, and the application may be an application installed on a user's mobile phone. The display interface of the application includes multiple function cards, and each function card controls a corresponding IoT device.
[0057] Step S202: determining the relationship to be bound among the IoT device, the server, and the application.
[0058] Here, the relationship to be bound includes: the connection relationship between the IoT device, the server and the application. The relationship to be bound between the IoT device, the server and the application represents the binding relationship that the IoT device currently needs to establish, that is, when the IoT device needs to be restored to factory settings, the binding relationship between the IoT device, the server and the application needs to be re-established. In other words, the relationship to be bound meets the communication requirements of the IoT device, the server and the application after the factory settings are restored.
[0059] Step S203: reconfigure the target network configuration data between the IoT device in the network configuration mode and the server, and the target association data between the IoT device and the application based on the relationship to be bound.
[0060] Here, the server reconfigures the network binding data of the IoT device in the network configuration mode based on the relationship to be bound. According to the relationship to be bound, the authentication data, communication protocol, configuration data, and network binding data such as the function card of the application required to establish the connection between the IoT device and the server and the application are determined. In this way, after the network binding data is reconfigured, the function card of the application is replaced with the function card of the re-determined application. The display form of the function card of the re-determined application can be the same as the display form of the historical function card, but the configuration data and authentication data of the IoT device associated with the re-determined function card of the application are different from the configuration data and authentication data of the IoT device associated with the deleted function card.
[0061] In a specific example, taking the IoT device as a smart speaker, if the user changes the mobile phone, the smart speaker needs to be restored to factory settings so that the smart speaker can be bound to the application on the new phone; in this way, the server releases the current binding relationship of the smart speaker and establishes a new binding relationship so that the application on the new phone can control the smart speaker.
[0062] In an embodiment of the present application, the server first unbinds the current network binding relationship of the IoT device, and the application deletes the current network binding data of the IoT device, so that the server reconfigures the network binding data of the IoT device by determining the latest relationship to be bound of the IoT device, that is, reconfigures the network of the IoT device, so that the IoT device can interact with the current application and server, so that the IoT device can be controlled in time through the application.
[0063] In some embodiments, in the following three cases, the server determines that the information to be restored to factory is received, and sends a factory restoration instruction to the IoT device, wherein:
[0064] Case 1: Triggered by the application, the server sends a factory reset command to the IoT device, which can be achieved by the following steps:
[0065] In the first step, the application sends a factory reset request to the server.
[0066] Here, the factory reset request of the IoT device is fed back to the server through the application on the user side. In some possible implementations, the user feeds back the factory reset request of the IoT device to the server by clicking or touching the application, and notifies the server that the IoT device needs to be restored to factory settings.
[0067] In the second step, the server receives a factory restore request for the IoT device fed back by an application associated with the IoT device, determines that the information to be restored to factory is received, and sends the factory restore instruction to the IoT device.
[0068] Here, the server receives the factory reset request fed back by the application, that is, it knows that the IoT device needs to be reset to factory settings, so the server sends a factory reset instruction to the IoT device to instruct the IoT device to reset to factory settings. In this way, the application associated with the IoT device triggers the server to send the factory reset instruction, thereby executing the factory reset operation, and the IoT device can be unbound anytime and anywhere, and the IoT device can be used flexibly.
[0069] Case 2: The IoT device calls the preset function interface to trigger the server to send a factory reset instruction. This can be achieved by following the steps below:
[0070] In the first step, the IoT device calls the preset function interface to send a factory reset request to the server.
[0071] Here, the IoT device can call a preset function interface through a command line interface or a key to send a factory reset request to the server through the preset function interface. The preset function interface can be any type of data interface for sending a request through the interface.
[0072] In the second step, the server receives the factory restore request and sends a factory restore instruction to the application associated with the IoT device.
[0073] Here, the server sends a factory restore instruction to the application to inform the application that the IoT device is ready to be restored to factory settings.
[0074] In the third step, the application receives the factory restore instruction, deletes the associated data between the IoT device and the application, and feeds back deleted information indicating that the data has been deleted to the server.
[0075] Here, the associated data between the IoT device and the application is used to represent the data required for the IoT device to interact with the application, such as the function card on the application used to control the IoT device, the configuration data of the IoT device on the terminal to which the application belongs (such as the name of the IoT device, the protocol data for binding with the terminal, etc.), and the configuration data of the IoT device in the application (such as the name of the IoT device in the application, the communication protocol for interacting with the application, etc.). After receiving the factory restore instruction, the application deletes the associated data such as the function card of the IoT device in the application, and at the same time feeds back to the server the deleted information indicating that the data has been deleted.
[0076] In the fourth step, upon receiving the deletion information of the associated data fed back by the application, the server determines that the information to be restored to factory settings has been received, and sends the factory restoration instruction to the IoT device.
[0077] Here, after receiving the deleted information fed back by the application, the server learns that the associated data has been deleted in the application, indicating that the server needs to reconfigure the associated data between the application and the IoT device. Therefore, the server sends a factory restore instruction to the IoT device to facilitate the factory restore operation. In this way, the IoT device synchronizes the factory restore to the server by calling the preset function interface, which can effectively solve the problem that the user cannot control the device through the application due to abnormal problems on the application side. In this way, the factory restore can be synchronized between the IoT device and the server, and the application can better control the IoT device; and the IoT device triggers the server to send a factory restore instruction, so that the factory settings can be restored even if the device is disconnected from the network.
[0078] Case 3: After the network configuration of the IoT device fails, the IoT device calls the preset function interface to send a factory reset request to the server, which can be achieved through the following process:
[0079] First, when at least two consecutive network configuration failures occur during the configuration process of the network binding data of the Internet of Things device, a factory reset request is received by the Internet of Things device calling the preset function interface.
[0080] Here, if the IoT device is interrupted during the network configuration process, that is, the network configuration fails, the device is restarted and the identification information is obtained, so that the device enters the client mode. The IoT device in client mode can be linked to the network signal sent by other routers in network communication. After the IoT device enters the client mode, it enters the process of network parameter configuration again, including: first scanning the IoT device through the application scan, and then, if the IoT device is scanned, a connection relationship between the IoT device, the server and the application is established, that is, network configuration is performed. If the network configuration fails again, the IoT device sends a factory restore request to the server by calling the preset function interface. If the network configuration is successful again, the application will feedback the factory restore request of the IoT device to the server to trigger the server to issue a factory restore instruction.
[0081] Then, in the case of receiving a factory restore request sent by the IoT device calling a preset function interface, sending a factory restore instruction to the application associated with the IoT device, so that the application deletes the associated data between the IoT device and the application;
[0082] Finally, when the deletion information of the associated data fed back by the application is received, it is determined that the information to be restored to factory settings is received, and the factory restoration instruction is sent to the IoT device.
[0083] In an embodiment of the present application, if at least two consecutive network configuration failures occur during the configuration process of the network binding data of the IoT device, the IoT device calls a preset function interface to send a factory restore request to the server to trigger the server to issue a factory restore instruction, thereby effectively solving the abnormal power failure of the IoT device during the factory restore process, resulting in an abnormal problem of restoring the factory settings.
[0084] The present application embodiment provides a method for restoring factory settings, which can be executed by an IoT device, such as Figure 3 As shown, Figure 3 A schematic diagram of an interactive process of restoring factory settings provided in an embodiment of the present application, combined with Figure 3 The steps shown are explained below:
[0085] Step S301: upon receiving the information to be restored to factory, the server sends a factory restore instruction to the IoT device.
[0086] Step S302: When the IoT device receives the factory reset instruction sent by the server, it sets the flag bit to a preset value and enters a waiting network configuration mode.
[0087] Here, after receiving the factory reset command sent by the server, the IoT device sets the flag bit to 1 and enters the waiting network configuration mode, that is, the AP mode of the IoT device, waiting for network configuration.
[0088] Step S303: The IoT device stores the flag bit in a preset storage repository so that the server can detect the flag bit.
[0089] Here, the IoT device stores a flag bit set to a preset value in a flash memory (FLASH), so that the server reads from the flash memory and detects whether the flag bit is the preset value.
[0090] Step S304: When the server detects that the flag bit is the preset value, the server configures the network binding data of the IoT device in the waiting network configuration mode.
[0091] Step S305: In response to completing the configuration of the network binding data, the server outputs prompt information.
[0092] Step S306: The IoT device receives the prompt information fed back by the server.
[0093] Here, the prompt information is used to prompt the Internet of Things device in the waiting network configuration mode that the network binding data has been configured. After the Internet of Things device receives the prompt information fed back by the server, it is informed that it can communicate with the application and the server.
[0094] In an embodiment of the present application, after the IoT device receives the factory restore instruction issued by the server, the flag is set to a preset value, so that when the server detects that the flag is the preset value, it configures the IoT device for the network, thereby achieving synchronization between the server and the IoT device, and then more accurately completing the network configuration of the IoT device to facilitate the control of the IoT device.
[0095] In some embodiments, after receiving the factory reset instruction sent by the server, the IoT device enters the waiting network configuration mode by reading the identification information, that is, the above step S302 can be implemented by the following steps S321 to S323 (not shown):
[0096] Step S321, when receiving the factory reset instruction sent by the server, the flag is set to the preset value and the restart state is entered.
[0097] Here, the IoT device receives the factory reset command, sets the flag to the preset value, and then automatically restarts.
[0098] In some possible implementations, after receiving the factory reset instruction sent by the server, the IoT device sets the flag bit and clears the IoT device's identification information, which includes a key and a service set identifier for the IoT device to communicate.
[0099] Step S322, in response to completing the restart state, reading the identification information of the Internet of Things device.
[0100] Here, after the IoT device automatically restarts, the IoT device reads the identification information of the IoT device from a preset storage repository, for example, the identification information of the IoT device is read from a flash memory.
[0101] Step S323: In response to not reading the identification information, entering the waiting network configuration mode.
[0102] Here, if the IoT device cannot read the identification information from the flash memory, it enters the AP mode to wait for network configuration. In this way, after the IoT device enters the restart state, if the IoT device identification information is not read, it enters the AP mode to wait for network configuration; in this way, the IoT device can be synchronized with the server to restore the factory settings.
[0103] In some embodiments, if the configuration process of the network binding data of the IoT device fails to configure the network for multiple times in a row, the IoT device sends a factory reset request to the server by calling a preset function interface, so that the server and the IoT device perform the factory reset operation synchronously, which can be achieved by the following steps:
[0104] The first step is to enter a restart state in the event that a network configuration failure occurs during the configuration process of the network binding data of the IoT device to read the identification information of the IoT device.
[0105] Here, after the network configuration fails, the IoT device automatically restarts to read the identification information of the IoT device from the flash memory. For example, the network configuration failure of the IoT device can be understood as the network configuration interruption of the IoT device due to token failure and other problems during the network configuration process.
[0106] The second step is to enter the client mode in response to reading the identification information, and send a broadcast packet carrying the device identification to the application associated with the IoT device, so that when the application scans the device identification in the broadcast packet, it will feedback the factory restore request of the IoT device to the server.
[0107] Here, if the IoT device reads the identification information, the IoT device enters the client mode and outputs a broadcast packet carrying the device identification, which may include the device serial number and device name, etc. The user terminal scans the broadcast packet through the application that controls the IoT device to identify the device identification. If the application does not scan the device identification, it continues to scan until the device identification is scanned. After that, the application feeds back the factory reset request of the IoT device to the server to trigger the server to re-configure the IoT device.
[0108] In the third step, upon receiving the factory restore request of the IoT device fed back by the application, the server sends a factory restore instruction to the IoT device, so that the IoT device sets the flag to a preset value and enters a waiting network configuration mode; when it is detected that the flag is the preset value, the network binding data of the IoT device in the waiting network configuration mode is configured.
[0109] In the fourth step, when the network configuration process of the network binding data fails again, a preset function interface is called to send a factory restore request to the server, so that the server sends the factory restore instruction.
[0110] Here, if the network binding data configuration process is successfully re-configured, the entire process is terminated. If the network binding data configuration process is re-configured, the IoT device calls the preset function interface through a key or command line interface to send a factory reset request to the server, triggering the server to perform a factory reset on the IoT device.
[0111] In this way, when the Internet of Things device fails to configure the network during the network configuration process, it enters the restart process and enters the client mode through the identification information read. After that, the Internet of Things device enters the network configuration process again, and the application scans the broadcast packet to determine whether the device identification is scanned. If the device identification is scanned, the server is triggered by the application to configure the device again, that is, the device waits for factory settings to be restored. If the Internet of Things device fails to configure the network again, a factory restore request is sent to the server by calling the preset function interface, so that the server issues the factory restore instruction and executes the operation of restoring the factory settings of the Internet of Things device. In this way, even in the event of an emergency such as an abnormal power outage in the Internet of Things device, the factory settings of the Internet of Things device can still be restored.
[0112] The following describes the application of the factory reset method provided in an embodiment of the present application in an actual scenario, taking a factory reset method applicable to an IoT device as an example.
[0113] In the embodiment of the present application, based on oftAP network configuration technology, a method for restoring factory settings is proposed, which can be implemented in the following three ways:
[0114] Method 1: Triggering a factory reset on the application side, including the following steps:
[0115] Step 1: After the IoT device is successfully connected to the network, the user sends a request to restore the factory settings to the server through the application.
[0116] Here, the user restores the IoT device to factory settings (or deletes the IoT device) through the application, and the application informs the server that the network configuration data related to the IoT device needs to be deleted.
[0117] Step 2: The server receives the request to restore factory settings and sends a command to the IoT device to restore factory settings. The server deletes the original network configuration data, and the IoT device re-enters AP mode and waits for network configuration.
[0118] Step 3: The IoT device receives the factory reset instruction and marks the factory reset flag as 1, saves the flag in the flash memory, and clears the SSID and password.
[0119] Step 4: The IoT device automatically restarts. If the IoT device cannot read the SSID and password, it enters AP mode and waits for network configuration.
[0120] Step 5: The IoT device is reconfigured, and the data of the configuration process is saved in the link_running file. The IoT device is connected to the cloud server. The server detects that the flag value of the factory reset mark is 1, unbinds the IoT device, notifies the application to delete the device card and other data, and then binds the IoT device to the application.
[0121] Step 6: The IoT device and server are successfully networked, and the server informs the IoT device and application.
[0122] In method one, by restoring the factory settings through the application, you can unbind the IoT device anytime and anywhere and use the IoT device flexibly.
[0123] Method 2: When the IoT device is in the network configuration state, the IoT device is restored to factory settings, which can include the following steps:
[0124] Step 1: The device calls the factory reset function interface through the command line interface (CLI) or by pressing a button to send a factory reset command to the server.
[0125] Step 2: After receiving the command, the server sends a command to the user's mobile application to inform the user that the IoT device has been restored to factory settings.
[0126] Step 3: After receiving the instruction, the application starts to directly delete the data related to the application side, and the application sends an instruction to the server to inform the server that the application side has deleted the relevant data.
[0127] Step 4: After receiving the instruction from the application side, the server sends the instruction to the IoT device.
[0128] Step 5: The IoT device receives the factory reset instruction sent by the server, marks the factory reset flag as 1, saves it in the flash, and clears the SSID and password.
[0129] Step 6: Restart the IoT device. If the IoT device cannot read the SSID and password, it will enter AP mode and wait for network configuration.
[0130] Step 7: The IoT device is reconfigured. The data of the configuration process is saved in the link_running file. The device is connected to the cloud server. The server detects that the flag value of restoring factory settings is 1, unbinds the IoT device, notifies the application to delete the device card and other data, and then binds it again.
[0131] Step 8: The IoT device and server are successfully networked, and the server informs the IoT device and application.
[0132] In method 2, the factory settings restored on the device side can be synchronized to the server, which can effectively solve the abnormal problem on the application side. The application will have the problem of losing the device card, which makes the user unable to control the IoT device through the application. In this case, the user needs to issue a factory settings restore operation from the IoT device side, and then re-configure the network through the application. Moreover, the factory settings on the device side can be restored even if the IoT device is disconnected from the network.
[0133] Method 3: When the IoT device fails to be configured, restore the factory settings, which may include the following process:
[0134] If the IoT device fails to configure the network at 99% due to token failure or other problems, the IoT device will restart. Since the SSID and password are obtained, the IoT device enters the client (station) mode and enters the network configuration process again. The mobile application cannot scan the device again, and the IoT device will fail to configure the network again. At this time, the device can be restored to factory settings through CLI or buttons, and the previous network configuration data can be deleted. The device enters AP mode, and the mobile application can scan the device ID and configure the network again to complete the network configuration. In some possible implementations, this can be done through Figure 4 The steps shown are to restore the device to factory settings when the IoT device fails to be configured on the network:
[0135] Step S401: The mobile phone application scans the broadcast packet of the IoT device and determines whether a device identification is scanned.
[0136] Here, if the mobile phone application scans the IoT device, the process goes to step S402 ; if the mobile phone application does not scan the device, the process returns to step S401 .
[0137] Step S402: configure the IoT device to a network and determine whether the configuration is successful.
[0138] Here, if the network configuration of the IoT device is unsuccessful, proceed to step S403; if the network configuration of the IoT device is successful, proceed to step S405.
[0139] Step S403: restore the IoT device to factory settings through CLI or keystrokes.
[0140] Step S404, deleting historical network configuration data, so that the IoT device enters AP mode.
[0141] Here, after the IoT device enters the AP mode, it waits for network configuration, so that the IoT device calls the function interface to trigger the server to restore the factory settings of the IoT device.
[0142] Step S405, the IoT device waits for restoration to factory settings and successfully completes re-networking.
[0143] In method three, the problem of abnormal power failure of IoT devices during factory reset, resulting in abnormal factory reset, can be effectively solved.
[0144] In the embodiment of the present application, any one of the above methods 1 to 3 can effectively solve the problem that the factory settings restoration between the device and the server are not synchronized, causing the application to display the device abnormally and unable to control the IoT device normally.
[0145] Based on the foregoing embodiments, the embodiments of the present application provide a device for restoring factory settings, which includes the units included and the modules included in the units, and can be implemented by a processor in a computer device; of course, it can also be implemented by a specific logic circuit; in the implementation process, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA), etc.
[0146] The present application embodiment provides a device for restoring factory settings. Figure 5 A schematic diagram of the structure of a device for restoring factory settings provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the factory reset device 500 includes:
[0147] The first sending module 501 is used to send a factory restore instruction to the IoT device when receiving the factory restore information, so that the IoT device sets the flag bit to a preset value and enters a waiting network configuration mode;
[0148] A first configuration module 502 is used to configure network binding data of the Internet of Things device in the waiting network configuration mode when it is detected that the flag bit is the preset value;
[0149] The first output module 503 is used to output prompt information in response to completing the configuration of the network binding data.
[0150] In some embodiments, the first configuration module 502 includes:
[0151] A first binding submodule is used to unbind the current network binding relationship of the IoT device, delete the network configuration data between the IoT device and the server, and send a data deletion instruction to the application associated with the IoT device, so that the application deletes the associated data between the IoT device and the application, when detecting that the flag bit is the preset value;
[0152] A first determination submodule is used to determine the relationship to be bound between the IoT device, the server and the application;
[0153] The first configuration submodule is used to reconfigure the target network configuration data between the Internet of Things device in the network configuration mode and the server, and the target association data between the Internet of Things device and the application based on the relationship to be bound; wherein the network binding data includes: the target network configuration data and the target association data.
[0154] In some embodiments, the apparatus further comprises:
[0155] The second sending module is used to determine that the information to be restored to factory is received, and send the factory restoration instruction to the Internet of Things device when a factory restoration request of the Internet of Things device is received from an application associated with the Internet of Things device.
[0156] In some embodiments, the apparatus further comprises:
[0157] A third sending module is used to send a factory restore instruction to the application associated with the IoT device when receiving a factory restore request sent by the IoT device calling a preset function interface, so that the application deletes the associated data between the IoT device and the application;
[0158] The fourth sending module is used to determine that the information to be restored to factory mode is received when the deletion information of the associated data fed back by the application is received, and send the factory restoration instruction to the Internet of Things device.
[0159] In some embodiments, the apparatus further comprises:
[0160] The first receiving module is used to receive a factory reset request sent by the Internet of Things device by calling the preset function interface when at least two consecutive network configuration failures occur during the configuration process of the network binding data of the Internet of Things device.
[0161] The present application embodiment further provides a device for restoring factory settings. Figure 6 A schematic diagram of the structure of a device for restoring factory settings provided in an embodiment of the present application is shown in FIG. Figure 6 As shown, the factory reset device 600 includes:
[0162] The first setting module 601 is used to set the flag bit to a preset value and enter a waiting network configuration mode when receiving a factory reset instruction sent by the server;
[0163] A first storage module 602, configured to store the flag bit in a preset storage repository so that the server can detect the flag bit;
[0164] The second receiving module 603 is used to receive the prompt information fed back by the server; wherein the prompt information is used to prompt that the network binding data of the Internet of Things device in the waiting network configuration mode has been configured.
[0165] In some embodiments, the first setting module 601 includes:
[0166] A first setting submodule is used to set the flag bit to the preset value and enter a restart state when receiving a factory reset instruction sent by the server;
[0167] A first reading submodule, configured to read identification information of the Internet of Things device in response to completing the restart state;
[0168] The first entry submodule is used to enter the waiting network configuration mode in response to the identification information not being read.
[0169] In some embodiments, the apparatus further comprises:
[0170] A first restart module, configured to enter a restart state to read identification information of the Internet of Things device when a network configuration failure occurs during the configuration process of the network binding data of the Internet of Things device;
[0171] a fifth sending module, configured to enter a client mode in response to reading the identification information, and send a broadcast packet carrying the device identification to an application associated with the IoT device, so that the application, when scanning the device identification in the broadcast packet, feeds back a factory restore request for the IoT device to the server;
[0172] The sixth sending module is used to call a preset function interface to send a factory reset request to the server when the network configuration process of the network binding data fails to configure the network again, so that the server sends the factory reset instruction.
[0173] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to execute the method described in the above method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.
[0174] It should be noted that in the embodiment of the present application, if the above-mentioned method of restoring factory settings is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a disk or an optical disk. In this way, the embodiment of the present application is not limited to any specific hardware, software or firmware, or any combination of hardware, software, and firmware.
[0175] An embodiment of the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, some or all of the steps in the above method are implemented.
[0176] The embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, some or all of the steps in the above method are implemented. The computer-readable storage medium can be transient or non-transient.
[0177] An embodiment of the present application provides a computer program, including a computer-readable code. When the computer-readable code is run in a computer device, a processor in the computer device executes some or all of the steps for implementing the above method.
[0178] The embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and when the computer program is read and executed by a computer, some or all of the steps in the above method are implemented. The computer program product can be implemented specifically by hardware, software or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium, and in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK) and the like.
[0179] It should be noted here that the description of the various embodiments above tends to emphasize the differences between the various embodiments, and the same or similar aspects can be referenced to each other. The description of the above device, storage medium, computer program and computer program product embodiments is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the embodiments of the device, storage medium, computer program and computer program product of this application, please refer to the description of the method embodiment of this application for understanding.
[0180] It should be noted that Figure 7 A hardware entity diagram of an electronic device that restores factory settings in an embodiment of the present application is shown in FIG. Figure 7 As shown, the hardware entity of the electronic device 700 includes: a processor 701, a communication interface 702 and a memory 703, wherein:
[0181] Processor 701 generally controls the overall operation of computer device 700 .
[0182] The communication interface 702 enables the computer device to communicate with other terminals or servers through a network.
[0183] The memory 703 is configured to store instructions and applications executable by the processor 701, and can also cache data to be processed or processed by the processor 701 and each module in the computer device 700 (for example, image data, audio data, voice communication data, and video communication data), which can be implemented by flash memory (FLASH) or random access memory (Random Access Memory, RAM). Data transmission can be performed between the processor 701, the communication interface 702, and the memory 703 through the bus 704.
[0184] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the serial number of each step / process mentioned above does not mean the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The serial numbers of the embodiments of the present application mentioned above are for description only and do not represent the advantages and disadvantages of the embodiments.
[0185] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.
[0186] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.
[0187] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0188] In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be a separate unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.
[0189] A person skilled in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, etc., various media that can store program codes.
[0190] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can essentially or in other words, the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.
[0191] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.
Claims
1. A method for restoring factory settings, characterized in that: The method comprises: When receiving the information to be restored to factory, a factory restore instruction is issued to the IoT device, so that the IoT device sets the flag bit to a preset value and enters a waiting network configuration mode; When it is detected that the flag bit is the preset value, the current network binding relationship of the IoT device is unbound, the network configuration data between the IoT device and the server is deleted, and a data deletion instruction is sent to the application associated with the IoT device, so that the application deletes the associated data between the IoT device and the application; Determining a relationship to be bound among the IoT device, the server, and the application; Based on the relationship to be bound, reconfigure the target network configuration data between the IoT device in the network configuration mode and the server, and the target association data between the IoT device and the application; wherein the network binding data includes: the target network configuration data and the target association data; In response to completing the configuration of the network binding data, prompt information is output.
2. The method according to claim 1, characterized in that The method further comprises: In the case of receiving a factory restore request for the IoT device fed back by an application associated with the IoT device, it is determined that the information to be restored to factory is received, and the factory restore instruction is issued to the IoT device.
3. The method according to claim 1, characterized in that The method further comprises: In the case of receiving a factory restore request sent by the IoT device calling a preset function interface, sending a factory restore instruction to an application associated with the IoT device, so that the application deletes the associated data between the IoT device and the application; When the deletion information of the associated data fed back by the application is received, it is determined that the information to be restored to factory is received, and the factory restoration instruction is sent to the Internet of Things device.
4. The method according to claim 3, characterized in that Before the method of sending a factory restore instruction to the application program upon receiving a factory restore request sent by the IoT device by calling a preset function interface so that the application program deletes the associated data of the IoT device, the method further includes: In the event that at least two consecutive network configuration failures occur during the configuration process of the network binding data of the Internet of Things device, a factory reset request is received by the Internet of Things device by calling the preset function interface.
5. A method for restoring factory settings, characterized in that: The method comprises: When receiving the factory reset command sent by the server, the flag is set to the preset value and the network configuration waiting mode is entered; Storing the flag bit in a preset storage repository so that the server can detect the flag bit; Receive the prompt information fed back by the server; wherein the prompt information is used to prompt that the network binding data of the Internet of Things device in the waiting network configuration mode has been configured; Wherein, when the server detects that the flag bit is the preset value, the network binding data of the Internet of Things device in the waiting network configuration mode is configured by the server; the server is used to: when it is detected that the flag bit is the preset value, unbind the current network binding relationship of the Internet of Things device, delete the network configuration data between the Internet of Things device and the server, and send a data deletion instruction to the application associated with the Internet of Things device, so that the application deletes the associated data between the Internet of Things device and the application; determine the relationship to be bound among the Internet of Things device, the server and the application; based on the relationship to be bound, reconfigure the target network configuration data between the Internet of Things device in the waiting network configuration mode and the server, as well as the target associated data between the Internet of Things device and the application; wherein the network binding data includes: the target network configuration data and the target associated data.
6. The method according to claim 5, characterized in that When receiving the factory reset instruction sent by the server, the flag is set to a preset value and the network configuration waiting mode is entered, including: When receiving a factory reset instruction sent by the server, the flag bit is set to the preset value and a restart state is entered; In response to completing the restart state, reading identification information of the Internet of Things device; In response to not reading the identification information, entering the waiting network configuration mode.
7. The method according to claim 5, characterized in that The method further comprises: In the event that network configuration fails during the configuration process of the network binding data of the IoT device, entering a restart state to read identification information of the IoT device; In response to reading the identification information, entering the client mode, and sending a broadcast packet carrying the device identification to the application associated with the IoT device, so that the application, when scanning the device identification in the broadcast packet, feeds back a factory restore request for the IoT device to the server; In the case that the network configuration process of the network binding data fails again, a preset function interface is called to send a factory restore request to the server, so that the server sends the factory restore instruction.
8. A device for restoring factory settings, characterized in that: The factory reset device comprises: A first sending module is used to send a factory restore instruction to the IoT device when receiving the information to be restored to factory, so that the IoT device sets the flag bit to a preset value and enters a waiting network configuration mode; A first binding submodule is used to unbind the current network binding relationship of the IoT device, delete the network configuration data between the IoT device and the server, and send a data deletion instruction to the application associated with the IoT device, so that the application deletes the associated data between the IoT device and the application, when detecting that the flag bit is the preset value; A first determination submodule is used to determine the relationship to be bound between the IoT device, the server and the application; A first configuration submodule is used to reconfigure the target network configuration data between the IoT device in the network configuration mode and the server, and the target association data between the IoT device and the application program based on the relationship to be bound; wherein the network binding data includes: the target network configuration data and the target association data; A first configuration module is used to configure the network binding data of the Internet of Things device in the waiting network configuration mode when it is detected that the flag bit is the preset value; The first output module is used to output prompt information in response to completing the configuration of the network binding data.
9. A device for restoring factory settings, characterized in that: The factory reset device comprises: The first setting module is used to set the flag bit to a preset value and enter the waiting network configuration mode when receiving the factory reset instruction issued by the server; wherein, when the server detects that the flag bit is the preset value, the network binding data of the Internet of Things device in the waiting network configuration mode is configured by the server; the server is used to: when detecting that the flag bit is the preset value, unbind the current network binding relationship of the Internet of Things device, delete the network configuration data between the Internet of Things device and the server, and send a data deletion instruction to the application associated with the Internet of Things device so that the application deletes the associated data between the Internet of Things device and the application; determine the waiting binding relationship between the Internet of Things device, the server and the application; based on the waiting binding relationship, reconfigure the target network configuration data between the Internet of Things device in the waiting network configuration mode and the server, as well as the target association data between the Internet of Things device and the application; wherein the network binding data includes: the target network configuration data and the target association data A first storage module, used for storing the flag bit in a preset storage repository so that the server can detect the flag bit; The first receiving module is used to receive the prompt information fed back by the server; wherein the prompt information is used to prompt that the network binding data of the Internet of Things device in the waiting network configuration mode has been configured.
10. A system for restoring factory settings, characterized in that: The factory reset system includes a server and an Internet of Things device; wherein the server is used to execute the method described in any one of claims 1 to 4 above; and the Internet of Things device is used to execute the method described in claims 5 to 7 above.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method described in any one of claims 1 to 4 is implemented; or, when the computer program is executed by a processor, the method described in any one of claims 5 to 7 is implemented.
Citation Information
Patent Citations
Application program management method and device of mobile terminal and mobile terminal
CN103268239A
Terminal information acquisition method and device
CN108206998A
Method and device for unbinding device, and electronic device
CN109219036A
Information processing method and device and storage medium
CN110311916A
Binding method for automatic equipment distribution network and anti-misconfiguration method for the automatic equipment distribution network and cloud server
CN110912761A
