Network processing method and apparatus, electronic device, storage medium, and product

Abstract

The present disclosure relates to a network processing method and device, electronic equipment, storage medium and product. The method comprises: receiving a first notification message sent by a mesh device, the first notification message being used to indicate that the mesh device is in an un-provisioning state; determining whether a local reset of the mesh device occurs; and in response to the local reset of the mesh device, sending network recovery information to the mesh device, wherein the network recovery information is used for the mesh device to recover access to a mesh network. Through the method of the present disclosure, the mesh device that has occurred a local reset can be reconnected to the mesh network without user awareness, and the use convenience of the mesh device is improved.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a network processing method, apparatus, electronic device, storage medium, and product. Background Technology

[0002] With the rapid development of the electronics industry, furniture, home appliances, and other equipment are becoming increasingly intelligent. After purchasing new furniture and appliances, they can be directly connected to a wireless mesh network through a configuration process or connected via a gateway device, and then bound to the user's account. Based on this, it is possible to control furniture and appliances through an application (APP).

[0003] However, furniture and appliances are susceptible to local resets triggered by grid voltage fluctuations or user errors, causing them to go offline and preventing users from controlling them via the app. If users continue to control these offline devices through the app, they must trigger a network configuration process to reconnect them to the mesh network. This reduces the ease of use of furniture and appliances, thus degrading the user experience. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this disclosure provides a network processing method, apparatus, electronic device storage medium and product, which can enable mesh devices that have undergone local reset to reconnect to the mesh network without the user's awareness, thereby improving the ease of use of mesh devices.

[0005] According to a first aspect of the present disclosure, a network processing method is provided, the method comprising: receiving a first notification message sent by a wireless mesh device, the first notification message indicating that the mesh device is in an unconfigured network state; determining whether the mesh device has undergone a local reset; and in response to the mesh device undergoing a local reset, sending network recovery information to the mesh device, wherein the network recovery information is used for the mesh device to restore access to the mesh network.

[0006] In this embodiment, since mesh devices typically transition from a network-configured state to an unconfigured state upon a local reset, a mesh device in an unconfigured state can send a first notification message to indicate its current unconfigured state. Based on this, the gateway device can receive the first notification message, determine whether a local reset has occurred, and, if so, send network recovery information to the mesh device, enabling it to reconnect to the mesh network. This allows the user to reconnect a locally reset mesh device to the mesh network without their knowledge, improving the ease of use of the mesh device.

[0007] In some embodiments, determining whether a mesh device has undergone a local reset includes: sending a first request message to a server device; wherein the first request message is used to request the server device to determine whether a mesh device has undergone a local reset; receiving network recovery information sent by the server device, the network recovery information being sent by the server device when it determines that a mesh device has undergone a local reset; and determining that a mesh device has undergone a local reset in response to receiving the network recovery information sent by the server device.

[0008] In this embodiment, since the server device stores network recovery information of the mesh devices during the network configuration process, the gateway device can obtain the network recovery information of the mesh devices from the server device, thus reducing the storage pressure on the gateway device.

[0009] In some embodiments, sending network recovery information to a mesh device includes: starting a timer in response to receiving a first notification message; and sending network recovery information to the mesh device in response to the timer duration reaching a first duration.

[0010] In this embodiment, it is considered that a local reset of the mesh device may also be a user-triggered reset. If the mesh device reset is user-triggered, the user will reconfigure the mesh device for the network in a short time. However, a reset caused by voltage issues or accidental user touch may not be noticed by the user in a short period of time, resulting in the mesh device being in an unconfigured state for an extended period. Therefore, the gateway device starts timing after receiving the first notification message and sends network recovery information to the mesh device after the timing duration reaches the first duration, so that the mesh device can restore access to the mesh network based on the network recovery information. In this way, the probability of mistaking a normal user reset operation for an accidental user reset and restoring the mesh network of the mesh device can be reduced.

[0011] In some embodiments, sending network recovery information to a mesh device includes: sending a second request message to the mesh device, wherein the second request message is used to request the establishment of a communication connection with the mesh device; and sending network recovery information to the mesh device based on the communication connection.

[0012] In this embodiment of the disclosure, before sending network recovery information to the mesh device, the gateway device may request to establish a communication connection with the mesh device and send the network recovery information to the mesh device based on the established communication connection. Compared with sending network recovery information to the mesh device through a broadcast channel, this can increase the transmission security of network recovery information.

[0013] In some embodiments, the method further includes: receiving a second notification message sent by a mesh device based on a communication connection, wherein the second notification message is sent by the mesh device when the authentication of the server device is successful; and sending network recovery information to the mesh device based on a communication connection, including: in response to receiving the second notification message, sending network recovery information to the mesh device based on a communication connection.

[0014] In this embodiment, the second notification message is sent from the mesh device to the gateway device after successful mutual authentication with the server device. Therefore, the gateway device can determine that the mesh device is an authenticated device based on receiving the second notification message. The gateway device sends network recovery information to the mesh device only after receiving the second notification message, which reduces the risk of unauthorized devices accessing the mesh network.

[0015] In some embodiments, network recovery information includes the device key of the mesh device; in response to a local reset of the mesh device, sending network recovery information to the mesh device includes: in response to a local reset of the mesh device, sending the device key to the mesh device, wherein the device key is used by the mesh device to decrypt the stored network configuration information and restore access to the mesh network based on the decrypted network configuration information.

[0016] In this embodiment, when a local reset occurs, the mesh device can obtain network configuration information and encrypt and store it. Based on this, after receiving the first notification message, the gateway device can obtain the device key of the mesh device from the server device and send the obtained device key to the mesh device. This allows the mesh device to decrypt the network configuration information based on the device key and restore access to the mesh network based on the decrypted network configuration information. Thus, the first restoration of access to the mesh network can be achieved without the user's awareness.

[0017] In some embodiments, the method further includes: receiving a third notification message sent by a mesh device, wherein the third notification message is sent by the mesh device after it has regained access to the mesh network; and the server device sending heartbeat information.

[0018] In this embodiment of the disclosure, after receiving the third notification message, the gateway device sends heartbeat information to the server device, which enables the server device to know the latest status of the mesh device in a timely manner.

[0019] According to a second aspect of the present disclosure, another network processing method is provided, the method comprising: in response to a mesh device being in an unconfigured network state, sending a first notification message, the first notification message indicating that the mesh device is in an unconfigured network state; receiving network recovery information sent by a gateway device, wherein the network recovery information is sent by the gateway device after determining, based on the first notification message, that the mesh device has undergone a local reset; and restoring access to the wireless mesh network based on the network recovery information.

[0020] In some embodiments, network recovery information includes the device key of the mesh device; restoring access to the mesh network based on the network recovery information includes: decrypting locally stored network configuration information based on the device key; and restoring access to the mesh network based on the decrypted network configuration information.

[0021] In some embodiments, the method further includes: in response to triggering a local reset of the mesh device, obtaining the network configuration information required for the mesh device to access the mesh network; and encrypting and storing the network configuration information.

[0022] In some embodiments, receiving network recovery information sent by a gateway device includes: receiving a second request message sent by the gateway device; establishing a communication connection with the gateway device based on the second request message; and receiving network recovery information sent by the gateway device through the communication connection.

[0023] In some embodiments, the method further includes: in response to successful authentication of the server device, sending a second notification message to the gateway device via a communication connection; and receiving network recovery information sent by the gateway device via the communication connection, including: receiving network recovery information sent by the gateway device via the communication connection after receiving the second notification message.

[0024] In some embodiments, the method further includes: in response to the mesh device re-accessing the mesh network, sending a third notification message to the gateway device; wherein the third notification message is used by the gateway device to send heartbeat information to the server device.

[0025] According to a third aspect of the present disclosure, another network processing method is provided, the method comprising: receiving a first request message sent by a gateway device, wherein the first request message is sent by the gateway device after receiving a first notification message sent by a mesh device, the first notification message being used to indicate that the mesh device is in an unconfigured state; determining whether the mesh device has undergone a local reset; and in response to determining that the mesh device has undergone a local reset, sending network recovery information to the gateway device; wherein the network recovery information is used by the gateway device to send to the mesh device so that the mesh device can restore access to the wireless mesh network based on the network recovery information.

[0026] In some embodiments, network recovery information includes a device key of the mesh device; in response to determining that the mesh device has undergone a local reset, sending network recovery information to the gateway device includes: in response to determining that the mesh device has undergone a local reset, sending a device key to the gateway device; wherein the device key is used by the gateway device to send to the mesh device so that the mesh device can decrypt the stored network configuration information based on the device key; the decoded network configuration information is used by the mesh device to restore access to the mesh network.

[0027] In some embodiments, determining whether a mesh device has undergone a local reset includes: determining whether the device information of the mesh device is bound to a user account; and determining that the mesh device has undergone a local reset in response to the device information of the mesh device being bound to a user account.

[0028] In some embodiments, the method further includes: receiving heartbeat information sent by a gateway device; wherein the heartbeat information is sent by the gateway device after receiving a third notification message, and the third notification message is sent by the mesh device to the gateway device after restoring access to the mesh network.

[0029] According to a fourth aspect of the present disclosure, a network processing apparatus is provided, the apparatus comprising: a first receiving module configured to receive a first notification message sent by a wireless mesh device, the first notification message indicating that the mesh device is in an unconfigured state; a determining module configured to determine whether the mesh device has undergone a local reset; and a first sending module configured to send network recovery information to the mesh device in response to the mesh device undergoing a local reset, wherein the network recovery information is used for the mesh device to restore access to the mesh network.

[0030] In some embodiments, the determining module is configured to: send a first request message to the server device; wherein the first request message is used to request the server device to determine whether a local reset has occurred in the mesh device; receive network recovery information sent by the server device, the network recovery information being sent by the server device when it determines that a local reset has occurred in the mesh device; and determine that a local reset has occurred in the mesh device in response to receiving the network recovery information sent by the server device.

[0031] In some embodiments, the first sending module is configured to: start timing in response to receiving a first notification message; and send network recovery information to the mesh device in response to the timing duration reaching a first duration.

