Maintenance endpoint device, method for communication, and computer readable medium

By exchanging CCMs between MEP devices and executing rules, the deadlock problem of CFM protocol when detecting and managing network connectivity failure is solved, ensuring effective utilization and stability of network resources.

CN113965485BActive Publication Date: 2024-11-15HEWLETT PACKARD ENTERPRISE DEV LP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111205169.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2016-12-21
Filing Date
2017-03-30
Publication Date
2024-11-15
Estimated Expiration
2037-03-30

AI Technical Summary

Technical Problem

The existing Ethernet Connectivity Failure Management (CFM) protocols can easily lead to deadlocks when detecting and managing network connectivity failures, especially when recovering after connection failures, which may cause the user network interface to be incorrectly specified as offline. This affects the effective utilization of network resources.

Method used

The maintenance endpoint (MEP) device exchanges continuity check messages (CCMs), including MEP identifiers and interface status information, to avoid deadlocks. The specific method is that when a connection failure is detected, the MEP device provides CCM to the corresponding MEP device to specify that the interface is offline, and when the connection is restored, it prevents unnecessary actions by executing rules to ensure that the interface status is updated accurately, thereby Avoid deadlocks.

Benefits of technology

It effectively avoids deadlocks, ensures the availability and effective utilization of network resources, reduces the need for reconfiguration of network administrators, and improves network stability and resource utilization efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113965485B_ABST
    Figure CN113965485B_ABST
Patent Text Reader

Abstract

Embodiments of the present disclosure relate to maintenance endpoint devices, methods for communication, and computer-readable media. A first maintenance endpoint (MEP) device may identify that a first interface of a first MEP device is associated with a connectivity failure. The first MEP device may provide a first continuity check message (CCM) to a second MEP device, the CCM including a MEP identifier of the first MEP device. The first CCM may cause the second MEP device to specify that a second interface of the second MEP device is offline. The first MEP device may receive a second CCM from the second MEP device, the second CCM including the MEP identifier of the first MEP device and information indicating that the second interface of the second MEP device is offline. The first MEP device may execute rules based on the second CCM including the MEP identifier of the first MEP device to avoid a deadlock condition.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Divisional Application Instructions

[0002] This application is a divisional application of a Chinese patent application with an application date of March 30, 2017, application number 201710203515.5, and invention name “Maintaining endpoint device, method for communication, and computer-readable medium”. Background Art

[0003] The Institute of Electrical Engineers (IEEE) 802.1ag standard, also known as Ethernet Connectivity Fault Management (CFM), defines protocols and practices for the operation, administration, and management (OAM) of paths through local area networks (LANs), metropolitan area networks (MANs), and wide area networks (WANs). The standard defines protocols and procedures for monitoring, detecting, verifying, and isolating connectivity failures in various networks. Summary of the invention

[0004] According to certain possible implementations, a first maintenance endpoint (MEP) device may include one or more processors to identify that a first interface of the first MEP device is associated with a connectivity failure. The one or more processors may provide a first continuity check message (CCM) to a second MEP device based on identifying that the first interface of the first MEP device is associated with a connectivity failure, the first CCM including a MEP identifier of the first MEP device. The first CCM may cause the second MEP device to designate a second interface of the second MEP device as offline. The one or more processors may receive a second CCM from the second MEP device based on the second MEP device designating the second interface of the second MEP device as offline, the second CCM including the MEP identifier of the first MEP device and information indicating that the second interface of the second MEP device is offline. The one or more processors may execute rules to avoid a deadlock condition based on the second CCM including the MEP identifier of the first MEP device.

[0005] According to certain possible embodiments, the one or more processors are further used to: identify a MEP identifier included in a second CCM; determine that the MEP identifier is a MEP identifier of a first MEP device; and the one or more processors, when executing rules to avoid a deadlock situation, are used to: execute rules to avoid a deadlock situation based on the MEP identifier being the MEP identifier of the first MEP device.

[0006] According to certain possible implementations, one or more processors are further used to: identify that a first interface of a first MEP device is not associated with a connectivity failure; based on identifying that the first interface of the first MEP device is not associated with a connectivity failure, provide a third CCM identifying that the first interface is online to a second MEP device, and the second MEP device specifies that a second interface of the second MEP device is online based on the third CCM.

[0007] According to certain possible implementations, the one or more processors are further used to: detect a connectivity failure based on a message associated with a customer edge device; and when the first interface of the first MEP device is associated with the connectivity failure, the one or more processors are used to: identify the first interface of the first MEP device as associated with the connectivity failure based on detecting the connectivity failure.

[0008] According to certain possible implementations, a first CCM causes a second MEP device to call an action profile; and one or more processes, when receiving a second CCM from a second MEP device, are used to: cause the second MEP device to call an action profile based on the first CCM to receive the second CCM, and the second MEP device specifies that a second interface of the second MEP device is offline based on the action profile.

[0009] According to some possible implementations, the rule, when executed, causes the first MEP device to prevent the first interface from being designated as offline based on the second CCM.

[0010] According to some possible implementations, the first CCM enables the second MEP device to store information identifying the first MEP device that enables the second MEP device to designate the second interface of the second MEP device as offline.

