Network switch and network architecture of network coupling backup

Abstract

A network architecture for network coupling backup comprises a backup network switch and at least one main network switch, is configured in a switch group of a main network, and is used for executing a network coupling backup method. The network coupling backup method comprises the following steps: periodically sending a first control packet by the backup network switch; in response to receiving the first control packet, at least one main network switch sends a first acknowledgement packet; the standby network switch performs link switching according to a first condition; the at least one main network switch sends a second control packet according to a second condition; in response to receiving the second control packet, the standby network switch replies a second acknowledgement packet and performs link switching according to the second control packet; and in response to receiving the second acknowledgement packet, the main network switch performs link switching.

Description

Technical Field

[0001] The present invention relates to a network coupling backup method, device and network architecture, and more particularly to a network coupling backup method, device and network architecture for backing up multiple main network switches with a backup network switch. Background Art

[0002] As the industry's requirements for production capacity and cost increase, connecting production equipment to the network has become a trend. Through network connection, data collection and analysis across machines become possible, which improves the speed, flexibility, and efficiency of the process, while reducing costs and producing higher quality products. However, in traditional industrial environments, there are often multiple independent local area networks (LANs) at the same time, and these LANs are composed of a variety of redundant network technologies, which makes integration and management difficult. In this case, the prior art has proposed network coupling technology, which can connect multiple LANs in series and enable data and function sharing or integration between different LANs. This technology can solve the interoperability and compatibility issues between different LANs and improve the efficiency and reliability of the system.

[0003] When performing network coupling, in order to avoid the network being unable to operate due to a single line failure, a second line is generally built as a backup line to improve the reliability and stability of network coupling. However, the current solution is mostly to couple the network through two network switches, one of which operates as the main switch and the other is on standby as a backup switch. In other words, two switches must be used for each sub-network connected. In this case, when the number of connected sub-networks is large, the number of network switch devices required must also increase accordingly. In addition to increasing the construction cost, it will also cause a significant increase in the amount of related control packets, thereby affecting performance. In addition, when applied to industrial control networks, it is inevitable that there will be multiple different sub-networks that need to be connected to the backbone network. Therefore, this problem needs to be further improved to improve efficiency and reduce costs. Summary of the invention

[0004] Therefore, the object of the present invention is to provide a one-to-many backup method and a network switch to achieve a redundancy mechanism while reducing costs and improving efficiency when performing network coupling.

[0005] An embodiment of the present invention discloses a main network switch, which is configured in a switch group of a main network and coupled to at least one first sub-network of a sub-network group through at least one first link. The main network switch includes a processing unit and a storage unit. The processing unit is used to execute a program code; the storage unit is coupled to the processing unit and is used to store the program code to instruct the processing unit to execute a network coupling backup method. The network coupling backup method includes receiving a first control packet from a backup network switch of the switch group; in response to receiving the first control packet, sending a first acknowledgment packet (ACK) including the connection status of the at least one first sub-network; sending a second control packet to the backup network switch; and in response to sending the second control packet, receiving a second acknowledgment packet from the backup network switch, and performing link switching after receiving the second acknowledgment packet.

[0006] An embodiment of the present invention also discloses a backup network switch, which is configured in a switch group of a main network and coupled to at least one first sub-network of a sub-network group through at least one first link. The backup network switch includes a processing unit and a storage unit. The processing unit is used to execute a program code; the storage unit is coupled to the processing unit and is used to store the program code to instruct the processing unit to execute a network coupling backup method. The network coupling backup method includes periodically sending a first control packet containing the connection status of the at least one first sub-network to at least one main network switch of the switch group; in response to sending the first control packet, receiving at least one first acknowledgment packet (ACK) from the at least one main network switch; performing link switching according to a first condition; and in response to receiving a second control packet from the at least one main network switch, sending a second acknowledgment packet and performing link switching according to the second control packet.

[0007] The embodiment of the present invention also discloses a network architecture for network coupling backup, comprising a plurality of sub-networks and a main network. The plurality of sub-networks belong to a plurality of sub-network groups. The main network comprises a plurality of switch groups, each of the plurality of switch groups is coupled to a sub-network group of the plurality of sub-network groups, and comprises at least one main network switch and a backup network switch. The at least one main network switch is coupled to at least one first sub-network of the sub-network group through at least one first link. The backup network switch is coupled to at least one second sub-network of the sub-network group through at least one second link. Wherein, each of the plurality of sub-network groups is used to execute a network coupling backup method, which includes the backup network switch periodically sending a first control packet including the connection status of the at least one second sub-network; in response to receiving the first control packet, the at least one main network switch sends a first confirmation packet (acknowledgment, ACK) including the connection status of the at least one first sub-network; the backup network switch performs link switching according to a first condition; the at least one main network switch sends a second control packet according to a second condition; in response to receiving the second control packet, the backup network switch replies with a second confirmation packet and performs link switching according to the second control packet; and in response to receiving the second confirmation packet, the main network switch performs link switching. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 A schematic diagram of a network system. Figure 2 Schematic diagram of a network system according to an embodiment of the present invention. Figure 3 FIG. 1 is a schematic diagram of a control packet according to an embodiment of the present invention. Figure 4 It is a flowchart of a network coupling backup method according to an embodiment of the present invention. Figure 5A , Figure 5B A schematic diagram of an implementation of a network coupling backup process for a group according to an embodiment of the present invention. Fig. 6A , Figure 6B It is a schematic diagram of another implementation of a group network coupling backup process according to an embodiment of the present invention. Fig. 7A , Figure 7B The present invention is a flowchart of a method for implementing network coupling backup by a backup network switch according to an embodiment of the present invention. Fig. 8A , Figure 8B The present invention is a flowchart of a method for implementing network coupling redundancy by a main network switch according to an embodiment of the present invention. Fig. 9 A schematic diagram of an incorrect configuration of an embodiment of the present invention. Fig.10 A schematic diagram of an incorrect configuration of an embodiment of the present invention. Fig.11 A schematic diagram of an incorrect configuration of an embodiment of the present invention. Fig.12 FIG. 1 is a schematic diagram of a network device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0009] Certain words are used in the specification and the subsequent claims to refer to specific components. It should be understood by those with ordinary knowledge in the field that hardware manufacturers may use different terms to refer to the same component. This specification and the subsequent claims do not use differences in names as a way to distinguish components, but use differences in the functions of the components as the criteria for distinction. The word "including" mentioned throughout the specification and the subsequent claims is an open-ended term and should be interpreted as "including but not limited to". In addition, the word "coupled" here includes any direct and indirect electrical connection means. Therefore, if the text describes a first device coupled to a second device, it means that the first device can be directly electrically connected to the second device, or indirectly electrically connected to the second device through other devices or connection means.

