CN110545198A

CN110545198A - ERPS loop damage method and main node

Info

Publication number: CN110545198A
Application number: CN201810533511.8A
Authority: CN
Inventors: 邢莉娜
Original assignee: Beijing Huawei Digital Technologies Co Ltd
Current assignee: Beijing Huawei Digital Technologies Co Ltd
Priority date: 2018-05-29
Filing date: 2018-05-29
Publication date: 2019-12-06
Anticipated expiration: 2038-05-29
Also published as: CN110545198B

Abstract

The embodiment of the application provides a method for breaking an Ethernet loop protection switching (ERPS) loop and a main node. The ERPS loop comprises a main node and at least two slave nodes, and the method comprises the following steps: if the master node does not send the NR-RB message within the preset time length and does not receive the ring protocol message sent by the slave node on the ERPS loop, switching the state of the RPL port to a blocking state; the NR-RB message is used for indicating that the state of the ERPS loop is a non-fault state; the master node sends NR-RB messages to at least two slave nodes. By implementing the embodiment of the application, the ring can be actively self-healed and damaged after the ERPS loop is formed into the ring, manual troubleshooting and intervention are not needed for damage, the consumed time is short, and the influence on the data transmission of the network is small.

Description

ERPS loop damage method and main node

Technical Field

the present application relates to the field of communications technologies, and in particular, to a method for breaking an ERPS loop and a host node.

Background

Ethernet Ring Protection Switching (ERPS) is a ring network protocol standard dedicated to the Ethernet link layer. The ERPS is an Ethernet loop protection mechanism, which achieves the purpose of eliminating a network two-layer loop by selectively blocking a network loop redundant link, avoids the proliferation and infinite circulation of messages in a loop network, and effectively prevents the formation of network storms.

The ERPS ring network equipment monitors the link state by periodically sending protocol messages and switches the state machine. If the ERPS ring network device receives the expired protocol message, it may cause the ERPS loop to fail to form a ring (for example, after the failure on the ERPS loop is recovered, if the failure protocol message in the previous state is received, the blocked port may be opened by mistake), a network storm is formed, the network cannot be broken by self-healing, the ring needs to be broken by human investigation and intervention, the consumed time is long, and the influence on the data transmission of the network is large.

Disclosure of Invention

The embodiment of the application provides an ERPS loop damage method, a host node and a computer readable storage medium, which can actively self-heal damage after the ERPS state machine is formed into a loop, do not need manual troubleshooting intervention, and have short time consumption and small influence on network data transmission.

In a first aspect, an embodiment of the present application provides a method for breaking an Ethernet Ring Protection Switching (ERPS) ring, where the ERPS ring includes a master node and at least two slave nodes, and the method includes:

If the master node does not send the NR-RB message within a preset time length and does not receive the ring protocol messages sent by the at least two slave nodes, switching the state of the RPL port to a blocking state; wherein, the NR-RB packet is used to indicate that the status of the ERPS loop is a no-fault status.

And the master node sends NR-RB messages to the at least two slave nodes.

By implementing the embodiment of the application, the self-healing damage can be actively and timely recovered after the condition is met, the state of the RPL port is switched from the forwarding state to the blocking state, manual troubleshooting intervention is not needed, the consumed time is short, and the influence on the data transmission of the network is small.

In a possible implementation manner, the ring protocol packet includes any one of the following: fault indication SF message, no fault NR message, forced switching FS message, and manual switching MS message.

In a possible implementation manner, before the switching the state of the RPL port to the blocking state if the master node does not send the NR-RB packet within a preset time period and does not receive the ring protocol packets sent by the at least two slave nodes, the method further includes:

And the master node receives a target message, wherein the target message is used for indicating that the master node is triggered to switch the state of the RPL port into a forwarding state.

And the master node switches the state of the RPL port into a forwarding state.

The master node stops sending the NR-RB messages to the other two slave nodes.

The embodiment of the application introduces the trigger condition of the state machine looping of the ERPS, and after the main node receives the target message, the main node switches the blocked port into a forwarding state and stops sending the NR-RB message.