[0011] According to certain possible implementations, a non-transitory computer-readable medium may store one or more instructions that, when executed by one or more processors of a first maintenance endpoint (MEP) device, cause the one or more processors to identify that a first interface of the first MEP device is associated with a connectivity failure. The one or more instructions may cause the one or more processors to provide a first continuity check message (CCM) to a second MEP device based on identifying that the first interface of the first MEP device is associated with a connectivity failure, the first CCM including a MEP identifier of the first MEP device. The first CCM may cause the second MEP device to designate a second interface of the second MEP device as offline. The one or more instructions may cause the one or more processors to receive a second CCM from the second MEP device based on the second MEP device designating the second interface of the second MEP device as offline, the second CCM including the MEP identifier of the first MEP device and information indicating that the second interface of the second MEP device is offline. The one or more instructions may cause the one or more processors to execute a rule to avoid a deadlock condition involving the first interface and the second interface based on the second CCM including the MEP identifier of the first MEP device.

[0012] According to certain possible implementations, one or more instructions, when executed by one or more processors, further cause the one or more processors to: determine that the MEP identifier associated with the second CCM is the MEP identifier of the first MEP device; and one or more instructions that cause the one or more processors to execute rules to avoid a deadlock situation cause the one or more processors to: execute rules to avoid a deadlock situation based on the MEP identifier being the MEP identifier of the first MEP device.

[0013] According to certain possible implementations, one or more instructions, when executed by one or more processors, further cause the one or more processors to: based on the first interface of the first MEP device not being associated with a connectivity failure, provide a third CCM including an MEP identifier of the first MEP device to the second MEP device, wherein the third CCM causes the second MEP device to designate a second interface of the second MEP device as online.

[0014] According to certain possible implementations, one or more instructions, when executed by one or more processors, further cause the one or more processors to: detect a connectivity failure based on a set of messages associated with a customer edge device; and one or more instructions that cause the one or more processors to identify that a first interface of a first MEP device is associated with a connectivity failure cause the one or more processors to: identify that the first interface of the first MEP device is associated with a connectivity failure based on detecting the connectivity failure.

[0015] According to some possible implementations, the one or more instructions that cause one or more processors to execute rules to avoid a deadlock situation cause the one or more processors to: execute rules based on the second CCM to prevent actions associated with an action profile of the first MEP device from being performed.

[0016] According to certain possible embodiments, one or more instructions, when executed by one or more processors, further cause the one or more processors to: store information identifying the MEP identifier of the first MEP device in a field of the first CCM; and one or more instructions causing one or more processors to receive a second CCM including the MEP identifier of the first MEP device from a second MEP device cause the one or more processors to: based on storing the information identifying the MEP identifier of the first MEP device in a field of the first CCM, receive a second CCM including a field storing information identifying the MEP identifier of the first MEP device, causing the second MEP device to analyze the first CCM to identify the information identifying the MEP identifier of the first MEP device, and provide a second CCM based on the information identifying the MEP identifier of the first MEP device.

[0017] According to certain possible implementations, one or more instructions, when executed by one or more processors, further cause the one or more processors to: receive a third CCM from a third MEP device, the third CCM including a MEP identifier of the first MEP device and information indicating that a third interface of the third MEP device is designated as offline.

[0018] According to certain possible implementations, a method may include: identifying, by a first maintenance endpoint (MEP) device, that a first interface of a first MEP device is unavailable. The method may include, based on identifying that the first interface of the first MEP device is unavailable, providing, by the first MEP device and to a second MEP device, a first continuity check message (CCM), the first CCM including a MEP identifier of the first MEP device. The first CCM may cause the second MEP device to designate a second interface of the second MEP device as offline. The method may include, based on the second MEP device designating the second interface of the second MEP device as offline, receiving, by the first MEP device and from the second MEP device, a second CCM including the MEP identifier of the first MEP device and information indicating that the second interface of the second MEP device is offline. The method may include, based on the second CCM including the MEP identifier of the first MEP device, executing, by the first MEP device, a rule to avoid a deadlock situation.

[0019] According to some possible implementations, the first interface is associated with a user network interface, and the user network interface is associated with the first MEP device and the customer edge device.

[0020] According to some possible implementations, further comprising: determining that the MEP identifier associated with the second CCM is the MEP identifier of the first MEP device; and wherein executing the rule to avoid the deadlock situation comprises: executing the rule based on the MEP identifier being the MEP identifier of the first MEP device.

[0021] According to some possible implementations, further comprising: identifying an action associated with an action profile of the first MEP device based on the second CCM; and wherein executing the rule to avoid the deadlock situation comprises: executing the rule to avoid the deadlock situation by preventing the action from being executed.

[0022] According to some possible implementations, it further includes: providing a third CCM to the second MEP device that identifies that the first interface is available; and receiving a fourth CCM including the MEP identifier of the second MEP device from the second MEP device based on the third CCM, the fourth CCM including information indicating that the second interface of the second MEP device is online.

[0023] According to some possible implementations, the first MEP device and the second MEP device are associated with the same maintenance association. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figures 1A-1E A diagram that is an overview of example implementations described herein;

[0025] Figure 2 is a diagram of an example environment in which the systems and / or methods described herein may be implemented;

[0026] Figure 3 for Figure 2 diagram of example components of one or more devices;

[0027] Figure 4 is a diagram of an example message structure associated with a continuity check message including an extended interface status; and

[0028] Figure 5A and 5B is a flow chart of an example process for deadlock avoidance using modified Ethernet connectivity fault management signaling. DETAILED DESCRIPTION

[0029] The following detailed description of example embodiments refers to the accompanying drawings.The same reference numbers in different drawings may identify the same or similar elements.

[0030] A network device (e.g., a router, a switch, etc.) may be associated with a particular maintenance domain. For example, a maintenance domain may refer to a network or a portion of a network that may manage faults in connectivity. In addition, a network device may be associated with a particular maintenance association. For example, a maintenance association may refer to a collection of network devices referred to as maintenance endpoints (MEPs), each of which is configured with the same maintenance association identifier and is established to monitor and verify the integrity of service instances for the entire maintenance domain.