[0010] Please refer to Figure 1 , Figure 1 It is a schematic diagram of a network system 1. In the network system 1, a main network 10 is coupled to a plurality of sub-networks 12_1 to 12_4. Specifically, the main network 10 is coupled to the sub-networks 12_1 to 12_4 through a plurality of main network switches 14_1 to 14_4 via a plurality of main links 15_1 to 15_4; at the same time, the main network 10 is also coupled to the sub-networks 12_1 to 12_4 through a plurality of backup network switches 16_1 to 16_4 via a plurality of backup links 17_1 to 17_4. Among them, the plurality of backup network switches 16_1 to 16_4 and the plurality of backup links 17_1 to 17_4 serve as backups for the plurality of main network switches 14_1 to 14_4 and the plurality of main links 15_1 to 15_4, and are in standby status. Figure 1 It can be seen that the network system 1 adopts a one-to-one network coupling backup method. That is, each time the main network 10 is connected to a sub-network, a main network switch and a backup network switch need to be configured accordingly to ensure the reliability and stability of the network coupling. In this case, when a large number of sub-networks need to be connected, the number of network switches required also increases exponentially. In addition, as the number of network switches increases, the number of control packets sent by the network switches will also increase, affecting performance.

[0011] Therefore, the present invention proposes a network coupling backup method, which can enable a backup network switch to simultaneously backup multiple operating main network switches connected to sub-networks, and can configure the backup network switch and the main network switch it backs up into the same group (hereinafter referred to as a switch group) in a group manner, so that the main network can connect to multiple different sub-network groups through multiple switch groups. Under this architecture, the network switch only needs to process control packets belonging to the same switch group, and the control packets can simultaneously carry the connection status of multiple sub-networks, further reducing the processing volume of control packets.

[0012] Please refer to Figure 2 , Figure 2 Schematic diagram of a network system 2 according to an embodiment of the present invention. In this embodiment, the network system 2 includes a main network 20 and a plurality of sub-networks N1-N10, which can be divided into a plurality of groups G1-G3. The main network 20 includes a plurality of standby network switches 22_1, 24_1 and 26_1 in standby state and a plurality of main network switches 22_2-22_5, 24_2-24_3 and 26_2 for data forwarding. It should be noted that the main network 20 is Figure 2 FIG. 2 shows a ring network, but is not limited thereto. The main network 20 can be a network topology of various types and suitable for different redundancy protocols. Figure 2 The number of sub-networks, the number of groups, and the number of network switches shown are for illustration only and are not limited thereto. A person skilled in the art may adjust and modify the numbers according to actual needs.

[0013] In detail, group G1 includes a switch group C1 and a sub-network group S1. Switch group C1 includes a backup network switch 22_1 and a plurality of main network switches 22_2 to 22_5, and sub-network group S1 includes sub-networks N1 to N4. The plurality of main network switches 22_2 to 22_5 are respectively coupled to sub-networks N1 to N4 through a plurality of links L5 to L8, and the backup network switch 22_1 is used as a backup for the main network switches 22_2 to 22_5 and is coupled to sub-networks N1 to N4 through a plurality of links L1 to L4. Similarly, group G2 includes a switch group C2 and a sub-network group S2. Switch group C2 includes a backup network switch 24_1 and a plurality of main network switches 24_2 to 24_3, and sub-network group S2 includes sub-networks N5 to N7. The main network switch 24_2 is coupled to the sub-networks N5 and N6 through links L12 and L13, respectively, and the main network switch 24_3 is coupled to the sub-network N7 through link L14. The backup network switch 24_1 is coupled to the sub-networks N5 to N7 through links L9 to L11 as a backup for the main network switches 24_2 and 24_3. The group G3 includes a switch group C3 composed of a backup network switch 26_1 and a main network switch 26_2, and a sub-network group S3 composed of sub-networks N8 to N10. The main network switch 26_2 is coupled to the sub-networks N8 to N10 through links L18 to L20, respectively, and the backup network switch 26_1 is coupled to the sub-networks N8 to N10 through links L15 to L17 as a backup for the main network switch 26_2.

[0014] For ease of explanation, Figure 2 The network system 2 shown includes different network coupling modes. Specifically, in group G1, sub-networks N1-N4 are connected and forwarded through main network switches 22_2-22_5 respectively, while backup network switch 22_1 connects all sub-networks N1-N4 in group G1 and serves as backup for all main network switches 22_2-22_5 in group G1. In group G3, all sub-networks N8-N10 are connected and forwarded through the same main network switch 26_2, and backup network switch 26_1 connects all sub-networks N8-N10 in group G3 and serves as backup for main network switch 26_2. In addition, in group G2, main network switch 24_2 connects two sub-networks N5 and N6, main network switch 24_3 connects another sub-network N7 in the same group, and backup network switch 24_1 connects sub-networks N5-N7 and serves as backup for two main network switches 24_2 and 24_3. In other words, in the same group, the main network switch can connect sub-networks in a one-to-one (such as group G1), one-to-many (such as group G3) or mixed (such as group G2) manner, and be backed up by a backup network switch.

[0015] In the network system 2, the network switches of the same switch group transmit information by exchanging control packets (controlframe) to obtain the connection status between other network switches and the connected sub-networks. In the embodiment of the present invention, the control packet can be transmitted on the main network 20 or the sub-networks N1-N10 by multicast, and the group identifier (ID) is included in the destination address of the control packet header for identification by the network switch on the main network 20. The network switch can only read the control packets with the same group identifier, and directly forward the control packets with different group identifiers without processing.