[0032] In some embodiments, the first sending module is configured to: send a second request message to the mesh device, wherein the second request message is used to request the establishment of a communication connection with the mesh device; and send network recovery information to the mesh device based on the communication connection.

[0033] In some embodiments, the apparatus further includes: a second receiving module configured to receive a second notification message sent by the mesh device based on a communication connection, wherein the second notification message is sent by the mesh device when the authentication of the server device is successful; and a first sending module configured to send network recovery information to the mesh device based on the communication connection in response to receiving the second notification message.

[0034] In some embodiments, the network recovery information includes the device key of the mesh device; the first sending module is configured to: in response to a local reset of the mesh device, send the device key to the mesh device, wherein the device key is used by the mesh device to decrypt the stored network configuration information and restore access to the mesh network based on the decrypted network configuration information.

[0035] In some embodiments, the apparatus further includes: a third receiving module configured to receive a third notification message sent by the mesh device, wherein the third notification message is sent by the mesh device after it has regained access to the mesh network; and a server device sending heartbeat information.

[0036] According to a fifth aspect of the present disclosure, another network processing apparatus is provided, the apparatus comprising: a first sending module configured to send a first notification message in response to a mesh device being in an unconfigured network state, the first notification message indicating that the mesh device is in an unconfigured network state; a receiving module configured to receive network recovery information sent by a gateway device, wherein the network recovery information is sent by the gateway device after determining, based on the first notification message, that the mesh device has undergone a local reset; and a recovery module configured to restore access to the wireless mesh network based on the network recovery information.

[0037] In some embodiments, network recovery information includes the device key of the mesh device; the recovery module is configured to: decrypt the locally stored network configuration information based on the device key; and restore access to the mesh network based on the decrypted network configuration information.

[0038] In some embodiments, the apparatus further includes: an acquisition module configured to acquire network configuration information required for the mesh device to access the mesh network in response to triggering a local reset of the mesh device; and an encryption module configured to encrypt and store the network configuration information.

[0039] In some embodiments, the receiving module is configured to: receive a second request message sent by the gateway device; establish a communication connection with the gateway device based on the second request message; and receive network recovery information sent by the gateway device through the communication connection.

[0040] In some embodiments, the apparatus further includes: a second sending module configured to send a second notification message to a gateway device via a communication connection in response to successful authentication of the server device; and a receiving module configured to receive network recovery information sent by the gateway device via a communication connection after receiving the second notification message.

[0041] In some embodiments, the apparatus further includes: a third sending module configured to send a third notification message to a gateway device in response to the mesh device re-accessing the mesh network; wherein the third notification message is used by the gateway device to send heartbeat information to the server device.

[0042] According to a sixth aspect of the present disclosure, another network processing apparatus is provided, the apparatus comprising: a first receiving module configured to receive a first request message sent by a gateway device, wherein the first request message is sent by the gateway device after receiving a first notification message sent by a mesh device, the first notification message being used to indicate that the mesh device is in an unconfigured network state; a determining module configured to determine whether a local reset has occurred in the mesh device; and a sending module configured to send network recovery information to the gateway device in response to determining that a local reset has occurred in the mesh device; wherein the network recovery information is sent by the gateway device to the mesh device to enable the mesh device to restore access to the wireless mesh network based on the network recovery information.

[0043] In some embodiments, the network recovery information includes a device key for the mesh device; a sending module is configured to: in response to determining that a local reset has occurred in the mesh device, send the device key to the gateway device; wherein the device key is used by the gateway device to send to the mesh device so that the mesh device can decrypt the stored network configuration information based on the device key; the decoded network configuration information is used by the mesh device to restore access to the mesh network.

[0044] In some embodiments, the determining module is configured to: determine whether the device information of the mesh device is bound to a user account; and in response to the device information of the mesh device being bound to a user account, determine that the mesh device has undergone a local reset.

[0045] In some embodiments, the apparatus further includes: a second receiving module configured to receive heartbeat information sent by a gateway device; wherein the heartbeat information is sent by the gateway device after receiving a third notification message, and the third notification message is sent by the mesh device to the gateway device after restoring access to the mesh network.

[0046] According to a seventh aspect of the present disclosure, a second device is provided, comprising:

[0047] A processor; a memory for storing computer programs or instructions; wherein the processor executes the computer programs or instructions to implement the steps of the methods described in the first, second, and / or third aspects above.

[0048] According to an eighth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, storing executable instructions or a computer program that, when executed by a processor, implements the steps of the methods described in the first, second, and / or third aspects.

[0049] According to a ninth aspect of the present disclosure, a computer program product is provided, including a computer program or instructions, which, when executed by a processor, implement the steps of the methods described in the first, second, and / or third aspects.

[0050] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0051] In this disclosure, mesh devices typically transition from a network-configured state to an unconfigured state upon a local reset. Therefore, a mesh device in an unconfigured state can send a first notification message to indicate its current unconfigured state. Based on this, the gateway device can receive the first notification message, determine whether a local reset has occurred, and, if so, send network recovery information to the mesh device, enabling it to reconnect to the mesh network. This allows for seamless reconnection of a locally reset mesh device to the mesh network without the user's awareness, improving the ease of use of mesh devices.

[0052] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0053] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0054] Figure 1 This is a schematic diagram illustrating an intelligent home appliance system according to an exemplary embodiment.

[0055] Figure 2 This is a flowchart illustrating a first network processing method according to an exemplary embodiment.

[0056] Figure 3 This is a flowchart illustrating a second network processing method according to an exemplary embodiment.

[0057] Figure 4 This is a flowchart illustrating a third network processing method according to an exemplary embodiment.

[0058] Figure 5 This is a flowchart illustrating a fourth network processing method according to an exemplary embodiment.

[0059] Figure 6 This is a block diagram illustrating a network processing apparatus according to an exemplary embodiment.

[0060] Figure 7 This is a block diagram illustrating another network processing apparatus according to an exemplary embodiment.

[0061] Figure 8 This is a block diagram illustrating yet another network processing apparatus according to an exemplary embodiment.

[0062] Figure 9 This is a structural block diagram of an electronic device according to an exemplary embodiment.

[0063] Figure 10 This is a block diagram illustrating an apparatus for network processing according to an exemplary embodiment. Detailed Implementation

[0064] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0065] With the rapid development of the electronics industry, furniture, home appliances, and other equipment are becoming increasingly intelligent. After purchasing new furniture and appliances, they can be directly connected to a wireless mesh network through a configuration process or connected via a gateway device, and then bound to the user's account. Based on this, it is possible to control furniture and appliances through an application (APP).

[0066] However, furniture and appliances are susceptible to local resets triggered by grid voltage fluctuations or user errors, causing them to go offline and preventing users from controlling them via the app. If users continue to control these offline devices through the app, they must trigger a network configuration process to reconnect them to the mesh network. This reduces the ease of use of furniture and appliances, thus degrading the user experience.

[0067] Figure 1 This is a schematic diagram illustrating an intelligent home appliance system according to an exemplary embodiment. Figure 1 The lighting device 'a' in the network is a smart home appliance. Multiple lighting devices 'a' form a mesh network 101. Each lighting device 'a' in the mesh network 101 is directly or indirectly connected to a Bluetooth gateway 102. The Bluetooth gateway 102 is connected to a router 103, which is connected to a server device 104. The server device 104 is connected to a terminal device 105. The lighting device 'a' and the Bluetooth gateway 102 are bound to a user account through a configuration process. This user account and the device information of the lighting device 'a' are stored in the server device 104. Based on this, the user can control the lighting device 'a' in the mesh network 101 through an APP installed on the terminal device 105, via the server device 104, the router device 103, and the gateway device 202.

[0068] However, lighting device A is susceptible to local resets triggered by grid voltage fluctuations or user error, causing it to go offline and preventing users from controlling it via the app. If users want to continue controlling the offline lighting device A through the app, they need to trigger a network configuration process to reconnect it to the mesh network. This reduces the ease of use of lighting device A and consequently degrades the user experience.

[0069] To address the aforementioned problems, this disclosure provides a first network processing method. Figure 2This is a flowchart illustrating a first network processing method according to an exemplary embodiment. The first network processing method provided in this disclosure can be executed by a gateway device. Exemplarily, gateway devices include, but are not limited to: Bluetooth gateways, Zigbee gateways, Long Range (LoRa) gateways, Narrowband Internet of Things (NB-IoT) gateways, etc.

[0070] In the following text, the gateway device will be used as the execution subject, and reference will be made. Figure 2 The steps shown illustrate a first network processing method provided by an embodiment of this disclosure. The method includes:

[0071] In step 201, a first notification message sent by the mesh device is received.

[0072] In some embodiments, the first notification message is used to indicate that the mesh device is in an unconfigured state.

[0073] Understandably, when a mesh device is in an unconfigured network state, it can send a first notification message to the gateway device to notify the gateway device that it is in an unconfigured network state. Based on this, the gateway device can receive the first notification message sent by the mesh device.

[0074] In some embodiments, the first notification message is sent by a mesh device connected to the mesh network in the event of a local reset.

[0075] In some embodiments, a mesh device can be any terminal device capable of accessing a mesh network. For example, a mesh device can include: furniture appliances, home appliances, and other smart devices. Home appliances include: speakers, refrigerators, air conditioners, televisions, robot vacuum cleaners, smoke detectors, switches, lighting fixtures, etc. Furniture appliances include, but are not limited to: curtain control devices, door and window control devices, motorized curtains, etc.

[0076] In some embodiments, the first notification message may carry device information of the mesh device. Based on this, after receiving the first notification message, the gateway device can determine that the mesh device with the device information carried in the first notification message is currently in an unconfigured state.

[0077] In some embodiments, the first notification message may be an unconfigured network broadcast or a notification message sent to the gateway device based on the communication connection established between the mesh device and the second device. This disclosure does not limit this.