[0031] In some cases, continuity check messages (CCMs) may be exchanged between MEPs, the CCMs including information identifying respective states of interfaces associated with respective MEPs. For example, assuming that a first MEP and a second MEP are associated with a MAN, the first MEP establishes connectivity with a first customer edge device (e.g., a router, a switch, etc.), and the second MEP establishes connectivity with a second customer edge device. In this case, network traffic may be exchanged between the first customer edge device and the second customer edge device via the MAN and via the first MEP and the second MEP.

[0032] As an example, assume that a first user network interface associated with a first MEP and a first customer edge device is associated with a connectivity failure (e.g., the fiber optic cable is damaged, destroyed, unavailable, etc.). In this case, the first MEP may provide a CCM to a second MEP that identifies the first user network interface as "out of service" (e.g., unable to provide and / or receive network traffic). In this case, the second MEP may designate a second user network interface associated with the second MEP and a second customer edge device as offline. As used herein, "designated as offline" may refer to a process in which a MEP does not notify an interface as available to receive network traffic, a process in which a MEP prevents network traffic from being provided across a maintenance domain, and the like. In this manner, the second customer edge device may prevent network traffic from being provided to the second MEP (e.g., because the first MEP is associated with a connectivity failure).

[0033] In some cases, a deadlock situation may occur based on CFM signaling. For example, continuing with the example, the second MEP may provide a CCM to the first MEP that identifies the second user network interface as being designated as offline (e.g., based on designating the second user network interface as being offline according to a CCM from the first MEP). The first MEP may receive a CCM from the second MEP and designate the first user network interface associated with the first MEP and the first customer edge device as being offline based on the CCM. As an example, assume that the first user network interface is no longer associated with a connectivity failure (e.g., the fiber optic cable is repaired, becomes available, etc.). In this case, the first MEP may receive a CCM from the second MEP that identifies the second user network interface as being designated as offline, and designate the first user network interface as being offline (e.g., based on incorrectly determining that the second MEP is associated with a connectivity failure). In this way, the first MEP and the second MEP may designate the corresponding user network interface as being offline, thereby causing a deadlock situation, despite the absence of a connectivity failure.

[0034] Embodiments described herein enable a first MEP to provide a first CCM identifying a connectivity failure, which may cause a second MEP to perform an action (e.g., designate an interface as offline). The second MEP may provide a second CCM identifying that the state of the interface of the second MEP is designated as offline and simultaneously identifying an identifier of the first MEP, and execute rules to avoid a deadlock situation (e.g., by preventing execution of an action associated with designating the interface of the first MEP as offline based on the identifier of the first MEP). In this manner, deadlock situations may be avoided, thereby improving network operation based on utilizing available resources.

[0035] Figures 1A-1E FIG. 1 is a diagram of an overview of an example implementation 100 described herein. Figure 1AAs shown, and with reference to reference numeral 105, MEP 1 can detect a connectivity failure associated with customer network interface 1. For example, assume that an optical link between customer edge device 1 and MEP 1 is associated with a failure (e.g., the optical link is damaged, etc.). In this case, MEP 1 can identify that an interface of MEP 1 is associated with a connectivity failure. Based on the connectivity failure, MEP 1 may be unable to provide network traffic to customer edge device 1 and / or receive network traffic from customer edge device 1 (e.g., via customer network interface 1).

[0036] like Figure 1B As shown, and with reference to reference numeral 110, MEP 1 may provide a first CCM including a MEP identifier of MEP 1 based on an interface state of MEP 1 associated with a connectivity failure. As shown, the first CCM may include type, length, value (TLV) information identifying the interface state of MEP 1 (e.g., “disabled”) and may include an extended status TLV including information identifying the MEP identifier of MEP 1 (e.g., “MEP 1”). Further as Figure 1B As shown, and with reference to reference numeral 115, MEP 2 may receive the first CCM and perform an action. For example, MEP 2 may store (e.g., in a list, table, or another type of data structure) information identifying an action profile that maps a set of events and a set of actions. As shown, based on the "MEP 1 interface disabled" event, MEP 2 may perform an action associated with the event (e.g., MEP 2 may specify that user network interface 2 is offline). Based on MEP 2 specifying user network interface 2 as offline, network traffic between customer edge device 2 and customer edge device 1 may be routed via another path (e.g., associated with MEP 3 and MEP 4).

[0037] like Figure 1C As shown, and with reference to reference numeral 120, MEP 2 may provide a second CCM including the MEP identifier of MEP 1 based on performing the action. For example, as shown, the second CCM may include information identifying the MEP 2 interface state (e.g., “disabled”) and information identifying the MEP identifier of MEP 1 (e.g., “MEP 1”). In this manner, MEP 1 may receive the second CCM and identify the MEP identifier of MEP 1.

[0038] Further Figure 1CAs shown, and with reference to reference numeral 125, MEP 1 may execute a rule to avoid a deadlock situation based on an Extended Status TLV of a second CCM that includes a MEP identifier of MEP 1. For example, as shown, MEP 1 may store information that causes MEP 1 to execute a rule that prevents execution of an action associated with an action profile based on a CCM that includes a MEP identifier of MEP 1 (e.g., "MEP 1"). In this manner, MEP 1 may prevent a deadlock situation. For example, if MEP 1 executes an action based on the second CCM (e.g., causing user network interface 1 to be designated as offline), MEP 1 will cause an action based on an underlying connectivity failure associated with MEP 1 to be executed (e.g., incorrectly determining a connectivity failure associated with a user network interface of MEP 2).

