Exception handling method, exception handling device, electronic equipment and readable storage medium

Through the coordinated work between routing equipment, mutual aid equipment and sub-device, the connection status is detected and the physical address routing table is updated, the problem of abnormal connections between multiple electronic devices is solved, and normal data transmission between electronic devices is achieved.

CN120200967APending Publication Date: 2025-06-24MIDEA GRP (SHANGHAI) CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311788081.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-12-22
Publication Date
2025-06-24

AI Technical Summary

Technical Problem

When multiple electronic devices are connected to the same network at the same time, how to efficiently handle connection abnormalities between electronic devices to ensure the normality of data transmission.

Method used

Through collaborative work between the routing device, mutual aid device and sub-device, the connection status is detected, the routing device is restarted, and instructions are sent to the mutual aid device and sub-device, and the dynamic host configuration protocol is initiated to update the physical address routing table.

Benefits of technology

It realizes efficient handling of connection abnormalities between the routing device and the mutual aid device, ensures that all electronic devices connected to the first network can transmit data normally, and improves the networking experience of the sub-device.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120200967A_ABST
    Figure CN120200967A_ABST
Patent Text Reader

Abstract

The invention provides an exception handling method, an exception handling device, electronic equipment and a readable storage medium, the exception handling method is executed by routing equipment, the routing equipment is connected to a first network, the routing equipment is connected with mutual assistance equipment, and the mutual assistance equipment is connected with sub-equipment. The exception handling method comprises the following steps: detecting a connection state with mutual assistance equipment; under the condition that the mutual assistance equipment is disconnected, restarting is carried out; after restarting, a first instruction is sent to the mutual assistance device and the sub-device in sequence, and the first instruction is used for notifying the mutual assistance device and the sub-device to initiate a dynamic host configuration protocol and update the physical address routing table.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of Internet of Things technology. Specifically, it relates to an exception handling method, an exception handling device, an electronic device, and a readable storage medium. Background Art

[0002] In related technologies, network connections are established between electronic devices to achieve data transmission between electronic devices. However, during the operation of electronic devices, connection anomalies may occur between electronic devices, which may further lead to abnormal data transmission between electronic devices. Especially when multiple electronic devices are connected to the same network simultaneously, how to efficiently handle exceptions when an electronic device encounters an anomaly has become an urgent problem to be solved. Summary of the Invention

[0003] This application aims to solve at least one of the technical problems existing in the prior art.

[0004] To this end, the first aspect of this application provides an exception handling method.

[0005] The second aspect of this application provides an exception handling method.

[0006] The third aspect of this application provides an exception handling method.

[0007] The fourth aspect of this application provides an exception handling device.

[0008] The fifth aspect of this application provides an exception handling device.

[0009] The sixth aspect of this application provides an exception handling device.

[0010] The seventh aspect of this application provides an electronic device.

[0011] The eighth aspect of this application provides a computer-readable storage medium.

[0012] The ninth aspect of this application provides a computer program product.

[0013] The first aspect of this application provides an exception handling method, which is executed by a routing device. The routing device is connected to a first network, the routing device is connected to a mutual assistance device, and the mutual assistance device is connected to a sub-device. The exception handling method includes: detecting the connection status with the mutual assistance device; restarting in the case of disconnection from the mutual assistance device; after restarting, sequentially sending a first instruction to the mutual assistance device and the sub-device, where the first instruction is used to notify the mutual assistance device and the sub-device to initiate a Dynamic Host Configuration Protocol and update the physical address routing table.

[0014] The exception handling method provided by this application can be executed by a routing device. Herein, the routing device is connected to a first network, the routing device is connected to a mutual assistance device, and the mutual assistance device is connected to a sub-device.

[0015] It can be understood that in the case where the sub-device does not meet the connection conditions of the first network, that is, when the sub-device cannot directly connect to the first network through the routing device, at least one mutual assistance device is searched. Among them, the mutual assistance device is connected to the first network, that is, the mutual assistance device is connected to the routing device of the first network, so as to realize connecting to the first network through the routing device. Thus, when the signal strength of the network signal of the routing device received by the sub-device is low and it cannot ensure a continuous and stable connection to the first network through the routing device, a continuous and stable connection to the first network is realized through the mutual assistance device, improving the networking experience of the sub-device.

[0016] Furthermore, after the sub-device is connected to the first network through the mutual assistance device, the connection status between the routing device and the mutual assistance device is detected. That is, it is detected whether the connection between the routing device and the mutual assistance device is abnormal.

[0017] Furthermore, in the case where the connection between the routing device and the mutual assistance device is disconnected, the routing device is restarted. After the routing device is restarted, the routing device is controlled to send a first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device step by step. The first instruction is used to notify the mutual assistance device and the sub-devices to initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

[0018] Correspondingly, after the mutual assistance device and the sub-devices receive the first instruction, they can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. After the mutual assistance device and the sub-devices update the physical address routing table, they can realize data transmission between devices according to the physical address routing table, thus realizing the handling of the connection exception between the routing device and the mutual assistance device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0019] The exception handling method provided by this application restarts the routing device in the case where the connection between the routing device and the mutual assistance device is disconnected. After the routing device is restarted, the routing device is controlled to send a first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device step by step. After the mutual assistance device and the sub-devices receive the first instruction, they can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thus, the connection exception between the routing device and the mutual assistance device is handled, and the normal data transmission of all electronic devices connected to the first network is ensured.

[0020] According to a second aspect of the present application, an exception handling method is provided, which is executed by a mutual assistance device. The mutual assistance device is connected to a first network through a routing device, and the mutual assistance device is connected to sub-devices. The exception handling method includes: receiving a first instruction sent by the routing device when the routing device restarts; and initiating a Dynamic Host Configuration Protocol (DHCP) and updating a physical address routing table according to the first instruction.

[0021] The exception handling method provided by the present application can be executed by a mutual assistance device. Among them, the mutual assistance device is connected to a first network through a routing device, and the mutual assistance device is connected to sub-devices.