[0016] Please refer to Figure 3 , Figure 3Schematic diagram of a control packet 3 according to an embodiment of the present invention. The control packet 3 can be used in the network system 2, and includes headers 30-33, a payload 34, and a frame check sequence (FCS) 35. The headers 30-33 may include a preamble 30, a destination address (Destination MAC) 31, a source address (Source MAC) 32, and an Ethernet type (Ethertype) 33 according to the data they carry. The destination address 31 may be a Media Access Control address (MAC address), in which a specific byte or bit of a specific MAC address may be used to carry different group identifiers, or a plurality of specific MAC addresses may be used as identifications of different groups, so as to be transmitted on the primary network 20 as a multicast address, and the implementation is not limited to this. Taking a specific byte of a specific MAC address carrying different group identifiers as an example, when the standby network switch 22_1 belonging to the group G1 and having the group identifier 1 sends a control packet, a control packet with a destination address of xx-xx-xx-xx-xx-01 may be sent. When the standby network switch 22_1 receives a control packet with a destination address of xx-xx-xx-xx-xx-01, it can determine in real time that the control packet is also sent by another network switch with group identifier 1, so it needs to read and parse the packet content; when receiving a control packet with a destination address of xx-xx-xx-xx-xx-02 or xx-xx-xx-xx-xx-03, it can determine that the control packet is sent by a network switch with group identifier 2 or 3, so it does not need to process the control packet and forwards it directly. In this way, the network switch on the main network 20 can identify the control packets of the same group and read the control packets from the same group to exchange information. It should be noted that bringing the group identifier into the specific byte of the MAC address as a multicast address is only one implementation method for identifying the group in the embodiment of the present invention, and is not limited to this. A person with ordinary knowledge in the art can use a suitable method to identify different groups with a multicast address according to actual needs.

[0017] Furthermore, the payload 34 of the control packet 3 includes a command 340, a sender address 341, a partner address 342, a link number 343, at least one link identifier 344 and its corresponding connection state 345. The command 340 is used to identify different control packets; the sender address 341 is the MAC address of the primary network switch or the backup network switch that sends the control packet; the partner address 342 is the transmission object of the control packet. For example, when the primary network switch sends the control packet, the partner address 342 can be the MAC address of the backup network switch belonging to the same group. In addition, the link number 343 is the number of link connection states carried by this control packet; the link identifier 344 is the sub-network identifier to which the link is connected, and the connection state 345 is the link connection state of the corresponding sub-network (in other words, the connection state of the sub-network). The connection state 345 can be determined as a connection (link-up) or a non-connection (link-down) state according to whether the electrical signal of the link is received. It should be noted that the control packet 3 only illustrates necessary fields for implementing the embodiment of the present invention and is not limited thereto. A person skilled in the art may adjust the specific content of the control packet 3 according to actual needs.

[0018] The groups G1 to G3 in the embodiment of the present invention can be regarded as the minimum unit for implementing the network coupling backup method in the network system 2. That is, each group is coupled to a sub-network group for the main network 20, and data is forwarded by at least one main network switch, and a backup network switch is on standby for backup. The network coupling backup method of the network system 2 can be summarized as a network coupling backup process 4, such as Figure 4 The network coupling redundancy process 4 includes the following steps:

[0019] Step 400: Start.

[0020] Step 402: The standby network switch periodically sends a first control packet.

[0021] Step 404: In response to receiving the first control packet, at least one master network switch sends a first acknowledgment packet (ACK).

[0022] Step 406: When the backup network switch does not receive a first confirmation packet from at least one primary network switch that satisfies a first condition, perform link switching.

[0023] Step 408: When the primary network switch meets a second condition, send a second control packet;

[0024] Step 410: In response to receiving the second control packet, the standby network switch sends a second confirmation packet and performs link switching according to the second control packet.

[0025] Step 412: In response to receiving the second confirmation packet, the primary network switch performs link switching.

[0026] Step 414: End.

[0027] According to the network coupling backup process 4, the backup network switch periodically sends a first control packet (step 402), and confirms the status of the main network switch according to the first confirmation packet responded by the main network switch (step 404). When the first condition is met, it can be determined that the main network switch has failed (such as failure or inability to connect), and link switching is performed for backup (step 406). In addition, when a second condition is met, the main network switch determines that a link switch is required, and therefore sends a second control packet to the backup network switch (step 408). The backup network switch responds to the second confirmation packet and performs a link switch based on the information in the second control packet (step 410). Finally, after receiving the second confirmation packet, the main network switch performs a link switch (step 412). Among them, the first control packet, the first confirmation packet, the second control packet, and the second confirmation packet can be referred to. Figure 3 The control packet 3 illustrates the specific format and content of the control packet used in the present invention.

[0028] For details, please also refer to Figure 5A , Figure 5B , Figure 5A , Figure 5B Draw Figure 2 An implementation method of the network coupling backup process 4 for the group G2 of the network system 2. Please refer to Figure 5A In step 402, the backup network switch 24_1 periodically sends the first control packet P1 in the main network 20 or the sub-networks N5~N7 (only the case where the first control packet P1 is sent in the main network 20 is shown). The content of the payload 34 of the first control packet P1 can be shown in Table 1 below. Among them, the sender address 341 is the address MAC1 of the backup network switch 24_1. The number of links 343 indicates the number of sub-networks connected to the backup network switch 24_1, and the link identifier 344 and the connection status 345 respectively record the connection status of the links L9~L11 connected from the network switch 24_1 to the sub-networks N5~N7. As shown in Table 1, when the connection status 345 is all link-up, it means that the backup network switch 24_1 can perform line switching for sub-networks N5~N7 at any time for backup. It should be noted that the first control packet P1 needs to carry the connection status of all sub-networks N5~N7 connected to the backup network switch 24_1. Table 1

[0029] Please continue to refer to Figure 5AIn step 404, after receiving the first control packet P1, the main network switches 24_2 and 24_3 need to send a first confirmation packet P1_ACK to report the connection status. The payload 34 content of the first confirmation packet P1_ACK sent by the main network switch 24_2 can be shown in Table 2 below. Among them, the sender address 341 is the address MAC2 of the main network switch 24_2, and the partner address 342 is the address MAC1 of the backup network switch 24_1. The number of links 343 indicates the number of sub-networks connected to the main network switch 24_2, and the link identifier 344 and the connection status 345 respectively record the connection status of the links L12 and L13 connected from the main network switch 24_2 to the sub-networks N5 and N6. As shown in Table 2, when the connection status 345 is link-up, it means that the links L12 and L13 connected to the sub-networks N5 and N6 by the main network switch 24_2 are operating normally. It should be noted that the first confirmation packet P1_ACK needs to carry the connection status of all sub-networks N5 and N6 connected to the main network switch 24_2. Table 2

