Network fault recovery method and device, and computer readable medium

Abstract

The invention provides a network failure recovery method, which comprises the following steps that: master node equipment receives child node attribute information sent by child node equipment directly connected with the master node equipment, determines a backup master node according to the child node attribute information and notifies the backup master node, so that the backup master node can replace the master node equipment when networking is carried out again due to a network failure; wherein the sub-node attribute information comprises at least one of the following information: capability information and load information of the sub-node equipment, and connection information of the sub-node equipment and the terminal equipment; automatic recovery of network faults can be realized; at least one of the capability of the sub-node equipment, the load of the whole network and the habit preference of connecting the terminal equipment with the sub-node equipment can be considered when the backup main node equipment is selected, the network performance after restoration is higher, and better data service experience can be provided for a user. The invention further provides a master node device, a child node device and a computer readable medium.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a network fault recovery method, device, and computer-readable medium. Background Art

[0002] Wireless Mesh network is a new type of wireless broadband access network. With its multi-hop interconnection and mesh topology characteristics, wireless Mesh network is suitable for a variety of wireless access networks such as broadband home networks, community networks, enterprise networks and metropolitan area networks. In related technologies, Mesh network includes a main node device and multiple sub-node devices. All sub-node devices synchronize the status of their downstream devices to the main node device at regular intervals. The main node device sets parameters for the sub-node devices according to demand and controls the sub-node devices. Usually, in the process of wireless Mesh networking and when problems are encountered in the use of Mesh network, users are required to manually reset the main node device and sub-node devices. Since most users are not technically skilled in the field, wireless Mesh networking causes them great difficulties.

[0003] Currently, there is technology that can complete mode switching and automatically join the Mesh network without manually setting up the master and sub-nodes during the networking process. This optimization provides convenience for users to establish a Mesh network, but it still cannot solve the problem of Mesh network failure in use. Users can only rely on manually restarting the device to solve it. Summary of the invention

[0004] The present disclosure provides a network failure recovery method, device and computer-readable medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a network fault recovery method, which is applied to a master node device in a first network, and the method includes:

[0006] Receiving sub-node attribute information sent by each sub-node device connected to the master node device, the sub-node attribute information including at least one of the following: capability information and load information of the sub-node device, and connection information between the sub-node device and the terminal device;

[0007] A backup master node device is determined according to the sub-node attribute information, and a backup master node notification message is sent to the backup master node device; the backup master node device is a sub-node device of the first network, and is used to replace the master node device when the first network fails and is re-established.

[0008] In another aspect, an embodiment of the present disclosure provides a network fault recovery method, which is applied to a sub-node device in a first network, and the method includes:

[0009] Sending first sub-node attribute information of the sub-node device to the master node device connected to the sub-node device;

[0010] When receiving the second sub-node attribute information sent by the downstream sub-node device of the sub-node device, sending the second sub-node attribute information to the master node device;

[0011] The first subnode attribute information and the second subnode attribute information include at least one of the following: capability information, load information, and connection information between the subnode device and the terminal device. The first subnode attribute information and the second subnode attribute information are used to determine the backup master node device.

[0012] On the other hand, an embodiment of the present disclosure also provides a master node device, comprising: one or more processors; a storage device, on which one or more programs are stored; when the one or more programs are executed by the one or more processors, the one or more processors implement the network fault recovery method as described above; one or more I / O interfaces, connected between the processor and the storage device, configured to implement information interaction between the processor and the storage device.

[0013] On the other hand, an embodiment of the present disclosure also provides a sub-node device, comprising: one or more processors; a storage device, on which one or more programs are stored; when the one or more programs are executed by the one or more processors, the one or more processors implement the network fault recovery method as described above; one or more I / O interfaces, connected between the processor and the storage device, configured to implement information interaction between the processor and the storage device.

[0014] On the other hand, an embodiment of the present disclosure further provides a computer-readable medium having a computer program stored thereon, wherein the program, when executed, implements the network failure recovery method as described above.

[0015] The network fault recovery method provided by the embodiment of the present disclosure comprises: a main node device receives sub-node attribute information sent by each sub-node device directly connected to it, determines a backup main node according to the sub-node attribute information and notifies the backup main node, so that the backup main node can replace the main node device when the network fails and the network is re-established; wherein the sub-node attribute information comprises at least one of the following: capability information, load information, and connection information between the sub-node device and the terminal device; the embodiment of the present disclosure determines the backup main node when the network is normal, so that when the network fails, the backup main node device can automatically switch to the main node device for re-establishing the network, thereby realizing automatic recovery of the network failure; the selection of the backup main node device will take into account at least one of the capability of the sub-node device itself, the load of the entire network, and the habitual preference of the terminal device to connect to the sub-node device, so that the network performance after recovery is higher, and a better data service experience can be provided to the user. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A schematic diagram of a network failure recovery process with a master node device as the execution subject provided in an embodiment of the present disclosure Figure 1 ;

[0017] Figure 2 A schematic diagram of a network failure recovery process with a master node device as the execution subject provided in an embodiment of the present disclosure Figure 2 ;

[0018] Figure 3 A schematic diagram of a network failure recovery process with a master node device as the execution subject provided in an embodiment of the present disclosure Figure 3 ;

[0019] Figure 4 A schematic diagram of switching between various modes of a sub-node device provided in an embodiment of the present disclosure;

[0020] Figure 5 A schematic diagram of a network failure recovery process with a subnode device as the execution subject provided in an embodiment of the present disclosure Figure 1 ;