[0078] In some embodiments, the device information carried in the first notification message includes, but is not limited to, at least one of the following: the mesh device's identifier (ID), the mesh device's Media Access Control address (MAC) address, and the mesh device's network status. The mesh device's network status is used to indicate whether the mesh device is currently connected to the mesh network or is in an unconfigured state.

[0079] For example, the device information carried in the first notification message may include at least one field from Table 1 below:

[0080] Table 1 Equipment Information Table

[0081] Fields adtype adlen company id fram ctrl pid fram cnt Mac mesh state Length (bytes) 1 1 2 2 2 1 6 2

[0082] It should be noted that the adtype, adlen, and company id fields in Table 1 are used to indicate that the first notification message is a Bluetooth broadcast message; the fram ctrl field in Table 1 is used to indicate the type of parameters carried in the first notification message; the pid field in Table 1 is the product identifier; the fram cnt field is the sequence number of the second communication message, used to indicate the number of messages exchanged between the mesh device and the gateway device in the second communication message; the mac field in Table 1 is the Bluetooth MAC address of the mesh device; and the mesh state field in Table 1 is used to indicate the network status of the mesh device.

[0083] In step 202, it is determined whether a local reset of the mesh device has occurred.

[0084] Understandably, after receiving the first notification message from the mesh device, the gateway device can determine whether the reason for the mesh device's failure to configure the network is a local reset.

[0085] In some embodiments, if a user resets a mesh device via an app, the app typically sends a reset command to the mesh device through the gateway device, or the app sends the reset command through both the server device and the gateway device. Therefore, if a user resets a mesh device via an app, the gateway device will receive a reset command for the mesh device. Based on this, after receiving the first notification message, the gateway device can determine whether it received a reset command for the mesh device within a second time period prior to receiving the first notification message. If the gateway device does not receive a reset command for the mesh device, it can determine that the reason the mesh device is not configured for the network is due to a local reset. If the gateway device receives a reset command for the mesh device, it can determine that the reset of the mesh device was not a local reset.

[0086] In some embodiments, the value of the second duration can be determined as needed, and this disclosure does not limit this.

[0087] For example, the second duration can be any duration between 5 minutes and 30 minutes.

[0088] For example, the second duration can be 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, etc.

[0089] In step 203, in response to a local reset of the mesh device, network recovery information is sent to the mesh device.

[0090] Understandably, if the gateway device determines that the mesh device's reset is a local reset, it can send network recovery information to the mesh device so that the mesh device can restore access to the mesh network based on the network recovery information.

[0091] In some embodiments, the network recovery information can be any network recovery information that can be used for mesh devices to restore access to the mesh network, and this disclosure does not limit this.

[0092] For example, network recovery information may include network configuration information. Network configuration information includes, but is not limited to, at least one of: network key (Netkey), application key (Appkey), mesh device address (Address), sequence number (SequenceNumber), initialization vector information (IV), subscription address (SubscriptionAddress), and Bluetooth long-term key (LTK).

[0093] In some embodiments, IV information includes, but is not limited to, the initialization vector index (IV Index).

[0094] In other embodiments, network recovery information may include device information of the mesh device.

[0095] For example, the device information of a mesh device may include, but is not limited to, the device key of the mesh device, message sequence number, etc.

[0096] In some embodiments, network recovery information may be stored locally on the gateway device or obtained by the gateway device from the server device.

[0097] In some embodiments, the gateway device can send network recovery information to the mesh device via a broadcast channel.

[0098] In this embodiment, since mesh devices typically transition from a network-configured state to an unconfigured state upon a local reset, a mesh device in an unconfigured state can send a first notification message to indicate its current unconfigured state. Based on this, the gateway device can receive the first notification message, determine whether a local reset has occurred, and, if so, send network recovery information to the mesh device, enabling it to reconnect to the mesh network. This allows the user to reconnect a locally reset mesh device to the mesh network without their knowledge, improving the ease of use of the mesh device.

[0099] In some embodiments, step 202 includes: sending a first request message to a server device; wherein the first request message is used to request the server device to determine whether a local reset has occurred in the mesh device; receiving network recovery information sent by the server device, the network recovery information being sent by the server device when it determines that a local reset has occurred in the mesh device; and determining that a local reset has occurred in the mesh device in response to receiving the network recovery information sent by the server device.

[0100] Understandably, after receiving the first notification message, the gateway device can send a first request message to the server device to request confirmation of whether a local reset of the mesh device has occurred. Correspondingly, the server device can determine whether a local reset of the mesh device has occurred based on the first request message. If the server device determines that the mesh device reset is a local reset, it can send network recovery information for the mesh device to the gateway device. Therefore, if the gateway device receives the network recovery information from the server device, it can confirm that a local reset of the mesh device has occurred.

[0101] In some embodiments, the first request message may carry device information of the mesh device, so that the server device can determine the network recovery information of the mesh device from the stored network recovery information based on the device information carried in the first request message.

[0102] In some embodiments, server-side equipment includes, but is not limited to, a single server or a cluster of servers.

[0103] In some embodiments, the gateway device can invoke the target interface on the server device through a first request message, so that the server device can obtain network recovery information of the mesh device based on the target interface.

[0104] For example, the target interface may include, but is not limited to, the ble_mesh_query_dev interface on the server device.

[0105] In this embodiment, since the server device stores network recovery information of the mesh devices during the network configuration process, the gateway device can obtain the network recovery information of the mesh devices from the server device, thus reducing the storage pressure on the gateway device.

[0106] In some embodiments, step 203 includes: starting a timer in response to receiving a first notification message; and sending network recovery information to the mesh device in response to the timer duration reaching a preset duration.

[0107] Understandably, the gateway device can start timing after receiving the first notification message. If the gateway device determines that the timing has reached the preset duration, it can send network recovery information to the mesh device.

[0108] In some embodiments, after receiving the first notification message, the gateway device may set a timer and set the timer duration to a first duration. Based on this, the gateway device may send network recovery information to the mesh device if the timer times out.

[0109] In some embodiments, the length of the first duration can be determined as needed, and this disclosure does not limit this.

[0110] For example, the first duration can be any duration between 10 minutes and 30 minutes.

[0111] For example, the first duration can be 10 minutes, 15 minutes, 20 minutes, 25 minutes, 30 minutes, etc.

[0112] In some embodiments, after the timing period reaches the first duration, the gateway device can determine the current network status of the mesh device. If the mesh device is still in an unconfigured state, it can send network recovery information to the mesh device.

[0113] For example, if the gateway device still receives the first notification message from the mesh device after the first timeout period has elapsed, it can determine that the mesh device is still in an unconfigured state. At this time, the gateway device can send network recovery information to the mesh device.

[0114] In this embodiment, it is considered that a local reset of the mesh device may also be a user-triggered reset. If the mesh device reset is user-triggered, the user will reconfigure the mesh device for the network in a short time. However, a reset caused by voltage issues or accidental user touch may not be noticed by the user in a short period of time, resulting in the mesh device being in an unconfigured state for an extended period. Therefore, the gateway device starts timing after receiving the first notification message and sends network recovery information to the mesh device after the timing duration reaches the first duration, so that the mesh device can restore access to the mesh network based on the network recovery information. In this way, the probability of mistaking a normal user reset operation for an accidental user reset and restoring the mesh network of the mesh device can be reduced.

[0115] In some embodiments, step 203 includes: sending a second request message to the mesh device, wherein the second request message is used to request the establishment of a communication connection with the mesh device; and sending network recovery information to the mesh device based on the communication connection.

[0116] Understandably, the gateway device can also send a second request message to the mesh device to request the establishment of a communication connection. Afterward, the gateway device can send network recovery information to the mesh device based on the established communication connection.

[0117] In some embodiments, the communication connection established between the gateway device and the mesh device includes, but is not limited to, a short-range communication connection.

[0118] For example, short-range communication connections include, but are not limited to, Bluetooth connections, Near Field Communication (NFC) connections, etc.

[0119] In this embodiment of the disclosure, before sending network recovery information to the mesh device, the gateway device may request to establish a communication connection with the mesh device and send the network recovery information to the mesh device based on the established communication connection. Compared with sending network recovery information to the mesh device through a broadcast channel, this can increase the transmission security of network recovery information.

[0120] In some embodiments, after establishing a communication connection with the server device, the gateway device can generate a session key. The gateway device can then encrypt network recovery information based on the session key and send the encrypted network recovery information to the mesh device.

[0121] In some embodiments, the algorithms used by the gateway device to generate session keys include, but are not limited to, key exchange algorithms (Diffie-Hellman Ephemeral, DHE), key derivation functions (KD F), etc.

[0122] For example, key exchange algorithms include, but are not limited to, Elliptic Curve Diffie-Hellman (ECDH) key exchange algorithm and Diffie-Hellman Key Exchange (DHKE) algorithm.

[0123] In this embodiment of the disclosure, the gateway device encrypts the network recovery information and sends the encrypted network configuration information to the mesh device, which can further improve the transmission security of the network recovery information.

[0124] In some embodiments, the method further includes: receiving a second notification message sent by a mesh device based on a communication connection, wherein the second notification message is sent by the mesh device upon successful authentication of the server device. Sending network recovery information to the mesh device based on the communication connection includes: in response to receiving the second notification message, sending network recovery information to the mesh device based on the communication connection.

[0125] Understandably, after establishing a communication connection with the mesh device, the mesh device can perform device authentication with the server device based on this connection. After successfully authenticating the server device, the mesh device can send a second notification message to the gateway device. Correspondingly, the gateway device can receive the second notification message from the mesh device. Upon receiving the second notification message, the gateway device can then send network recovery information to the mesh device based on the established communication connection.

[0126] In some embodiments, after establishing a communication connection with the mesh device, the gateway device can send a network recovery start (RECOVER_START) command to the mesh device. Then, the gateway device can receive first authentication information sent by the mesh device based on the network recovery start command. Next, the gateway device can send an authentication request to the server device, including the first authentication information in the authentication request, so that the server device can authenticate the mesh device based on the first authentication information. The gateway device can also receive second authentication information sent by the server device after successfully authenticating the mesh device. Then, the gateway device can send an authentication request to the mesh device, including the second authentication information, so that the mesh device can authenticate the server device based on the second authentication information. Based on this, the gateway device can receive a second notification message sent by the second device after successfully authenticating the server device.