[0022] After the mutual assistance device receives the first instruction, it can initiate a DHCP according to the first instruction, and then update the physical address routing table. The first instruction is sent by the routing device. Specifically, when the connection between the routing device and the mutual assistance device is disconnected, the routing device is restarted. After the routing device restarts, it controls the routing device to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level.

[0023] After the mutual assistance device and the sub-devices update the physical address routing table, data transmission between devices can be realized according to the physical address routing table, thereby realizing the handling of the connection exception between the routing device and the mutual assistance device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0024] The exception handling method provided by the present application controls the routing device to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level after the routing device restarts. After the mutual assistance device receives the first instruction, it can initiate a DHCP according to the first instruction, and then update the physical address routing table. Thereby realizing the handling of the connection exception between the routing device and the mutual assistance device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0025] According to a third aspect of the present application, an exception handling method is provided, which is executed by a sub-device. The sub-device is connected to a mutual assistance device, the mutual assistance device is connected to a routing device, and the routing device is connected to a first network. The exception handling method includes: receiving a first instruction sent by the routing device when the routing device restarts; and initiating a DHCP and updating a physical address routing table according to the first instruction.

[0026] The exception handling method provided by the present application can be executed by a sub-device. Among them, the sub-device is connected to a mutual assistance device, the mutual assistance device is connected to a routing device, and the routing device is connected to a first network.

[0027] After the sub-device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. The first instruction is sent by the routing device. Specifically, when the connection between the routing device and the mutual assistance device is disconnected, the routing device is restarted. After the routing device is restarted, control the routing device to send the first instruction to the sub-devices level by level.

[0028] After the sub-device updates the physical address routing table, it can realize data transmission between devices according to the physical address routing table, thereby realizing the handling of the connection anomaly of the routing device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0029] The exception handling method provided by this application controls the routing device to send the first instruction to the sub-devices level by level after the routing device is restarted. After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thereby realizing the handling of the connection anomaly of the routing device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0030] According to the fourth aspect of this application, an exception handling device for a routing device is proposed. The routing device is connected to the first network, the routing device is connected to the mutual assistance device, and the mutual assistance device is connected to the sub-device. The exception handling device includes: a detection unit for detecting the connection status with the mutual assistance device; a control unit for restarting when disconnected from the mutual assistance device; a sending unit for sending the first instruction to the mutual assistance device and the sub-device in sequence after restarting, where the first instruction is used to notify the mutual assistance device and the sub-device to initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

[0031] The exception handling device provided by this application restarts the routing device when the connection between the routing device and the mutual assistance device is disconnected. After the routing device is restarted, control the routing device to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level. After the mutual assistance device and the sub-device receive the first instruction, they can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thereby realizing the handling of the connection anomaly between the routing device and the mutual assistance device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0032] According to the fifth aspect of the present application, an exception handling device for a mutual assistance device is proposed. The mutual assistance device is connected to a first network through a routing device, and the mutual assistance device is connected to a sub-device. The exception handling device includes: a receiving unit, configured to receive a first instruction sent by the routing device when the routing device restarts; and a control unit, configured to initiate a Dynamic Host Configuration Protocol (DHCP) and update a physical address routing table according to the first instruction.

[0033] The exception handling device provided by the present application controls the routing device to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level after the routing device restarts. After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thereby, the connection exception between the routing device and the mutual assistance device is processed, and the normal data transmission of all electronic devices connected to the first network is ensured.

[0034] According to the sixth aspect of the present application, an exception handling device for a sub-device is proposed. The sub-device is connected to a mutual assistance device, the mutual assistance device is connected to a routing device, and the routing device is connected to a first network. The exception handling device includes: a receiving unit, configured to receive a first instruction sent by the routing device when the routing device restarts; and a control unit, configured to initiate a Dynamic Host Configuration Protocol (DHCP) and update a physical address routing table according to the first instruction.

[0035] The exception handling device provided by the present application controls the routing device to send the first instruction to the sub-devices level by level after the routing device restarts. After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thereby, the connection exception of the routing device is processed, and the normal data transmission of all electronic devices connected to the first network is ensured.

[0036] According to the seventh aspect of the present application, an electronic device is proposed, including: a processor and a memory, where the memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, the steps of the exception handling method provided in any one of the first aspect, the second aspect, and the third aspect are implemented.

[0037] The electronic device provided by the present application includes a memory and a processor, and also includes a program or instruction stored on the memory. When the program or instruction is executed by the processor, the steps of the exception handling method in any one of the above-mentioned first aspect, second aspect, and third aspect can be implemented. Therefore, the electronic device has all the beneficial effects of the above-mentioned exception handling method, which will not be elaborated here.

[0038] According to an eighth aspect of the present application, a computer-readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the first aspect, the second aspect, and the third aspect are implemented.

[0039] For the computer-readable storage medium provided by the present application, a program or instruction is stored thereon. Since when the program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the first aspect, the second aspect, and the third aspect can be implemented, this computer-readable storage medium has all the beneficial effects of the above-mentioned exception handling method, which will not be elaborated herein.

[0040] According to a ninth aspect of the present application, a computer program product is provided, including a computer program or instruction. When the computer program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the first aspect, the second aspect, and the third aspect are implemented.

[0041] For the computer program product provided by the present application, including a computer program or instruction, when the computer program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the first aspect, the second aspect, and the third aspect are implemented. Therefore, this computer program product has all the beneficial effects of the above-mentioned exception handling method, which will not be elaborated herein.

[0042] The additional aspects and advantages of the present application will become apparent in the following description section, or be learned through the practice of the present application. Brief Description of the Drawings

[0043] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0044] Figure 1 One of the flow diagrams showing the exception handling method provided according to an embodiment of the present application;

[0045] Figure 2 Another flow diagram showing the exception handling method provided according to an embodiment of the present application;

[0046] Figure 3 Another flow diagram showing the exception handling method provided according to an embodiment of the present application;

[0047] Figure 4 One of the block diagrams showing the structure of the exception handling device provided according to an embodiment of the present application;

[0048] Figure 5 Another block diagram showing the structure of the exception handling device provided according to an embodiment of the present application;