[0021] Figure 6 A schematic diagram of a network failure recovery process with a subnode device as the execution subject provided in an embodiment of the present disclosure Figure 2 ;

[0022] Figure 7 A schematic diagram of a network failure recovery process with a subnode device as the execution subject provided in an embodiment of the present disclosure Figure 3 ;

[0023] Figure 8 A schematic diagram of a network failure recovery process with a subnode device as the execution subject provided in an embodiment of the present disclosure Figure 4 ;

[0024] Fig. 9 A schematic diagram of a network failure recovery process with a subnode device as the execution subject provided in an embodiment of the present disclosure Figure 5 ;

[0025] Fig.10a A schematic diagram of the Mesh network topology for the initial networking provided by an embodiment of the present disclosure;

[0026] Fig.10b A schematic diagram of the Mesh network topology after selecting a backup master node device provided in an embodiment of the present disclosure;

[0027] Fig.10c A schematic diagram of the topology after the rapid reorganization of the network provided by the embodiment of the present disclosure;

[0028] Fig.11a A schematic diagram of a module of a master node device provided in an embodiment of the present disclosure;

[0029] Fig.11b A schematic diagram of a module of a sub-node device provided in an embodiment of the present disclosure;

[0030] Fig.12 A schematic diagram of the structure of a master node device and a sub-node device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] Example embodiments will be described more fully below with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete and to enable those skilled in the art to fully understand the scope of the present disclosure.

[0032] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0033] The terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, the presence of the features, wholes, steps, operations, elements and / or components is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof is not excluded.

[0034] The embodiments described herein may be described with reference to plan views and / or cross-sectional views by means of idealized schematic diagrams of the present disclosure. Therefore, the example illustrations may be modified according to manufacturing techniques and / or tolerances. Therefore, the embodiments are not limited to the embodiments shown in the accompanying drawings, but include modifications of the configurations formed based on the manufacturing process. Therefore, the regions illustrated in the accompanying drawings have schematic properties, and the shapes of the regions shown in the figures illustrate the specific shapes of the regions of the elements, but are not intended to be limiting.

[0035] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless explicitly defined as such herein.

[0036] The Mesh network is composed of a master node device and multiple sub-node devices. The uplink connection of the master node device can provide WAN (Wide Area Network) access to itself and the sub-node devices. If the WAN connection of the master node device or the Mesh network connection cannot be restored due to special software or hardware reasons, the entire Mesh network will be paralyzed. In the related art, the above problem is solved by selecting a backup master node device to switch the master node device. The basis for selecting the backup master node device is a preset value, and the sub-node device with the largest received signal strength or greater than the preset value among all sub-node devices is selected as the backup master node device. However, selecting the backup master node device based solely on the received signal strength does not fully consider the relevant information of the candidate sub-node device itself. It is possible that the candidate master node device selected based on the received signal strength will lower the performance of the entire Mesh network.

[0037] To solve the above problems, the disclosed embodiment provides a network fault recovery method, which is applied to a master node device in a first network. In the disclosed embodiment, the first network refers to a Mesh network. Figure 1 As shown, the method comprises the following steps:

[0038] Step S11, receiving sub-node attribute information sent by each sub-node device connected to the main node device, the sub-node attribute information includes at least one of the following: capability information of the sub-node device, load information, and connection information between the sub-node device and the terminal device.

[0039] In a Mesh network, the master node device is connected to each sub-node device of the first level, and each sub-node device of the first level is connected to its downstream sub-node device (i.e., the second-level sub-node device). Each sub-node device reports its own sub-node attribute information to its upstream node device. If its upstream node device is another sub-node device, the other sub-node device will further report it to the upstream sub-node device of the other sub-node device until it is reported to the master node device.

[0040] Each sub-node device can carry sub-node attribute information in the extended information of the 1905 protocol. The sub-node attribute information is the information of the sub-node device itself, which can include one of the following or any combination: capability information of the sub-node device, load information, and connection information between the sub-node device and the terminal device. Capability information can include theoretical supported bandwidth of the sub-node device, supported network standard information, for example, whether it supports 5G network, etc.; load information can include the number of data transceiver packets and transmission rate of the terminal device connected to the sub-node device, such as TX, RX data transceiver information; connection information between the sub-node device and the terminal device can include the number of terminal devices connected to the sub-node device, connection duration, and traffic used by the terminal device on the sub-node device. The connection information between the sub-node device and the terminal device can be a connection list, which can reflect the user's usage preferences. For example, the terminal device accesses the router in the living room the most times and has the longest connection duration, indicating that the user's frequent activities are in the living room.

[0041] In order to select a backup master node device, each sub-node device and the master node device will periodically exchange information, and the information includes at least one of the following: MAC address, RSSI (Received Signal Strength Indication) information, connection information between the sub-node device and the terminal device, WAN / LAN capability information, and actual data transmission and reception information of each sub-node device. In the embodiment of the present disclosure, the information may also include at least one of the following: WAN side bandwidth, theoretical and actual rates; LAN side (including wired and wireless) theoretical bandwidth, actual rate, WiFi capability information. The information can be sent via a socket or carried in an extended field of the 1905 protocol.

[0042] Step S12, determine the backup master node device according to the sub-node attribute information, and send a backup master node notification message to the backup master node device; the backup master node device is a sub-node device of the first network, used to replace the main node device when the first network fails and is re-established.

