WO2017020287A1 - Link detection method and device - Google Patents

Abstract

Provided in an embodiment of the invention are a link detection method and device. The method comprises: receiving, by a relay device, multiple first continuity check message (CCM) packets transmitted by multiple maintenance end points (MEPs), wherein the first CCM packet transmitted by each MEP carries an ID of the MEP; performing, by the relay device, combination processing on the multiple first CCM packets to generate a second CCM packet, wherein a source media access control (MAC) address of the second CCM packet is an MAC address of the relay device, and the second CCM packet carries the IDs of the multiple MEPs; and transmitting, by the relay device, the second CCM packet to an RMEP so that the RMEP determines, according to the second CCM packet, link continuity between itself and the multiple MEPs. The link detection method and device provided in the embodiment of the invention can reduce the number of CCM packets accumulated on a link, thereby solving a problem in which the CCM packets occupy too much bandwidth on the link.

Description

Link detection method and device Technical field

The present invention relates to the field of communications and, more particularly, to a method and apparatus for link detection.

Background technique

In traditional Ethernet, operators generally use the Simple Network Management Protocol (SNMP) to implement Ethernet management. However, this management method can manage a limited number of network elements, requires a large amount of Internet Protocol (IP), and is also costly in the process of deploying, managing, and maintaining Ethernet.

In response to these problems, the prior art utilizes Operations Administration and Maintenance (OAM) to implement management and maintenance of Ethernet. The scheme of link detection in the prior art will be briefly introduced below with reference to FIG. As shown in Figure 1, the connectivity fault management (CFM) function is enabled on device A, device B, and device D, and the maintenance end point (MEP) is set on the Ethernet ports of these devices. . One or more MEPs can be set on each device. The MEP on each device can be called a local MEP. The MEP on other devices connected to it is a remote maintenance end point relative to the device. , RMEP), for convenience of description, the MEP on device A and device B is referred to as MEP, and the MEP on device D is referred to as RMEP. When performing link detection, multiple MEPs on device A and device B send multiple connectivity check messages (CCM) messages to the RMEP, and device C acts as a relay device, and it will receive multiple CCMs. The packets are aggregated and sent to RMEP. The RMEP can detect the connectivity of the link according to the condition of receiving the CCM packet. If the RMEP does not receive the CCM packet within a certain period of time, the RMEP considers that the corresponding link is interrupted. If the RMEP can receive the CCM packet, The corresponding link is considered to be connected, and the RMEP can also determine the link connectivity between the RMEP and the MEP according to the status information carried in the received CCM message. This achieves link detection between MEP and RMEP.

The problem of the prior art is that the device C aggregates the received multiple CCM packets sent by the multiple MEPs and transmits them to the RMEP, so that the RMEP receives too many CCM packets and occupies too many aggregation links. (eg, the link between device C and device D in Figure 1) bandwidth.

Summary of the invention

The embodiment of the invention provides a method and a device for detecting link detection, so as to reduce the number of CCM packets on the aggregation link, thereby reducing the problem that the CCM packet occupies too much bandwidth of the aggregation link.

The first aspect provides a method for link detection, including: receiving, by a relay device, a plurality of first connectivity check message CCM messages sent by a plurality of maintenance end node MEPs, where the first CCM report sent by each MEP Transmitting the ID of each MEP; the relay device performs a combining process on the multiple first CCM packets to generate a second CCM packet, where the source MAC address of the second CCM packet is The MAC address of the transit device, and the second CCM message carries the IDs of the multiple MEPs; the transit device sends the second CCM message to the RMEP, so that the RMEP is according to the The second CCM message determines link connectivity between the RMEP and the plurality of MEPs.

With reference to the first aspect, in an implementation manner of the first aspect, the second CCM packet further carries status information of each of the multiple MEPs, where the status information is used to indicate each Link connection status obtained by the MEP.

In conjunction with the first aspect, or any one of the foregoing implementation manners, in another implementation manner of the first aspect, the ID and status information of each MEP is included in a vendor specific type length of the second CCM packet. Value in the TLV field.

With reference to the first aspect, or any one of the foregoing implementation manners, in another implementation manner of the foregoing aspect, the source MAC address of the first CCM packet sent by the at least one MEP of the multiple MEPs is The private MAC address of at least one MEP.

With the first aspect or the foregoing implementation manner, in another implementation manner of the first aspect, the transit device receives the first unicast packet sent by the RMEP, where the first unicast packet carries An ID of any one of the plurality of MEPs; the relay device according to the ID of the one MEP carried in the first unicast packet, and an ID of the plurality of MEPs acquired in advance and the plurality of MEPs The mapping of the MAC address, the second unicast packet corresponding to any one of the plurality of MEPs, wherein the source MAC address of the second unicast packet corresponding to the any MEP is the MAC of the RMEP The address, the destination MAC address is the MAC address of any one of the MEPs, and the transit device sends the second unicast packet to any one of the plurality of MEPs.

A second aspect provides a method for detecting a link, where the remote maintenance end node RMEP receives a first CCM packet sent by the relay device, where the first CCM packet carries multiple Maintaining an ID of the end node MEP, where the source media access control MAC address of the first CCM message is a MAC address of the transit device; and the RMEP determines the RMEP and the plurality according to the IDs of the multiple MEPs Link connectivity between MEPs.

With reference to the second aspect, in an implementation manner of the second aspect, the first CCM packet further carries state information of each of the multiple MEPs, where the state information is used to indicate the foregoing Link connection status obtained by MEP.