[0030] The content of the payload 34 of the first confirmation packet P1_ACK sent by the main network switch 24_3 can be shown in Table 3 below. Among them, the sender address 341 is the address MAC3 of the main network switch 24_3, and the partner address 342 is the address MAC1 of the backup network switch 24_1. The number of links 343 indicates the number of sub-networks connected to the main network switch 24_3, and the link identifier 344 and the connection status 345 record the connection status of the link L14 connected from the main network switch 24_3 to the sub-network N7. As shown in Table 3, when the connection status 345 is link-up, it means that the link L14 connecting the main network switch 24_3 to the sub-network N7 is operating normally. Table 3

[0031] In step 406, the backup network switch 24_1 receives the first confirmation packet P1_ACK sent from the main network switches 24_2 and 24_3. Through the first confirmation packet P1_ACK, the backup network switch 24_1 can obtain the connection status of the main network switches 24_2 and 24_3 and the sub-networks N5~N7. When the backup network switch 24_1 does not receive the first confirmation packet P1_ACK from one of the main network switches, it should confirm whether the first condition is met to decide whether to perform link switching. The first condition can be when the first confirmation packet P1_ACK from the same main network switch is not received for more than a predetermined number of times, or when the first confirmation packet P1_ACK from the same main network switch is not received for more than a predetermined time, etc., and is not limited to this. When the first condition is met, the backup network switch 24_1 can determine that the main network switch has failed or malfunctioned, and perform link switching as its backup. Please refer to Figure 5B , which illustrates the situation when the main network switch 24_2 fails. When the main network switch 24_2 fails, the backup network switch 24_1 will not be able to receive the first confirmation packet P1_ACK sent by the main network switch 24_2. When the first condition is met, for example, the backup network switch 24_1 sends the first control packet P1 to the main network 20 three times in a row, and only receives the first confirmation packet P1_ACK replied by the main network switch 24_3 but does not receive the first confirmation packet P1_ACK replied by the main network switch 24_2, the backup network switch 24_1 can determine that the main network switch 24_2 has failed or malfunctioned. In this case, the backup network switch 24_1 will serve as a backup for the main network switch 24_2 and perform link switching. If Figure 5B As shown, the backup network switch 24_1 will open the port connected to the sub-networks N5 and N6 (set to forwarding), and forward data between the main network and the sub-networks N5 and N6 through the links L9 and L10. Accordingly, the backup network switch can detect whether the backup main network switch fails and provide backup for it. It should be noted that the backup network switch 24_1 can store the sub-network information related to the main network switches 24_2 and 24_3 respectively (obtained through the first confirmation packet P1_ACK before the device fails). Therefore, when it is determined that the main network switches 24_2 and 24_3 fail, the stored information can be loaded, and the link of the sub-network connected to the failed main network switch can be switched accordingly.

[0032] Please refer to Fig. 6A , Figure 6B , Fig. 6A , Figure 6B Draw Figure 2 Another implementation method of the network coupling backup process 4 for the group G2 of the network system 2. Please refer to Fig. 6AIn step 408, when the main network switch 24_2 satisfies the second condition, it sends a second control packet P2 to request link switching. The second condition may include the situation that when the main network switch 24_2 starts or resumes operation, the path backed up by the backup network switch 24_1 needs to be switched back, and when the main network switch 24_2 detects that the connected link recovers from a failed state to a connected state, it needs to switch back. On the other hand, the second condition may also include the situation that when the main network switch 24_2 detects that the connected link fails, it needs to be handed over to the backup network switch 24_1 for backup. The second control packet P2 at least carries the sub-network connection status corresponding to the link to be switched, so that the backup network switch can perform link switching according to the second control packet P2.

[0033] by Fig. 6A For example, when the main network switch 24_2 detects that the link L12 between it and the sub-network N5 fails, the main network switch 24_2 can send a second control packet P2 in the main network 20 to notify the backup network switch 24_1 to switch the link for backup. The content of the payload 34 of the second control packet P2 sent by the main network switch 24_2 can be shown in Table 4 below. Among them, the sender address 341 is the address MAC2 of the main network switch 24_2, and the partner address 342 is the address MAC1 of the backup network switch 24_1. The number of links 343 indicates the number of sub-networks whose links need to be changed in the sub-networks connected to the main network switch 24_2. The link identifier 344 and the connection status 345 can be used to record the connection status of the links L12 and L13 connected from the main network switch 24_2 to the sub-networks N5 and N6. As shown in Table 4, the subnet identifier 344 of the subnet N5 connected to the main network switch 24_2 is 5, and its corresponding connection state 345 is link-down. In other words, the second control packet P2 carries the operating status (non-connected state) of the link L12 connecting the main network switch 24_2 to the subnet N5. It should be noted that the second control packet P2 only needs to carry the link state of the link L12 that needs to be switched, and does not need to carry the link state of the link L13 whose connection state has not changed. Table 4

[0034] Please refer to Figure 6BAccording to the network coupling backup process 4, in step 410, the backup network switch 24_1 that receives the second control packet P2 sends a second confirmation packet P2_ACK. The payload 34 content of the second confirmation packet P2_ACK sent by the backup network switch 24_1 can be shown in Table 5 below. Among them, the sender address 341 is the address MAC1 of the backup network switch 24_1, and the partner address is the address MAC2 of the main network switch 24_2 that sends the second control packet P2. The number of links 343 indicates the number of sub-networks whose links need to be changed in the sub-network connected to the backup network switch 24_1. The link identifier 344 and the connection status 345 can be used to record the connection status of the links L9~L11 connected from the backup network switch 24_1 to the sub-networks N5~N7. As shown in Table 5, the second confirmation packet P2_ACK carries the subnet identifier 344 of the subnet N5 connected to the backup network switch 24_1 as 5, and its corresponding connection state 345 is link-up. Therefore, the connection between the main network 20 and the subnet N5 can be switched from the failed link L12 connected to the main network switch 24_2 to the link L9 connected by the backup network switch 24_1. In this process, the backup network switch 24_1 needs to change the communication port connected to the link L9 from the blocking state to the forwarding state to forward data between the main network 20 and the subnet N5. It should be noted that the second confirmation packet P2_ACK only needs to carry the link state information corresponding to the subnet in the second control packet P2, that is, the link state of the link L9 corresponding to the subnet N5. Table 5