[0127] In some embodiments, when the mesh device is a Bluetooth device, the authentication request sent by the gateway device to the server device can be a Bluetooth mesh device authentication (ble_mesh_dev_auth) request.

[0128] In some embodiments, the first authentication information includes, but is not limited to, the device certificate and signature of the mesh device.

[0129] In some embodiments, the second authentication information includes, but is not limited to, the server device's device certificate, signature, etc.

[0130] In this embodiment, the second notification message is sent from the mesh device to the gateway device after successful mutual authentication with the server device. Therefore, the gateway device can determine that the mesh device is an authenticated device based on receiving the second notification message. The gateway device sends network recovery information to the mesh device only after receiving the second notification message, which reduces the risk of unauthorized devices accessing the mesh network.

[0131] In some embodiments, the network recovery information includes the device key of the mesh device. Step 203 includes: in response to a local reset of the mesh device, sending the device key to the mesh device, wherein the device key is used by the mesh device to decrypt the stored network configuration information and restore access to the mesh network based on the decrypted network configuration information.

[0132] Understandably, the network recovery information obtained by the gateway device from the server device may include the device key of the mesh device. Based on this, the gateway device can send the device key to the mesh device, enabling the mesh device to decrypt the stored network configuration information based on the device key and restore access to the mesh network based on the decrypted network configuration information.

[0133] In some embodiments, the device key of a mesh device is a random key generated by the mesh device during the network configuration process.

[0134] In some embodiments, the device information stored in the mesh device may be one less field than those in Table 2 below:

[0135] Table 2. Equipment Information for Mesh Devices

[0136]

[0137] It should be noted that the netkey field is the network key, the appkey field is the application key, the address field is the device address, the seq field is the message sequence number, the ivindex is the initialization vector index, the sublist field is the list of subscription addresses, and the ltmk field is the Bluetooth long-term key.

[0138] In this embodiment, when a local reset occurs, the mesh device can obtain network configuration information and encrypt and store it. Based on this, after receiving the first notification message, the gateway device can obtain the device key of the mesh device from the server device and send the obtained device key to the mesh device. This allows the mesh device to decrypt the network configuration information based on the device key and restore access to the mesh network based on the decrypted network configuration information. Thus, the first restoration of access to the mesh network can be achieved without the user's awareness.

[0139] In some embodiments, the method further includes: receiving a third notification message sent by the mesh device, wherein the third notification message is sent by the mesh device after it has regained access to the mesh network; and sending heartbeat information to the server device.

[0140] Understandably, the mesh device can also send a third notification message to the gateway device after regaining access to the mesh network. Correspondingly, the gateway device can receive the third notification message sent by the mesh device. After receiving the third notification message, the gateway device can determine that the mesh device has regained access to the mesh network. At this point, the gateway device can send heartbeat information to the server device to inform it that the mesh device has regained access to the mesh network.

[0141] In some embodiments, the third notification message may be a network configuration broadcast sent by the mesh device. This network configuration broadcast is used to indicate that the mesh device is in a network configuration state.

[0142] In some embodiments, the gateway device may disconnect the communication connection with the mesh device after receiving the fourth notification message. The fourth notification message is sent by the mesh device after configuring network recovery information into its protocol stack.

[0143] In some embodiments, the heartbeat information can be any information that can indicate that the mesh device has returned to the network configuration state, and this disclosure does not limit this.

[0144] In some embodiments, the heartbeat information may include the device identifier of the mesh device.

[0145] In some embodiments, the device identifier of a mesh device can be any identification information that can uniquely identify a device.

[0146] For example, the device identifier of a mesh device may include, but is not limited to, the device ID of the mesh device, the MAC address of the mesh device, etc.

[0147] In this embodiment of the disclosure, after receiving the third notification message, the gateway device sends heartbeat information to the server device, which enables the server device to know the latest status of the mesh device in a timely manner.

[0148] To address the aforementioned issues, this disclosure also provides a second network processing method. Figure 3 This is a flowchart illustrating a second network processing method according to an exemplary embodiment. In the following text, a mesh device will be used as the execution subject, with reference to... Figure 3 The steps shown below describe a second network processing method. This method includes:

[0149] In step 301: In response to the mesh device being in an unconfigured state, a first notification message is sent.

[0150] In some embodiments, the first notification message is used to indicate that the mesh device is in an unconfigured state.

[0151] Understandably, when a mesh device undergoes a local reset, it typically transitions from a network-configured state to an unconfigured state. Therefore, when a mesh device is in an unconfigured state, it can send a first notification message to inform the gateway device that the mesh device is currently in an unconfigured state.

[0152] In some embodiments, when a mesh device detects a reset command, it can determine whether the current reset is a local reset. If the mesh device determines that the current reset is a local reset, it can send a first notification message to the gateway device.

[0153] In some embodiments, if a mesh device determines that the current reset is a local reset, it can delete the network configuration information in the protocol stack, thereby changing the mesh device from an accessed mesh network state to an unconfigured state. Afterward, the mesh device can send a first notification message to the gateway device.

[0154] In some embodiments, when the mesh device is in an unconfigured state, it may send a first notification message to the gateway device at a first cycle until the duration of the unconfigured state reaches a third duration. That is, when the duration of the unconfigured state reaches the third duration, the mesh device stops sending the first notification message to the second device.

[0155] In this embodiment, since the first notification message can be a broadcast message without network configuration, other users' terminal devices can also receive the first notification message. Therefore, by stopping the mesh device from sending the first notification message to the second device after the third duration, the probability of the mesh device being bound to other users' terminal devices can be reduced.

[0156] In step 302, network recovery information sent by the gateway device is received.

[0157] In some embodiments, network recovery information is sent by the gateway device upon determining that a local reset has occurred in the mesh device.

[0158] Understandably, after receiving the first notification message, the gateway device can determine whether the reason for the mesh device being in an unconfigured state is a local reset. If the gateway device determines that the reason for the mesh device being in an unconfigured state is a local reset of the mesh device, it can send network recovery information to the mesh device. Correspondingly, the mesh device can receive the network recovery information sent by the gateway device.

[0159] It should be noted that the specific information included in the network recovery information can be referred to the relevant explanation of network recovery information in the first network processing method described above, and this embodiment of the disclosure does not limit it in this way.

[0160] In step 303, access to the mesh network is restored based on the network recovery information.

[0161] Understandably, after receiving network recovery information, mesh devices can restore access to the mesh network based on the obtained network recovery information.

[0162] In some embodiments, when the network recovery information includes network configuration information, the mesh device can configure the network configuration information included in the network recovery information into the protocol stack to restore access to the mesh network.

[0163] In this embodiment of the disclosure, the mesh device can restore access to the mesh network by configuring the received network configuration information into the protocol stack, which improves the convenience of network recovery.

[0164] In some embodiments, network recovery information includes the device key of the mesh device; step 303 includes: decrypting the stored mesh configuration information based on the device key; and restoring access to the mesh network based on the decrypted mesh configuration information.

[0165] Understandably, the network recovery information received by the mesh device may include the mesh device's device key. Based on this, after receiving the device key, the mesh device can decrypt the network configuration information stored locally on the mesh device and restore access to the mesh network based on the decrypted network configuration information.

[0166] In some embodiments, the mesh device can read network configuration information from a memory or file system in a first cycle while in network configuration mode, and encrypt and store the read network configuration information. Based on this, after receiving the device key sent by the gateway device, the mesh device can decrypt the stored network configuration information to obtain the decrypted network configuration information.

[0167] In some embodiments, the mesh device can configure the decrypted network configuration information into the mesh device's protocol stack to restore access to the mesh network.

[0168] In this embodiment, the mesh device stores and encrypts the network configuration information generated during the historical time periods when it accessed the mesh network. In the event of a local reset of the mesh device, the network configuration information can be decrypted based on the device key transmitted by the gateway device, and access to the mesh network can be restored based on the decrypted network configuration information. This not only improves the convenience of network recovery but also reduces the amount of data transmitted between the gateway device and the mesh device for network recovery information.

[0169] In some embodiments, the method further includes: in response to triggering a local reset of the mesh device, obtaining the network configuration information required for the mesh device to access the mesh network; and encrypting and storing the network configuration information.

[0170] In some embodiments, a local reset of the mesh device can be triggered if reset conditions are met.

[0171] For example, when a mesh device meets a reset condition, it can determine that a local reset of the mesh device is triggered, including at least one of the following: when the mesh device detects that a user has triggered a reset button, it determines that the mesh device meets the reset condition; when the mesh device has reached a preset number of power-on and / or power-off times within a preset time period, it can determine that the mesh device meets the reset condition.

[0172] In some embodiments, the reset button can be a single button on the mesh device or a combination of multiple buttons on the mesh device that have other functions.

[0173] In some embodiments, the preset duration and the number of preset times can be set as needed, and the embodiments disclosed herein do not limit this.

[0174] For example, the preset duration can be any value from 1 minute to 24 hours. For instance, the preset duration can be 1 minute, 30 minutes, 1 hour, 2 hours, 5 hours, 8 hours, 12 hours, 18 hours, 24 hours, etc.

[0175] For example, the preset number of times can be any integer from 1 to 10. For instance, the preset number of times can be 1 time, 3 times, 5 times, 8 times, 10 times, etc.

[0176] For example, if the mesh device is a downlight, and the downlight is powered on and off 5 times within a preset time period, it can be determined that the downlight meets the reset condition.

[0177] It should be noted that when a high-power appliance on the same wiring as the downlight is turned on, causing voltage fluctuations, the downlight may be triggered to power on and off multiple times.

[0178] It should be noted that the preset number of times a mesh device is powered on and off within a preset time period includes: the sum of the preset number of times a mesh device is powered on and off within a preset time period reaches the preset number, or both the preset number of times a mesh device is powered on and off within a preset time period reach the preset number.