In another possible implementation manner, the target packet includes any one of the following: the target message is an indication message in the last state of the ERPS loop.

According to the embodiment of the application, under the condition that the main node receives the overdue target message and causes the ERPS loop to form a ring, the ring can be actively and automatically broken in time, manual troubleshooting and intervention are not needed to be carried out, time consumption is short, influence on data transmission of a network is small, reliability of a system is improved, and user experience is good.

in another possible implementation manner, the preset duration is N message sending periods, where the message sending period is the target message sending period, or the message sending period is the NR-RB message sending period, and N is a positive integer greater than or equal to 2.

In the embodiment of the application, the preset time length is set to be at least two message periods, if the master node does not send the NR-RB message and does not receive the ring protocol messages sent by the at least two slave nodes within the preset time length, it means that an ERPS loop forms a ring, and the ring needs to be broken in time, so as to avoid network storm.

In another possible implementation manner, the preset duration is three message sending periods.

In the embodiment of the application, the preset duration is set as three message sending periods, the time is reserved to determine whether an ERPS loop forms a loop or not, if the ERPS loop forms a loop, the ERPS loop can self-heal and break the loop in time, the consumed time is short, and the influence on the data transmission of a network is small.

In a second aspect, an embodiment of the present application provides a master node, which is applied to an ethernet ring protection switching ERPS ring, where the ERPS ring includes the master node and at least two slave nodes, and the master node includes:

a switching unit, configured to switch the state of the RPL port to a blocking state if no NR-RB packet is sent within a preset time period and no ring protocol packet sent by the at least two slave nodes is received; wherein, the NR-RB packet is used to indicate that the status of the ERPS loop is a no-fault status.

A sending unit, configured to send the NR-RB packet to the at least two slave nodes.

In one possible implementation manner, the master node further includes:

a receiving unit, configured to receive a target packet before the switching unit switches the state of the RPL port from the forwarding state to the blocking state, where the target packet is used to trigger the master node to switch the state of the RPL port to the forwarding state.

The switching unit is further configured to switch the state of the RPL port to a forwarding state after the receiving unit receives the target packet.

and the transmission stopping unit is used for stopping transmitting the NR-RB message to the at least two slave nodes.

In a third aspect, an embodiment of the present application provides a master node, where an ERPS loop is applied to ethernet loop protection switching, where the ERPS loop includes the master node and at least two slave nodes, and the master node includes: a processor, a memory, and a transceiver, wherein:

The processor, the memory, and the transceiver are interconnected, the memory for storing a computer program comprising program instructions, the processor configured to invoke the program instructions to perform the steps of:

If the transceiver does not send the NR-RB message within a preset time length and does not receive the ring protocol messages sent by the at least two slave nodes, switching the state of the RPL port to a blocking state; wherein, the NR-RB packet is used to indicate that the status of the ERPS loop is a no-fault status.

Transmitting, by the transceiver, the NR-RB message to the at least two slave nodes.

In a possible implementation manner, if the transceiver does not send the NR-RB packet within a preset time period and does not receive the ring protocol packets sent by the at least two slave nodes, the transceiver receives a target packet before the state of the RPL port is switched from the forwarding state to the blocking state, where the target packet is used to trigger the master node to switch the state of the RPL port to the forwarding state.

And switching the state of the RPL port to a forwarding state.

Causing the transceiver to stop transmitting NR-RB messages to the at least two slave nodes.

In a fourth aspect, the present application provides a computer-readable storage medium, where a computer program is stored, where the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to execute the method for breaking an ERPS loop provided in the first aspect of the present application or any one of the possible implementations of the first aspect.

It can be seen that the embodiment of the application provides an ERPS loop ring-breaking method, a host node and a computer-readable storage medium, which can actively and self-heal the ERPS loop ring-breaking in time after the ERPS loop ring-forming, do not need human troubleshooting intervention, have short time consumption, have little influence on network data transmission, increase system reliability and have good user experience.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the embodiments will be briefly described below.

Fig. 1 is a schematic diagram of a networking structure of an ERPS loop according to an embodiment of the present application;

Fig. 2-5 are schematic diagrams of an ERPS loop protection switching scenario;