[0043] The master node device can calculate a current optimal sub-node device based on the sub-node attribute information reported by each sub-node and in combination with the Mesh topology diagram, and use the current optimal sub-node device as the backup master node device. In some embodiments, the backup master node device can be one of the sub-node devices. Once the Mesh network fails and cannot be restored, the master node device exits the Mesh network, and the backup master node device switches to the master node device for rapid re-networking. In some embodiments, multiple backup master node devices can also be determined, each backup master node device is a sub-node device, and a backup master node device queue is obtained by sorting by priority. The sub-node device with the best sub-node attribute information is placed in front of the queue. In the case that the Mesh network fails and cannot be restored, the master node device will switch to the sub-node device with the highest priority first. In the case that the sub-node device is unable to perform the function, the next sub-node device in the queue will be selected as the master node device.

[0044] In some embodiments, the backup master node device can be determined based on the subnode attribute information and the priority or weight of the preset subnode attribute information. The priority or weight can be set based on user needs, so that the determined backup master node device better meets user needs and further improves the user service experience.

[0045] After determining the backup master node device, the master node device can send a backup master node notification message to the backup master node device to notify the backup master node device that it has been selected as the backup master node. After receiving the backup master node notification message, the backup master node device can broadcast in the Mesh network to announce that it has been selected as the backup master node device.

[0046] The network fault recovery method provided by the embodiment of the present disclosure comprises: a main node device receives sub-node attribute information sent by each sub-node device directly connected to it, determines a backup main node according to the sub-node attribute information and notifies the backup main node, so that the backup main node can replace the main node device when the network fails and the network is re-established; wherein the sub-node attribute information comprises at least one of the following: capability information, load information, and connection information between the sub-node device and the terminal device; the embodiment of the present disclosure determines the backup main node when the network is normal, so that when the network fails, the backup main node device can automatically switch to the main node device for re-establishing the network, thereby realizing automatic recovery of the network failure; the selection of the backup main node device will take into account at least one of the capability of the sub-node device itself, the load of the entire network, and the habitual preference of the terminal device to connect to the sub-node device, so that the network performance after recovery is higher, and a better data service experience can be provided to the user.

[0047] In some embodiments, Figure 2As shown, after determining the backup master node device according to the subnode attribute information and sending the backup master node notification message to the backup master node device (ie, step S12), the method further includes the following steps:

[0048] Step S13, when the backup master node device is different from the backup master node device determined last time, a sub-node recovery message is sent to the backup master node device determined last time, and the sub-node recovery message is used to indicate that the backup master node device determined last time is restored to a sub-node device; wherein, the backup master node device determined last time is determined by the master node device based on the sub-node attribute information received last time.

[0049] Each sub-node device may send its own sub-node attribute information according to a preset first period, or send its own sub-node attribute information when the sub-node attribute information of the sub-node device changes. For each sub-node attribute information reported by each sub-node device, the master node device will determine the current backup master node device. If the backup master node device determined this time is different from the backup master node device determined last time, the backup master node device determined last time will be restored to the identity of the sub-node device.

[0050] In addition to accessing the first network, the master node device also has upstream access to the second network. In some embodiments, the first network is a Mesh network and the second network is the Internet. In the Mesh network, the master node device and the sub-node device are connected via a LAN (Local Area Network) or Wifi, and the master node device accesses the Internet via a WAN.

[0051] Since a Mesh network involves multiple sub-node devices, the user may not be able to determine which sub-node device has a problem, resulting in a poor user experience. In order to solve the above problem, the embodiment of the present disclosure adds a first network connection detection function to the master node device. Therefore, in some embodiments, the method may also include the following steps: detecting the connection status of the first network and / or the connection status of the second network.

[0052] The following combination Figure 3 , the network failure recovery process is described in detail, such as Figure 3 As shown, the network failure recovery process includes the following steps:

[0053] Step S21, detecting the connection status of the first network and the connection status of the second network. If the first network connection is normal and the second network connection is abnormal, executing step S22; if the first network connection is abnormal, executing step S26.

[0054] If the master node device does not receive the Mesh message sent by its downstream child node device within the timeout period A, it will be marked and stored. If the master node device does not receive the Mesh message sent by all downstream child nodes within the timeout period B, it is considered that there is a problem with the Mesh network connection between the master node device and each child node device, that is, the first network connection is abnormal. In this case, execute step S26.

[0055] If the master node device receives Mesh messages sent by all its downstream child node devices within the timeout period A, it is considered that the first network connection is normal.

[0056] In the disclosed embodiments, the data transmission and reception situation can be monitored by a monitoring thread to detect whether the connection between the main node device and the second network is normal. When necessary, the main node can also detect whether the connection with the second network is normal by actively initiating a ping of the second network. In some embodiments, the second network connection is abnormal, including: the second network connection is detected abnormally a preset number of times, the preset number of times can be three times. For example, when the WAN connection abnormality is detected for the first time, a second detection is performed. If the connection is still abnormal, a third detection is performed. If the WAN connection is still abnormal in this detection, the second network connection is considered abnormal. Continuously detecting the second network connection status for multiple times can improve the accuracy of network connection status detection, avoid frequent networking, and improve network stability.

[0057] If the first network connection is normal and the second network connection is abnormal, step S22 is executed.

[0058] Step S22: Send a second network abnormality notification message to each sub-node device connected to the master node device.

[0059] If the Mesh network connection is normal and the Internet connection is abnormal, the master node device sends a second network abnormality notification message to the downstream sub-node devices connected to it, so that each sub-node device can switch from the normal working mode to the waiting mode, and each sub-node device starts the preset time duration locally.

[0060] Step S23: repair the connection of the second network.