[0179] In some embodiments, the mesh device may retrieve network configuration information from storage or the file system only if a local reset is determined to be triggered.

[0180] In some embodiments, the mesh device can encrypt the acquired network configuration information using the mesh device's device key and calculate the message authentication code.

[0181] In some embodiments, the mesh device can use a symmetric encryption algorithm to encrypt the network configuration information using the mesh device's MAC address, message sequence number, and other information as a one-time random number (nonce) to generate ciphertext and a message authentication code (MIC), and store the ciphertext and message authentication code in the mesh device's file system or flash memory.

[0182] For example, the symmetric encryption algorithms used by mesh devices include, but are not limited to, Advanced Encryption Standard (AES) and Data Encryption Standard (DES).

[0183] For example, the AES encryption algorithm includes, but is not limited to, AES-128, AES-192, and AES-256. In AES-128, 128 indicates that the key length is 128; in AES-192, 192 indicates that the key length is 192; and in AES-256, 256 indicates that the key length is 256.

[0184] In some embodiments, the length of the message authentication code can be determined as needed, and this disclosure does not limit this.

[0185] For example, the number of bytes included in the message authentication code can be any integer from 2 to 10. For instance, the number of bytes included in the message authentication code can be 2, 4, 6, 8, 10, etc.

[0186] In this embodiment of the disclosure, when a local reset is triggered, the mesh device encrypts and stores the network distribution information, which can increase the storage security of the network distribution information.

[0187] In some embodiments, step 302 includes: receiving a second request message sent by a gateway device; establishing a communication connection with the gateway device based on the second request message; and receiving network recovery information sent by the gateway device through the communication connection.

[0188] Understandably, the mesh device can also receive a second request message from the gateway device. After receiving the second request message, the mesh device can establish a communication connection with the gateway device based on the second request message. Subsequently, the mesh device can receive network recovery information sent by the gateway device based on the communication connection.

[0189] It should be noted that the type of communication connection established between the mesh device and the gateway device can be referred to the above description of the type of communication connection established between the mesh device and the gateway device, and will not be repeated here in this embodiment.

[0190] In some embodiments, the method further includes: in response to successful authentication of the server device, sending a second notification message to the gateway device via a communication connection; and receiving network recovery information sent by the gateway device via the communication connection, including: receiving network recovery information sent by the gateway device via the communication connection after receiving the second notification message.

[0191] Understandably, after establishing a communication connection with the gateway device, the mesh device can perform relevant authentication with the server device based on that connection. If the mesh device successfully authenticates the server device, it can send a second notification message to the gateway device via the communication connection. Correspondingly, the gateway device can receive the second notification message from the mesh device. After receiving the second notification message, the gateway device can send network recovery information to the mesh device through the communication connection with it.

[0192] In some embodiments, after establishing a communication connection with the gateway device, the mesh device can receive a network recovery start command sent by the gateway device. Upon receiving the network recovery start command, the mesh device can send its device certificate and signature to the gateway device, enabling the gateway device to forward the received device certificate and / or signature to the server device. The mesh device's device certificate and / or signature can be used by the server device to authenticate the mesh device. The mesh device can also receive the server device's device certificate and / or signature forwarded by the gateway device and authenticate the server device based on the received server device's certificate and / or signature. After successfully authenticating the server device, the mesh device can send a second notification message to the gateway device.

[0193] In some embodiments, after receiving a network recovery start command, the mesh device can also generate a session key and encrypt information sent to the gateway device through the communication connection based on the generated session key.

[0194] In some embodiments, the method further includes: in response to the mesh device re-accessing the mesh network, sending a third notification message to the gateway device; wherein the third notification message is used by the gateway device to send heartbeat information to the server device.

[0195] Understandably, after a mesh device regains access to the mesh network based on network recovery information, it can send a third notification message to the gateway device to inform it that the mesh device has regained access. Additionally, this third notification message can also be used by the gateway device to send heartbeat information to the server device, indicating that the mesh device has regained access to the mesh network.

[0196] In some embodiments, the heartbeat information can be any information that can indicate that the mesh device has returned to the network configuration state, and this disclosure does not limit this.

[0197] In some embodiments, the heartbeat information may include the device identifier of the mesh device.

[0198] In some embodiments, the device identifier of a mesh device can be any identification information that can uniquely identify a device.

[0199] For example, the device identifier of a mesh device may include, but is not limited to, the device ID of the mesh device, the MAC address of the mesh device, etc.

[0200] To address the aforementioned issues, this disclosure also provides a third network processing method. Figure 4 This is a flowchart illustrating a third network processing method according to an exemplary embodiment. In the following text, the server device will be considered the execution entity, with reference to... Figure 4 The steps shown below introduce a third network processing method. This method includes:

[0201] In step 401, a first request message sent by the gateway device is received.

[0202] In some embodiments, the first request message is sent by the gateway device after receiving a first notification message from the mesh device.

[0203] In some embodiments, the first notification message is used to indicate that the mesh device is in an unconfigured state.

[0204] Understandably, if a mesh device is in an unconfigured state, it can send a first notification message to the gateway device to inform it that it is in an unconfigured state. Based on this, the gateway device can receive the first notification message from the mesh device. After receiving the first notification message, the gateway device can send a first request message to the server device. Thus, the server device can receive the first request message from the gateway device.

[0205] In some embodiments, the first request message may carry device information of the mesh device.

[0206] It should be noted that the specific information included in the device information of the mesh device can be referred to the relevant description of the device information of the mesh device in the first network processing method, and will not be repeated here in this embodiment.

[0207] In step 402, it is determined whether a local reset of the mesh device has occurred.

[0208] Understandably, after receiving the first request message, the server device can determine whether the mesh device has undergone a local reset.

[0209] In some embodiments, if a user resets the mesh device via an app, the app typically sends a reset command to the mesh device through a server device. Therefore, if a user resets the mesh device via an app, the server device will receive a reset command for the mesh device. Based on this, after receiving the first request message, the server device can determine whether it received a reset command for the mesh device within a fourth time period prior to receiving the first request message. If the server device does not receive a reset command for the mesh device, it can determine that the reason the mesh device is not configured for the network is due to a local reset. If the server device receives a reset command for the mesh device, it can determine that the reset of the mesh device was not a local reset.

[0210] In some embodiments, the value of the fourth duration can be determined as needed, and this disclosure does not limit this.

[0211] For example, the fourth duration can be any duration between 1 second and 5 minutes.

[0212] For example, the fourth duration can be 1 second, 30 seconds, 1 minute, 2 minutes, 3 minutes, 5 minutes, etc.

[0213] In step 403, in response to a local reset of the mesh device, network recovery information is sent to the gateway device.

[0214] In some embodiments, network recovery information is sent from the gateway device to the mesh device so that the mesh device can restore access to the mesh network based on the network recovery information.

[0215] Understandably, when the server device determines that a mesh device has undergone a local reset, it can obtain the mesh device's network recovery information and send it to the gateway device. This allows the gateway device to forward the network recovery information to the mesh device, enabling it to regain access to the mesh network based on the recovery information.

[0216] In some embodiments, the network recovery information can be any network recovery information that can be used for mesh devices to restore access to the mesh network, and this disclosure does not limit this.

[0217] For example, network recovery information may include network configuration information. Network configuration information includes, but is not limited to, at least one of: network key, application key, device address of the mesh device, message sequence number, IV information, subscription address, and Bluetooth long-term key.

[0218] In some embodiments, IV information includes, but is not limited to, the initialization vector index (IV Index).

[0219] In some embodiments, the network recovery information includes the device key of the mesh device; step 403 includes: in response to determining that the mesh device has undergone a local reset, sending the device key to the gateway device; wherein the device key is used by the gateway device to send to the mesh device so that the mesh device can decrypt the stored network configuration information based on the device key; the decoded network configuration information is used by the mesh device to restore access to the mesh network.

[0220] Understandably, when the server device determines that a mesh device has undergone a local reset, it can obtain the device key of the mesh device stored locally and send the obtained device key to the gateway device. This allows the gateway device to forward the device key to the mesh device. In this way, the mesh device can decrypt the locally stored network configuration information based on the received device key and restore access to the mesh network based on the decrypted network configuration information.

[0221] In some embodiments, the device key is a random key generated by the mesh device and stored on the server device during the previous network configuration process of the mesh device.

[0222] In some embodiments, step 402 includes: determining whether the device information of the mesh device is bound to a user account; and in response to the device information of the mesh device being bound to a user account, determining that the mesh device has undergone a local reset.

[0223] Understandably, when a user resets a mesh device, they typically delete the device information directly through an app provided by the Internet of Things (IoT) platform, and the server device also unbinds the mesh device information from the user account. Therefore, upon receiving the first request message, the server device can determine whether the mesh device information is bound to the user account. If the mesh device information is bound to the user account, the server device can confirm that a local reset of the mesh device has occurred.

[0224] In some embodiments, if the device information of the mesh device is not bound to a user account, the server device can determine that the reset of the mesh device is not a local reset.

[0225] In some embodiments, the method further includes: receiving heartbeat information sent by a gateway device; wherein the heartbeat information is sent by the gateway device after receiving a third notification message, and the third notification message is sent by the mesh device to the gateway device after restoring access to the mesh network.

[0226] Understandably, after a mesh device regains access to the mesh network based on network recovery information, it can send a third notification message to the gateway device to inform it that the mesh device has regained access. Upon receiving the third notification message, the gateway device can send a heartbeat message to the server device to indicate that the mesh device has regained access. In this way, the server device can receive the heartbeat message.

[0227] In some embodiments, the heartbeat information can be any information that can indicate that the mesh device has returned to the network configuration state, and this disclosure does not limit this.

[0228] In some embodiments, the heartbeat information may include the device identifier of the mesh device.

[0229] In some embodiments, the device identifier of a mesh device can be any identification information that can uniquely identify a device.

[0230] For example, the device identifier of a mesh device may include, but is not limited to, the device ID of the mesh device, the MAC address of the mesh device, etc.