With reference to the second aspect, or any one of the foregoing implementation manners, in another implementation manner of the second aspect, the RMEP determines, between the RMEP and the plurality of MEPs, according to an ID of the multiple MEPs The link connectivity includes: determining, by the RMEP, whether the multiple MEPs and the RMEP are in a connected state according to the IDs of the multiple MEPs; when the multiple MEPs are in a connected state with the RMEPs, The RMEP determines link connectivity between the RMEP and the plurality of MEPs according to status information of the multiple MEPs.

With reference to the second aspect, or any one of the foregoing implementation manners, in another implementation manner of the second aspect, the ID and status information of the multiple MEPs are included in a vendor specific type length of the first CCM message. Value in the TLV field.

In conjunction with the second aspect, or any one of the foregoing implementation manners, in another implementation manner of the second aspect, the method further includes: sending, by the transit device, a first unicast packet, the first unicast packet The ID of the MEP of any one of the plurality of MEPs is received, and the third unicast message sent by any one of the plurality of MEPs is received, so that the RMEP determines the RMEP and any of the plurality of MEPs. The link connectivity between the MEPs, wherein the transit device is based on the ID of the any one of the MEPs carried in the first unicast packet, and the IDs of the plurality of MEPs acquired in advance and the plurality of MEPs Generating a second unicast packet corresponding to any MEP of the plurality of MEPs, and transmitting the second unicast packet to the MEP of the corresponding MEP corresponding ID, the third The unicast packet is a packet in which the any MEP replies to the second unicast packet.

A third aspect provides an apparatus for detecting a link, comprising: a receiving module, configured to receive a plurality of first connectivity check message CCM messages sent by a plurality of maintenance end node MEPs, where each MEP sends the first a CCM message carrying the ID of each of the MEPs; an execution module, configured to perform a combination process on the plurality of first CCM messages, to generate a second CCM message, where the source of the second CCM message The MAC address is the MAC address of the transit device, and the second CCM message carries the IDs of the multiple MEPs; the sending module is configured to send the second to the RMEP a CCM message, so that the RMEP determines link connectivity between the RMEP and the plurality of MEPs.

With reference to the third aspect, in an implementation manner of the third aspect, the second CCM message further carries status information of each of the multiple MEPs, where the status information is used to indicate each Link connection status obtained by the MEP.

In conjunction with the third aspect, or any one of the foregoing implementation manners, in another implementation manner of the third aspect, the ID and status information of each MEP is included in a vendor-specific type length of the second CCM packet. Value in the TLV field.

With the third aspect or the foregoing implementation manner, in another implementation manner of the third aspect, the source MAC address of the first CCM packet sent by the at least one MEP of the multiple MEPs is The private MAC address of at least one MEP.

With the third aspect or any of the foregoing implementation manners, in another implementation manner of the third aspect, the receiving module is further configured to: receive the first unicast packet sent by the RMEP, where the first The unicast message carries the ID of any one of the plurality of MEPs; the execution module is configured to use the ID of the any one of the MEPs carried in the first unicast packet, and the pre-acquired plurality of MEPs a mapping between the ID and the MAC address of the multiple MEPs, and generating a second unicast packet corresponding to any one of the plurality of MEPs, where the source MAC address of the second unicast packet corresponding to any one of the MEPs The address is the MAC address of the RMEP, and the destination MAC address is the MAC address of the any MEP. The sending module is configured to send the second unicast packet to any one of the multiple MEPs.

According to a fourth aspect, a device for detecting link detection includes: a receiving module, configured to receive a first CCM message sent by a relay device, where the first CCM message carries multiple IDs of a maintenance end node MEP The source media access control MAC address of the first CCM packet is a MAC address of the transit device, and the determining module is configured to determine, between the RMEP and the plurality of MEPs according to the IDs of the multiple MEPs Link connectivity.

With reference to the fourth aspect, in an implementation manner of the fourth aspect, the first CCM packet further carries state information of each of the plurality of MEPs.

With reference to the fourth aspect, or any one of the foregoing implementation manners, in another implementation manner of the fourth aspect, the determining module is specifically configured to: determine the multiple MEPs according to the IDs of the multiple MEPs Whether the RMEP is in a connected state; when the plurality of MEPs are in a connected state with the RMEP, the RMEP determines the RMEP according to status information of the multiple MEPs. Link connectivity with the plurality of MEPs, wherein the state information is used to indicate a link connection condition acquired by each of the MEPs.

With reference to the fourth aspect, or any one of the foregoing implementation manners, in another implementation manner of the fourth aspect, the ID and status information of the multiple MEPs are included in a vendor specific type of the first CCM message. The length value is in the TLV field.

In conjunction with the fourth aspect, or any one of the foregoing implementation manners, in another implementation manner of the fourth aspect, the device further includes: a sending module, configured to send the first unicast packet to the transit device, The first unicast packet carries an ID of any one of the plurality of MEPs; the receiving module is configured to receive a third unicast packet sent by any one of the plurality of MEPs, so as to determine the RMEP Link connectivity between the RMEP and any one of the plurality of MEPs; wherein the transit device is based on the ID of the any one of the MEPs carried in the first unicast packet, and pre-acquired A mapping relationship between the IDs of the plurality of MEPs and the MAC addresses of the plurality of MEPs, generating a second unicast packet corresponding to any one of the plurality of MEPs, and sending the second unicast packet to the The MEP corresponding to the ID, the third unicast message is a message that the any MEP replies to the second unicast message.