[0049] Figure 6Shows the third structural block diagram of the exception handling device provided according to an embodiment of the present application;

[0050] Figure 7 Shows the topology diagram of the network connection provided according to an embodiment of the present application;

[0051] Figure 8 Shows the schematic diagram of the address mode during the data transmission process provided according to an embodiment of the present application;

[0052] Figure 9 Shows the first schematic diagram of the address link of the network connection provided according to an embodiment of the present application;

[0053] Figure 10 Shows the second schematic diagram of the address link of the network connection provided according to an embodiment of the present application.

[0054] Among them, Figures 4 to 7 The corresponding relationship between the reference numerals and the component names in

[0055] 400 Exception handling device, 402 Detection unit, 404 Control unit, 500 Exception handling device, 502 Receiving unit, 504 Control unit, 600 Exception handling device, 602 Receiving unit, 604 Control unit, 702 Device to be connected, 704 Routing device, 706 Mutual assistance device, 708 Target mutual assistance device. Specific implementation manners

[0056] In order to be able to more clearly understand the above objects, features, and advantages of the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific implementation manners. It should be noted that, without conflict, the embodiments of the present application and the features in the embodiments can be combined with each other.

[0057] Many specific details are set forth in the following description in order to fully understand the present application. However, the present application may also be implemented in other ways different from those described herein. Therefore, the protection scope of the present application is not limited by the specific embodiments disclosed below.

[0058] Next, refer to Figures 1 to 10 to describe the exception handling method, exception handling device, electronic device, and readable storage medium provided according to some embodiments of the present application.

[0059] As Figure 1 shown, according to an embodiment of the present application, an exception handling method is proposed, which is executed by a routing device. Among them, the routing device is connected to a first network, the routing device is connected to a mutual assistance device, and the mutual assistance device is connected to a sub-device. The exception handling method includes:

[0060] S102, detecting the connection status with the mutual assistance device;

[0061] S104, restart when disconnected from the mutual assistance device;

[0062] S106, after restarting, sequentially send a first instruction to the mutual assistance device and the sub-devices;

[0063] Wherein, the first instruction is used to notify the mutual assistance device and the sub-devices to initiate the Dynamic Host Configuration Protocol.

[0064] The exception handling method provided by this application can be executed by a routing device. Among them, the routing device is connected to a first network, the routing device is connected to a mutual assistance device, and the mutual assistance device is connected to sub-devices.

[0065] It can be understood that when the sub-devices do not meet the connection conditions of the first network, that is, when the sub-devices cannot be directly connected to the first network through the routing device, at least one mutual assistance device is searched. Among them, the mutual assistance device is connected to the first network, that is, the mutual assistance device is connected to the routing device of the first network, so as to realize the connection to the first network through the routing device. Thus, when the signal strength of the network signal of the routing device received by the sub-devices is low and it is impossible to ensure a continuous and stable connection to the first network through the routing device, a continuous and stable connection to the first network is realized through the mutual assistance device, improving the networking experience of the sub-devices.

[0066] Furthermore, after the sub-devices are connected to the first network through the mutual assistance device, the connection status between the routing device and the mutual assistance device is detected. That is, it is detected whether the connection between the routing device and the mutual assistance device is abnormal.

[0067] Furthermore, when the connection between the routing device and the mutual assistance device is disconnected, the routing device is restarted. After the routing device is restarted, control the routing device to sequentially send a first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device. Wherein, the first instruction is used to notify the mutual assistance device and the sub-devices to initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

[0068] Correspondingly, after the mutual assistance device and the sub-devices receive the first instruction, they can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. After the mutual assistance device and the sub-devices update the physical address routing table, they can realize data transmission between devices according to the physical address routing table, thus realizing the handling of the connection exception between the routing device and the mutual assistance device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0069] The exception handling method provided by this application restarts the routing device when the connection between the routing device and the mutual assistance device is disconnected. After the routing device restarts, it controls the routing device to send a first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level. After the mutual assistance device and the sub-devices receive the first instruction, they can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thus, the connection exception between the routing device and the mutual assistance device is handled, ensuring the normal data transmission of all electronic devices connected to the first network.

[0070] In some embodiments, optionally, before restarting when the connection with the mutual assistance device is disconnected, the exception handling method further includes: saving the device information of the mutual assistance device connected to the routing device and the Address Resolution Protocol of the routing device.

[0071] In this embodiment, after the routing device is disconnected from the mutual assistance device, it can be controlled to save the device information of the mutual assistance device connected to it and the Address Resolution Protocol of the routing device. Thus, after the routing device restarts, it can find the device information of the mutual assistance device previously connected to it and determine the physical address of the mutual assistance device through the Address Resolution Protocol. Furthermore, after the routing device restarts, it can send the first instruction to the mutual assistance device and the sub-devices connected to it, so that the mutual assistance device and the sub-devices can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table.

[0072] In some embodiments, optionally, before saving the device information of the mutual assistance device connected to the routing device and the Address Resolution Protocol of the routing device, the exception handling method further includes: clearing the physical addresses of the mutual assistance device and the sub-devices.

[0073] In this embodiment, after the routing device is disconnected from the mutual assistance device, first, the physical addresses of the mutual assistance device and the sub-devices connected to the routing device can be cleared, so as to avoid interference from the previously saved physical addresses of the mutual assistance device and the sub-devices to the actual physical addresses in the re-established network after the routing device restarts and establishes a connection with the mutual assistance device and the sub-devices.

[0074] As Figure 2 shown, according to an embodiment of the present application, an exception handling method is proposed, which is executed by a mutual assistance device. Among them, the mutual assistance device is connected to a first network through a routing device, and the mutual assistance device is connected to sub-devices. The exception handling method includes:

[0075] S202, when the routing device restarts, receive the first instruction sent by the routing device;

[0076] S204. Initiate the Dynamic Host Configuration Protocol (DHCP) and update the physical address routing table according to the first instruction.

[0077] The exception handling method provided in this application can be executed by a mutual assistance device. The mutual assistance device is connected to a first network through a routing device and is connected to a sub-device.