Fig. 6 is a flowchart of a method for breaking an ERPS loop according to an embodiment of the present disclosure;

Fig. 7 is a flowchart of another method for breaking an ERPS loop according to an embodiment of the present disclosure;

Fig. 8 is a schematic structural diagram of a host node according to an embodiment of the present disclosure;

Fig. 9 is a schematic structural diagram of another host node according to an embodiment of the present disclosure;

Fig. 10 is a schematic structural diagram of another host node according to an embodiment of the present application.

Detailed Description

the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

First, please refer to fig. 1. Fig. 1 is a schematic diagram of a networking structure of an ERPS loop provided in the embodiment of the present application. As shown in fig. 1, the ERPS loop includes: a master node, at least two slave nodes. Fig. 1 illustrates an example where the ERPS loop includes X slave nodes. And the master node is directly connected with the at least two slave nodes to form an ERPS loop. The master node can be connected with the communication terminal for data interaction, and the data traffic of the communication terminal can be transmitted to any slave node on the ERPS loop through the master node. Two ports of the master node on the ring are respectively defined as a master port a1 and a slave port a2, a link directly connected with the slave port a2 may be referred to as a Ring Protection Link (RPL), and the slave port a2 may be referred to as an RPL port.

Under normal conditions, the ERPS loop is in a non-fault state, and the RPL port is in a blocking state in the non-fault state, that is, the slave port a2 of the master node in fig. 1 is in the blocking state, so that data traffic cannot pass through the slave port a2 of the master node, and it is ensured that a data transmission service does not form a closed loop, thereby achieving the purpose of breaking the two-layer loop. When a link between two nodes on the ERPS ring fails or a node fails, as shown in fig. 2, taking the link between the slave node 1 and the slave node 2 as an example, the node (slave node 1 and slave node 2) that detects the failure gradually transmits the failure, sends a failure indication (SF) message, and sets the states of the port B2 and the port C1 to a blocking state. When the master node receives the SF message sent by the failed node, the state of the RPL port a2 is switched from the blocking state to the forwarding state, that is, the master node opens the data forwarding function of the slave port a2, so that the data traffic can pass through the slave port a2 of the master node, and the data traffic can still be transmitted to each node on the ERPS loop, as shown in fig. 3, so far, protection switching of the loop is completed, and forwarding of data is quickly resumed.

After the protection switching of the loop is completed, if the failed link between the slave node 1 and the slave node 2 recovers, the two ports B1 and B2 of the slave node 1 on the ring and the two ports C1 and C2 of the slave node 2 on the ring send out no-failure (NR) messages. To prevent looping, port B2 and port C1 are still blocked. When the master node receives the NR packet, a Wait To Restore (WTR) timer is started. When the WTR timer is over time, the master node switches the state of the RPL port a2 from the forwarding state to the blocking state, and sends a no request-environmental protection link blocked (NR-RB) packet to the outside, as shown in fig. 4. When the slave node 1 and the slave node 2 receive the NR-RB packet transmitted by the master node, the states of the port B2 and the port C1 are switched from the blocking state to the forwarding state, and the slave node 1 and the slave node 2 stop transmitting the NR packet, as shown in fig. 5.

It should be noted that the NR-RB message, the NR message, and the SF message are all sent periodically.

it can be known that the master node and the slave node in the embodiment of the present application may be a switch, a router, or other transmission devices that support the ERPS protocol.

Next, a network structure schematic diagram of the ERPS loop provided in fig. 1 and a scene schematic diagram of the ERPS loop protection switching provided in fig. 2 to fig. 5 are combined to describe the method for breaking the ERPS loop provided in the embodiment of the present application. As shown in fig. 6, the method for breaking the ERPS loop may at least include the following steps:

S601: and if the master node does not send the NR-RB message within the preset time length and does not receive the ring protocol message sent by the slave node, switching the state of the RPL port to a blocking state.

Specifically, the ring protocol packet sent by the slave node may be, for example, an SF packet, an NR packet, a Forced Switch (FS) packet, a Manual Switch (MS) packet, or the like.