In the embodiment of the present invention, the relay device receives multiple CCM packets from multiple MEPs. At this time, the transit device does not pass the multiple CCM packets through the link between the transit device and the RMEP as in the prior art. After being transmitted to the RMEP, the multiple CCM messages are combined and sent to the RMEP through the link. In this way, the number of CCM messages on the link can be reduced, thereby solving the CCM message. The problem of excessive bandwidth occupied on this link.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only some of the present invention. For the embodiments, those skilled in the art can obtain other drawings according to the drawings without any creative work.

FIG. 1 is a schematic diagram of an application scenario for detecting link connectivity;

2 is a schematic flowchart of a method for detecting link connectivity according to an embodiment of the present invention;

3 is a diagram showing an example of content of a second CCM message;

4 is a schematic flowchart of a method for detecting link connectivity according to another embodiment of the present invention;

FIG. 5 is a schematic block diagram of an apparatus for detecting a link according to an embodiment of the present invention; FIG.

6 is a schematic block diagram of an apparatus for detecting a link according to another embodiment of the present invention;

FIG. 7 is a schematic block diagram of an apparatus for detecting a link according to still another embodiment of the present invention; FIG.

FIG. 8 is a schematic block diagram of an apparatus for detecting a link according to still another embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 2 illustrates a method of link detection in accordance with an embodiment of the present invention. As shown in Figure 2, the method includes:

210. The transit device receives the multiple first CCM messages sent by the multiple MEPs, where the first CCM message sent by each MEP carries the ID of each MEP.

It should be understood that the source MAC address of the first CCM message sent by each MEP may be the MAC address of each MEP, and the destination MAC address of the multiple first CCM messages may include the MAC address of the same RMEP. That is, the multiple first CCM messages can be aggregated on the link between the transit device and the same RMEP.

The transit device performs a process of combining the multiple first CCM messages to generate a second CCM message, where the source MAC address of the second CCM message is the MAC address of the transit device, and the second CCM message The document carries the IDs of the plurality of MEPs.

It should be understood that the foregoing merge process may be understood as encapsulating a plurality of first CCM messages into a second CCM message, and the source MAC address of the second CCM message is replaced with the current MAC address of the transit device. In addition, the destination MAC address of the second CCM message may include the MAC address of the RMEP.

230. The transit device sends the second CCM message to the RMEP, so that the RMEP determines link connectivity between the RMEP and the plurality of MEPs.

In the embodiment of the present invention, the relay device receives multiple CCM packets from multiple MEPs. At this time, the transit device does not pass the multiple CCM packets through the link between the transit device and the RMEP as in the prior art. After being transmitted to the RMEP, the multiple CCM messages are combined and sent to the RMEP through the link. In this way, the number of CCM messages on the link can be reduced, thereby solving the CCM message. The problem of excessive bandwidth occupied on this link.

It should be understood that the multiple MEPs and the RMEPs have the CFM function enabled, and the multiple MEPs that have the CFM function enabled can send the first CCM message to the RMEP, and the destination MAC address of the first CCM message can be a multicast MAC address, that is, The destination MAC address of the first CCM packet may include the MAC address of the RMEP, and may also include the MAC address of the other RMEP. However, since the destination MAC address of the CCM packet sent by the multiple MEPs includes the MAC address of the same RMEP, The link between the transit device and the RMEP will be aggregated.

It should also be understood that after receiving the second CCM message sent by the relay device, the RMEP only needs to determine the source MAC address of the second CCM message, instead of receiving multiple MEP transmissions as in the prior art. The source MAC address of each CCM packet is determined after multiple CCM messages. Therefore, the MAC learning number of the RMEP can be reduced, and the occupation of the Layer 2 forwarding table resources is reduced.

Optionally, as an embodiment, after receiving the second CCM packet sent by the transit device, the RMEP parses the second CCM packet to search for the ID of the MEP, and if the ID of the MEP exists in the packet, The link between the MEP and the RMEP is considered to be in a connected state. If the RMEP cannot find the ID of a MEP in the second CCM message received in consecutive cycles, the link between the MEP and the RMEP can be considered to be in the disconnected state.

Optionally, as an embodiment, the second CCM message may further carry status information of each MEP in the multiple MEPs, or in other words, the second CCM message may further indicate the IDs of the multiple MEPs and the Correspondence between status information of multiple MEPs.