[0078] After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. The first instruction is sent by the routing device. Specifically, when the connection between the routing device and the mutual assistance device is disconnected, the routing device is restarted. After the routing device is restarted, the routing device is controlled to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level.

[0079] After the mutual assistance device and the sub-devices update the physical address routing table, data transmission between devices can be realized according to the physical address routing table, thereby handling the connection exception between the routing device and the mutual assistance device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0080] The exception handling method provided in this application controls the routing device to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level after the routing device is restarted. After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thereby, the connection exception between the routing device and the mutual assistance device is handled, and the normal data transmission of all electronic devices connected to the first network is ensured.

[0081] In some embodiments, optionally, after initiating the Dynamic Host Configuration Protocol and updating the physical address routing table according to the first instruction, the exception handling method further includes: sending a second instruction to the sub-device, where the second instruction is used to notify the sub-device to clear the Address Resolution Protocol (ARP) and the physical address routing table of the sub-device.

[0082] In this embodiment, when the connection between the routing device and the mutual assistance device is disconnected, the mutual assistance device discovers that it is disconnected from the routing device and is in an offline state. At this time, the mutual assistance device can send a second instruction to the sub-devices connected to it. The second instruction is used to notify the sub-devices to clear their own Address Resolution Protocol and physical address routing tables.

[0083] Further, after the routing device restarts, the control sub-device sends a connection request to the mutual assistance device again. Then, after the sub-device reconnects to the mutual assistance device, the Address Resolution Protocol and the physical address routing table of the sub-device are re-established to ensure the accuracy of the Address Resolution Protocol and the physical address routing table stored in the sub-device itself after the sub-device connects to the first network, and further ensure that the sub-device can transmit data normally in the first network.

[0084] In some embodiments, optionally, the exception handling method further includes: detecting the connection status with the sub-device; in the case where the sub-device is disconnected, clearing the node of the sub-device in the physical address routing table; and sending the physical address routing table after clearing the node of the sub-device to the routing device.

[0085] In this embodiment, by detecting the connection status between the mutual assistance device and the sub-device, it is determined whether the connection between the mutual assistance device and the sub-device is abnormal.

[0086] Further, after determining that the connection between the mutual assistance device and the sub-device is disconnected, the mutual assistance device can be controlled to clear the node of the sub-device in the physical address routing table. That is, after the mutual assistance device discovers that the sub-device is disconnected, it determines that the sub-device is no longer in the physical address routing table of the current first network. At this time, the mutual assistance device can clear the node of the sub-device in the physical address routing table to update the physical address routing table of the first network.

[0087] Further, after clearing the node of the sub-device in the physical address routing table, the mutual assistance device can also be controlled to send the updated physical address routing table to the routing device to notify the routing device that the sub-device connected to the mutual assistance device has been disconnected at this time.

[0088] In some embodiments, optionally, detecting the connection status with the sub-device includes: receiving a detection signal sent by the sub-device according to a preset time interval; and determining the connection status with the sub-device according to the detection signal.

[0089] In this embodiment, after the sub-device connects to the first network through the mutual assistance device, the sub-device can be controlled to send a detection signal to the mutual assistance device according to a preset time interval. Specifically, the preset time interval can be 1 minute, that is, a detection signal is sent every 1 minute. Further, the mutual assistance device is controlled to send a reply signal to the sub-device after receiving the detection signal, and then the connection status between the sub-device and the mutual assistance device can be detected according to the detection signal and the reply signal to determine the abnormality between the sub-device and the mutual assistance device.

[0090] Specifically, if the mutual assistance device does not receive the sub-device detection signal for 2 minutes, it is considered that the sub-device is lost, and the relevant information of the sub-device is cleared. In addition, when the sub-device does not receive the reply of the mutual assistance device to the detection signal, it indicates that the connection fails, and all devices under this node need to be notified to clear the connection relationship and search for the network again.

[0091] By sending the detection signal of the sub-device, the connection status between the sub-device and the mutual assistance device can be detected in real time, and then it can be determined in time whether the sub-device is connected to the mutual assistance device to determine the abnormality between the sub-device and the mutual assistance device.

[0092] As Figure 3 shown, according to an embodiment of the present application, an exception handling method is proposed, which is executed by the sub-device. Wherein, the sub-device is connected to the mutual assistance device, the mutual assistance device is connected to the routing device, and the routing device is connected to the first network. The exception handling method includes:

[0093] S302, when the routing device restarts, receive the first instruction sent by the routing device;

[0094] S304, according to the first instruction, initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

[0095] The exception handling method provided by the present application can be executed by the sub-device. Wherein, the sub-device is connected to the mutual assistance device, the mutual assistance device is connected to the routing device, and the routing device is connected to the first network.

[0096] After the sub-device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Wherein, the first instruction is sent by the routing device. Specifically, when the connection between the routing device and the mutual assistance device is disconnected, the routing device is restarted. After the routing device restarts, control the routing device to send the first instruction to the sub-device step by step.

[0097] After the sub-device updates the physical address routing table, it can realize data transmission between devices according to the physical address routing table, thereby realizing the handling of the connection exception of the routing device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0098] The exception handling method provided by the present application, after the routing device restarts, controls the routing device to send the first instruction to the sub-device step by step. After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thereby realizing the handling of the connection exception of the routing device and ensuring the normal data transmission of all electronic devices connected to the first network.

[0099] In some embodiments, optionally, after initiating the Dynamic Host Configuration Protocol and updating the physical address routing table according to the first instruction, the exception handling method further includes: receiving a second instruction sent by a mutual assistance device; and clearing the Address Resolution Protocol and the physical address routing table according to the second instruction.

[0100] In this embodiment, after the disconnection between the routing device and the mutual assistance device, the mutual assistance device discovers that it is disconnected from the routing device and is in an offline state. At this time, the mutual assistance device can send a second instruction to the sub-devices connected to it. The second instruction is used to notify the sub-devices to clear their own Address Resolution Protocol and physical address routing tables.