[0035] According to the network coupling redundancy process 4, in step 410, after the primary network switch 24_2 receives the second confirmation packet P2_ACK replied by the backup network switch 24_1, the primary network switch 24_2 needs to change the communication port connected to the link L12 from the forwarding state to the blocking state, and the data forwarding between the main network 20 and the sub-network N5 is handed over to the backup network switch 24_1 through the link L9.

[0036] On the other hand, according to the network coupling backup process 4, when the main network switch 24_2 detects that the link L12 between it and the sub-network N5 is restored to connection, in step 408, the main network switch 24_2 can send a second control packet P2 requesting link switching again in the main network 20, and the content of its payload 34 can be shown in the following Table 6. Among them, the sub-network identifier 344 carrying the sub-network N5 connected to the main network switch 24_2 is 5, and its corresponding connection state 345 is link-up. In other words, the link L12 has been restored to the connection state. When the backup network switch 24_1 receives the second control packet P2, it will reply with a second confirmation packet P2_ACK and perform link switching. In other words, the connection between the main network 20 and the sub-network N5 can be switched from the link L9 connected by the backup network switch 24_1 to the link L12 connected by the main network switch 24_2. During this process, the backup network switch 24_1 needs to change the communication port connected to the link L9 from the forwarding state to the blocking state to continue to stand by as a backup; the main network switch 24_2 needs to change the communication port connected to the link L12 from the blocking state to the forwarding state to re-transmit data between the main network 20 and the sub-network N5. Table 6

[0037] Accordingly, the network system 2 divides the network switch of the main network 20 into a plurality of switch groups by means of groups, and connects them to a plurality of sub-network groups respectively. By setting a multicast address (destination address 31) specifically in the control packet, the groups do not interfere with each other. In each switch group, a backup network switch can simultaneously back up multiple main network switches, thereby reducing the number of devices required. In addition, the switch group realizes a network coupling backup method by exchanging control packets, and the control packets simultaneously carry the connection status of a plurality of links, which can effectively reduce the number of control packets circulating, and at the same time, can be compatible with a variety of connection methods with the main network switch and the sub-network.

[0038] The above-mentioned method for implementing network coupling redundancy by a backup network switch, taking the backup network switch 24_1 as an example, can be summarized into processes 70 and 72. Fig. 7A , Figure 7B The process 70 comprises the following steps:

[0039] Step 700: Start.

[0040] Step 701: Periodically send a first control packet.

[0041] Step 702: Receive a first confirmation packet.

[0042] Step 703: Determine whether the first condition is met. If yes, execute step 704; if no, execute step 702.

[0043] Step 704: Perform backup and link switching.

[0044] Step 705: End.

[0045] According to the process 70, in step 701, the backup network switch 24_1 periodically sends a first control packet to the main network 20 or the sub-networks N5-N7, and the first control packet includes the connection status between the backup network switch 24_1 and the sub-networks N5-N7. In step 702, the backup network switch 24_1 receives a first confirmation packet from the main network switches 24_2 and 24_3 belonging to the same group. In step 703, the backup network switch 24_1 determines the operation status of the main network switches 24_2 and 24_3 according to the received first confirmation packet. When the received first confirmation packet satisfies the first condition, it is determined that one of the main network switches 24_2 and 24_3 has failed, and step 704 is executed. Taking the failure of the main network switch 24_2 as an example, in step 704, the backup network switch 24_1 serves as a backup for the main network switch 24_2 and performs link switching, so that the sub-networks N5 and N6 originally connected by the main network switch 24_2 are connected to the backup network switch 24_1 through the links L9 and L10 to forward data between the main network 20 and the sub-networks N5 and N6.

[0046] When the standby network switch executes process 70, it also executes process 72 synchronously to monitor whether there is a second control packet from the main network switch. Process 72 includes the following steps:

[0047] Step 720: Start.

[0048] Step 721: Wait for the second control packet.

[0049] Step 722: Determine whether the second control packet is received. If yes, execute step 723; if no, execute step 721.

[0050] Step 723: Send a second confirmation packet.

[0051] Step 724: Perform backup and link switching.

[0052] Step 725: End.

[0053] According to process 72, in step 721, the standby network switch 24_1 continuously monitors the second control packet from the main network switches 24_2 and 24_3 in the same group. The second control packet includes the connection status between the main network switch and the sub-network to which it is connected. In step 722, the standby network switch 24_1 determines whether the second control packet has been received. If so, step 723 is executed. For example, the standby network switch 24_1 receives the second control packet from the main network switch 24_2. In step 723, the standby network switch 24_1 sends a second confirmation packet to the main network switch 24_2. Then, in step 724, the standby network switch 24_1 performs link switching according to the link connection status contained in the second control packet.

[0054] The above method for implementing network coupling redundancy by the main network switch can be summarized into processes 80 and 82, taking the main network switch 24_2 as an example. Fig. 8A , Figure 8B The process 80 comprises the following steps:

[0055] Step 800: Start.

[0056] Step 801: Wait for the first control packet.

[0057] Step 802: Determine whether the first control packet is received. If yes, execute step 803; if no, execute step 804.

[0058] Step 803: Send a first confirmation packet.

[0059] Step 804: Determine whether the third condition is met. If yes, execute step 805; if no, execute step 801.

[0060] Step 805: Execute link switching.

[0061] Step 806: End.