[0039] like Figure 1D As shown, and referring to reference numeral 130 , MEP 1 may detect that the connectivity failure has been resolved. For example, MEP 1 may determine that MEP 1 may provide network traffic to and receive network traffic from customer edge device 1 via user network interface 1 .

[0040] like Figure 1E As shown, and with reference to reference numeral 135, MEP 1 may provide a third CCM including a MEP identifier of MEP 1 based on the interface state of MEP 1. As shown, the third CCM may include information identifying the interface state of MEP 1 (e.g., “enabled”) and may include information identifying the MEP identifier of MEP 1 (e.g., “MEP 1”). Further, as Figure 1E As shown, and referring to reference numeral 140, MEP 2 may receive the third CCM and perform an action based on the MEP identifier of MEP 1. For example, MEP 2 may determine that user network interface 1 is online, and may designate user network interface 2 as online (e.g., becoming able to receive and / or provide network traffic).

[0041] Based on the designation of user network interface 2 as online, network traffic from customer edge device 2 to customer edge device 1 can be routed through the path associated with MEP 1 and MEP 2. In this way, deadlock conditions are avoided. For example, a deadlock condition may be associated with a scenario in which MEP 1 and MEP 2 designate the corresponding user network interface as offline despite the absence of an underlying connectivity failure. The embodiments described herein enable MEPs to exchange CCMs without causing deadlock. In this way, the embodiments described herein improve network operation by utilizing available network resources.

[0042] As mentioned above, Figures 1A-1E It is provided as an example only. Other examples are possible and may differ from Figures 1A-1E The content described.

[0043] Figure 2 FIG. 1 is a diagram of an example environment in which the systems and / or methods described herein may be implemented. Figure 2 As shown, environment 200 may include one or more customer edge devices 210-1 to 210-M (M≥1) (hereinafter, collectively referred to as "customer edge device 210" and individually referred to as "customer edge device 210"), one or more MEPs 220-1 to 220-N (N≥1) (hereinafter, collectively referred to as "MEP 220" and individually referred to as "MEP 220"), and network 230. The devices of environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0044] Customer edge device 210 includes one or more network devices (e.g., one or more traffic delivery devices) capable of processing and delivering network traffic. For example, customer edge device 210 may include a router, a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a server executing a virtual machine, etc.), a security device, an intrusion detection device, a load balancer, a line card (e.g., in a chassis-based system), or a similar type of device. In some embodiments, customer edge device 210 may be located at the edge of a customer's premises and may communicate with MEP 220 to gain access to a service provider's core network.

[0045] MEP 220 includes one or more network devices (e.g., one or more traffic delivery devices) capable of processing and delivering network traffic. For example, MEP 220 may include a router, a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a server executing a virtual machine, etc.), a security device, an intrusion detection device, a load balancer, a line card (e.g., in a chassis-based system), or a similar type of device. In some embodiments, MEP 220 and customer edge device 210 may be associated with a user network interface (e.g., a demarcation point between the responsibilities of a service provider and the responsibilities of a user). For example, a user network interface may represent an interface between MEP 220 and customer edge device 210.

[0046] The network 230 includes one or more wired and / or wireless networks. For example, the network 230 may include a cellular network (e.g., a fifth generation (5G) network, a long term evolution (LTE) network, a code multiple access (CDMA) network, a third generation (3G) network, another type of advanced generation network), a public land mobile network (PLMN), a local area network (LAN), a WAN, a MAN, a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-based network, a cloud computing network, etc., and / or a combination of these or other types of networks.

[0047] Figure 2 The number and arrangement of devices and networks shown are provided as examples. In practice, there may be more than Figure 2 Additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, and differently arranged devices and / or networks are shown. Figure 2 Two or more of the devices shown may also be implemented in a single device, or Figure 2 The single device shown may be implemented as multiple distributed devices. Furthermore, alternatively, a collection of devices (eg, one or more devices) of environment 200 may perform one or more functions described as being performed by another collection of devices of environment 200.

[0048] Figure 3 300. Device 300 may correspond to customer edge device 210 and / or MEP 220. In some embodiments, customer edge device 210 and / or MEP 220 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown, the device 300 may include one or more input components 305-1 to 305-B (B≥1) (hereinafter, collectively referred to as input components 305 and individually referred to as input components 305), a switching component 310, one or more output components 315-1 to 315-C (C≥1) (hereinafter, collectively referred to as output components 315 and individually referred to as output components 315), and a controller 320.

[0049] The input component 305 can be an attachment point for a physical link and can be an entry point for incoming traffic (such as a packet). The input component 305 can process incoming traffic, such as by performing data link layer encapsulation and decapsulation. In some embodiments, the input component 305 can send / receive packets. In some embodiments, the input component 305 may include an input line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), a packet forwarding component, a line card controller component, an input port, a processor, a memory, and / or an input queue. In some embodiments, the device 300 may include one or more input components 305.

[0050] The switch component 310 can interconnect the input component 305 with the output component 315. In some embodiments, the switch component 310 can be implemented via one or more crossbar switches, via a bus, and / or using a shared memory. The shared memory can be used as a temporary buffer to store packets from the input component 305 before they are finally scheduled for transmission to the output component 315. In some embodiments, the switch component 310 can enable the input component 305, the output component 315, and / or the controller 320 to communicate.