[0061] In order to avoid frequent networking and improve network stability, in the event of an abnormal WAN connection, the master node device can also repair the connection failure of the second network. For example, the WAN connection can be repaired by a soft restart (restarting the protocol stack).

[0062] Step S24, determining whether the second network connection is restored to normal within the first preset time period, if the second network connection is restored to normal within the first preset time period, executing step S25; otherwise, ending the process.

[0063] Step S25: Send a second network recovery notification message to each sub-node device connected to the master node device.

[0064] If the WAN connection is successfully repaired within the first preset time, that is, the WAN connection returns to normal, the master node device sends a second network recovery notification message to its connected downstream child node devices, so that each child node device can switch from waiting mode to normal working mode and clear the timing of the first preset time.

[0065] Step S26: repair the connection of the first network.

[0066] If the Mesh network connection is abnormal, the master node device can also try to repair the Mesh network connection. Specifically, the master node device determines whether the abnormal Mesh network connection is caused by a backhaul problem or a Mesh master process problem. If it is a backhaul problem, it is repaired by restarting the master process. If it is a Mesh master process problem, it is repaired by restarting the WiFi driver.

[0067] If the Mesh network connection can be repaired, the sub-node device switches to the normal working mode within the timeout period C; if the Mesh network connection cannot be repaired, the sub-node device can only wait for the timeout period C to expire and then switch to the fast networking mode.

[0068] Step S27, determining whether the first network connection is restored to normal within the second preset time period, if so, executing step S28; otherwise, ending the process.

[0069] Step S28: Send a first network recovery notification message to each sub-node device connected to the master node device.

[0070] If the master node device restores the Mesh network connection to normal within the second preset time period, the master node device sends a first network recovery notification message to each child node device connected to the master node device, so that each child node device can switch from the waiting mode to the normal working mode, and clear the timing of the second preset time period locally.

[0071] It should be noted that the user can pre-set whether to repair the WAN or Mesh connection abnormality on the master node device. If the user chooses not to repair the connection abnormality, the sub-node device can directly enter the fast networking mode from the normal working mode.

[0072] Figure 4 A schematic diagram of switching between various modes of a sub-node device provided in an embodiment of the present disclosure, such as Figure 4 As shown, the sub-node device has the following four modes: normal working mode, waiting mode, fast networking mode and backup master node mode.

[0073] The waiting mode is used to wait for the upstream node to send a network recovery notification message; the fast networking mode is used to perform the Mesh network discovery process and re-establish a WiFi or LAN connection with the new master node device; the backup master node mode can replace the master node device to continue managing the Mesh network when a problem occurs with the master node device.

[0074] The conditions for switching between normal working mode and waiting mode are abnormal Mesh / WAN connection or Mesh / WAN connection recovery. The conditions for switching between normal working mode and backup master node mode are specified or cancelled by the master node device. Backup master node mode is a special mode of the child node. The conditions for switching between this mode and waiting mode are the same as those for switching between normal working mode and waiting mode. The conditions for switching between waiting mode and fast networking mode are that if the waiting timeout occurs, the device will switch from waiting mode to fast networking mode.

[0075] In some embodiments, after determining the backup master node device according to the subnode attribute information and sending the backup master node notification message to the backup master node device (i.e., step S13), the method may further include the following steps: in the case of an update of the backup information, sending a backup information notification message carrying the updated backup information to the backup master node device, and receiving a backup information confirmation message sent by the backup master node device; or, receiving a backup information request message sent by the backup master node device, and sending a backup information response message carrying the backup information to the backup master node device. The determined backup master node device may obtain the backup information by actively sending a master node information request message, or passively receiving a backup information notification message sent by the master node device, to prepare for the subsequent switch to the master node device.

[0076] The backup information is the information stored in the master node device for use in Mesh networking, and may include at least one of the following: network topology information, identity authentication information (such as Mesh connection key), routing information, connection device information of each sub-node, etc.

[0077] The embodiment of the present disclosure also provides a network fault recovery method, which is applied to a sub-node device in a first network, such as Figure 5 As shown, the method comprises the following steps:

[0078] Step S31: Send first sub-node attribute information of a sub-node device to the main node device to which the sub-node device is connected.

[0079] In the case that the upstream node device of the sub-node device is the master node device, the sub-node device sends its own first sub-node attribute information to the master node device.

[0080] In some embodiments, the sub-node device sends first sub-node attribute information of the sub-node device to the main node device to which the sub-node device is connected according to a preset first period, or sends first sub-node attribute information of the sub-node device to the main node device to which the sub-node device is connected when the first sub-node attribute information of the sub-node device changes.

[0081] Step S32, upon receiving the second sub-node attribute information sent by the downstream sub-node device of the sub-node device, the second sub-node attribute information is sent to the main node device; wherein the first sub-node attribute information and the second sub-node attribute information include at least one of the following: capability information, load information, and connection information between the sub-node device and the terminal device of the sub-node device, and the first sub-node attribute information and the second sub-node attribute information are used to determine the backup main node device.

[0082] When the upstream node device of the sub-node device is another sub-node device in the first network, the sub-node device sends its own second sub-node attribute information to its upstream sub-node device, so that the second sub-node attribute information is sent to the master node device step by step.

[0083] Each sub-node device can carry sub-node attribute information in the extended information of the 1905 protocol. The sub-node attribute information is the information of the sub-node device itself, which may include one of the following or any combination: capability information of the sub-node device, load information, and connection information between the sub-node device and the terminal device. Capability information may include theoretical supported bandwidth of the sub-node device, supported network standard information, such as whether it supports 5G network, etc.; load information may include the number of data transceiver packets and transmission rate of the terminal device connected to the sub-node device, such as TX, RX data transceiver information; connection information between the sub-node device and the terminal device may include the number of terminal devices connected to the sub-node device, connection duration, and traffic used by the terminal device on the sub-node device. The connection information between the sub-node device and the terminal device may be a connection list, which can reflect the user's usage preferences. For example, the terminal device has the most access to the router in the living room and the longest connection duration, indicating that the user's frequent activities are in the living room.