[0101] Further, after the routing device restarts, control the sub-devices to send connection requests to the mutual assistance device again. Then, after the sub-devices are reconnected to the mutual assistance device, re-establish the Address Resolution Protocol and the physical address routing tables of the sub-devices to ensure the accuracy of the Address Resolution Protocol and the physical address routing tables stored in the sub-devices themselves after the sub-devices are connected to the first network, and further ensure that the sub-devices can transmit data normally in the first network.

[0102] In a specific embodiment, as Figure 7 shown, when the device to be connected 702 needs to be connected to the first network, first, control the device to be connected 702 to send a connection request for the first network to discover connectable Internet access devices. Specifically, the device to be connected 702 can send a connection request every 0.5 s. If no response from other devices is received for a long time, the device to be connected 702 can send requests at random intervals of 0.1 s within 5 s. At the same time, the device to be connected 702 also listens to the beacon sent by the routing device 704, and makes a comprehensive judgment based on the scanned wireless access point and the device information of the mutual assistance device 706 to determine whether to connect to the routing device 704 or the mutual assistance device 706.

[0103] Specifically, during the process of information interaction among the device to be connected 702, the routing device 704, and the mutual assistance device 706, the information sent includes multiple fields. Among them, the key fields include ability display, frame type, message ID, CMD, level, etc. In one embodiment, the key fields are described as follows: Ability display: 8 bits, b0:1 supports mutual assistance; b0:0 does not support mutual assistance; other bits are reserved; Frame type: 01: probe request; 02: probe response; 03: action; Message ID: global ID, set by the initiator, and the responder returns the same ID. CMD: 01: key negotiation; 02: password update; 03: routing table update; Level: the network layer where the mutual assistance device 706 is located. The mutual assistance device 706 directly connected to the routing device 704 is layer 0, the mutual assistance device 706 connected to the mutual assistance device 706 directly connected to the routing device 704 is 1, the leaf connected to 1 is 2... The level range can be less than or equal to 4 layers.

[0104] Specifically, the connection request sent by the device to be connected 702 may include the following fields: protocol version, ability display, frame type, message ID, CMD, negotiation step, Pubkey, Sha, R1. In one embodiment, the protocol version is used to indicate the version of the communication protocol of the sent connection request; the ability display is used to show whether the device to be connected 702 supports the connection of the mutual assistance device; the frame type is used to indicate the message type of the sent connection request; the message ID is used to show the sent ID information, set by the initiator, and the responder returns the same ID; CMD, 01 represents key negotiation, 02 represents password update, 03 represents routing table update; the negotiation step is used to show the process in the current connection process; Pub key is the public key generated by the device to be connected 702; Sha is the ciphertext encryption method; R1 is the ciphertext encrypted based on the public key.

[0105] Further, after receiving the response information of the routing device 704, the strength of the network signal of the routing device 704 that the device to be connected 702 can receive is determined according to the response information of the routing device 704. If the strength of the network signal of the routing device 704 that the device to be connected 702 can receive is lower than -55 dBm, it will cause the device to be connected 702 to be unable to connect to the routing device 704 or experience frequent disconnections. At this time, it can be determined whether the response information of the mutual assistance device 706 is received.

[0106] When the mutual assistance device 706 receives a connection request, it sends a response message after rule judgment. The judgment rules are as follows: 1. It allows the device to be connected to access itself; 2. The device that the device to be connected 702 requests to access is the mutual assistance device 706; 3. The name of the routing device 704 requesting access is the same as the network it accesses itself. The response message includes other information such as the commercial private information, the number of connected terminals, and the floor where it is located.

[0107] Specifically, the response message sent by the mutual assistance device 706 may include the following fields in addition to the fields in the connection request sent by the device to be connected 702: level, which is used to indicate the level of the mutual assistance device 706 in the first network; the number of access points, which is used to indicate the number of devices accessed by the mutual assistance device 706; the strength of the network signal; R2, which is the ciphertext encrypted based on the public key of the mutual assistance device 706; R1.

[0108] Further, according to the response messages sent by multiple mutual assistance devices 706, a target mutual assistance device 708 is determined among the multiple mutual assistance devices 706. First, a preliminary selection can be made according to the signal strength of the mutual assistance device 706, the floor of the mutual assistance device 706 in the first network, and the number of devices connected by the mutual assistance device 706. Specifically, the mutual assistance devices 706 with a signal strength greater than -55 dBm, a floor less than or equal to 4 floors, and a connection point number less than 6 can be screened out.

[0109] Further, among the screened mutual assistance devices 706, the connection index of the mutual assistance device 706 is determined according to the signal strength of the mutual assistance device 706, the floor of the mutual assistance device 706 in the first network, and the number of devices connected by the mutual assistance device 706. The mutual assistance device 706 with the largest connection index is determined as the target mutual assistance device 708. Specifically, first, the signal strength of the mutual assistance device 706, the strength weight and strength score corresponding to the signal strength, the floor weight and floor score corresponding to the floor, and the point weight and point score corresponding to the number of connection points can be determined, and then the connection index of each mutual assistance device 706 is calculated.

[0110] Specifically, the connection index can be calculated according to the formula P = A×a + B×b + C×c, where P is the connection index, A is the strength score, a is the strength weight, B is the point score, b is the point weight, C is the level score, and c is the level weight. For example, the strength weight of the signal strength is 0.5, and when the signal strength is -50 dBm, the corresponding strength score is 4. The point weight of the number of connection points is 0.5, and when the number of connection points is 5, the point score is 4. The floor weight of the floor is 0.3, and when the floor is 3, the corresponding floor score is 4. When the model strength of the mutual assistance device 706 is -50 dBm, the number of connection points is 5, and the floor is 3, the connection index of this mutual assistance device is: P = 4×0.5 + 4×0.3 + 4×0.2 = 4.

[0111] Further, after determining the target mutual assistance device 708, the control device 702 to be connected negotiates a key with the target mutual assistance device 708 to generate a key for data transmission between the device 702 to be connected and the target mutual assistance device 708. The connection request sent by the device 702 to be connected includes the text R1 encrypted with the public key of the device 702 to be connected. Correspondingly, the response information sent by the target mutual assistance device 708 to the device 702 to be connected includes R1 and the texts R1 and R2 encrypted with the public key of the device 702 to be connected.