[0231] The following text will use a specific embodiment, taking a mesh device as a Bluetooth device, a gateway device as a Bluetooth gateway, and a server device as a cloud server, to further illustrate the network processing method provided in the above embodiment. The method includes:

[0232] In step one, the Bluetooth device undergoes a local reset.

[0233] Before a local reset occurs on a Bluetooth device, both the Bluetooth device and the Bluetooth gateway are bound to the same user account for network configuration. The Bluetooth gateway can obtain device information for each Bluetooth device through the cloud server. This device information includes, but is not limited to: the Bluetooth device's vendor ID, product ID, device ID, MAC address, and device key. The device key is a random key generated by the Bluetooth device itself during the network configuration process and stored on the cloud server.

[0234] If the Bluetooth device experiences multiple power outages and / or power-ups, or if the user physically resets the Bluetooth device using the reset button or key combination, and the reset conditions are met, a local reset occurs. In the event of a local reset, the device information bound to the user's account information in the cloud server will not be deleted.

[0235] Unlike local resets, if a Bluetooth device undergoes a cloud reset, the user can directly delete the Bluetooth device through the mobile app provided by the IoT platform and send a reset command to the Bluetooth device via Bluetooth, Wi-Fi, or other channels. At this time, the cloud server will unbind the Bluetooth device information from the user's account.

[0236] In step two, the Bluetooth device saves the network pairing information and then disconnects from the network.

[0237] When reset conditions are met, the Bluetooth device reads network configuration information from its memory or file system. This network configuration information includes, but is not limited to: network key, application key, device address, message sequence number, IV information, subscription address list, and Bluetooth long-term key. After obtaining the network configuration information, the Bluetooth device can encrypt it using its device key and calculate a message authentication code. For example, the Bluetooth device can use the AES128-CCM symmetric encryption algorithm, using its MAC address, message sequence number (seq), and other information as a one-time random number to enhance security, encrypting and generating ciphertext and a 4-byte message authentication code, and storing them in the Bluetooth device's file system or flash memory.

[0238] Bluetooth devices can reset a mesh network, deleting all mesh configuration information from the protocol stack. At this point, the Bluetooth device has removed its device key and cannot decrypt the encrypted configuration information itself, thus reducing the risk of spam attacks.

[0239] A Bluetooth device initiates a Bluetooth Unconfigured Broadcast, which may include device information used to identify the Bluetooth device. For example, the device information included in the Unconfigured Broadcast includes, but is not limited to, product ID, MAC address, and Mesh network configuration status. This Unconfigured Broadcast can be captured by a Bluetooth gateway or a mobile app and used to perform the normal network configuration process. The Unconfigured Broadcast will continue for a period of time before being turned off to prevent it from being bound to other user accounts.

[0240] In step three, the Bluetooth gateway detects Bluetooth devices that are not configured to use the network.

[0241] After the Bluetooth gateway captures the unconfigured broadcast of a Bluetooth device, it first queries the cloud server to see if the device information of the Bluetooth device has been deleted, that is, to confirm whether the device information of the Bluetooth device is still under the user account and has not been unbound.

[0242] The Bluetooth gateway, etc., takes a first time to avoid misidentifying normal local reset operations by users as erroneous resets, and initiates the recovery process before the unconfigured network broadcast of the Bluetooth device is turned off.

[0243] In step four: the device key is sent to complete the recovery.

[0244] The Bluetooth gateway queries the cloud server for the device key stored in the network configuration process. The Bluetooth gateway establishes a secure link with the sub-device via a direct connection or broadcast channel, and verifies the Bluetooth device's information using a certificate chain or pre-configured keys. The Bluetooth gateway and Bluetooth device derive a session key using a key exchange algorithm or key derivation function. The Bluetooth gateway initiates a network recovery start request to the Bluetooth device and transmits the Bluetooth device's device key, encrypted with the session key, to the Bluetooth device. Upon receiving the device key, the Bluetooth device decrypts the encrypted network configuration information stored in the file system and reconfigures the decrypted network configuration information into the protocol stack, enabling the Bluetooth device to reconnect to the mesh network. The Bluetooth gateway reports to the cloud server that the Bluetooth device has reconnected to the mesh network.

[0245] The following text uses a smart downlight as an example to further describe the network processing method provided in the above embodiments:

[0246] The smart downlight does not have a reset button. Therefore, if the smart downlight is powered on and off 5 times within a preset time, it will trigger a local reset.

[0247] When the smart downlight detects a local reset, it reads and concatenates the network configuration information shown in Table 2. Then, the smart downlight encrypts the network configuration information in Table 2 using the AES128-CCM algorithm. The encryption key uses the smart downlight's device key, and the encryption nonce uses the smart downlight's MAC address and message sequence number. The smart downlight stores the encrypted ciphertext and a 4-byte message verification code in flash memory.

[0248] The smart downlight uses the reset interface provided by the protocol stack to reset the mesh network, which means deleting the network configuration information and device key from the smart downlight's protocol stack, thus restoring the smart downlight to an unconfigured state. Afterwards, the smart downlight initiates an unconfigured broadcast, which includes the information shown in Table 1. The unconfigured broadcast includes fields such as the product ID (PID) and MAC address to identify the smart downlight, as well as a mesh state field to identify the smart downlight's network configuration status. The mobile app and Bluetooth gateway can then initiate a new network configuration process based on the information included in the unconfigured broadcast.

[0249] The smart downlight will broadcast continuously for 30 minutes, after which it will turn off until it is powered on again or reset locally. This step is to prevent the smart downlight from being bound by other users. After the Bluetooth gateway captures the smart downlight's unconfigured broadcast, it requests the smart downlight's device information from the cloud server using the `ble_mesh_query_dev` interface. Since the user has not unbound the smart downlight's device information on the cloud server, the cloud server returns the smart downlight's device key and message sequence number, among other device information. If the smart downlight does not reconnect to the mesh network within 20 minutes, the Bluetooth gateway can send a connection request to the smart downlight to establish a Bluetooth connection. After establishing a Bluetooth connection with the smart downlight, the Bluetooth gateway can send a `RECOVER_START` command to the smart downlight based on the Bluetooth connection. Both the Bluetooth gateway and the smart downlight use an elliptic curve key exchange algorithm to generate the session key for this connection. After receiving the device certificate and signature from the smart downlight, the Bluetooth gateway sends a `ble_mesh_dev_auth` request to the cloud server. The cloud server verifies the smart downlight's signature and then transmits its server certificate and signature to the smart downlight via the Bluetooth gateway. The smart downlight verifies the server signature to complete two-way authentication. The Bluetooth gateway encrypts the smart downlight's device key using a session key and sends it to the smart downlight, enabling the smart downlight to decrypt and recover stored network configuration information based on the device key. Afterward, the smart downlight can reply with a `RECOVERY_SUCC` message to the Bluetooth gateway. Upon receiving the `RECOVERY_SUCC` message, the Bluetooth gateway can disconnect the Bluetooth connection. After receiving the smart downlight's network configuration broadcast, the Bluetooth gateway sends a heartbeat message (`ble_mesh_keepalive`) to the cloud server to instruct the smart downlight to reconnect.

[0250] Figure 5 This is a flowchart illustrating a fourth network processing method according to an exemplary embodiment. In the following text, reference will be made to... Figure 5 The steps shown herein, taking a mesh device as a Bluetooth device, a gateway device as a Bluetooth gateway, and a server device as a cloud server as an example, further illustrate the network processing method provided in the above embodiment with a specific example. The method includes:

[0251] In step 501, the Bluetooth gateway receives an unconfigured broadcast sent by the Bluetooth device.

[0252] In step 502, the Bluetooth gateway calls the ble_mesh_query_dev interface on the cloud server to query whether the Bluetooth device information is bound to the user account.

[0253] In step 503, the Bluetooth gateway receives the device information of the Bluetooth device sent by the cloud server. The device information of the Bluetooth device is sent by the cloud server after determining that the device information of the Bluetooth device is bound to the user account.

[0254] In step 504, if the time elapsed between the moment when the Bluetooth gateway first receives the unconfigured broadcast and the current moment reaches 20 minutes, the Bluetooth gateway establishes a Bluetooth connection with the Bluetooth device.

[0255] In step 505, the Bluetooth gateway sends a network recovery start command to the Bluetooth device based on the established Bluetooth connection.

[0256] In step 506, the Bluetooth gateway receives the device public key sent by the Bluetooth device.

[0257] In step 507, the Bluetooth gateway sends the gateway public key to the Bluetooth device.

[0258] It is important to note that both the device public key and the gateway public key can be public keys in elliptic curve cryptography. The device public key is used by the gateway device to generate a session key, and the gateway public key is used by the Bluetooth device to generate a session key. Steps 504 to 507 constitute the key exchange process.

[0259] In step 508, the Bluetooth gateway receives the device certificate chain and signature encrypted by the Bluetooth device using the session key.

[0260] In step 509, the Bluetooth gateway sends a ble_mesh_dev_auth request to the cloud server.

[0261] In step 510, the Bluetooth gateway receives the server certificate chain and signature sent by the cloud server.

[0262] It should be noted that the server certificate chain and signature are sent by the cloud server after the Bluetooth device has been successfully authenticated.

[0263] In step 511, the Bluetooth gateway sends the server certificate chain and signature to the Bluetooth device.

[0264] In step 512, the Bluetooth gateway receives a second notification message sent by the Bluetooth device, which indicates that the Bluetooth device has successfully verified the cloud server.

[0265] Steps 508 to 512 constitute the two-way authentication process between the Bluetooth device and the cloud server.

[0266] In step 513, the Bluetooth gateway sends a device key to the Bluetooth device.

[0267] It should be noted that the device key is included in the device information sent from the cloud server to the Bluetooth device.

[0268] In step 514, the Bluetooth gateway receives a network recovery success message (RECOVERYSUCC) sent by the Bluetooth device.

[0269] In step 515, the Bluetooth gateway disconnects the Bluetooth connection with the Bluetooth device.

[0270] In step 516, the Bluetooth gateway receives a network-configured broadcast sent by the Bluetooth device.