specifically, after the ERPS loop is looped, it means that the entire ERPS loop is a path, and no faulty node or faulty link exists on the ERPS loop. The ports of all nodes on the ERPS ring are in a forwarding state, including the RPL ports being in the forwarding state. The master node stops sending the NR-RB message to other slave nodes on the ERPS loop, and the slave node does not send the ring protocol message to the master node, that is, the master node cannot receive the ring protocol messages sent by the at least two slave nodes, and at this time, the ERPS loop forms a ring, which may cause a network storm and hinder transmission of data traffic. Therefore, if the master node does not send the NR-RB message within the preset time period and does not receive the ring protocol messages sent by the at least two slave nodes, the master node actively self-heals and breaks the ring, and switches the state of the RPL port from the forwarding state to the blocking state.

Specifically, in the networking of the ERPS loop provided in fig. 1, the RPL port is the slave port a2 of the master node. The states of the RPL ports include blocking states and forwarding states. In the blocking state, data traffic cannot pass through the RPL port, and in the forwarding state, data traffic can pass through the RPL port.

specifically, under the condition that the ERPS loop normally works, if the master node receives an expired protocol packet that can trigger the RPL port to be opened, the RPL port is switched to the forwarding state. And when the ERPS loop is in a normal working state, the ports of other slave nodes are in a forwarding state. Therefore, when the master node receives an expired protocol message which can trigger the RPL port to be opened, the ports of all the nodes on the ERPS loop are all in a forwarding state, the ERPS loop forms a ring, and a network storm is caused. The expired protocol message may be, for example, an expired SF message, an expired FS message, or an expired MS message. An expired protocol packet here refers to a packet sent out for a state where the ERPS loop is not current. For example, the expired SF message is a message sent out for the last failure state of the ERPS loop.

Optionally, if the master node receives an expired SF message, that is, the SF message received by the master node is an SF message indicating a last failure state of the ERPS loop, the RPL port may be opened by mistake, that is, the state of the slave port a2 is switched from a blocking state to a forwarding state, and since the SF message is an expired message, that is, the expired SF message indicates a last failure state of the ERPS loop and is not a failure indication message at this time on the ERPS loop, the slave node that sends the SF message may not send the SF message periodically, and there is no failure link or failure node on the ERPS loop, and ports of all slave nodes on the ERPS loop are in a forwarding state, and at this time, after the master node opens the RPL port, the entire ERPS loop is looped.

Optionally, if the master node receives an expired FS message, that is, the FS message received by the master node indicates the last forced link switching of the ERPS loop, the RPL port may be opened by mistake, that is, the state of the slave port a2 is switched from the blocking state to the forwarding state, and because the FS message is the expired message, the current forced link switching of the ERPS loop is not really indicated, so that the slave node that sends the FS message does not send the FS message periodically, a failed link or a failed node does not exist on the ERPS loop, ports of all slave nodes on the ERPS loop are in the forwarding state, and at this time, after the master node opens the RPL port, the entire ERPS loop is looped.

Optionally, if the master node receives an expired MS packet, that is, the MS packet received by the master node indicates the last manual switching of the ERPS loop, the RPL port may be erroneously opened, that is, the state of the slave port a2 is switched from the blocking state to the forwarding state, and because the MS packet is an expired packet, the current manual switching of the ERPS loop is not really indicated, so that the slave node that sends the MS packet does not periodically send the MS packet, but there is no faulty link or faulty node on the ERPS loop, ports of all slave nodes on the ERPS loop are in the forwarding state, and at this time, after the master node opens the RPL port, the whole ERPS loop is looped.

It can be known that, under some abnormal conditions, the state machine on the ERPS loop is no longer running, which may cause the ports of all nodes on the loop to be in a forwarding state, and the whole ERPS loop forms a loop, and at this time, the master node does not receive and transmit the protocol packet on the ERPS loop.

Specifically, the preset duration may be N message sending periods, where N is a positive integer greater than or equal to 2. The message sending period may be a sending period of an SF message, or the message period may be a sending period of an NR-RB message, or a sending period of another message. The message sending period may be, for example, 1s, 2s, 5s, 10s, and the like.