[0084] In the network fault recovery method provided by the embodiment of the present disclosure, each sub-node device reports its own sub-node attribute information to the main node device in a step-by-step manner, so that the main node device can determine the backup main node device when the network is normal. In this way, when a network failure occurs, the backup main node device can automatically switch to the main node device for re-networking, thereby realizing automatic recovery of the network failure. The selection of the backup main node device will take into account at least one of the sub-node device's own capabilities, the load of the entire network, and the terminal device's habitual preference for connecting to the sub-node device. The network performance after recovery is higher, and can provide users with a better data service experience.

[0085] In some embodiments, Figure 6 As shown, the method may further include the following steps:

[0086] Step S41: receiving a second network abnormality notification message sent by the master node device, and switching the sub-node device from a normal working mode to a waiting mode.

[0087] The second network is a network that the master node device accesses upstream. In the embodiment of the present disclosure, the second network is the Internet. The sub-node device receives the second network abnormality notification message sent by the master node device, indicating that the WAN connection between the master node device and the Internet is abnormal at this time. In this case, the sub-node device switches from the normal working mode to the waiting mode, and starts the timing of the first preset time length, waiting for the WAN connection of the master node device to return to normal.

[0088] Step S42: When a second network recovery notification message sent by the master node device is received within the first preset time period, the sub-node device is switched from the waiting mode to the normal working mode.

[0089] If the sub-node device receives the second network recovery notification message sent by the master node device within the first preset time, it means that the master node device has repaired the WAN connection failure in time, then the sub-node device can switch from the waiting mode to the normal working mode and clear the timing of the first preset time.

[0090] Step S43: If no second network recovery notification message sent by the master node device is received within the first preset time period, the sub-node device is switched from the waiting mode to the fast networking mode.

[0091] If the sub-node device does not receive the second network recovery notification message sent by the master node device within the first preset time, it means that the master node device cannot repair the WAN connection failure in time, and the sub-node device can switch from the waiting mode to the fast networking mode.

[0092] Since a Mesh network involves multiple sub-node devices, users may not be able to determine which sub-node device has a problem, resulting in a poor user experience. In order to solve the above problem, the embodiment of the present disclosure adds a first network connection detection function to the sub-node device. Therefore, in some embodiments, such as Figure 7 As shown, the method may further include the following steps:

[0093] Step S51, detecting the connection status of the first network, if the first network connection is abnormal, executing step S52; otherwise, ending this process.

[0094] In the disclosed embodiment, the first network connection is abnormal, including: the first network connection is detected abnormally for a preset number of times, the preset number of times may be three times, and illustratively, when the Mesh network connection is detected abnormally for the first time, a second detection is performed, and if the connection is still abnormal, a third detection is performed, and if the connection is still abnormal during this detection, the Mesh network connection is considered abnormal. Multiple consecutive detections of the Mesh network connection status can improve the accuracy of the network connection status detection, avoid frequent networking, and improve network stability.

[0095] Each sub-node device can detect the connection status of the first network according to a preset period, that is, detect the status of its own access to the first network. In this way, if the connection is abnormal, it can be known which sub-node has a problem.

[0096] Step S52: Switch the subnode device from the normal working mode to the waiting mode.

[0097] If the sub-node device detects that its own connection in the first network is abnormal, the sub-node device switches from the normal working mode to the waiting mode, and waits for the first network connection to be restored within a second preset time period.

[0098] Step S53, determining whether a message broadcast by the master node device or a first network recovery notification message sent by the master node device is received within a second preset time period, if so, executing step S54; otherwise, executing step S55.

[0099] Step S54: Switch the subnode device from the waiting mode to the normal mode.

[0100] If the child node device receives a message broadcast by the master node device or a first network recovery notification message sent by the master node device within the second preset time period, indicating that the master node device has repaired the first network connection in time, the child node device can switch from the waiting mode back to the normal working mode and clear the timing of the second preset time period.

[0101] Step S55: Switch the subnode device from the waiting mode to the fast networking mode.

[0102] If the sub-node device does not receive the message broadcast by the master node device or the first network recovery notification message sent by the master node device within the second preset time, it means that the master node device cannot repair the first network connection in time, and the sub-node device can switch from the waiting mode to the fast networking mode.

[0103] In some embodiments, Figure 8 As shown, the method may further include the following steps:

[0104] Step S61, detecting the connection status of the second network, if the second network connection is abnormal, executing step S62; otherwise, ending this process.

[0105] In the disclosed embodiment, the second network connection is abnormal, including: the second network connection is detected abnormally for a preset number of times, the preset number of times may be three times, and illustratively, when the WAN connection is detected abnormally for the first time, a second detection is performed, and if the connection is still abnormal, a third detection is performed, and if the WAN connection is still abnormal during this detection, the second network connection is considered abnormal. Multiple consecutive detections of the second network connection status can improve the accuracy of the network connection status detection, avoid frequent networking, and improve network stability.

[0106] Step S62: Switch the subnode device from the normal working mode to the waiting mode.

[0107] If the sub-node device detects that the second network connection is abnormal, the sub-node device switches from the normal working mode to the waiting mode, and waits for the second network connection to be restored within a first preset time period.