[0062] According to the process 80, in step 801, the main network switch 24_2 waits for the first control packet from the backup network switch 24_1 in the same group, and determines whether the first control packet is received in step 802. If the main network switch 24_2 receives the first control packet, it can be determined that the backup network switch 24_1 operates normally, and sends a first confirmation packet to the backup network switch 24_1 in step 803. If the main network switch 24_2 does not receive the first control packet, it is necessary to determine whether the third condition is met in step 804 for subsequent processing. The third condition includes determining that the backup network switch 24_1 has failed and the link state to which the main network switch 24_2 is connected is connected and the corresponding port is non-forwarding. Determining whether the backup network switch 24_1 has failed can be based on not receiving the first control packet of the backup network switch 24_1 for more than a predetermined time, but is not limited thereto. When the third condition is met, the primary network switch 24_2 performs link switching to replace the link originally backed up by the failed backup network switch 24_1 in step 805. The first confirmation packet includes the connection status of the links L12 and L13 between the primary network switch 24_2 and the sub-networks N5 and N6 connected thereto.

[0063] When the main network switch executes process 80, process 82 is also executed synchronously to notify the backup network switch when link switching is required. Process 82 includes the following steps:

[0064] Step 820: Start.

[0065] Step 821: Detect link connection status.

[0066] Step 822: Determine whether the second condition is met. If yes, execute step 823; if no, execute step 821.

[0067] Step 823: Send a second control packet.

[0068] Step 824: Receive a second confirmation packet.

[0069] Step 825: Perform link switching.

[0070] Step 826: End.

[0071] According to process 82, in step 821, the main network switch 24_2 continuously detects the connection status of the links L12 and L13 between the sub-networks N5 and N6. In step 822, the main network switch 24_2 determines whether the second condition is met. If so, step 823 is executed. Taking the failure of the link L12 between the main network switch 24_2 and the sub-network L5 as an example, in step 823, the main network switch 24_2 sends a second control packet to the backup network switch 24_1. The payload 34 of the second control packet is as shown in Table 4, wherein the link L12 connected to the sub-network L5 is in a disconnected state, and the backup network switch 24_1 can perform link switching accordingly. Then, in step 824, the main network switch 24_2 receives the second confirmation packet from the backup network switch 24_1. Finally, in step 825, the main network switch 24_2 performs link switching.

[0072] In the embodiment of the present invention, the first control packet and the first confirmation packet can carry the link connection status of multiple sub-networks at the same time, thereby effectively reducing the number of packets; the second control packet and the second confirmation packet can only carry the sub-network and corresponding link information that need to be switched, thereby reducing the amount of information in the packet. In addition, through this mechanism, network configuration errors can be detected and tolerated, and error information can be reported.

[0073] Please refer to Fig. 9 , Fig. 9 A schematic diagram of an incorrect configuration according to an embodiment of the present invention. Fig. 9 The network coupling configuration of another group G4 in the network system 2 is shown. Specifically, the group G4 includes sub-networks N11 to N13, main network switches 27_2 and 27_3, and backup network switches 27_1 and 27_4. The backup network switch 27_1 is coupled to the sub-networks N11 and N12 via links L21 and L22, and the backup network switch 27_4 is coupled to the sub-network N13 via link L23. The main network switch 27_2 is coupled to the sub-networks N11 and N13 via links L24 and L26, and the main network switch 27_3 is coupled to the sub-network N12 via link L25. Fig. 9It can be seen that two backup network switches are incorrectly configured in group G4. When the backup network switches 27_1 and 27_4 send the first control packet and receive the first confirmation packet sent from the main network switches 27_2 and 27_3, the wrong connection status can be detected through the first confirmation packet. Specifically, when the backup network switch 27_1 receives the first confirmation packet from the main network switch 27_2, after parsing the first confirmation packet, the information of the main network switch 27_2 connecting to the sub-networks N11 and N13 can be obtained through the link identifier 344. Since the sub-network N13 does not belong to one of the sub-networks N11 and N12 connected to the backup network switch 27_1, the backup network switch 27_1 can detect that there is an incorrect network configuration in group G4. Similarly, the backup network switch 27_4 can also find out through the first confirmation packet that the main network switches 27_2 and 27_3 are respectively connected to the sub-network N11 and the sub-network N12 that the backup network switch 27_4 is not connected to. Therefore, the backup network switch 27_4 can detect that there is an incorrect network configuration in the group G4. In this case, when a conflict occurs in the connection mode of the sub-network, the backup network switches 27_1 and 27_4 can continue to operate and report an error message.

[0074] Please refer to Fig.10 , Fig.10 FIG. 4 is a schematic diagram of another incorrect configuration of an embodiment of the present invention. Fig.10 The network coupling configuration of another group G5 in the network system 2 is shown. Specifically, the group G5 includes sub-networks N14 and N15, main network switches 28_2 and 28_3, and backup network switches 28_1 and 28_4. The backup network switch 28_1 is coupled to the sub-networks N14 and N15 via links L27 and L28, and the backup network switch 28_4 is coupled to the sub-network N15 via link L29. The main network switch 28_2 is coupled to the sub-network N14 via link L30, and the main network switch 28_3 is coupled to the sub-network N15 via link L31. Fig.10It can be seen that two backup network switches 28_1 and 28_4 are incorrectly configured in group G5, and the two backup network switches 28_1 and 28_4 are simultaneously connected to sub-network N15. In this case, the main network switches 28_2 and 28_3 can detect the incorrect connection status through the first control packet or the second confirmation packet from the backup network switches 28_1 and 28_4. Specifically, the main network switch 28_3 can receive the first control packet from the backup network switch 28_1, and after parsing the first control packet, the information that the backup network switch 28_1 is connected to the sub-network N15 can be obtained through the link identifier 344. Similarly, the main network switch 28_3 can also receive the first control packet from the backup network switch 28_4, and after parsing the first control packet, the information that the backup network switch 28_4 is also connected to the sub-network N15 can be obtained through the link identifier 344. Accordingly, the main network switch 28_3 detects that there is an incorrect network configuration in group G4 and reports an error message. In this case, when the main network switch 28_3 sends the first confirmation packet, the object of the transmission will be the one with the smaller MAC address among the two backup network switches 28_1 and 28_4. Assuming that the backup network switch 28_1 has the smaller MAC address, that is, in the first confirmation packet sent by the main network switch 28_3, the partner address 342 will be set to the MAC address of the backup network switch 28_1. In this case, when the main network switch 28_3 detects that the link L31 fails, it will send a second control packet to the backup network switch 28_1. That is, in the second control packet sent by the main network switch 28_3, the partner address 342 will also be set to the MAC address of the backup network switch 28_1.