Specifically, the preset duration may be three message sending periods, and in order to reserve time to determine whether the ERPS loop forms a loop, an error result of the formation of the ERPS loop is avoided, so that the node on the ERPS loop frequently switches the port state, the workload of the node is increased, and meanwhile, after the formation of the ERPS loop is determined, the node is timely broken by self, so that the influence on network data transmission is reduced, the reliability of the system is increased, and the user experience is improved.

optionally, the master node may start a timer after receiving a message triggering the RPL port to open, where a duration of the timer is set to the preset duration. If the timer is overtime, the main node detects that the main node does not send the NR-RB message and does not receive the ring protocol message sent by the slave node, the ERPS loop is determined to form a ring, and the main node switches the state of the RPL port into a blocking state. If the master node is detected to send the NR-RB message or the ring protocol message sent by the slave node is received before the timer is overtime, the timer is cleared, and timing is restarted until the overtime event of the timer is detected.

Optionally, after the master node receives the message triggering the RPL port to open, switches the state of the RPL port to a forwarding state, and stops sending the NR-RB message to other slave nodes, the master node may start a timer, and the duration of the timer is set to the preset duration. If the timer is overtime, the main node detects that the main node does not send the NR-RB message and does not receive the ring protocol message sent by the slave node, the ERPS loop is determined to form a ring, and the main node switches the state of the RPL port into a blocking state. If the master node is detected to send the NR-RB message or the ring protocol message sent by the slave node is received before the timer is overtime, the timer is cleared, and timing is restarted until the overtime event of the timer is detected. Specifically, the message triggering the RPL port to open may be, but is not limited to, an SF message, an FS message, an MS message, and the like. The RPL port open means that the state of the RPL port is set to a forwarding state.

S602: the master node sends NR-RB messages to at least two slave nodes.

specifically, after the master node actively self-heals and breaks the ring, the whole ERPS loop returns to normal, all nodes on the ERPS loop enter an idle state, and the master node periodically sends NR-RB messages to other slave nodes to maintain the normal operation of the ERPS loop.

By implementing the embodiment of the application, the ring of the ERPS loop can be formed, the ring can be actively self-healed and damaged in time, manual troubleshooting and intervention are not needed, the consumed time is short, the influence on the data transmission of the network is small, the reliability of the system is improved, and the user experience is good.

An embodiment of the present application provides another method for breaking an ERPS loop, as shown in fig. 7, the method for breaking an ERPS loop may include at least the following steps:

s701: the master node receives a target message.

specifically, the target packet includes any one of the following: SF message, FS message, MS message.

The target message is an expired message, that is, an indication message indicating the last state of the ERPS loop. For example, when the target message is an SF message, the expired SF message indicates the last failure state of the ERPS loop; when the target message is an FS message, the expired FS message indicates the last forced switching of the ERPS loop; and when the target message is an MS message, the expired MS message indicates the last manual switching of the ERPS loop. Before the master node receives the target message, the ports of all the slave nodes on the ERPS loop are in a forwarding state.

S702: the master node switches the state of the blocked port to the forwarding state.

Specifically, after receiving the expired target packet, the master node may erroneously determine that the ERPS loop has a fault at this time, so as to release the RPL port that is originally in the blocking state, that is, switch the state of the slave port a2 from the blocking state to the forwarding state, so that data traffic may pass through the slave port of the master node and be transmitted to other nodes on the ERPS loop, thereby completing protection switching of the loop.

S703: the master node stops sending the NR-RB messages to at least two slave nodes.

specifically, after receiving the expired target message, the master node determines that a fault occurs in the loop at the time, and stops sending the NR-RB message to other slave nodes.

S704: and if the master node does not send the NR-RB message within the preset time length and does not receive the ring protocol message sent by the slave node, switching the state of the RPL port to a blocking state.

Specifically, the ring protocol packet sent by the slave node may be, but is not limited to: SF message, NR message, FS message, MS message, etc.

