Method and system for transmitting connectivity fault management messages in ethernet, and a node device

• US 8,406,143 B2
• Filed: 11/09/2007
• Issued: 03/26/2013
• Est. Priority Date: 11/09/2006
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Long, Hao, Deng, Zhusheng
• Primary Examiner(s): Faroul, Farah
• Application Number:
  US11/983,693
• Publication Number:
  US 20080112331A1
• Time in Patent Office: 1,964 Days
• Field of Search: 370/241.1, 370/248
• US Class Current: 370/241.1
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 43/0811 by checking connectivity

Abstract

A method for transmitting a Connectivity Fault Management (CFM) message of Ethernet includes: receiving a CFM message transmitted from a source node, the CFM message including identifier of a path and a connection maintenance target address; determining whether the connection maintenance target address matches address of a receiving node, and if yes, terminating the CFM message; otherwise forwarding the CFM message to a next hop based upon the path identifier of the path. Another method and a system for transmitting a CFM message of Ethernet, a node for transmitting a CFM message of Ethernet, and a node for receiving a CFM message of Ethernet are also disclosed. With the invention, a CFM message may be forwarded according to information of a Medium Access Control (MAC) address and a Virtual Local Area Network Identifier (VLAN ID) of a path identifier where a monitored service is located, and thus may be forwarded correctly in a Provider Backbone Bridge Traffic Engineering (PBB-TE) network.

Claims

1. A method for implementing connectivity fault management (CFM) in a Provider Backbone Transport (PBT) network, comprising:

receiving, by a receiving node, a connectivity fault management message transmitted from a source node, wherein the connectivity fault management message carries a path identifier and a connection maintenance target address, wherein the path identifier consists of a destination media access control (MAC) address and a virtual local area network identifier (VLAN ID), and wherein the connection maintenance target address is contained in a protocol data unit of the connectivity fault management message;

determining, by a maintenance domain intermediate point (MIP), whether the connection maintenance target address matches an address of the receiving node;

if the connection maintenance target address matches the address of the receiving node, transmitting a connectivity fault management reply message; and

if the connection maintenance target address does not match the address of the receiving node, forwarding the connectivity fault management message to a next hop based on the VLAN ID and the destination MAC address in the path identifier.

2. The method according to claim 1, wherein the connectivity fault management message further comprises explicit route information, and wherein the receiving node forwards the connectivity fault management message to the next hop according to the explicit routing information.

3. The method according to claim 2, wherein the explicit route information comprises a sequence of egress ports or a sequence of media access control addresses.

4. The method according to claim 1, wherein the method further comprises encapsulating the connectivity fault management message with a destination address which is a media access control address dedicated for a connectivity fault management function, and wherein the receiving node drops the connectivity fault management message to be processed according to the media access control address dedicated for the connectivity fault management function.

5. The method according to claim 4, wherein the protocol data unit of the connectivity fault management message further comprises a media access control address part of identifier of a forwarding path for the connectivity fault management message.

6. The method according to claim 1, wherein the protocol data unit of the connectivity fault management message carries information of a return path, and wherein a header of the connectivity fault management reply message is encapsulated according to the information of the return path.

7. The method according to claim 6, wherein the information of the return path comprises a media access control address or a virtual local area network identifier of an identifier of the return path.

8. The method of claim 1, wherein the connection maintenance target address is not the same as the destination MAC address.

9. A receiving node device used in a Provider Backbone Transport (PBT) network, wherein the receiving node device is a maintenance domain intermediate point (MIP), and wherein the MIP comprises:

a message transceiver, configured to receive a connectivity fault management message transmitted from a source node device;

a hardware-implemented address determiner, configured to determine whether a connection maintenance target address in the connectivity fault management message matches an address of the MIP, wherein the connection maintenance target address is contained in a protocol data unit of the connectivity fault management message; and

a hardware-implemented connectivity fault management processor, configured to transmit a connectivity fault management reply message if the connection maintenance target address matches the address of the MIP, and to forward the connectivity fault management message received via the message transceiver to a next hop based on a virtual local area network identifier (VLAN ID) and a destination media access control (MAC) address in a path identifier carried in the connectivity fault management message if the connection maintenance target address does not match the address of the MIP.

10. A system for implementing connectivity fault management, comprising the receiving node device of claim 9 and the source node device, wherein the source node device comprises:

a hardware-implemented connectivity fault management message generator, configured to generate the connectivity fault management message comprising the connection maintenance target address; and

a second message transceiver, configured to transmit the connectivity fault management message generated by the hardware-implemented connectivity fault management message generator and to receive the connectivity fault management reply message.

11. The system according to claim 10, wherein the protocol data unit of the connectivity fault management message further carries information of a return path, and wherein a header of the connectivity fault management reply message is encapsulated according to the information of the return path.

12. The system according to claim 11, wherein the system further comprises an intermediate node configured to receive the connectivity fault management reply message transmitted by the receiving node and to forward the connectivity fault management reply message to a second next hop based on the information of the return path.

13. The system according to claim 11, wherein the information of the return path comprises a media access control address or a virtual local area network identifier of a return path.

14. The receiving node device of claim 9, wherein the path identifier consists of the destination MAC address and the VLAN ID.

15. The receiving node device of claim 14, wherein the connectivity fault management message comprises the following fields in the following order:

the destination MAC address, a source address, a VLAN tag protocol identifier (TPI), a priority, the VLAN ID, an Ethernet type, a maintenance domain level, a version, an operation code, at least one flag, at least one type-length-value (TLV) offset, a loopback transaction identifier, a loopback target MAC address, a return path MAC address, a return path VLAN ID, and a frame check sequence (FCS).

16. The receiving node device of claim 9, wherein the connectivity fault management message comprises the following fields in the following order:

the destination MAC address, a source address, a VLAN tag protocol identifier (TPI), a priority, the VLAN ID, an Ethernet type, a maintenance domain level, a version, an operation code, at least one flag, at least one type-length-value (TLV) offset, a loopback transaction identifier, a loopback target MAC address, a path MAC address, a return path MAC address, a return path VLAN ID, and a frame check sequence (FCS).

17. The system according to claim 10, wherein the connectivity fault management message comprises the following fields in the following order:

the destination MAC address, a source address, a VLAN tag protocol identifier (TPI), a priority, the VLAN ID, an Ethernet type, a maintenance domain level, a version, an operation code, at least one flag, at least one type-length-value (TLV) offset, a loopback transaction identifier, a loopback source address, a path MAC address, and a frame check sequence (FCS).

18. The receiving node of claim 9, wherein the connection maintenance target address is not the same as the destination MAC address.