[0271] In step 517, the Bluetooth gateway sends heartbeat information to the cloud server.

[0272] Steps 513 to 517 are the process of restoring the Bluetooth device's access to the mesh network.

[0273] Figure 6 This is a block diagram illustrating a network processing apparatus according to an exemplary embodiment. Figure 6 As shown, the device includes: a first receiving module 601, configured to receive a first notification message sent by a wireless mesh device, the first notification message being used to indicate that the mesh device is in an unconfigured network state; a determining module 602, configured to determine whether the mesh device has undergone a local reset; and a first sending module 603, configured to send network recovery information to the mesh device in response to the mesh device undergoing a local reset, wherein the network recovery information is used for the mesh device to restore access to the mesh network.

[0274] In some embodiments, the determining module 602 is configured to: send a first request message to the server device; wherein the first request message is used to request the server device to determine whether the mesh device has undergone a local reset; receive network recovery information sent by the server device, the network recovery information being sent by the server device when it determines that the mesh device has undergone a local reset; and determine that the mesh device has undergone a local reset in response to receiving the network recovery information sent by the server device.

[0275] In some embodiments, the first sending module 603 is configured to: start timing in response to receiving a first notification message; and send network recovery information to the mesh device in response to the timing duration reaching a first duration.

[0276] In some embodiments, the first sending module 603 is configured to: send a second request message to the mesh device, wherein the second request message is used to request the establishment of a communication connection with the mesh device; and send network recovery information to the mesh device based on the communication connection.

[0277] In some embodiments, the apparatus further includes: a second receiving module configured to receive a second notification message sent by the mesh device based on a communication connection, wherein the second notification message is sent by the mesh device when the authentication of the server device is successful; and a first sending module 603 configured to send network recovery information to the mesh device based on a communication connection in response to receiving the second notification message.

[0278] In some embodiments, the network recovery information includes the device key of the mesh device; the first sending module 603 is configured to: in response to a local reset of the mesh device, send the device key to the mesh device, wherein the device key is used by the mesh device to decrypt the stored network configuration information and restore access to the mesh network based on the decrypted network configuration information.

[0279] In some embodiments, the apparatus further includes: a third receiving module configured to receive a third notification message sent by the mesh device, wherein the third notification message is sent by the mesh device after it has regained access to the mesh network; and a server device sending heartbeat information.

[0280] Figure 7 This is a block diagram illustrating another network processing apparatus according to an exemplary embodiment, such as... Figure 7 As shown, the device includes: a first sending module 701, configured to send a first notification message in response to a mesh device being in an unconfigured state, the first notification message indicating that the mesh device is in an unconfigured state; a receiving module 702, configured to receive network recovery information sent by a gateway device, wherein the network recovery information is sent by the gateway device after determining that the mesh device has undergone a local reset based on the first notification message; and a recovery module 703, configured to restore access to the wireless mesh network based on the network recovery information.

[0281] In some embodiments, the network recovery information includes the device key of the mesh device; the recovery module 703 is configured to: decrypt the locally stored network configuration information based on the device key; and restore access to the mesh network based on the decrypted network configuration information.

[0282] In some embodiments, the apparatus further includes: an acquisition module configured to acquire network configuration information required for the mesh device to access the mesh network in response to triggering a local reset of the mesh device; and an encryption module configured to encrypt and store the network configuration information.

[0283] In some embodiments, the receiving module 702 is configured to: receive a second request message sent by the gateway device; establish a communication connection with the gateway device based on the second request message; and receive network recovery information sent by the gateway device through the communication connection.

[0284] In some embodiments, the apparatus further includes: a second sending module configured to send a second notification message to a gateway device via a communication connection in response to successful authentication of the server device; and a receiving module 702 configured to receive network recovery information sent by the gateway device via a communication connection after receiving the second notification message.

[0285] In some embodiments, the apparatus further includes: a third sending module configured to send a third notification message to a gateway device in response to the mesh device re-accessing the mesh network; wherein the third notification message is used by the gateway device to send heartbeat information to the server device.

[0286] Figure 8 This is a block diagram illustrating yet another network processing apparatus according to an exemplary embodiment, such as... Figure 8 As shown, the device includes: a first receiving module 801, configured to receive a first request message sent by a gateway device, wherein the first request message is sent by the gateway device after receiving a first notification message sent by a mesh device, and the first notification message is used to indicate that the mesh device is in an unconfigured state; a determining module 802, configured to determine whether the mesh device has undergone a local reset; and a sending module 803, configured to send network recovery information to the gateway device in response to determining that the mesh device has undergone a local reset; wherein the network recovery information is sent by the gateway device to the mesh device so that the mesh device can restore access to the wireless mesh network based on the network recovery information.

[0287] In some embodiments, the network recovery information includes the device key of the mesh device; the sending module 803 is configured to: in response to determining that the mesh device has undergone a local reset, send the device key to the gateway device; wherein, the device key is used by the gateway device to send to the mesh device so that the mesh device can decrypt the stored network configuration information based on the device key; the decoded network configuration information is used by the mesh device to restore access to the mesh network.

[0288] In some embodiments, the determining module 802 is configured to: determine whether the device information of the mesh device is bound to a user account; and in response to the device information of the mesh device being bound to a user account, determine that the mesh device has undergone a local reset.

[0289] In some embodiments, the apparatus further includes: a second receiving module configured to receive heartbeat information sent by a gateway device; wherein the heartbeat information is sent by the gateway device after receiving a third notification message, and the third notification message is sent by the mesh device to the gateway device after restoring access to the mesh network.

[0290] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0291] Figure 9 This is a structural block diagram of an electronic device 900 according to an exemplary embodiment. Exemplarily, the electronic device 900 may be a mesh device as described in the above embodiments.

[0292] Reference Figure 9 The electronic device 900 may include one or more of the following components: processing component 902, memory 904, power supply component 906, multimedia component 908, audio component 910, input / output (I / O) interface 912, sensor component 914, and communication component 916.

[0293] Processing component 902 typically controls the overall operation of electronic device 900, such as operations associated with at least one of display, telephone call, data communication, camera operation, and recording operation. Processing component 902 may include one or more processors 920 to execute instructions to complete all or part of the steps of the methods performed by the electronic device described above. Furthermore, processing component 902 may include one or more modules to facilitate interaction between processing component 902 and other components. For example, processing component 902 may include a multimedia module to facilitate interaction between multimedia component 908 and processing component 902.

[0294] Memory 904 is configured to store various types of data to support operation on electronic device 900. Examples of such data include at least one of the following: instructions for any application or method operating on electronic device 900, contact data, phonebook data, messages, pictures, and videos. Memory 904 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.

[0295] Power supply component 906 provides power to various components of electronic device 900. Power supply component 906 may include at least one of the following: a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 900.

[0296] Multimedia component 908 includes a screen that provides an output interface between electronic device 900 and user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a Touch Panel, the screen 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 sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 908 includes a front-facing camera and / or a rear-facing camera. When electronic device 900 is in an operating mode, such as a shooting mode or video 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.

[0297] Audio component 910 is configured to output and / or input audio signals. For example, audio component 910 includes a microphone (MIC) configured to receive external audio signals when electronic device 900 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 904 or transmitted via communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.

[0298] I / O interface 912 provides an interface between processing component 902 and peripheral interface modules, such as keyboards, click wheels, and buttons. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0299] Sensor assembly 914 includes one or more sensors for providing state assessments of various aspects of electronic device 900. For example, sensor assembly 914 may detect the on / off state of electronic device 900, the relative positioning of components such as the display and keypad of electronic device 900, changes in position of electronic device 900 or one of its components, the presence or absence of user contact with electronic device 900, orientation or acceleration / deceleration of electronic device 900, and temperature changes of electronic device 900. Sensor assembly 914 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 914 may also include an optical sensor, such as a complementary metal-oxide-semiconductor (CMOS) or charge-coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, sensor assembly 914 may also include, but is not limited to, at least one of the following: an accelerometer, a gyroscope, a magnetometer, a pressure sensor, and a temperature sensor.

[0300] Communication component 916 is configured to facilitate wired or wireless communication between electronic device 900 and other devices. Electronic device 900 can access wireless networks based on communication standards, such as Wi-Fi, 4G, 5G, or combinations thereof. In one exemplary embodiment, communication component 916 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 916 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), Infrared Data Association (IrDA), Ultra Wide Band (UWB), Bluetooth (BT), and other technologies.

[0301] In an exemplary embodiment, the electronic device 900 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.

[0302] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including executable instructions or a computer program, which can be executed by a processor 920 of an electronic device 900 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0303] A non-transitory computer-readable storage medium, when instructions on the storage medium are executed by a processor of an electronic device, enables the electronic device to perform any of the network processing methods described in the embodiments of this disclosure. For example, the method includes:

[0304] Receive a first notification message from a wireless mesh device, the first notification message indicating that the mesh device is in an unconfigured state; determine whether the mesh device has undergone a local reset; in response to the mesh device undergoing a local reset, send network recovery information to the mesh device, wherein the network recovery information is used for the mesh device to restore access to the mesh network.

[0305] This disclosure provides a computer program product comprising a computer program or executable instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or executable instructions from the computer-readable storage medium and executes the computer program or executable instructions, causing the computer device to perform any of the network processing methods described in this disclosure.

[0306] Figure 10This is a block diagram illustrating an apparatus 1000 for network processing according to an exemplary embodiment. For example, apparatus 1000 may be provided as a server or a gateway. (Refer to...) Figure 10 The device 1000 includes a processing component 1022, which further includes one or more processors, and memory resources represented by memory 1032 for storing instructions, such as application programs, that can be executed by the processing component 1022. The application programs stored in memory 1032 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 1022 is configured to execute instructions to perform any of the aforementioned network processing methods. For example, the method includes:

[0307] In response to the mesh device being in an unconfigured state, a first notification message is sent, which indicates that the mesh device is in an unconfigured state; network recovery information is received from the gateway device, which is sent by the gateway device after determining that the mesh device has undergone a local reset; based on the network recovery information, access to the wireless mesh network is restored.