specifically, since the target packet is an expired protocol packet, the slave node that sends the expired target packet does not periodically send the target packet. And after receiving the target message, the master node opens the RPL port and stops sending the NR-RB message. At this time, there is no protocol message in the ERPS loop, and the master node will not send the NR-RB message, nor receive the loop protocol message sent by the slave node. If the master node does not send the NR-RB message within the preset time length and does not receive the ring protocol message sent by the slave node, the ERPS loop is judged to be in a ring, the master node switches the state of the RPL port A2 from a forwarding state to a blocking state, the ERPS loop is actively broken by self-healing, the transmission of data flow is prevented from being influenced by the formation of a network storm, and the influence on the transmission of network data is reduced.

specifically, the preset duration may be N message sending periods, where N is a positive integer greater than or equal to 2. The message sending period may be a sending period of a target message, or the message period may be a sending period of an NR-RB message. The transmission period of the SF message and the transmission period of the NR-RB message may be the same. The transmission period of the two messages may be, for example, 1s, 2s, 5s, 10s, and so on.

Optionally, after the primary node receives the target packet, a timer may be started, and a duration of the timer is set to the preset duration. If the timer is overtime, the main node detects that the main node does not send the NR-RB message and does not receive the ring protocol message sent by the slave node, the ERPS loop is determined to form a ring, and the main node switches the state of the RPL port into a blocking state. If the main node is detected to send the NR-RB message or receive the target message before the timer is overtime, the timer is cleared, and timing is restarted until the overtime event of the timer is detected.

Optionally, after the master node receives the target packet, switches the state of the RPL port to the forwarding state, and stops sending the NR-RB packet to another slave node, the timer may be started, and the duration of the timer is set to the preset duration. If the timer is overtime, the main node detects that the main node does not send the NR-RB message and does not receive the ring protocol message sent by the slave node, the ERPS loop is determined to form a ring, and the main node switches the state of the RPL port into a blocking state. If the main node is detected to send the NR-RB message or receive the target message before the timer is overtime, the timer is cleared, and timing is restarted until the overtime event of the timer is detected.

S705: the master node sends NR-RB messages to at least two slave nodes.

Specifically, after the master node actively self-heals and breaks the ring, the whole ERPS loop returns to normal, and all nodes on the ERPS loop enter an idle state. The master node continues to periodically send NR-RB messages to other slave nodes, and the normal operation of the ERPS loop is maintained.

By implementing the embodiment of the application, under the condition that the main node receives the overdue target message to cause the ERPS loop to form a ring, the ring can be actively and automatically broken in time, manual troubleshooting and intervention are not needed to be carried out, time consumption is short, the influence on data transmission of a network is small, the reliability of a system is improved, and user experience is good.

An embodiment of the present application further provides a master node, which is applied in the ERPS loop shown in fig. 1, as shown in fig. 8, the master node 80 may at least include: switching section 810, transmitting section 820; wherein:

A switching unit 810, configured to switch the state of the RPL port to a blocking state if the master node 80 does not send the NR-RB packet within a preset time period and does not receive the ring protocol packets sent by the at least two slave nodes; the NR-RB message is used to indicate that the status of the ERPS loop is a no-fault status, and the detailed description may refer to the description of S601.

a sending unit 820, configured to send the NR-RB packet to at least two slave nodes, for details, refer to the description of S602.

In a possible embodiment, the ring protocol packet includes any one of the following: fault indication SF message, no fault NR message, forced switching FS message, and manual switching MS message.

In one possible embodiment, the master node 80 may further include a receiving unit 830 and a stop transmitting unit 840 in addition to the switching unit 810 and the transmitting unit 820, as shown in fig. 9; wherein:

The receiving unit 830 is configured to receive the target packet before the switching unit 810 switches the state of the RPL port to the blocking state, and the detailed description may refer to the description of S701.

The switching unit 810 is further configured to switch the state of the RPL port to a forwarding state after the receiving unit 830 receives the target packet, and the detailed description may refer to the description of S702.

The stop transmitting unit 840 is configured to stop transmitting the NR-RB packet to at least two slave nodes after the switching unit 810 switches the state of the RPL port to the forwarding state, and the detailed description may refer to the description of S703.