[0051] Output component 315 can store packets, and schedule packets for transmission on output physical link. Output component 315 can support data link layer encapsulation or decapsulation, and / or various high-level protocols. In some embodiments, output component 315 can send packets and / or receive packets. In some embodiments, output component 315 may include an output line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and / or output queues. In some embodiments, device 300 may include one or more output components 315. In some embodiments, input component 305 and output component 315 can be implemented by a collection of the same components (e.g., an input / output component can be a combination of input component 305 and output component 315).

[0052] The controller 320 includes a processor in the form of, for example, a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or other types of processing components. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some embodiments, the controller 320 may include one or more processors that can be programmed to perform functions.

[0053] In some embodiments, the controller 320 may include random access memory (RAM), read-only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic storage, optical storage, etc.) to store information and / or instructions for use by the controller 320.

[0054] In some embodiments, the controller 320 can communicate with other devices, networks, and / or systems connected to the device 300 to exchange information about the network topology. The controller 320 can create a routing table based on the network topology information, create a forwarding table based on the routing table, and forward the forwarding table to the input component 305 and / or the output component 315. The input component 305 and / or the output component 315 can use the forwarding table to perform a route lookup for an inbound / outbound packet.

[0055] The controller 320 may perform one or more processes described herein. The controller 320 may perform these processes in response to executing software instructions stored by a non-transitory computer readable medium. A computer readable medium is defined herein as a non-transitory memory device. A memory device includes a memory space within a single physical storage device or a memory space across multiple physical storage devices.

[0056] The software instructions may be read from another computer-readable medium or from another device into a memory and / or storage component associated with the controller 320 via a communication interface. The software instructions stored in the memory and / or storage component associated with the controller 320, when executed, may cause the controller 320 to perform one or more processes described herein. In addition, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any specific combination of hardware circuitry and software.

[0057] Figure 3 The number and arrangement of devices shown are provided as examples. In practice, there may be more than Figure 3 Additional components, fewer components, different components, differently arranged components than shown. In addition, or alternatively, a set of components of device 300 (e.g., one or more components) can perform one or more functions described as being performed by another set of components of device 300.

[0058] Figure 4 FIG. 2 is a diagram of an example message structure associated with a continuity check message including an extended interface status. For example, the first MEP 220 may provide the second MEP 220 with a message including: Figure 4The CCM of message structure 400 is shown to enable connectivity fault management while preventing deadlock.

[0059] As used herein, a message may refer to a communication structure for conveying a message, such as a protocol data unit (PDU), a network packet, a datagram, a segment, a block, a cell, a frame, a subframe, a timeslot, a symbol, a portion of any of the above communication structures, and / or another type of formatted or unformatted data unit capable of being transmitted via a network.

[0060] like Figure 4 As shown, a CCM including an extended interface status type, length, value (TLV) may include a "type" field, a "length" field, an "interface status" field, and a "MEP identifier" field. In some embodiments, the "type" field may include information identifying the type of the CCM (e.g., the CCM includes extended interface status information). In some embodiments, the "length" field may include information identifying the length of the CCM (e.g., the number of fields associated with the CCM, the number of octets, the number of bytes, etc.).

[0061] In some embodiments, the "Interface State" field may include information indicating the state of an interface of MEP 220. For example, the "Interface State" field may include information identifying a state, such as "enabled," "disabled," "testing," "unknown," "dormant," "absent," "lower layer disabled," etc. For example, "enabled" may indicate that the interface is ready to pass packets, "disabled" may indicate that the interface cannot pass packets, "testing" may indicate that the interface is in a test mode, "unknown" may indicate that the state of the interface cannot be determined, "dormant" may indicate that the interface is not in a state of passing packets but is in a suspended state (e.g., waiting for an external event), "absent" may indicate that a component of the interface is missing, and "lower layer disabled" may indicate that the interface is disabled due to the state of a lower layer interface.

[0062] Although not shown in the figure, in some embodiments, the CCM may include a “Port Status TLV” including information identifying the ability of a port of MEP 220 to pass data (eg, “Blocked,” “Enabled,” etc.).

[0063] In some embodiments, the “MEP Identifier” field may include information identifying MEP 220 (eg, a device identifier, an interface identifier, a port identifier, a network address, etc.).

[0064] although Figure 4 An example of a message structure associated with a continuity check message including an extended interface status is shown. In some embodiments, the message structure associated with a continuity check message including an extended interface status may include a Figure 4Additional fields, fewer fields, different fields, or differently arranged fields as depicted in FIG.

[0065] Figure 5A and 5B FIG. 5 is a flow chart of an example process 500 for avoiding deadlock using modified Ethernet connectivity fault management signaling. In some embodiments, Figure 5A and / or Figure 5B One or more processing blocks in may be performed by MEP 220-1 and / or MEP 220-M (eg, hereinafter referred to as MEP 220-2). In some embodiments, Figure 5A and / or Figure 5B One or more processing blocks in may be performed by another device or a group of devices (such as user edge device 210) that is separate from MEP 220-1 and / or MEP 220-2 or includes MEP 220-1 and / or MEP 220-2.

[0066] like Figure 5A As shown, process 500 may include providing a first continuity check message (CCM) including a MEP identifier of a first maintenance endpoint (MEP) based on an interface state of the first MEP associated with the connectivity failure (block 510). For example, MEP 220-1 may provide a first CCM including the MEP identifier of MEP 220-1 to MEP 220-2 based on an interface state of MEP 220-1 associated with the connectivity failure.