[0112] During the key negotiation process, the encryption key is obtained using the ECC encryption algorithm (elliptic curve encryption algorithm). While the device 702 to be connected initiates a scan, it also initiates key negotiation, and the target mutual assistance device 708 responds to implement the second step of key negotiation. The third and fourth steps use ACTION frames to confirm the key.

[0113] First, after the device 702 to be connected receives the response information from the target mutual assistance device 708, it decrypts the encrypted text. If the decrypted text includes R1, it indicates that the key negotiation between the device 702 to be connected and the mutual assistance device 706 is successful. Then the device 702 to be connected encrypts the negotiation result "OK" based on the public key of the mutual assistance device 706 and sends it to the mutual assistance device 706. After receiving the negotiation result, the mutual assistance device 706 generates a key based on R1 and R2, encrypts the text "OK" based on the generated key, and sends it to the device 702 to be connected, completing the key negotiation. Then, data transmission is performed between the device 702 to be connected and the mutual assistance device 706 based on the generated key. Specifically, during the key negotiation process, the device 702 to be connected sends key negotiation information using a 4-address mode action frame. Among them, the information sent by the device 702 to be connected and the mutual assistance device 706 can include the following fields: protocol version, capability display, frame type, message ID, CMD, negotiation step, and ciphertext.

[0114] Further, after the key negotiation is completed, the device node link of the first network can be updated. Specifically, in the original link of the first network, if there is no device node downstream of the target mutual assistance device 708, the device node of the device 702 to be connected can be directly added downstream of the target mutual assistance device 708 in the original link to update the device node link of the first network.

[0115] If the downstream node of the target mutual assistance device 708 is occupied, that is, there is a device node downstream of the target mutual assistance device 708. At this time, the original link of the first network can be assisted to generate a replication link, and the replication link is the same as the original link of the first network. Then, the downstream device node of the target mutual assistance device 708 in the replication link is replaced with the device node of the device to be connected 702, so as to generate a new device node link and complete the update of the device node link of the first network.

[0116] For example, as Figure 9 and Figure 10 shown, the original link is A - B - C - D. When E accesses, D adds E to the end to get A - B - C - D - E. At the same time, the device node in front of D reports the addition of E at the end of the A - B - C - D routing table. After each node receives this information, it will add E after D. The node synchronization is completed. If a new F is added to the end of D on the A - B - C - D path at the same time. At this time, D finds that its end is occupied, so it replicates a link and adds F to the end of D. At the same time, the D node synchronizes the information that needs to be added to the end to the root node. If each node is occupied, it is also replicated and added. Each node gets the complete two linked lists of A - B - C - D - F and A - B - C - D - E. Specifically, the data sent to the device node in front can include the following fields: protocol version; ability display; frame type; message ID; CMD; Sub, used to update the linked list to the associated network link; Len, used to indicate the length of the string, usually a multiple of 6; Macdata, mac data, 6(N + 2) bytes, where N represents the layer where the device is currently located. Mac is in little - endian alignment and is arranged sequentially from the mutual assistance device connected to the routing device to the back. MACdata arrangement example: MAC root, MAC1, MAC2... MACend.

[0117] Further, after the device to be connected 702 is connected to the first network through the target mutual assistance device 708, the data forwarding rules are as follows:

[0118] Such as Figure 8As shown in the figure, the data is transmitted between the device to be connected 702 and the target mutual assistance device 708 in a 4-address mode. Between the target mutual assistance device 708 and other mutual assistance devices 706, and between the target mutual assistance device 708 and the routing device 704, the data is transmitted in a 3-address mode. The device to be connected 702 is connected to the target mutual assistance device 708, the target mutual assistance device 708 is connected to the routing device 704, and the routing device 704 is connected to the host device. The process of the device to be connected 702 sending data to the host device: The device to be connected 702 sends 4 addresses to the target mutual assistance device 708: receiving address (RA) - physical address of the target mutual assistance device 708, sending address (TA) - physical address of the device to be connected 702, destination address (DA) - physical address of the host device, source address (SA) - physical address of the device to be connected 702; The target mutual assistance device 708 sends 3 addresses to the routing device 704: receiving address (RA) - physical address of the routing device 704, source address (SA) - physical address of the target mutual assistance device 708, destination address (DA) - physical address of the host device; The routing device 704 sends 3 addresses to the host device: destination address (DA) - physical address of the host device, sending address (TA) - physical address of the routing device 704, source address (SA) - physical address of the target mutual assistance device 708.

[0119] The process of the host device sending data to the device to be connected 702: The host device sends 3 addresses to the routing device 704: receiving address (RA) - physical address of the routing device 704, source address (SA) - physical address of the host device, destination address (DA) - physical address of the target mutual assistance device 708; The routing device 704 sends 3 addresses to the target mutual assistance device 708: destination address (DA) - physical address of the target mutual assistance device 708, sending address (TA) - physical address of the routing device 704, source address (SA) - physical address of the host device; The target mutual assistance device 708 sends 4 addresses to the device to be connected 702: receiving address (RA) - physical address of the device to be connected 702, sending address (TA) - physical address of the target mutual assistance device 708, destination address (DA) - physical address of the device to be connected 702, source address (SA) - physical address of the host device.

[0120] Specifically: When the device to be connected 702 actively sends data, it is detected whether the address resolution protocol (ARP table) of the device to be connected 702 contains the physical address of the target mutual assistance device 708. If so, it is directly sent to the target mutual assistance device 708 in a 4-address mode. If not, the data is sent to the mutual assistance device 706 connected to the routing device 704 through the target mutual assistance device 708 step by step in a 4-address mode.

[0121] When the mutual assistance device 706 connected to the routing device 704 receives the data sent by the routing device 704, it first determines whether the logical address of the local machine exists in the received data. If the logical address of the local machine exists, the data is transmitted to the application layer of the local machine. If not, the physical address of the next-level device is determined from the physical address routing table stored in the local machine, and the data is transmitted to the next-level device.