in a possible embodiment, the target message includes any one of the following: fault indication SF message, forced switching FS message, and manual switching MS message, wherein the target message is an indication message in the last state of the ERPS loop. In a possible embodiment, the preset duration is N message sending periods, the message sending period is the target message sending period, or the message sending period is the NR-RB message sending period, and N is a positive integer greater than or equal to 2.

In another possible embodiment, the preset duration is three message sending periods.

By implementing the embodiment of the application, the ERPS loop can be looped, and then the loop can be actively self-healed and damaged in time, so that manual troubleshooting and intervention damage are not needed, the consumed time is short, the influence on the transmission of network data is small, the reliability of a system is improved, and the user experience is good.

an embodiment of the present application further provides another master node, as shown in fig. 10, the master node 90 may at least include: at least one processor 901, at least one network interface 904, a user interface 903, memory 905, at least one communication bus 902, a display screen 906. Where the communication bus 902 is used to implement connection communication between these components, it should be understood that each component in the master node 90 may also be coupled through other connectors, which may include various interfaces, transmission lines or buses, etc., and in various embodiments of the present application, coupling refers to mutual association through a specific manner, including direct connection or indirect connection through other devices.

Among other things, the processor 901 may include at least one of the following types: a general Central Processing Unit (CPU), a Digital Signal Processor (DSP), a microprocessor, an Application Specific Integrated Circuit (ASIC), a Microcontroller (MCU), a Field Programmable Gate Array (FPGA), or an Integrated Circuit for implementing logical operations. For example, the processor 901 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The multiple processors or units included within processor 901 may be integrated on one chip or located on multiple different chips.

the user interface 903 may include a keypad, physical buttons (push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, a light mouse (a light mouse is a touch-sensitive surface that does not display visual output, or is an extension of a touch-sensitive surface formed by a touch screen), and so forth. The network interface 904 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface).

The Memory 905 may be a nonvolatile Memory, such as an EMMC (Embedded multimedia Card), an UFS (Universal Flash Storage) or a Read-Only Memory (ROM), optionally, the Memory 905 includes a Flash Memory in the embodiment of the present application, or other types of static Storage devices capable of storing static information and instructions, or a nonvolatile Memory (volatile Memory), such as a Random Access Memory (RAM) or other types of dynamic Storage devices capable of storing information and instructions, or an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM), or other optical Disc Storage, optical Disc Storage (including Compact Disc, and optical Disc), or other optical Disc Storage, Optical disks, digital versatile disks, blu-ray disks, etc.), magnetic disk storage media or other magnetic storage devices, or any other computer-readable storage medium that can be used to carry or store program code in the form of instructions or data structures and that can be accessed by a computer, but are not limited to such. Optionally, the memory 905 may also be at least one memory system located remotely from the processor 901. As shown in fig. 10, the memory 905, which is a type of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and program instructions.

The memory 905 may be separate and coupled to the processor 901 through a connector. The memory 905 may also be integrated with the processor 901. The memory 905 can store various computer program instructions for executing the program instructions of the present application, and the processor 901 controls the execution of the computer program instructions, and the executed computer program instructions can also be regarded as a driver of the processor 901. For example, the processor 901 is configured to execute computer program instructions stored in the memory 905 to implement the method in the method embodiment of fig. 6 or fig. 7 in the present application. The computer program instructions may be provided in large numbers to form computer-executable instructions that can be executed by at least one of the processors 901 to drive the relevant processor to perform various types of processing, such as a communication signal processing algorithm, an operating system operation, or an application operation that supports the various types of wireless communication protocols described above.

A display screen 906 for displaying information input by the user. Illustratively, the display screen 906 may include a display panel and a touch panel. The Display panel may be configured by a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), a Light-Emitting Diode (LED) Display device, a Cathode Ray Tube (CRT), or the like. The touch panel, also called a touch screen, a touch sensitive screen, etc., may collect contact or non-contact operations (such as operations performed by a user on or near the touch panel using any suitable object or accessory, such as a finger, a stylus, etc., and may also include somatosensory operations; the operations include single-point control operations, multi-point control operations, etc.) on or near the touch panel, and drive the corresponding connection device according to a preset program.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. For the type of storage medium, reference is made to the description of the memory 905.