[0308] or,

[0309] The method also includes:

[0310] The system receives a first request message from the gateway device, wherein the first request message is sent by the gateway device after receiving a first notification message from the mesh device, and the first notification message is used to indicate that the mesh device is in an unconfigured state; determines whether the mesh device has undergone a local reset; and in response to determining that the mesh device has undergone a local reset, sends network recovery information to the gateway device; wherein the network recovery information is sent by the gateway device to the mesh device so that the mesh device can restore access to the wireless mesh network based on the network recovery information.

[0311] Device 1000 may also include a power supply component 1026 configured to perform power management of device 1000, a wired or wireless network interface 1050 configured to connect device 1000 to a network, and an input / output (I / O) interface 1058. Device 1000 can operate an operating system stored in memory 1032, such as Windows Server™, Mac OSX™, Unix™, Linux™, FreeBSD™, or similar.

[0312] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure 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 disclosure are indicated by the claims.

[0313] It should be understood that this disclosure is not limited to the precise structures 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 disclosure is limited only by the appended claims.

Claims

1. A network processing method, characterized in that, The method includes: Receive a first notification message sent by a wireless mesh device, the first notification message being used to indicate that the mesh device is in an unconfigured state; Determine whether the mesh device has undergone a local reset; In response to a local reset of the mesh device, network recovery information is sent to the mesh device, wherein the network recovery information is used for the mesh device to restore access to the mesh network.

2. The method according to claim 1, characterized in that, Determining whether the mesh device has undergone a local reset includes: Send a first request message to the server device; wherein the first request message is used to request the server device to determine whether the mesh device has undergone a local reset; Receive network recovery information sent by the server device, wherein the network recovery information is sent by the server device when it determines that the mesh device has undergone a local reset; In response to receiving the network recovery information sent by the server device, it is determined that the mesh device has undergone a local reset.

3. The method according to claim 1, characterized in that, Sending network recovery information to the mesh device includes: In response to receiving the first notification message, a timer is started; In response to the first duration being reached, the network recovery information is sent to the mesh device.

4. The method according to claim 1, characterized in that, Sending network recovery information to the mesh device includes: Send a second request message to the mesh device, wherein the second request message is used to request the establishment of a communication connection with the mesh device; Based on the communication connection, the network recovery information is sent to the mesh device.

5. The method according to claim 4, characterized in that, The method further includes: Based on the communication connection, a second notification message sent by the mesh device is received, wherein the second notification message is sent by the mesh device after successful authentication of the server device; The step of sending the network recovery information to the mesh device based on the communication connection includes: In response to receiving the second notification message, the network recovery information is sent to the mesh device based on the communication connection.

6. The method according to any one of claims 1 to 5, characterized in that, The network recovery information includes the device key of the mesh device; The step of sending network recovery information to the mesh device in response to a local reset includes: In response to a local reset of the mesh device, the device key is sent to the mesh device, wherein the device key is used by the mesh device to decrypt the stored network configuration information and restore access to the mesh network based on the decrypted network configuration information.

7. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive a third notification message sent by the mesh device, wherein the third notification message is sent by the mesh device after it has regained access to the mesh network; Send heartbeat information to the server device.

8. A network processing method, characterized in that, The method includes: In response to the wireless mesh device being in an unconfigured state, a first notification message is sent, the first notification message being used to indicate that the mesh device is in an unconfigured state; Receive network recovery information sent by the gateway device, wherein the network recovery information is sent by the gateway device when it determines that the mesh device has undergone a local reset based on the first notification message; Based on the network recovery information, access to the mesh network is restored.

9. The method according to claim 8, characterized in that, The network recovery information includes the device key of the mesh device; The step of restoring access to the mesh network based on the network recovery information includes: Based on the device key, the locally stored network configuration information is decrypted; Based on the decrypted network configuration information, access to the mesh network is restored.

10. The method according to claim 9, characterized in that, The method further includes: In response to triggering a local reset of the mesh device, obtain the network configuration information required for the mesh device to access the mesh network; The power distribution network information is stored in encrypted form.

11. The method according to claim 8, characterized in that, The network recovery information sent by the receiving gateway device includes: Receive the second request message sent by the gateway device; Establish a communication connection with the gateway device based on the second request message; Receive the network recovery information sent by the gateway device through the communication connection.

12. The method according to claim 11, characterized in that, The method further includes: In response to successful authentication of the server device, a second notification message is sent to the gateway device through the communication connection; Receiving the network recovery information sent by the gateway device through the communication connection includes: The gateway device receives network recovery information sent through the communication connection after receiving the second notification message.

13. The method according to claim 8, characterized in that, The method further includes: In response to the mesh device reconnecting to the mesh network, a third notification message is sent to the gateway device; The third notification message is used by the gateway device to send heartbeat information to the server device.

14. A network processing method, characterized in that, The method includes: The gateway device receives a first request message, wherein the first request message is sent by the gateway device after receiving a first notification message from the wireless mesh device, and the first notification message is used to indicate that the mesh device is in an unconfigured state. Determine whether the mesh device has undergone a local reset; In response to determining that the mesh device has undergone a local reset, network recovery information is sent to the gateway device; wherein the network recovery information is sent by the gateway device to the mesh device so that the mesh device can restore access to the mesh network based on the network recovery information.

15. The method according to claim 14, characterized in that, The network recovery information includes the device key of the mesh device; The step of sending network recovery information to the gateway device in response to determining that the mesh device has undergone a local reset includes: In response to determining that the mesh device has undergone a local reset, the device key is sent to the gateway device; The device key is sent by the gateway device to the mesh device so that the mesh device can decrypt the stored network configuration information based on the device key; the decoded network configuration information is used by the mesh device to restore access to the mesh network.

16. The method according to claim 14, characterized in that, Determining whether the mesh device has undergone a local reset includes: Determine whether the device information of the mesh device is bound to the user account; In response to the binding of the device information of the mesh device with the user account, it is determined that the mesh device has undergone a local reset.

17. The method according to claim 14, characterized in that, The method further includes: Receive heartbeat information sent by the gateway device; The heartbeat information is sent by the gateway device after receiving the third notification message, which is sent by the mesh device to the gateway device after restoring access to the mesh network.

18. A network processing device, characterized in that, The device includes: The first receiving module is configured to receive a first notification message sent by a wireless mesh device, the first notification message being used to indicate that the mesh device is in an unconfigured network state. The module is configured to determine whether the mesh device has undergone a local reset. The first sending module is configured to send network recovery information to the mesh device in response to a local reset of the mesh device, wherein the network recovery information is used for the mesh device to restore access to the mesh network.

19. The apparatus according to claim 18, characterized in that, The determining module is configured as follows: Send a first request message to the server device; wherein the first request message is used to request the server device to determine whether the mesh device has undergone a local reset; Receive network recovery information sent by the server device, wherein the network recovery information is sent by the server device when it determines that the mesh device has undergone a local reset; In response to receiving the network recovery information sent by the server device, it is determined that the mesh device has undergone a local reset.

20. The apparatus according to claim 18, characterized in that, The first sending module is configured as follows: In response to receiving the first notification message, a timer is started; In response to the first duration being reached, the network recovery information is sent to the mesh device.

21. The apparatus according to any one of claims 18 to 20, characterized in that, The network recovery information includes the device key of the mesh device; The first sending module is configured as follows: In response to a local reset of the mesh device, the device key is sent to the mesh device, wherein the device key is used by the mesh device to decrypt the stored network configuration information and restore access to the mesh network based on the decrypted network configuration information.

22. A network processing device, characterized in that, The device includes: The first sending module is configured to send a first notification message in response to a wireless mesh device being in an unconfigured state, the first notification message being used to indicate that the mesh device is in an unconfigured state. The receiving module is configured to receive network recovery information sent by the gateway device, wherein the network recovery information is sent by the gateway device when it determines that the mesh device has undergone a local reset based on the first notification message; The recovery module is configured to restore access to the wireless mesh network based on the network recovery information.

23. The apparatus according to claim 22, characterized in that, The network recovery information includes the device key of the mesh device; The recovery module is configured as follows: Based on the device key, the locally stored network configuration information is decrypted; Based on the decrypted network configuration information, access to the mesh network is restored.

24. The apparatus according to claim 22, characterized in that, The device further includes: The acquisition module is configured to acquire the network configuration information required for the mesh device to access the mesh network in response to triggering a local reset of the mesh device. The encryption module is configured to encrypt and store the distribution network information.

25. A network processing device, characterized in that, The device includes: The first receiving module is configured to receive a first request message sent by the gateway device, wherein the first request message is sent by the gateway device after receiving a first notification message sent by the wireless mesh device, and the first notification message is used to indicate that the mesh device is in an unconfigured state. The module is configured to determine whether the mesh device has undergone a local reset. The sending module is configured to send network recovery information to the gateway device in response to determining that the mesh device has undergone a local reset; wherein the network recovery information is sent by the gateway device to the mesh device so that the mesh device can restore access to the mesh network based on the network recovery information.

26. The apparatus according to claim 25, characterized in that, The network recovery information includes the device key of the mesh device; The sending module is configured as follows: In response to determining that the mesh device has undergone a local reset, the device key is sent to the gateway device; wherein, the device key is used by the gateway device to send to the mesh device so that the mesh device can decrypt the stored network configuration information based on the device key; the decoded network configuration information is used by the mesh device to restore access to the mesh network.

27. The apparatus according to claim 25, characterized in that, The determining module is configured as follows: Determine whether the device information of the mesh device is bound to the user account; In response to the binding of the device information of the mesh device with the user account, it is determined that the mesh device has undergone a local reset.

28. An electronic device, characterized in that, include: processor; Memory used to store computer programs or instructions; The processor executes the computer program or instructions to implement the steps of the method according to any one of claims 1 to 17.

29. A non-transitory computer-readable storage medium storing a computer program or instructions, characterized in that, When the computer program or instructions in the storage medium are executed by a processor, the steps of the method according to any one of claims 1 to 17 are implemented.

30. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 17.

Images