The status information of the MEP may be the connection status of the link that is perceived by the MEP. For example, the status information of the MEP may include the following: the Ethernet OAM connection message of the MEP is lost; the MEP receives the remote fault indication ( The Ethernet OAM connection detection packet of the remote defect Indication (RDI); the MEP receives the incorrect Ethernet OAM connectivity detection packet; the MEP receives the cross-connected Ethernet OAM connectivity detection packet.

It should be understood that the relay device may regenerate a new packet, that is, the second CCM packet, according to the information carried in the multiple first CCM packets, in particular, the transit device will have its own MAC address. The source MAC address of the second CCM packet is set, and the IDs of the plurality of MEPs and the status information of the plurality of MEPs in the plurality of first CCM messages are placed in the second CCM report according to the correspondence between the ID and the state information. In addition, the destination MAC address of the second CCM message includes the MAC address of the same remote maintenance end node RMEP. The second CCM message can carry information of multiple MEPs in multiple first CCM messages, and can reduce the number of CCM messages.

Optionally, as an embodiment, the ID and status information of each MEP may be included in a vendor specific type length value (TLV) field of the second CCM message. Specifically, the CCM packet can be extended by the vendor-specific type length value TLV field defined in the IEEE 802.1ag, and the extended CCM packet of the first CCM packet is generated, so that the extended packet can carry the ID of the MEP in batches. And status information. The definition of the TLV in the OAM message is as shown in Table 1. The vendor-specific type length value field of type Type 31 can be extended to enable the field to carry the ID and status information of the MEP in batches. As shown in Table 2, the value Value is used to carry the ID of each MEP and its status information. Each MEP occupies 4 bytes. The specific structure is shown in Figure 3. In Figure 3, the MEP ID carries the ID of the MEP, which occupies two bytes. The status Status carries the current status information of the MEP and occupies one byte. For example, the status information of the MEP carried in the MEP can be as follows: The Ethernet OAM connection packet of the MEP is lost; the MEP receives an Ethernet OAM connection detection packet with a Remote Defect Indication (RDI); the MEP receives an incorrect Ethernet OAM connection detection packet; The MEP receives the Ethernet OAM connectivity detection packet of the cross-connection.

Table 1 Type length value correspondence table

TLV or organization Type field End TLV 0 Sender ID TLV 1 Port Status TLV 2 Data TLV 3 Interface Status TLV 4 Reply Ingress TLV 5 Reply Egress TLV 6 LTM Egress Identifier TLV 7 LTR Egress Identifier TLV 8 Reserved for IEEE 802.1 9-30 Organization-Specific TLV 31 Defined by ITU-T Y.1731 32-63 Reserved for IEEE 802.1 64-255

Table 2: Correspondence table of specific type length values

Organization-Specific TLV format Octet Type=31 1 Length 2-3 OUI 4-6 Sub-Type 7 Value(optional) 8-(Length+3)

Optionally, as an embodiment, the source MAC address of the first CCM packet sent by the at least one MEP of the multiple MEPs is the private MAC address of the at least one MEP. Specifically, when an Ethernet port on a single access device is configured with multiple MEPs, multiple MEPs require the device to provide multiple public bridge MAC addresses, and the public bridge MAC address is limited. The private MAC address of the device can be set to the source address of the first CCM packet and the first CCM packet is sent to the transit device, so that the occupation of the public network MAC address can be reduced, thereby solving the public bridge MAC address. Insufficient problems.

Optionally, as an embodiment, the transit device may further receive the first unicast packet sent by the RMEP, where the first unicast packet carries the ID of any MEP of the multiple MEPs; the transit device may be based on multiple MEPs acquired in advance. The mapping between the ID of the ID and the MAC address of the multiple MEPs, and obtaining the MAC address corresponding to the ID of any MEP of the plurality of MEPs in the unicast packet, thereby generating any MEP corresponding to the second unicast report of the plurality of MEPs The source MAC address of the second unicast packet corresponding to the any one MEP is the MAC address of the RMEP, and the destination MAC address is the MAC address corresponding to the ID of the any MEP; the transit device sends the MAC address to the any MEP. Second unicast message. After receiving the second unicast packet, the MEP sends a third unicast packet to the RMEP for replying to the second unicast packet, and the RMEP completes the detection of the link after receiving the third unicast packet.

It should be understood that the transit device can not only receive the first unicast packet sent by the RMEP, but also receive the packet similar to the first unicast packet sent by other MEPs. . The first unicast packet sent by the RMEP may be a unicast packet other than the CCM packet. For example, the first unicast packet may be a packet used for loopback detection (LB) transmission, or may be used. The message sent by Linktrace (LT). It should be understood that RMEP may be sent to one of a plurality of MEPs for LB or For the LT message, one of the multiple MEPs may also send a message for the LB or LT to the RMEP. In addition, the transit device can obtain the mapping relationship between the IDs of the multiple MEPs and the MAC addresses of the multiple MEPs according to the content of the received multiple CCM packets, and the transit device can also obtain the unicast packets according to the received unicast packets. The mapping relationship between the IDs of the MEPs and the MAC addresses of multiple MEPs. After obtaining the mapping relationship, the transit device can immediately process the packet according to the mapping relationship, or store the mapping relationship for later processing of the packet or for other purposes.

Optionally, as an embodiment, when a link does not support or cannot use the CFM function, if the link supports other OAM technologies, the MEP or RMEP may be used to convert the detected link results to CFM technology. The detection result, that is to say, the MEP and RMEP here can also detect the non-CFM link, and can map the detection result into the CCM message.

The method for detecting link detection in the embodiment of the present invention is described in detail above with reference to FIG. 2 and FIG. 3, and the method for link detection according to the embodiment of the present invention is described in detail below with reference to FIG. As shown in FIG. 4, the method includes:

410. The RMEP receives the first CCM message sent by the transit device, where the first CCM message carries the ID of the multiple MEP, and the source MAC address of the first CCM message is the MAC address of the transit device.

It should be understood that the first CCM message received by the RMEP may correspond to the second CCM message in the embodiment of FIGS. 2 and 3, that is, they may be the same message. In addition, the destination MAC address of the first CCM message sent by the relay device may include the MAC address of the RMEP.

420. The RMEP determines link connectivity between the RMEP and the plurality of MEPs according to the IDs of the multiple MEPs.

In the embodiment of the present invention, the RMEP receives the packet obtained by combining the received CCM packets by the transit device. In this manner, the number of CCM packets on the link can be reduced. Solve the problem that the CCM packet occupies too much bandwidth on the link.

It should be understood that after receiving the first CCM message, the RMEP only needs to determine the source MAC address of the first CCM message, instead of receiving multiple CCM messages sent by multiple MEPs as in the prior art. The MAC address of each CCM packet is determined. Therefore, the MAC learning number of the RMEP can be reduced, and the occupation of the Layer 2 forwarding table resource is reduced.

Optionally, as an embodiment, after receiving the first CCM packet sent by the transit device, the RMEP parses the first CCM packet to search for the ID of the MEP, and if the ID of the MEP exists in the packet, the MME considers The link between the MEP and the RMEP is in a connected state. If the RMEP cannot find the ID of a certain MEP in the first CCM message received in consecutive consecutive cycles, the link between the MEP and the RMEP is considered to be in the disconnected state.

Optionally, as an embodiment, the first CCM message received by the RMEP may further carry status information of each MEP in the multiple MEPs, where the status information is used to indicate a link connection status acquired by the MEP. For example, the status information of the MEP may include the following: the Ethernet OAM connection packet of the MEP is lost; the MEP receives the Ethernet OAM connection detection packet with a Remote Defect Indication (RDI); The Ethernet OAM is connected to the detection packet. The MEP receives the Ethernet OAM connection detection packet.

Specifically, when the first CCM message carries the ID of the MEP and the status information of the MEP, the first CCM packet may be parsed first, and then the ID of the MEP is searched. If the ID of the MEP exists in the packet, The link between the MEP and the RMEP is considered to be in a connected state, and then the connectivity of the link between the RMEP and a MEP of the plurality of MEPs is determined according to the state information of the MEP.

Optionally, as an embodiment, the ID and status information of each MEP may be included in a vendor specific type length value (TLV) field of the first CCM message.

Optionally, as an embodiment, the RMEP may further send the first unicast packet to the transit device, where the first unicast packet carries the ID of any MEP of the multiple MEPs; after receiving the first unicast packet, the transit device receives the first unicast packet. The destination MAC address of the first unicast packet is set to the destination MAC address of the first unicast packet by using the ID of any one of the plurality of MEPs carried in the unicast packet according to the mapping between the ID of the multiple MEPs and the MAC addresses of the multiple MEPs. A MAC address of any one of the plurality of MEPs to generate a second unicast packet. Next, the transit device sends a second unicast packet to the MEP. After receiving the second unicast packet, the MEP sends a third unicast packet to the RMEP to reply to the second unicast packet.

Optionally, the first unicast packet sent by the RMEP may be a unicast packet other than the CCM packet. For example, the first unicast packet may be a packet for the LB, or may be a packet for the LT. Text. The mapping relationship between the IDs of the plurality of MEPs and the MAC addresses of the plurality of MEPs obtained by the transit device may be that the transit device acquires the IDs and the plurality of MEPs according to the content carried by the plurality of first CCM packets received by the transit device. The mapping relationship between the MAC addresses of MEPs can also be medium. The mapping device obtains a mapping relationship between the IDs of the plurality of MEPs and the MAC addresses of the plurality of MEPs according to the received unicast packets. After the mapping relationship is obtained, the transit device can process the received packet according to the mapping relationship, or store the mapping relationship for later processing of the packet or other purposes.

Optionally, as an embodiment, when a link does not support or cannot use the CFM function, if the link supports other OAM technologies, the MEP or RMEP may be used to convert the detected link results to CFM technology. The detection result, that is to say, the MEP and RMEP here can also detect the non-CFM link, and can map the detection result into the CCM message.

The method for link detection provided by the embodiment of the present invention is described in detail with reference to FIG. 1 to FIG. 4, and the device for link detection provided by the embodiment of the present invention is described in detail below with reference to FIG. 5 to FIG. It should be understood that the apparatus of FIGS. 5-8 can implement the various steps of the method of FIGS. 1 through 4, and to avoid repetition, it will not be described in detail herein.

FIG. 5 is a schematic block diagram of an apparatus for detecting a link according to an embodiment of the present invention. The apparatus 500 of FIG. 5 is capable of implementing the various steps performed by the relay device of FIGS. 2 and 4, and to avoid repetition, it will not be described in detail herein. The apparatus 500 includes a receiving module 510, an executing module 520, and a transmitting module 530.

The receiving module 510 is configured to receive a plurality of first CCM messages sent by the multiple MEPs, where the first CCM message sent by each MEP carries the ID of each MEP;

The execution module 520 is configured to perform a combination process on the multiple CCM messages to generate a second CCM message, where the source MAC address of the second CCM message is the MAC address of the transit device, and the second CCM The packet carries the IDs of the multiple MEPs;

It should be understood that the foregoing merge process may be understood as encapsulating a plurality of first CCM messages into a second CCM message, and the source MAC address of the second CCM message is replaced with the current MAC address of the transit device. In addition, the destination MAC address of the second CCM message may include the MAC address of the RMEP.

The sending module 530 is configured to send the second CCM message to the RMEP, so that the RMEP determines link connectivity between the RMEP and the plurality of MEPs.

In the embodiment of the present invention, the device 500 receives multiple CCM messages from multiple MEPs. At this time, the device 500 does not transparently transmit multiple CCM messages through the link between the device 500 and the RMEP as in the prior art. To RMEP, the CCM packets are combined and sent to the RMEP through the link. In this way, the number of CCM packets on the link is reduced. The problem of excessive bandwidth occupied by CCM packets on the link is solved.

Further, after receiving the second CCM message sent by the device 500, the RMEP only needs to determine the source MAC address of the second CCM message, instead of receiving multiple MEP transmissions as in the prior art. After the CCM message, the MAC address of each CCM message is determined. Therefore, the MAC learning number of the RMEP can be reduced, and the occupation of the Layer 2 forwarding table resources is reduced.

Optionally, as an embodiment, the second CCM message sent by the sending module 530 of the device 500 further carries status information of each MEP in the multiple MEPs, where the status information is used to indicate the link connection acquired by each MEP. Happening.

Optionally, as an embodiment, the ID and status information of each MEP is included in a vendor specific TLV field of the second CCM message.

Optionally, as an embodiment, the source MAC address of the first CCM packet sent by the at least one MEP of the multiple MEPs is the private MAC address of the at least one MEP.

Optionally, as an embodiment, the receiving module 510 is further configured to receive the first unicast packet sent by the RMEP, where the first unicast packet carries an ID of any one of the multiple MEPs, and the executing module 520 is configured to The mapping between the ID of the MEP carried in the first unicast packet and the MAC address of the plurality of MEPs and the MAC address of the plurality of MEPs, and generating a second corresponding to any one of the plurality of MEPs a unicast packet, where the source MAC address of the second unicast packet corresponding to the any MEP is the MAC address of the RMEP, and the destination MAC address is the MAC address of the any MEP. The sending module 530 is configured to send the multiple MEPs. Any one of the MEPs sends the second unicast message. After receiving the second unicast packet, the MEP sends a third unicast packet to the RMEP for replying to the second unicast packet, and the RMEP completes the detection of the link after receiving the third unicast packet.

FIG. 6 is a schematic block diagram of an apparatus for detecting a link according to another embodiment of the present invention. The apparatus 600 of FIG. 6 can implement the various steps performed by the RMEP in FIGS. 2 and 4, and to avoid repetition, it will not be described in detail herein. The apparatus 600 includes a receiving module 610 and a determining module 620.

The receiving module 610 is configured to receive the first CCM packet sent by the transit device, where the first CCM packet carries the ID of the MEP, and the source MAC address of the first CCM packet is the MAC address of the transit device.

The executing module 620 is configured to determine link connectivity between the RMEP and the multiple MEPs according to the IDs of the multiple MEPs.

In the embodiment of the present invention, the device 600 receives the received multiple CCMs from the relay device. In this way, the number of CCM packets on the link can be reduced, and the problem that the CCM packet occupies too much bandwidth on the link is solved.

Further, after receiving the first CCM message, the device 600 only needs to determine the source MAC address of the first CCM message, instead of receiving multiple CCM messages sent by multiple MEPs as in the prior art. To determine the MAC address of each CCM packet, the MAC learning number of the RMEP can be reduced, and the occupation of the Layer 2 forwarding table resources is reduced.

Optionally, as an embodiment, the first CCM message may further carry status information of each MEP in the multiple MEPs.

Optionally, as an embodiment, the first CCM message carries state information of each of the plurality of MEPs.

Optionally, as an embodiment, when the first CCM message can also carry the status information of each of the multiple MEPs, the determining module 620 is specifically configured to: determine multiple MEPs and devices according to the IDs of the multiple MEPs. Whether the 600 is in a connected state; when a plurality of MEPs are in a connected state with the device 600, determining link connectivity between the device 600 and the plurality of MEPs according to the status information of the plurality of MEPs, wherein the status information is used to indicate each Link connection status obtained by MEP.

Optionally, as an embodiment, the ID and status information of each MEP is included in a vendor specific TLV field of the first CCM message.

Optionally, as an embodiment, the apparatus 600 further includes: a sending module 630, configured to send a first unicast packet to the transit device, where the first unicast packet carries an ID of any one of the plurality of MEPs; Receiving a third unicast message sent by any one of the plurality of MEPs, so as to determine link connectivity between the device 600 and any one of the plurality of MEPs; wherein the transit device is carried according to the first unicast packet The mapping between the ID of any MEP and the pre-acquisition of the IDs of the multiple MEPs and the MAC addresses of the multiple MEPs, and generating a second unicast packet corresponding to any MEP of the plurality of MEPs, where the third unicast packet is Any message that the MEP replies to the second unicast packet.

FIG. 7 is a schematic block diagram of an apparatus for detecting a link according to still another embodiment of the present invention. The apparatus 700 of FIG. 7 can implement the various steps performed by the RMEP in FIGS. 2 and 4, and to avoid repetition, it will not be described in detail herein. The apparatus 700 includes a receiver 710, a processor 720, and a transmitter 730.

The receiver 710 is configured to receive multiple first CCM messages sent by multiple MEPs, where the first CCM message sent by each MEP carries the ID of each MEP.

The processor 720 is configured to perform a combining process on the multiple first CCM messages to generate a second CCM. a packet, where the source MAC address of the second CCM packet is a MAC address of the transit device, and the second CCM packet carries the ID of the multiple MEPs;

It should be understood that the foregoing merge process may be understood as encapsulating a plurality of first CCM messages into a second CCM message, and the source MAC address of the second CCM message is replaced with the current MAC address of the transit device. In addition, the destination MAC address of the second CCM message may include the MAC address of the RMEP.

The sender 730 is configured to send the second CCM message to the RMEP, so that the RMEP determines link connectivity between the RMEP and the plurality of MEPs.

In the embodiment of the present invention, the device 700 receives multiple CCM messages from multiple MEPs. At this time, the device 700 does not transparently transmit multiple CCM messages through the link between the device 700 and the RMEP as in the prior art. To the RMEP, the CCM packets are combined and processed and then sent to the RMEP through the link. In this way, the number of CCM packets on the link is reduced, so that the CCM packets are occupied on the link. The problem of excessive bandwidth.

Further, after receiving the second CCM message sent by the device 700, the RMEP only needs to determine the source MAC address of the second CCM message, instead of receiving multiple MEP transmissions as in the prior art. After the CCM message, the MAC address of each CCM message is determined. Therefore, the MAC learning number of the RMEP can be reduced, and the occupation of the Layer 2 forwarding table resources is reduced.

Optionally, as an embodiment, the second CCM message sent by the transmitter 730 of the device 700 further carries status information of each MEP in the multiple MEPs, where the status information is used to indicate a link connection acquired by each MEP. Happening.

Optionally, as an embodiment, the ID and status information of each MEP is included in a vendor specific TLV field of the second CCM message.

Optionally, as an embodiment, the source MAC address of the first CCM packet sent by the at least one MEP of the multiple MEPs is the private MAC address of the at least one MEP.

Optionally, as an embodiment, the receiver 710 is further configured to receive the first unicast packet sent by the RMEP, where the first unicast packet carries an ID of any one of the multiple MEPs;

The processor 720 is configured to generate any one of the plurality of MEPs according to the ID of the one MEP carried in the first unicast packet, and the mapping relationship between the IDs of the plurality of MEPs and the MAC addresses of the plurality of MEPs. a second unicast packet corresponding to the MEP, where the source MAC address of the second unicast packet corresponding to the any MEP is the MAC address of the RMEP, and the destination MAC address is the MAC address of the any MEP; To the multiple MEPs Any one of the MEPs sends the second unicast message.

FIG. 8 is a schematic block diagram of an apparatus for detecting a link according to still another embodiment of the present invention. The apparatus 800 of FIG. 8 can implement the various steps performed by the RMEP in FIGS. 2 and 4, and to avoid repetition, it will not be described in detail herein. The device 800 includes a receiver 810 and an actuator 820.

The receiver 810 is configured to receive a first CCM packet sent by the relay device, where the first CCM packet carries the ID of the multiple MEP, and the source MAC address of the first CCM packet is the MAC address of the transit device.

The processor 820 is configured to determine link connectivity between the RMEP and the multiple MEPs according to the IDs of the multiple MEPs.

In the embodiment of the present invention, the RMEP receives the packet obtained by combining the received CCM packets by the transit device. In this manner, the number of CCM packets on the link can be reduced. Solve the problem that the CCM packet occupies too much bandwidth on the link. Further, after receiving the first CCM message, the device 800 only needs to determine the source MAC address of the first CCM message, instead of receiving multiple CCM messages sent by multiple MEPs as in the prior art. To determine the MAC address of each CCM packet, the MAC learning number of the RMEP can be reduced, and the occupation of the Layer 2 forwarding table resources is reduced.

Optionally, as an embodiment, when the first CCM message further carries status information of each of the plurality of MEPs.

Optionally, as an embodiment, when the first CCM message carries the status information of each of the multiple MEPs, the processor 820 is specifically configured to: determine, according to the IDs of the multiple MEPs, whether the multiple MEPs and the device 800 are When the plurality of MEPs are in a connected state, the link connectivity between the device 800 and the plurality of MEPs is determined according to the status information of the plurality of MEPs, wherein the status information is used to indicate each MEP. Get the link connection status.

Optionally, as an embodiment, the ID and status information of each MEP is included in a vendor specific type length value TLV field of the second CCM message.

Optionally, as an embodiment, the apparatus 800 further includes: a transmitter 830, configured to send, to the transit device, a first unicast packet, where the first unicast packet carries an ID of any one of the plurality of MEPs; and the receiver 810 uses Receiving a third unicast message sent by any one of the plurality of MEPs, so as to determine link connectivity between the device 800 and any one of the plurality of MEPs; wherein the transit device is carried according to the first unicast packet The ID of any MEP and the mapping relationship between the IDs of multiple MEPs acquired in advance and the MAC addresses of multiple MEPs are generated in multiple MEPs. The second unicast packet corresponding to any MEP, and the third unicast packet is a packet that any MEP replies to the second unicast packet.

It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims (20)

A method for link detection, comprising: The transit device receives a plurality of first connectivity check message CCM messages sent by the maintenance end node MEP, where the first CCM message sent by each MEP carries the ID of each MEP; The transit device performs a process of combining the multiple first CCM messages to generate a second CCM message, where the source media access control MAC address of the second CCM message is the MAC address of the transit device And the second CCM message carries an ID of the multiple MEPs; Transmitting, by the relay device, the second CCM message to the RMEP, so that the RMEP determines link connectivity between the RMEP and the multiple MEPs according to the second CCM message. The method according to claim 1, wherein the second CCM message further carries status information of each of the plurality of MEPs, the status information is used to indicate the acquisition by each MEP. Link connection status. The method according to claim 2, wherein the ID and status information of each MEP is included in a vendor specific type length value TLV field of the second CCM message. The method according to any one of claims 1 to 3, wherein a source MAC address of the first CCM message sent by at least one of the plurality of MEPs is a private MAC address of the at least one MEP. . The method according to any one of claims 1 to 4, further comprising: Receiving, by the relay device, the first unicast packet sent by the RMEP, where the first unicast packet carries an ID of any one of the multiple MEPs; The relay device generates the multiple according to the mapping relationship between the ID of the one MEP carried in the first unicast packet and the ID of the plurality of MEPs that are acquired in advance and the MAC addresses of the multiple MEPs. a second unicast packet corresponding to any one of the MEPs, where the source MAC address of the second unicast packet corresponding to any one of the MEPs is the MAC address of the RMEP, and the destination MAC address is any one of the MEPs. MAC address; The transit device sends the second unicast packet to any one of the multiple MEPs. A method for link detection, comprising: The remote maintenance terminal RMEP receives the first CCM packet sent by the transit device, where the first CCM packet carries the IDs of the plurality of maintenance end node MEPs, and the source media access control MAC of the first CCM packet The address is the MAC address of the transit device; The RMEP determines link connectivity between the RMEP and the plurality of MEPs according to IDs of the plurality of MEPs. The method according to claim 6, wherein the first CCM message further carries status information of each of the plurality of MEPs, and the status information is used to indicate that each MEP is obtained. Link connection situation. The method according to claim 7, wherein the RMEP determines link connectivity between the RMEP and the plurality of MEPs according to the IDs of the plurality of MEPs, including: Determining, by the RMEP, whether the plurality of MEPs and the RMEP are in a connected state according to an ID of the multiple MEPs; When the plurality of MEPs are in a connected state with the RMEP, the RMEP determines link connectivity between the RMEP and the plurality of MEPs according to status information of the multiple MEPs. The method according to claim 7 or 8, wherein the ID and status information of the plurality of MEPs are included in a vendor specific type length value TLV field of the first CCM message. The method according to any one of claims 6 to 9, wherein the method further comprises: Transmitting, by the transit device, a first unicast packet, where the first unicast packet carries an ID of any one of the multiple MEPs; Receiving a third unicast message sent by any one of the plurality of MEPs, so that the RMEP determines link connectivity between the RMEP and any one of the plurality of MEPs; The transit device generates a map according to the mapping between the ID of the any one of the MEPs and the IDs of the plurality of MEPs that are acquired in advance in the first unicast packet and the MAC addresses of the multiple MEPs. Transmitting a second unicast message corresponding to any one of the plurality of MEPs, and sending the second unicast message to the MEP of the ID of the any MEP, where the third unicast message is any one of the MEP pairs. The packet in which the second unicast packet is replied. A device for detecting a link, comprising: a receiving module, configured to receive multiple first connectivity checks sent by multiple maintenance end node MEPs a message CCM message, where the first CCM message sent by each MEP carries the ID of each MEP; An execution module, configured to perform a merge process on the multiple first CCM messages, to generate a second CCM message, where the source media access control MAC address of the second CCM message is a MAC address of the transit device, And the second CCM message carries an ID of the multiple MEPs; And a sending module, configured to send the second CCM message to the RMEP, so that the RMEP determines link connectivity between the RMEP and the multiple MEPs. The apparatus according to claim 11, wherein the second CCM message further carries status information of each of the plurality of MEPs, the status information is used to indicate the acquisition of each MEP. Link connection status. The apparatus according to claim 12, wherein the ID and status information of each MEP is included in a vendor specific type length value TLV field of the second CCM message. The device according to any one of claims 11 to 13, wherein a source MAC address of the first CCM message sent by at least one of the plurality of MEPs is a private MAC address of the at least one MEP. . The device according to any one of claims 11 to 14, wherein the receiving module is further configured to: Receiving a first unicast packet sent by the RMEP, where the first unicast packet carries an ID of any one of the multiple MEPs; The executing module is configured to generate, according to the mapping between the ID of the any one of the MEPs and the pre-acquired IDs of the multiple MEPs and the MAC addresses of the multiple MEPs. a second unicast packet corresponding to any one of the plurality of MEPs, where the source MAC address of the second unicast packet corresponding to any one of the MEPs is the MAC address of the RMEP, and the destination MAC address is any The MAC address of a MEP; The sending module is configured to send the second unicast packet to any one of the multiple MEPs. A device for detecting a link, comprising: a receiving module, configured to receive a first CCM message sent by the transit device, where the first CCM message carries multiple IDs of the maintenance end node MEP, and the source media access control MAC address of the first CCM message Is the MAC address of the transit device; An execution module, configured to determine, according to an ID of the multiple MEPs, the RMEP and the multiple Link connectivity between MEPs. The apparatus according to claim 16, wherein the first CCM message further carries status information of each of the plurality of MEPs. The device according to claim 17, wherein the determining module is specifically configured to: Determining, according to the IDs of the plurality of MEPs, whether the plurality of MEPs and the RMEP are in a connected state; When the plurality of MEPs are in a connected state with the RMEP, the RMEP determines link connectivity between the RMEP and the plurality of MEPs according to status information of the plurality of MEPs, where The status information is used to indicate the link connection status acquired by each MEP. The apparatus according to claim 17 or 18, wherein the ID and status information of the plurality of MEPs are included in a vendor specific type length value TLV field of the first CCM message. The device according to any one of claims 16 to 19, wherein the device further comprises: a sending module, configured to send a first unicast packet to the transit device, where the first unicast packet carries an ID of any one of the multiple MEPs; The receiving module is configured to receive a third unicast packet sent by any one of the multiple MEPs, so that the RMEP determines link connectivity between the RMEP and any one of the multiple MEPs. Sex The transit device generates a map according to the mapping between the ID of the any one of the MEPs and the IDs of the plurality of MEPs that are acquired in advance in the first unicast packet and the MAC addresses of the multiple MEPs. The second unicast packet corresponding to any one of the plurality of MEPs, the second unicast packet is sent to the MEP corresponding to the ID, and the third unicast packet is the any one of the MEP pairs. The second unicast packet is replied to the packet.

Images