[0122] Further, after the device to be connected 702 is connected to the first network through the target mutual assistance device 708, the device to be connected 702 sends detection data to the target mutual assistance device 708 once every 1 minute. If the target mutual assistance device 708 does not receive the detection data of the device to be connected 702 for 2 minutes, it is considered that the device to be connected 702 is lost, and the relevant information of the device to be connected 702 is cleared; when the device to be connected 702 does not receive the detection data reply from the target mutual assistance device 708, it means that the connection fails, and all devices under this node need to be notified to clear the connection relationship and search for the network again. The detection data may include the following fields: protocol version, capability display, frame type, message ID, and CMD.

[0123] Further, after the device to be connected 702 is connected to the first network through the target mutual assistance device 708, it is necessary to detect the connection exception of the device to be connected 702 in real time. Specifically, when the connection between the target mutual assistance device 708 and the routing device 704 is disconnected, the routing device 704 should retain the device information of all mutual assistance devices 706 connected to it and the address resolution protocol. After the routing device 704 is restarted, at this time, it is not necessary to clear the device information of the mutual assistance devices 706 connected to the routing device 704 and the address resolution protocol, and only the device addresses in the address resolution protocol need to be cleared. Then, an instruction is sent to the mutual assistance device 706 connected to it to notify the mutual assistance device 706 to re-initiate the Dynamic Host Configuration Protocol and update the physical address routing table, so that the mutual assistance device 706 and the routing device 704 can re-establish a connection. Among them, the instruction sent by the routing device 704 may include the following fields: protocol version, capability display, frame type, message ID, and CMD.

[0124] Further, when the target mutual assistance device 708 finds that it is disconnected from the routing device 704, it can send an instruction to the device to be connected 702 connected to it to notify the device to be connected 702 to re-initiate the connection. Specifically, the instruction sent by the target mutual assistance device 708 may include the following fields: protocol version, capability display, frame type, message ID, and CMD.

[0125] According to the fourth aspect of the present application, as Figure 4As shown, an exception handling device 400 is proposed for a routing device. The routing device is connected to a first network, the routing device is connected to a mutual assistance device, and the mutual assistance device is connected to a sub-device. The exception handling device includes: a detection unit 402 for detecting the connection status with the mutual assistance device; a control unit 404 for restarting in the case of disconnection from the mutual assistance device; a sending unit for sending a first instruction to the mutual assistance device and the sub-device in sequence after restarting, where the first instruction is used to notify the mutual assistance device and the sub-device to initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

[0126] The exception handling device 400 provided in this application restarts the routing device when the connection between the routing device and the mutual assistance device is disconnected. After the routing device restarts, it controls the routing device to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level. After the mutual assistance device and the sub-devices receive the first instruction, they can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thus, the connection exception between the routing device and the mutual assistance device is handled, ensuring the normal data transmission of all electronic devices connected to the first network.

[0127] Furthermore, the exception handling device 400 further includes a storage unit for storing the device information of the mutual assistance device connected to the routing device and the Address Resolution Protocol of the routing device.

[0128] Furthermore, the control unit 404 is also used to clear the physical addresses of the mutual assistance device and the sub-devices.

[0129] According to the fifth aspect of this application, as Figure 5 shown, an exception handling device 500 is proposed for a mutual assistance device. The mutual assistance device is connected to a first network through a routing device, and the mutual assistance device is connected to a sub-device. The exception handling device includes: a receiving unit 502 for receiving the first instruction sent by the routing device when the routing device restarts; a control unit 504 for initiating the Dynamic Host Configuration Protocol and updating the physical address routing table according to the first instruction.

[0130] The exception handling device 500 provided in this application controls the routing device to send the first instruction to the mutual assistance device and the sub-devices connected to the mutual assistance device level by level after the routing device restarts. After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thus, the connection exception between the routing device and the mutual assistance device is handled, ensuring the normal data transmission of all electronic devices connected to the first network.

[0131] Further, the exception handling device further includes a sending unit, configured to send a second instruction to the sub-device, where the second instruction is used to notify the sub-device to clear the Address Resolution Protocol and the physical address routing table of the sub-device.

[0132] Further, the exception handling device further includes a detection unit, configured to detect the connection status with the sub-device; the control unit is further configured to, when the sub-device is disconnected, clear the node of the sub-device in the physical address routing table; the sending unit is further configured to send the physical address routing table after clearing the node of the sub-device to the routing device.

[0133] Further, the receiving unit 502 is specifically configured to receive the detection signal sent by the sub-device according to a preset time interval; and determine the connection status with the sub-device according to the detection signal.

[0134] According to the sixth aspect of the present application, as Figure 6 shown, an exception handling device 600 is proposed, which is used for a sub-device. The sub-device is connected to a mutual assistance device, the mutual assistance device is connected to a routing device, and the routing device is connected to a first network. The exception handling device includes: a receiving unit 602, configured to receive a first instruction sent by the routing device when the routing device restarts; a control unit 604, configured to initiate a Dynamic Host Configuration Protocol and update the physical address routing table according to the first instruction.

[0135] The exception handling device 600 provided by the present application controls the routing device to send the first instruction to the sub-device step by step after the routing device restarts. After the mutual assistance device receives the first instruction, it can initiate the Dynamic Host Configuration Protocol according to the first instruction, and then update the physical address routing table. Thus, the connection exception of the routing device is processed, and the normal data transmission of all electronic devices connected to the first network is ensured.

[0136] Further, the receiving unit 602 is further configured to receive a second instruction sent by the mutual assistance device; the control unit 604 is further configured to clear the Address Resolution Protocol and the physical address routing table according to the second instruction.

[0137] According to the seventh aspect of the present application, an electronic device is proposed, including: a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the exception handling method provided in any one of the above embodiments are implemented.

[0138] The electronic device provided by the present application includes a memory and a processor, and also includes a program or instruction stored on the memory. When the program or instruction is executed by the processor, the steps of the exception handling method in any one of the above embodiments can be implemented. Therefore, the electronic device has all the beneficial effects of the above exception handling method, which will not be elaborated here.