[0067] In some embodiments, MEP 220-1 and MEP 220-2 may be associated with a particular maintenance domain. For example, a maintenance domain may refer to a network or a portion of a network that can manage failures in connectivity. Additionally or alternatively, MEP 220-1 and MEP 220-2 may be associated with a particular maintenance association. For example, a maintenance association may refer to a collection of MEPs, each of which is configured with the same maintenance association identifier and is established to monitor and verify the integrity of service instances of the entire maintenance domain.

[0068] In some embodiments, MEP 220-1 and MEP 220-2 may exchange CCMs. For example, CCMs may include multicast PDUs that are periodically transmitted by a particular MEP 220 to ensure continuity on a maintenance association to which MEP 220 belongs (e.g., connectivity between MEPs 220, connectivity between customer edge devices 210 and MEPs, etc.). In some embodiments, and as described above in conjunction with Figure 4 As described, a CCM may include a specific TLV format and / or include multiple TLV values. For example, a CCM may include a type field, a length field, a status field, and a MEP identifier field.

[0069] In some embodiments, the MEP 220-1 may provide a first CCM including a MEP identifier associated with the MEP 220-1 based on an interface state of the MEP 220-1 associated with the connectivity failure. In some embodiments, the connectivity failure may refer to the MEP 220-1 being unable to provide network traffic to the customer edge device 210 and / or receive network traffic from the customer edge device 210. For example, the MEP 220-1 may provide the first CCM based on a failure of a user network interface (e.g., an optical link, etc.) between the MEP 220-1 and the customer edge device 210-1, a failure of an interface associated with the MEP 220-1, and the like. Additionally or alternatively, the connectivity failure may refer to the MEP 220-1 being unable to receive a threshold number of consecutive CMMs from another MEP 220 in the maintenance association, being unable to receive a specific message (e.g., a heartbeat message, etc.) from the customer edge device 210-1, and the like.

[0070] In some embodiments, the first CCM may include Figure 4 , and may include information associated with a "MEP Identifier" field identifying MEP 220-1. In this manner, MEP 220-1 may notify the entire maintenance association that a user network interface associated with MEP 220-1 and customer edge device 210-1 is designated as offline (e.g., deactivated).

[0071] like Figure 5A As further shown, process 500 may include receiving a first CCM including a MEP identifier of a first MEP, and performing an action based on the first CCM (block 520). For example, MEP 220-2 may receive a first CCM including a MEP identifier of MEP 220-1 from MEP 220-1, and perform an action based on the first CCM.

[0072] In some embodiments, MEP 220-2 may be configured with an action profile. For example, an action profile may refer to information that maps a set of events and a set of actions. In some embodiments, MEP 220-2 may perform an action based on a value associated with a CCM received from MEP 220-1. As an example, if MEP 220-2 receives a CCM that includes a status of "disabled" associated with the "interface status" field of the CCM, MEP 220-2 may specify that an interface associated with MEP 220-2 is offline (e.g., to prevent network traffic from being provided and / or received via the interface). In this manner, MEP 220-2 may prevent network traffic from being provided within the entire maintenance domain, thereby reducing network congestion, packet loss, excessive delays, etc. (e.g., by preventing network traffic from being provided to MEP 220-1 associated with a connectivity failure).

[0073] In some embodiments, MEP 220-2 may receive the first CCM, analyze the first CCM to identify values ​​associated with particular fields of the first CCM, and detect an event based on one or more values ​​(e.g., a user network interface associated with MEP 220-1 and customer edge device 210-1 is associated with a connectivity failure). Additionally, or alternatively, MEP 220-2 may perform an action based on the event (e.g., a user network interface associated with MEP 220-2 may be designated as offline).

[0074] In some embodiments, MEP 220-2 may store information identifying that MEP 220-2 performed an action based on a CCM associated with MEP 220-1 (eg, MEP 220-2 caused an action to be performed based on a connectivity failure associated with MEP 220-1).

[0075] like Figure 5A As further shown, process 500 may include providing a second CCM including the MEP identifier of the first MEP based on performing the action (block 530). For example, MEP 220-2 may provide the second CCM including the MEP identifier of MEP 220-1 to MEP 220-1 based on performing the action. In some embodiments, MEP 220-2 may provide the second CCM based on specifying that a user network interface associated with MEP 220-2 and customer edge device 210-2 is offline. In this manner, MEP 220-2 may notify MEP 220-1 and / or other MEPs 220 maintaining the association that the user network interface associated with MEP 220-2 is offline.

[0076] In some embodiments, the second CCM may include a MEP identifier associated with MEP 220-1. For example, the second CCM may include a combination of Figure 4 2 and includes information associated with a “MEP Identifier” that identifies MEP 220-1. In some embodiments, MEP 220-2 may include a MEP identifier associated with MEP 220-1 in a “MEP Identifier” field of a second CCM based on MEP 220-1’s CCM causing MEP 220-2 to invoke the action profile.

[0077] like Figure 5A As further shown in FIG. 5 , process 500 may include receiving a second CCM including a MEP identifier of the first MEP (block 540), and executing rules to avoid a deadlock condition based on the second CCM including the MEP identifier of the first MEP (block 550). For example, MEP 220-1 may receive a second CCM including a MEP identifier of MEP 220-1 from MEP 220-2, and execute rules to avoid a deadlock condition based on the second CCM including the MEP identifier of MEP 220-1.

[0078] In some embodiments, MEP 220-1 may receive the second CCM, analyze the second CCM, and identify information associated with the "MEP identifier" field. Additionally, or alternatively, MEP 220-1 may compare information associated with the "MEP identifier" field and information identifying a MEP identifier associated with MEP 220-1 (e.g., may compare MEP identifiers). In some embodiments, if the MEP identifiers are the same, MEP 220-1 may execute a rule to avoid a deadlock condition. For example, MEP 220-1 may prevent execution of an action associated with an action profile of MEP 220-1. For example, MEP 220-1 may execute a rule to prevent an action from being executed based on a CCM that includes information identifying a MEP identifier associated with MEP 220-1, thereby preventing a possible deadlock condition from occurring.