[0108] Step S63, determining whether a second network recovery notification message sent by the master node device is received within the first preset time period, if so, executing step S64; otherwise, executing step S65.

[0109] Step S64: Switch the subnode device from the waiting mode to the normal mode.

[0110] If the sub-node device receives the second network recovery notification message sent by the master node device within the first preset time, it means that the master node device has repaired the second network connection in time, then the sub-node device can switch from the waiting mode to the normal working mode and clear the timing of the first preset time.

[0111] Step S65: Switch the subnode device from the waiting mode to the fast networking mode.

[0112] If the sub-node device does not receive the second network recovery notification message sent by the master node device within the first preset time period, it means that the master node device cannot repair the second network connection in time, and the sub-node device can switch from the waiting mode to the fast networking mode.

[0113] It should be noted that since the backup master node device is a special sub-node device, the backup master node device will also detect the connection status of the first network and the second network. The backup master node mode of the backup master node is equivalent to the normal working mode of an ordinary sub-node device. The process of switching between the backup master node mode and the waiting mode of the backup master node device is the same as the process of switching between the normal working mode and the waiting mode of the ordinary sub-node device.

[0114] In some embodiments, when the child node device is a backup master node device, Fig. 9As shown, the method may further include the following steps:

[0115] Step S71: receiving a backup master node notification message sent by the master node device, and switching the sub-node device from a normal working mode to a backup master node mode.

[0116] If a sub-node device receives a backup master node notification message sent by the master node device, it indicates that the sub-node device has been selected as a backup master node device, and therefore, the normal working mode can be switched to the backup master node mode.

[0117] Step S72: receiving a sub-node recovery message sent by the master node device, and switching the sub-node device from the backup master node mode to the normal working mode.

[0118] If the master node backup device receives a sub-node recovery message sent by the master node device, it means that the master node device has re-determined a new backup master node device and needs to restore the original backup master node device to a normal sub-node device. Therefore, after receiving the sub-node recovery message sent by the master node device, the master node backup device switches from the backup master node mode to the normal working mode.

[0119] In some embodiments, after switching the sub-node device from the normal working mode to the backup master node mode (step S71), the method may further include the following steps: receiving a backup information notification message sent by the master node device, and obtaining the backup information carried in the backup information notification message; or, sending a backup request message to the master node device according to a preset second period, receiving a backup information response message sent by the master node device, and obtaining the backup information carried in the backup information response message.

[0120] After the backup master node device is determined, in order to be able to perform Mesh network reorganization later, it is necessary to store backup information for network reorganization in the backup master node device. In the embodiment of the present disclosure, the backup master node device obtains the backup information in two ways: (1) the master node device actively sends the backup information, and the backup information update triggers the master node device to send the backup information to the backup master node device, so that the backup master node device can perform Mesh rapid networking based on the backup information later; (2) the master node device passively sends the backup information, and the backup master node device periodically requests the master node device to obtain the backup information.

[0121] After the waiting mode times out, the backup master node device will switch to the fast networking mode. After entering the fast networking mode, the Mesh master node will be reconstructed according to the backup information obtained from the master node device, and the master backup node device will be switched to the master node device. All sub-node devices in the Mesh network will enter the fast networking mode one after another. The new master node device starts the Mesh master control process and monitoring thread. The master control process will reconstruct the access information according to the previously obtained Mesh connection key information, and wait for each sub-node device to connect until all the sub-node devices that can be connected on the Mesh network are successfully connected. Other sub-node devices begin to execute the Mesh discovery process to find the master node device that can be connected. The new master node device performs sub-node backhaul connection verification according to the stored Mesh connection key information. Only after the verification is passed, the sub-node device is allowed to access the Mesh network.

[0122] Fig.10a A schematic diagram of a mesh network topology for initial networking provided in an embodiment of the present disclosure, such as Fig.10a As shown, the controller is the main node device, the agent is the sub-node device, and the agent can connect to the terminal device. Fig.10b A schematic diagram of the Mesh network topology after selecting a backup master node device according to an embodiment of the present disclosure is shown in FIG. Fig.10b As shown, the controller selects an agent as the backup master node device. Fig.10c A schematic diagram of the topology after the rapid reorganization of the network provided by the embodiment of the present disclosure is shown in FIG. Fig.10c As shown in the figure, after the Mesh network is re-established, Fig.10b The backup master node device in becomes the master node device, and the original master node device exits the Mesh network.

[0123] The disclosed embodiment uses two fault recovery technologies (i.e., soft restart and sub-node competition for backup master node) when problems occur in the Mesh network master node device, which can effectively solve the problems of Mesh disconnection and unusability caused by WAN connection and Mesh connection encountered by users during the use of the Mesh network. The solution of the disclosed embodiment does not require human participation and can be completed independently, greatly improving the user experience.