[0139] According to the eighth aspect of the present application, a computer-readable storage medium is provided, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the above embodiments are implemented.

[0140] For the computer-readable storage medium provided by the present application, on which a program or instruction is stored, when the program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the above embodiments can be implemented. Therefore, the computer-readable storage medium has all the beneficial effects of the above exception handling method, which will not be elaborated herein.

[0141] According to the ninth aspect of the present application, a computer program product is provided, including a computer program or instruction, and when the computer program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the above embodiments are implemented. For the computer program product provided by the present application, including a computer program or instruction, when the computer program or instruction is executed by a processor, the steps of the exception handling method provided in any one of the above embodiments are implemented. Therefore, the computer program product has all the beneficial effects of the above exception handling method, which will not be elaborated herein.

[0142] In the description of the present application, the term "plurality" means two or more, unless otherwise clearly defined. The orientation or positional relationship indicated by terms such as "upper", "lower", etc. is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation to the present application; terms such as "connection", "installation", "fixation", etc. should all be understood in a broad sense. For example, "connection" can be a fixed connection, a detachable connection, or an integral connection; it can be directly connected, or indirectly connected through an intermediate medium. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to specific circumstances.

[0143] In the description of this specification, the descriptions of terms such as "one embodiment", "some embodiments", "specific embodiments", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or more embodiments or examples.

[0144] The above are only the preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various modifications and variations can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the protection scope of the present application.

Claims

1. An exception handling method, which is executed by a routing device, characterized in that, The routing device is connected to a first network, the routing device is connected to a mutual assistance device, and the mutual assistance device is connected to a sub-device. The exception handling method includes: Detect the connection status with the mutual assistance device; Restart in the case of disconnection from the mutual assistance device; After restarting, send a first instruction to the mutual assistance device and the sub-device in sequence, where the first instruction is used to notify the mutual assistance device and the sub-device to initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

2. The exception handling method according to claim 1, wherein Before restarting in the case of disconnection from the mutual assistance device, the exception handling method further includes: Save the device information of the mutual assistance device connected to the routing device and the Address Resolution Protocol of the routing device.

3. The exception handling method according to claim 2, wherein Before saving the device information of the mutual assistance device connected to the routing device and the Address Resolution Protocol of the routing device, the exception handling method further includes: Clear the physical addresses of the mutual assistance device and the sub-device.

4. An exception handling method, which is executed by a mutual assistance device, characterized in that, The mutual assistance device is connected to the first network through a routing device, and the mutual assistance device is connected to a sub-device. The exception handling method includes: In the case of restart of the routing device, receive the first instruction sent by the routing device; According to the first instruction, initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

5. The exception handling method according to claim 4, characterized in that, After initiating the Dynamic Host Configuration Protocol and updating the physical address routing table according to the first instruction, the exception handling method further includes: Send a second instruction to the sub-device, where the second instruction is used to notify the sub-device to clear the Address Resolution Protocol and the physical address routing table of the sub-device.

6. The exception handling method according to claim 4, characterized in that Further includes: Detect the connection status with the sub-device; In the case of disconnection of the sub-device, clear the node of the sub-device in the physical address routing table; Send the physical address routing table after clearing the node of the sub-device to the routing device.

7. The exception handling method according to claim 6, wherein The detecting the connection status with the sub-device includes: Receive the detection signal sent by the sub-device according to a preset time interval; Determine the connection status with the sub-device according to the detection signal.

8. An exception handling method, which is executed by a sub-device, characterized in that The sub-device is connected to a mutual assistance device, the mutual assistance device is connected to a routing device, and the routing device is connected to a first network. The exception handling method includes: In the case of restart of the routing device, receive the first instruction sent by the routing device; According to the first instruction, initiate the Dynamic Host Configuration Protocol and update the physical address routing table.

9. The exception handling method according to claim 8, wherein After initiating the Dynamic Host Configuration Protocol and updating the physical address routing table according to the first instruction, the exception handling method further includes: Receive the second instruction sent by the mutual assistance device; According to the second instruction, clear the Address Resolution Protocol and the physical address routing table.

10. An exception handling device for a routing device, characterized in that, The routing device is connected to a first network, the routing device is connected to a mutual assistance device, and the mutual assistance device is connected to a sub-device. The exception handling device includes: A detection unit for detecting the connection status with the mutual assistance device; A control unit for restarting in the case of disconnection from the mutual assistance device; A sending unit, configured to sequentially send a first instruction to the mutual assistance device and the sub-device after a restart, where the first instruction is used to notify the mutual assistance device and the sub-device to initiate a Dynamic Host Configuration Protocol (DHCP) and update a physical address routing table.

11. An exception handling device for a mutual assistance device, characterized in that, The mutual assistance device is connected to a first network through a routing device, and the mutual assistance device is connected to the sub-device. The exception handling device includes: A receiving unit, configured to receive the first instruction sent by the routing device when the routing device restarts; A control unit, configured to initiate a DHCP and update a physical address routing table according to the first instruction.

12. An exception handling device for a sub-device, characterized in that, The sub-device is connected to the mutual assistance device, the mutual assistance device is connected to the routing device, and the routing device is connected to the first network. The exception handling device includes: A receiving unit, configured to receive the first instruction sent by the routing device when the routing device restarts; A control unit, configured to initiate a DHCP and update a physical address routing table according to the first instruction.

13. An electronic device, characterized in that, Including: A processor and a memory, where the memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to any one of claims 1 to 3 and / or the steps of the method according to any one of claims 4 to 7 and / or the steps of the method according to claim 8 or 9 are implemented.

14. A computer-readable storage medium, characterized in that, A program or instruction is stored on the computer-readable storage medium, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 3 and / or the steps of the method according to any one of claims 4 to 7 and / or the steps of the method according to claim 8 or 9 are implemented.

15. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 3 and / or the steps of the method according to any one of claims 4 to 7 and / or the steps of the method according to claim 8 or 9 are implemented.