[0079] For example, assume that a connectivity failure associated with MEP 220-1 and customer edge device 210 is corrected. In this case, if MEP 220-1 performs an action based on a CCM received from MEP 220-2, a deadlock situation may occur. For example, although the connectivity failure with MEP 220-1 is corrected, MEP 220-1 may receive a CCM from MEP 220-2 that identifies that a user network interface associated with MEP 220-2 is offline. In addition, MEP 220-1 may perform an action (e.g., causing the user network interface associated with MEP 220-1 to become offline) based on the CCM that identifies that the user network interface associated with MEP 220-2 is offline (e.g., thereby causing a deadlock).

[0080] In other words, MEP 220-1 may provide a CCM identifying that a user network interface of MEP 220-1 is offline. MEP 220-2 may specify that the user network interface of MEP 220-2 is offline based on the CCM and provide a CCM identifying that the user network interface of MEP 220-2 is specified as offline (e.g., caused by the user network interface of MEP 220-2 being offline). MEP 220-1 may receive the CCM and incorrectly determine that the user network interface of MEP 220-2 is associated with a connectivity failure (e.g., which is not the case). Thereafter, MEP 220-1 and MEP 220-2 may continue to exchange CCMs and both incorrectly determine that the other MEP 220 is associated with a connectivity failure (e.g., which is not the case).

[0081] In this way, the embodiments described herein reduce the number of deadlock situations caused by CFM signaling and / or action profiles, thereby improving utilization of available network resources.

[0082] like Figure 5B As shown, process 500 may include providing a third CCM including a MEP identifier of the first MEP based on the interface state of the first MEP (block 560). For example, MEP 220-1 may provide a third CCM including a MEP identifier of MEP 220-1 to MEP 220-2 based on the interface state of MEP 220-1. In some embodiments, the interface state of MEP 220-1 may not be associated with a connectivity failure. For example, assume that the connectivity failure is corrected. In this case, MEP 220-1 may provide a third CCM including information associated with an "Interface State" field that identifies that a user network interface associated with customer edge device 210-1 and MEP 220-1 is online.

[0083] like Figure 5BAs further shown in FIG. 5 , process 500 may include receiving a third CCM and performing an action based on the MEP identifier of the first MEP (block 570). For example, MEP 220-2 may receive a third CCM from MEP 220-1 and perform an action based on the MEP identifier of MEP 220-1. In some embodiments, MEP 220-2 may identify information associated with a “MEP identifier” field of the third CCM, determine that the information identifies MEP 220-1, and perform an action based on the information identifying MEP 220-1. For example, MEP 220-2 may designate a user network interface associated with MEP 220-2 and customer edge device 210-2 as online. For example, MEP 220-2 can determine based on the third CCM that MEP 220-1 (e.g., the first CCM associated with MEP 220-1) caused MEP 220-2 to perform the action (e.g., associated with block 520), and determine that MEP 220-1 is not associated with the connectivity failure. In this manner, MEP 220-2 can again receive network traffic from customer edge device 210-2 and provide network traffic to customer edge device 210-1 via MEP 220-1 (or vice versa).

[0084] In this manner, the embodiments described herein reduce the number of deadlock situations caused by CFM signaling and / or action profiles, thereby improving network resource utilization. For example, the embodiments described herein enable MEP 220 to exchange CCMs and perform actions based on the CCMs, thereby diverting traffic from the maintenance association in the event of a connectivity failure, and thereby conserving processor and / or memory resources of the customer edge device 210, the MEP 220, and / or network resources. In addition, the embodiments described herein prevent deadlock situations associated with CCM exchanges, thereby reducing the amount of time associated with the maintenance association being offline, reducing the need for a network administrator to reconfigure the MEP 220, enabling the MEP 220 to carry network traffic, etc. In this manner, the embodiments described herein improve network resource utilization by enabling a MEP 220 that is capable of providing network traffic to carry network traffic.

[0085] although Figure 5A and 5B Example blocks of process 500 are shown. In some embodiments, process 500 may include Figure 5A and 5B Additional blocks, fewer blocks, different blocks, or differently arranged blocks as depicted in. Additionally, or alternatively, two or more blocks in process 500 may be executed in parallel.

[0086] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above disclosure and may be acquired from practice of the embodiments.

[0087] As used herein, the term component is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software.

[0088] Certain embodiments described herein are related to thresholds. As used herein, satisfying a threshold may refer to a value being greater than a threshold, more than a threshold, above a threshold, greater than or equal to a threshold, less than a threshold, less than a threshold, below a threshold, less than or equal to a threshold, equal to a threshold, etc.

[0089] It is apparent that the systems and / or methods described herein may be implemented by various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not a limitation of the embodiments. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it should be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0090] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly refer to only one claim, the disclosure of possible implementations includes the combination of each dependent claim with every other claim in the claim group.

[0091] Elements, actions or instructions used herein should not be interpreted as critical or necessary unless clearly described as such. In addition, as used herein, the articles "one" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the term "set" is intended to include one or more projects (e.g., related projects, unrelated projects, combinations of related and unrelated projects, etc.), and can be used interchangeably with "one or more". When only intended to a project, the term "one" or similar language is used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless clearly stated otherwise.

Claims