[0124] The disclosed embodiment can effectively solve WiFi Mesh network failures, and is particularly suitable for scenarios where the entire Mesh network is paralyzed due to an unrepairable problem in the main node device. It repairs and solves Mesh network failures for problems caused by abnormal WAN connection or abnormal WiFi / LAN connection that cause Mesh network abnormalities. The disclosed embodiment can quickly restore the Mesh network without the need for users to participate in re-networking. In the disclosed embodiment, the main node device and the sub-node device regularly detect whether the WAN connection and the Mesh connection are normal. In addition to regularly reporting the connection information between its downstream sub-node and the terminal device, each sub-node device also reports its own WAN / LAN service capabilities and service status to its upstream node device, including TX, RX packet receiving and sending status, and the actual and theoretical capabilities of WAN / LAN. The main node device collects the WAN / LAN service capabilities and service status of all sub-node devices, and will comprehensively judge the network usage of the terminal devices connected to each sub-node device in the Mesh network, find out the user's preferences, and make a comprehensive judgment based on the network topology and the network load of each sub-node device to select the backup main node device. The selected backup master node device will broadcast, and each sub-node device will save the information of the backup master node device for use when the Mesh quickly re-networks. The backup master node device can obtain the topology map and other necessary information for networking from the master node device and save it locally. If the master node device detects that the WAN connection is abnormal, it will try to repair it by itself and restart the relevant protocol stack. The sub-node device will also switch to waiting mode. If the master node successfully repairs the WAN connection, it will notify each sub-node device that the network connection is restored, and each sub-node device will switch back to normal working mode; if it cannot be repaired, it means that there is a problem with the master node device itself, and a rapid re-networking operation is performed at this time. Correspondingly, the backup master node device is converted to a master node device based on the backup information obtained from the master node. The backup information includes fronthaul (forward return) and backhaul (return) information. Other sub-node devices switch to fast networking mode after the waiting mode times out. Then the master node device receives the network access request from the sub-node device, responds and establishes a connection.

[0125] The present disclosure also provides a master node device, such as Fig.11aAs shown, the master node device includes: a fault detection module, a message transceiver module, a notification module, a problem repair module, and a backup master node selection module. Among them, the fault detection module is used to detect whether the WAN and Mesh connections are abnormal, and three detections can determine whether the connection is abnormal or not. The problem repair module performs repairs based on the results of the fault detection module. If the WAN connection is abnormal, the WAN side repair function is started, and a soft restart is performed, including a protocol stack restart and a power-off and power-on mechanism of the WAN module; for Mesh connection abnormalities, the repair mechanism includes silently executing WiFi switch operations, reloading WiFi drivers and FW (Firewall), and re-powering on and off the WiFi module. The message transceiver module is used to send broadcast messages at regular intervals, receive topology change information of subnodes, and report messages. The notification module is used for the master node device to notify each subnode of the abnormal message when it determines that the abnormality itself cannot be recovered and the Mesh connection is normal, and to notify the backup master node device when there is a change in the topology map or terminal connection. The backup master node selection module is used to select the backup master node device according to the subnode attribute information obtained by the message transceiver module and the priority order set by the user.

[0126] The present disclosure also provides a sub-node device, such as Fig.11b As shown, the sub-node device includes: a fault detection module, a message transceiver module, a notification module, a mode switching module, an information storage module, a problem repair module and a backup master node selection module. Among them, the fault detection module is used to determine whether the uplink WAN and uplink Mesh connections of the sub-node are normal, and its internal loop mechanism detects whether the WAN and Mesh connections are normal. At the same time, it determines whether the fault has occurred according to the message provided by the message transceiver module. The message transceiver module is used to report the sub-node itself and the downstream device information to the upstream node, and receive the broadcast message in the Mesh to synchronize the Mesh topology, master node information, etc. The notification module is used to broadcast messages when the WAN connection is detected to be abnormal and the Mesh is normal. For the device that becomes the backup master node, the notification module is used to inform other sub-node devices of the identity of the backup master node so as to perform Mesh networking later. The mode switching module is used to manage the state machine of the four modes of the sub-node device. The information storage module is used to store the Mesh connection key information, topology map, and terminal connection list of each sub-node device fed back by the master node device. The problem repair module and the backup master node selection module are enabled when the child node device becomes the master node device, and the specific functions are the same as those of the problem repair module and the backup master node selection module in the master node device.

[0127] The present disclosure also provides a master node device and a sub-node device, such as Fig.12 As shown, including:

[0128] at least one processor 1201;

[0129] A memory 1202 storing at least one program, and when the at least one program is executed by the at least one processor, the at least one processor implements the network failure recovery method provided in the above embodiments;

[0130] At least one I / O interface 1203 is connected between the processor and the memory and is configured to implement information exchange between the processor and the memory.

[0131] Among them, the processor 1201 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 1202 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); the I / O interface (read-write interface) 1203 is connected between the processor 1201 and the memory 1202, and can realize information interaction between the processor 1201 and the memory 1202, including but not limited to a data bus (Bus), etc.

[0132] In some embodiments, the processor 1201 , the memory 1202 , and the I / O interface 1203 are connected to each other via a bus, and further connected to other components of the computing device.

[0133] The embodiments of the present disclosure further provide a computer-readable medium on which a computer program is stored, wherein when the computer program is executed, the network failure recovery method provided in the aforementioned embodiments is implemented.

[0134] It will be appreciated by those skilled in the art that all or some of the steps in the method disclosed above, the functional modules / units in the device may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0135] Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for limiting purposes. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly stated, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, it will be understood by those skilled in the art that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A network failure recovery method, It is characterized in that Applied to a master node device in a first network, the method comprises: Receiving sub-node attribute information sent by each sub-node device connected to the master node device, the sub-node attribute information including at least one of the following: capability information and load information of the sub-node device, and connection information between the sub-node device and the terminal device; A backup master node device is determined according to the sub-node attribute information, and a backup master node notification message is sent to the backup master node device; the backup master node device is a sub-node device of the first network, and is used to replace the master node device when the first network fails and is re-established.

2. The method according to claim 1, It is characterized in that The step of determining a backup master node device according to the subnode attribute information includes: The backup master node device is determined according to the sub-node attribute information and the priority or weight of the preset sub-node attribute information.