[0075] It should be noted that although the main network switch 28_3 sends the first confirmation packet and the second control packet to the backup network switch 28_1, the backup network switch 28_4 belonging to the same group G5 can also receive the first confirmation packet and the second control packet sent by the main network switch 28_3. Specifically, as mentioned above, the control packets of the same group are sent in a multicast manner on the main network 20 through the destination address 31 with the group identifier, so the network switches 28_1~28_4 belonging to the same group can read and parse the control packets sent by each other. Therefore, the backup network switch 28_4 can also parse the first confirmation packet and the second control packet sent by the main network switch 28_3 to the backup network switch 28_1, and obtain the information of the backup by another backup network switch 28_1 according to the partner address 342. In this case, when the main network switch 28_3 fails, the backup network switch 28_4 does not need to perform link switching for backup. Accordingly, the network system 2 can effectively detect errors and tolerate faults.

[0076] Please refer to Fig.11 , Fig.11 FIG. 4 is a schematic diagram of another incorrect configuration of an embodiment of the present invention. Fig.11 The network coupling configuration of another group G6 in the network system 2 is shown. Specifically, the group G6 includes sub-networks N16 and N17, main network switches 29_2 and 29_3, and a backup network switch 29_1. The backup network switch 29_1 is coupled to the sub-networks N16 and N17 via links L32 and L33. The main network switch 29_2 is coupled to the sub-network N16 via link L34, and the main network switch 29_3 is coupled to the sub-networks N16 and N17 via links L35 and L36. Fig.11 It can be seen that two main network switches 29_2 and 29_3 are mistakenly configured to connect to the sub-network L16 in the group G6. In this case, the backup network switch 29_1 can detect the wrong connection status through the first confirmation packet or the second control packet from the main network switches 29_2 and 29_3, and report the error information. Specifically, after the backup network switch 29_1 sends the first control packet, it can receive the first confirmation packet from the main network switch 29_2. After parsing the first confirmation packet, the information that the main network switch 29_2 is connected to the sub-network N16 can be obtained through the link identifier 344. Similarly, the backup network switch 29_1 can receive the first confirmation packet from the main network switch 29_3. After parsing the first confirmation packet, the information that the main network switch 29_3 is connected to the sub-networks N16 and N17 can be obtained through the link identifier 344. Therefore, the backup network switch 29_1 can detect that the primary network switches 29_2 and 29_3 are simultaneously connected to the sub-network L16.

[0077] For further information, please refer to Fig.12 , which is a schematic diagram of a network device 120 according to an embodiment of the present invention. The network device 120 may be used to implement the main network switches 22_2 to 22_5, 24_2 to 24_3, 26_2, 27_2, 24_3, 28_2, 28_3, 29_2, 29_3 and the backup network switches 22_1, 24_1, 26_1, 27_1, 27_4, 28_1, 28_4, 29_1 according to an embodiment of the present invention. Fig.12As shown, the network device 120 may include a processing unit 1200 and a storage unit 1202. The processing unit 1200 may be a general purpose processor, a microprocessor, an application specific integrated circuit (ASIC), etc. or a combination thereof. The storage unit 1202 is coupled to the processing unit 1200 and may be any data storage device for storing a program code 1204, and the program code 1204 is read and executed by the processing unit 1200. For example, the storage unit 1202 may be a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, an optical data storage device, and a non-volatile storage unit, etc., but is not limited thereto. In addition, the device 120 also includes a plurality of ports (not shown in the figure) for connecting a plurality of sub-networks and a plurality of network devices of the main network.

[0078] The network device 120 is used to represent the necessary elements required to implement the embodiments of the present invention. A person skilled in the art may make different modifications and adjustments accordingly, but the invention is not limited thereto. For example, when the network device 120 is used to implement the main network switch, the processes 80 and 82 of the network coupling backup method may be compiled into program code 1204 and stored in the storage unit 1202, and the network coupling backup method is executed by the processing unit 1200. When the network device 120 is used to implement the backup network switch, the processes 70 and 72 of the network coupling backup method may be compiled into program code 1204 and stored in the storage unit 1202, and the network coupling backup method is executed by the processing unit 1200. In addition, the storage unit 1202 is also used to store the connection status information of the network switches in the same switch group and the sub-networks to which they are connected, as well as the data required when the network coupling backup method is executed, but the invention is not limited thereto.

[0079] In summary, the present invention provides a network coupling backup method, device and network architecture, which can use a backup network switch to backup multiple main network switches during network coupling, thereby reducing the number of devices required. The network switch is divided into multiple groups by grouping, so that the groups do not interfere with each other, thereby reducing the number of control packets required to be processed. In addition, the control packet can carry the connection status of multiple links at the same time, further reducing the number of control packets. Thus, while ensuring the reliability and stability of network coupling, the cost is reduced and the performance is improved, thereby improving the shortcomings of the prior art.

[0080] The above description is only a preferred embodiment of the present invention. All equivalent changes and modifications made within the scope of the claims of the present invention should fall within the scope of the present invention. Description of Reference Numerals

[0081] 1: Network system 10: Main Network 12_1~12_4: Sub-network 14_1~14_4: Main network switch 16_1~16_4: Backup network switch 15_1~15_4、17_1~17_4: Link 2: Network system 20: Main Network N1~N10: Sub-network L1~L20: Link G1~G3: Group C1~C3: Switch Group S1~S3: Sub-network groups 22_1, 24_1, 26_1: Backup network switches 22_2~22_5, 24_2, 24_3, 26_2: Main network switch 3: Control Packet 30: Previous 31: Destination address 32: Source address 33:Ether Type 34: Payload 35: Frame Check Sequence 340: Instructions 341:Sender's address 342:Partner Address 343: Number of links 344: Link Identifier 345: Connection status 4: Process 400~414: Steps P1: First control packet P1_ACK: First acknowledgment packet P2: Second control packet P2_ACK: Second acknowledgment packet 70, 72, 80, 82: Process 700~705、720~725、800~806、820~826: Steps G4~G6: Group L21~L36: Link N11~N17: Sub-network 27_1, 27_4, 28_1, 28_4, 29_1: Backup network switches 27_2, 27_3, 28_2, 28_3, 29_2: Main network switch 120: Network device 1200: Processing unit 1202: Storage unit 1204: Program code