Embodiments of the present application also provide a computer-readable storage medium having stored therein instructions, which when executed on a computer or a processor, cause the computer or the processor to perform one or more steps of any of the above methods for disruption of an ERPS loop. The respective constituent modules of the above-described apparatus may be stored in the computer-readable storage medium if they are implemented in the form of software functional units and sold or used as independent products.

based on such understanding, the embodiments of the present application also provide a computer program product containing instructions, where a part of or all or part of the technical solution that substantially contributes to the prior art may be embodied in the form of a software product stored in a storage medium, and the computer program product includes instructions for causing a computer device, a mobile terminal, or a processor therein to execute all or part of the steps of the method described in the embodiments of the present application. The storage medium is described with reference to the memory 905.

The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.

The modules in the device can be merged, divided and deleted according to actual needs.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. a method for breaking Ethernet Ring Protection Switching (ERPS) ring, the ERPS ring includes a main node and at least two slave nodes, the method includes:

If the master node does not send a fault-free-environment-friendly protection link blocking NR-RB message within a preset time length and does not receive ring protocol messages sent by the at least two slave nodes, switching the state of an RPL port of a ring protection link into a blocking state; the NR-RB message is used for indicating that the state of the ERPS loop is a no-fault state;

And the master node sends NR-RB messages to the at least two slave nodes.

2. The method according to claim 1, wherein before the master node switches the state of the RPL port to the blocking state if the NR-RB packet is not sent within a preset time period and the ring protocol packets sent by the at least two slave nodes are not received, the method further comprises:

The master node receives a target message, wherein the target message is used for triggering the master node to switch the state of the RPL port into a forwarding state;

The master node switches the state of the RPL port into a forwarding state;

The master node stops sending the NR-RB messages to the at least two slave nodes.

3. The method of claim 2, wherein the target packet comprises any one of: fault indication SF message, forced switching FS message and manual switching MS message; the target message is an indication message in the last state of the ERPS loop.

4. The method according to claim 2 or 3, wherein the preset duration is N message sending periods, the message sending period is the target message sending period, or the message sending period is the NR-RB message sending period, and N is a positive integer greater than or equal to 2.

5. The method of claim 4, wherein the predetermined duration is three messaging periods.

6. a master node, applied to an Ethernet Ring Protection Switching (ERPS) ring, where the ERPS ring includes the master node and at least two slave nodes, and the master node includes:

the switching unit is used for switching the state of the RPL port of the protection link to a blocking state if the NR-RB message is not sent and the ring protocol messages sent by the at least two slave nodes are not received within a preset time length; the NR-RB message is used for indicating that the state of the ERPS loop is a no-fault state;

7. The master node of claim 6, wherein the master node further comprises:

A receiving unit, configured to receive a target packet before the switching unit switches the state of the RPL port to the blocking state, where the target packet is used to trigger the master node to switch the state of the RPL port to the forwarding state;

The switching unit is further configured to switch the state of the RPL port to a forwarding state after the receiving unit receives the target packet;

8. the master node of claim 7, wherein the target packet comprises any one of: fault indication SF message, forced switching FS message and manual switching MS message; the target message is an indication message in the last state of the ERPS loop.

9. The master node according to claim 7 or 8, wherein the preset duration is N message sending periods, the message sending period is the target message sending period, or the message sending period is the NR-RB message sending period, and N is a positive integer greater than or equal to 2.

10. The master node of claim 9, wherein the predetermined duration is three message transmission cycles.

11. A master node, applied to an Ethernet Ring Protection Switching (ERPS) ring, where the ERPS ring includes the master node and at least two slave nodes, and the master node includes: a processor, a memory, and a transceiver, wherein:

The processor, the memory and the transceiver are interconnected, the memory is used for storing a computer program, the computer program comprises program instructions, the processor is configured for calling the program instructions to execute the ERPS loop damage method according to any one of claims 1-5.

12. a computer-readable storage medium, characterized in that it stores a computer program comprising program instructions which, when executed by a processor, cause the processor to carry out the method of disruption of an ERPS loop according to any one of claims 1-5.