3. The method according to claim 1, It is characterized in that After determining a backup master node device according to the subnode attribute information and sending a backup master node notification message to the backup master node device, the method further includes: In the case that the backup master node device is different from the backup master node device determined last time, a sub-node recovery message is sent to the backup master node device determined last time, and the sub-node recovery message is used to indicate that the backup master node device determined last time is restored to a sub-node device; wherein, the backup master node device determined last time is determined by the master node device based on the sub-node attribute information received last time.

4. The method according to claim 1, It is characterized in that The master node device accesses the second network, and the method further includes: Detecting a connection status of the first network and / or a connection status of the second network.

5. The method according to claim 4, It is characterized in that The method further comprises: When the first network connection is normal and the second network connection is abnormal, sending a second network abnormality notification message to each sub-node device connected to the master node device; Restoring the connection of the second network; When the second network connection returns to normal within a first preset time period, a second network recovery notification message is sent to each sub-node device connected to the master node device.

6. The method according to claim 4, It is characterized in that The method further comprises: When the first network connection is abnormal, repairing the connection of the first network; When the first network connection returns to normal within a second preset time period, a first network recovery notification message is sent to each sub-node device connected to the master node device.

7. The method according to claim 1, It is characterized in that After determining a backup master node device according to the subnode attribute information and sending a backup master node notification message to the backup master node device, the method further includes: In the case where the backup information is updated, sending a backup information notification message carrying the updated backup information to the backup master node device, and receiving a backup information confirmation message sent by the backup master node device; or, A backup information request message sent by the backup master node device is received, and a backup information response message carrying backup information is sent to the backup master node device.

8. A network failure recovery method, It is characterized in that Applied to a sub-node device in a first network, the method comprises: Sending first sub-node attribute information of the sub-node device to the master node device connected to the sub-node device; When receiving the second sub-node attribute information sent by the downstream sub-node device of the sub-node device, sending the second sub-node attribute information to the master node device; The first subnode attribute information and the second subnode attribute information include at least one of the following: capability information, load information, and connection information between the subnode device and the terminal device. The first subnode attribute information and the second subnode attribute information are used to determine the backup master node device.

9. The method according to claim 8, It is characterized in that The sending the first sub-node attribute information of the sub-node device to the master node device connected to the sub-node device includes: The first subnode attribute information of the subnode device is sent to the main node device to which the subnode device is connected according to a preset first period, or the first subnode attribute information of the subnode device is sent to the main node device to which the subnode device is connected when the first subnode attribute information of the subnode device changes.

10. The method according to claim 8, It is characterized in that The method further comprises: A second network abnormality notification message sent by the master node device is received, and the sub-node device is switched from a normal working mode to a waiting mode, wherein the second network is a network to which the master node device is connected uplink.

11. The method according to claim 10, It is characterized in that After switching the sub-node device from the normal working mode to the waiting mode, the method further includes: When receiving a second network recovery notification message sent by the master node device within a first preset time period, switching the sub-node device from the waiting mode to the normal working mode; or, When the second network recovery notification message sent by the master node device is not received within the first preset time period, the sub-node device is switched from the waiting mode to the fast networking mode.

12. The method according to claim 8, It is characterized in that The method further comprises: detecting a connection status of the first network; In case that the first network connection is abnormal, switching the sub-node device from a normal working mode to a waiting mode; When receiving a message broadcast by the master node device or a first network recovery notification message sent by the master node device within a second preset time period, switching the sub-node device from the waiting mode to the normal mode; or, When no message broadcast by the master node device or a first network recovery notification message sent by the master node device is received within a second preset time period, the sub-node device is switched from the waiting mode to the fast networking mode.

13. The method according to claim 8, It is characterized in that The method further comprises: Detecting a connection status of a second network, where the second network is a network to which the master node device is connected uplink; In case that the second network connection is abnormal, switching the sub-node device from a normal working mode to a waiting mode; When receiving a second network recovery notification message sent by the master node device within a first preset time period, switching the sub-node device from the waiting mode to the normal mode; or, When the second network recovery notification message sent by the master node device is not received within the first preset time period, the sub-node device is switched from the waiting mode to the fast networking mode.

14. The method according to claim 8, It is characterized in that The method further comprises: Receive a backup master node notification message sent by the master node device, and switch the sub-node device from a normal working mode to a backup master node mode.

15. The method of claim 14, It is characterized in that After switching the sub-node device from the normal working mode to the backup master node mode, the method further includes: Receive a sub-node recovery message sent by the master node device, and switch the sub-node device from the backup master node mode to a normal working mode.

16. The method of claim 14, It is characterized in that After switching the sub-node device from the normal working mode to the backup master node mode, the method further includes: receiving a backup information notification message sent by the master node device, and acquiring the backup information carried in the backup information notification message; or, A backup request message is sent to the master node device according to a preset second period, a backup information response message sent by the master node device is received, and the backup information carried in the backup information response message is acquired.

17. A master node device, include: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the network fault recovery method according to any one of claims 1 to 7; One or more I / O interfaces are connected between the processor and the storage device and are configured to implement information interaction between the processor and the storage device.

18. A subnode device, include: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the network fault recovery method according to any one of claims 8 to 16; One or more I / O interfaces are connected between the processor and the storage device and are configured to implement information interaction between the processor and the storage device.

19. A computer readable medium having a computer program stored thereon, in, When the program is executed, the network fault recovery method according to any one of claims 1 to 7 is implemented, or the network fault recovery method according to any one of claims 8 to 16 is implemented.

Images