Claims

1. A main network switch, characterized in that: A switch group configured in a main network is coupled to at least one first sub-network of a sub-network group through at least one first link, comprising: a processing unit for executing a program code; as well as A storage unit is coupled to the processing unit and is used to store the program code to instruct the processing unit to execute a network coupling backup method, wherein the network coupling backup method comprises: receiving a first control packet from a backup network switch of the switch group; In response to not receiving the first control packet, performing link switching according to a first switching condition; In response to receiving the first control packet, sending a first confirmation packet including a connection status of the at least one first sub-network; Sending a second control packet to the backup network switch; as well as In response to sending the second control packet, a second confirmation packet is received from the backup network switch, and link switching is performed after receiving the second confirmation packet.

2. The main network switch according to claim 1, characterized in that: The first switching condition is that the first control packet of the backup network switch is not received for a predetermined time and a link state of a link connected to the main network switch is an online state and a corresponding port is in a non-forwarding state.

3. The main network switch according to claim 1, characterized in that: The first control packet, the first confirmation packet, the second control packet and the second confirmation packet are sent in multicast, and destination addresses of the first control packet, the first confirmation packet, the second control packet and the second confirmation packet include a group identifier of the switch group.

4. The main network switch according to claim 1, characterized in that: The backup network switch is coupled to at least one second sub-network of the sub-network group through at least one second link, and the first control packet includes a connection status of the at least one second sub-network.

5. The main network switch according to claim 4, characterized in that: An error detection of network configuration is performed according to the connection status of the at least one second sub-network in the first control packet.

6. The main network switch according to claim 1, characterized in that: When the switch group includes another backup network switch, a media access control address of the other backup network switch is greater than a media access control address of the backup network switch, and the main network switch reports an error message.

7. The main network switch according to claim 1, characterized in that: The second control packet is sent to the backup network switch when the main network switch resumes operation or when a link of the at least one first link fails or resumes connection.

8. The main network switch according to claim 7, characterized in that: The second control packet at least includes a connection status of a sub-network that needs to perform link switching.

9. A backup network switch, characterized in that: A switch group configured in a main network is coupled to at least one first sub-network of a sub-network group through at least one first link, comprising: a processing unit for executing a program code; as well as A storage unit is coupled to the processing unit and is used to store the program code to instruct the processing unit to execute a network coupling backup method, wherein the network coupling backup method comprises: Periodically sending a first control packet including the connection status of the at least one first sub-network to at least one main network switch of the switch group; receiving at least one first confirmation packet from the at least one primary network switch in response to sending the first control packet; Performing link switching according to a first condition; as well as In response to receiving a second control packet from the at least one master network switch, a second confirmation packet is sent, and link switching is performed according to the second control packet.

10. The backup network switch according to claim 9, characterized in that: The first control packet, the at least one first confirmation packet, the second control packet and the second confirmation packet are sent in multicast, and destination addresses of the first control packet, the at least one first confirmation packet, the second control packet and the second confirmation packet include a group identifier of the switch group.

11. The backup network switch according to claim 9, characterized in that: Each of the at least one master network switch is coupled to at least one second sub-network of the sub-network group via at least one second link, and each of the at least one first confirmation packets includes a connection status of the at least one second sub-network of each master network switch.

12. The backup network switch according to claim 11, characterized in that: The network coupling redundancy method further includes performing an error detection of network configuration according to the connection status of the at least one second sub-network in the at least one first confirmation packet.

13. The backup network switch according to claim 12, wherein: When a first confirmation packet of the at least one first confirmation packet carries a connection status of a sub-network that does not belong to the at least one first sub-network, an error message is reported.

14. The backup network switch according to claim 12, wherein: When different first confirmation packets of the at least one first confirmation packet carry connection status of the same sub-network, an error message is reported.

15. The backup network switch according to claim 11, characterized in that: The first condition is a number of times that the first confirmation packet of the at least one primary network switch is not received; link switching according to the first condition is to switch the at least one second link of the primary network switch when the number of times the first condition exceeds a predetermined number.

16. The backup network switch according to claim 9, characterized in that: The link switching is performed according to the second control packet according to the connection status of at least one sub-network carried in the second control packet.

17. A network architecture for network coupling redundancy, characterized in that: Include: a plurality of sub-networks belonging to a plurality of sub-network groups; and A main network includes a plurality of switch groups, each of the plurality of switch groups is coupled to a sub-network group of the plurality of sub-network groups, and includes: at least one main network switch coupled to the sub-network group, wherein each main network switch of the at least one main network switch is coupled to at least one first sub-network of the sub-network group via at least one first link; as well as a backup network switch coupled to the sub-network group via at least one second link; Each of the plurality of switch groups is used to execute a network coupling redundancy method, comprising: The standby network switch periodically sends a first control packet including the connection status of the at least one second link; In response to receiving the first control packet, each of the at least one master network switch sends a first confirmation packet including a connection status of the at least one first link; The standby network switch performs link switching according to a first condition; The at least one master network switch sends a second control packet according to a second condition; In response to receiving the second control packet, the standby network switch replies with a second confirmation packet and performs link switching according to the second control packet; and In response to receiving the second confirmation packet, the at least one master network switch performs link switching.

18. The network architecture according to claim 17, wherein: The first control packet, the first confirmation packet, the second control packet and the second confirmation packet are sent by multicast, and the destination addresses of the first control packet, the first confirmation packet, the second control packet and the second confirmation packet include a group identifier of the switch group to which they belong.

19. The network architecture according to claim 17, wherein: In the network coupling backup method, the first condition is the number of times that the backup network switch has not received the first confirmation packet of a primary network switch of the at least one primary network switch; the backup network switch switches the link according to the first condition by switching the at least one first link of the primary network switch when the number of times the first condition exceeds a predetermined number.

20. The network architecture of claim 17, wherein: In the network coupling backup method, the second condition is that when a master network switch of the at least one master network switch resumes operation or when a link of the at least one first link fails or resumes connection, the master network switch sends the second control packet.

21. The network architecture of claim 17, wherein: The link switching is performed according to the second control packet according to the connection status of at least one sub-network carried in the second control packet.

Images