1. A first maintenance endpoint (MEP) device, comprising: Memory; and One or more processors for: receiving, from a second MEP device, a first continuity check message (CCM) based on a first interface state of the second MEP device associated with a connectivity failure, The first CCM includes a MEP identifier of the second MEP device; performing an action based on an action profile and based on receiving the first CCM; providing a second CCM to the second MEP device, the second CCM including the MEP identifier of the second MEP device and information indicating that the action is performed, The second CCM causes the second MEP device to execute rules to avoid a deadlock condition; and specifying an interface state of the first MEP device based on receiving a third CCM, the third CCM identifying a second interface state of the second MEP device, The first interface status of the second MEP device is different from the second interface status of the second MEP device.

2. The first MEP device of claim 1, wherein the one or more processors are further configured to: Upon receiving the first CCM, analyzing the first CCM to identify a value associated with a particular field of the first CCM; and Based on the value, detecting that the first interface state of the second MEP device is associated with the connectivity failure.

3. The first MEP device of claim 1 , wherein when performing the actions, the one or more processors are configured to: Based on determining that the second MEP device is associated with a connectivity failure, network traffic is prevented from being received via an interface of the first MEP device.

4. The first MEP device of claim 1 , wherein the one or more processors are further configured to: Information indicating that the first MEP device has performed the action is stored.

5. The first MEP device of claim 1 , wherein the one or more processors are further configured to: Based on the action profile, the interface status of the first MEP device is designated as offline.

6. The first MEP device of claim 5, wherein the one or more processors are further configured to: Based on specifying that the interface status of the first MEP device is offline, the second CCM is notified to one or more other MEP devices.

7. The first MEP device of claim 1 , wherein when specifying the first interface state of the first MEP device, the one or more processors are configured to: The first interface state of the first MEP device is designated as being capable of receiving and providing network traffic.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising: One or more instructions that, when executed by one or more processors of a first maintenance endpoint (MEP) device, cause the one or more processors to: receiving, from a second MEP device, a first continuity check message (CCM) based on a first interface state of the second MEP device associated with a connectivity failure, The first CCM includes a MEP identifier of the second MEP device; performing an action based on the action profile and receiving the first CCM; providing a second CCM to the second MEP device, the second CCM including the MEP identifier of the second MEP device and information indicating that the action is performed, The second CCM causes the second MEP device to execute rules to avoid a deadlock condition; and specifying an interface state of the first MEP device based on receiving a third CCM, the third CCM identifying a second interface state of the second MEP device, The first interface status of the second MEP device is different from the second interface status of the second MEP device.

9. The non-transitory computer readable medium of claim 8, wherein when executed by the one or more processors, the one or more instructions further cause the one or more processors to: Upon receiving the first CCM, analyzing the first CCM to identify a value associated with a particular field of the first CCM; and Based on the value, detecting that the first interface state of the second MEP device is associated with the connectivity failure.

10. The non-transitory computer readable medium of claim 8, wherein the one or more instructions to perform the actions cause the one or more processors to: Based on determining that the second MEP device is associated with a connectivity failure, network traffic is prevented from being received via an interface of the first MEP device.

11. The non-transitory computer readable medium of claim 8, wherein when executed by the one or more processors, the one or more instructions further cause the one or more processors to: Information indicating that the first MEP device has performed the action is stored.

12. The non-transitory computer readable medium of claim 8, wherein when executed by the one or more processors, the one or more instructions further cause the one or more processors to: Based on the action profile, the interface status of the first MEP device is designated as offline.

13. The non-transitory computer readable medium of claim 12, wherein when executed by the one or more processors, the one or more instructions further cause the one or more processors to: Based on specifying that the interface status of the first MEP device is offline, the second CCM is notified to one or more other MEP devices.

14. The non-transitory computer readable medium of claim 8, wherein the one or more instructions to specify the interface state of the first MEP device further cause the one or more processors to: The first interface state of the first MEP device is designated as being capable of receiving and providing network traffic.

15. A method for maintenance, comprising: receiving, by a first maintenance endpoint (MEP) device and from a second MEP device, a first continuity check message (CCM) based on a first interface state of the second MEP device associated with a connectivity failure, The first CCM includes a MEP identifier of the second MEP device; Based on the action profile and receiving the first CCM, the first MEP device performs an action; providing, by the first MEP device and to the second MEP device, a second CCM, the second CCM including the MEP identifier of the second MEP device and information indicating that the action is performed, The second CCM causes the second MEP device to execute rules to avoid a deadlock condition; and The first MEP device specifies the interface state of the first MEP device based on receiving a third CCM, the third CCM identifying the second interface state of the second MEP device, The first interface status of the second MEP device is different from the second interface status of the second MEP device.

16. The method according to claim 15, further comprising: upon receiving the first CCM, analyzing the first CCM to identify a value associated with a particular field of the first CCM; as well as Based on the value, detecting that the first interface state of the second MEP device is associated with the connectivity failure.

17. The method of claim 15, wherein performing the action comprises: Based on determining that the second MEP device is associated with a connectivity failure, network traffic is prevented from being received via an interface of the first MEP device.

18. The method according to claim 15, comprising: Information indicating that the first MEP device has performed the action is stored.

19. The method according to claim 15, comprising: Based on the action profile, specifying the interface status of the first MEP device as offline; as well as Based on specifying that the interface status of the first MEP device is offline, the second CCM is notified to one or more other MEP devices.

20. The method of claim 15, wherein specifying the interface status of the first MEP device comprises: The first interface state of the first MEP device is designated as being capable of receiving and providing network traffic.