Patent Publication Number: US-2007097857-A1

Title: Method and Apparatus for Fault Management in Ethernet and Multi-Protocol Label Switching Network Interworking Network

Description:
This application is a continuation of International Patent Application No. PCT/CN2006/000648, filed Apr. 11, 2006, which claims priority to Chinese Patent Application No. 200510064584.X, filed Apr. 15, 2005, all of which are hereby incorporated by reference. 
    
    
     FIELD OF THE TECHNOLOGY  
      The present invention relates to communication technologies, and more particularly, to a method and corresponding device for fault management in Ethernet and Multi-protocol Label Switching (MPLS) network interworking network.  
     BACKGROUND OF THE INVENTION  
      Along with the development of network communication technologies, Ethernet services are developing from Local Area Network (LAN) to Metropolitan Area Network (MAN) and telecommunication network. In the Next Generation Ethernet service for which the demands are increasing, MPLS, based on its unique advantages, such as rapid recovery, network extendibility, Quality of Service (QoS) ability, service congregation ability and inter-operability of services, has become the first option of network technologies. That is to say, the Ethernet and MPLS network interworking network has become the trend.  
      A guideline definition of the Ethernet and MPLS network interworking Model has been made in the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) Y.1415 document, and at the same time, the Pseudo-Wire Emulation Edge-to-Edge (PWE3) of the Internet Engineering Task Force (IETF) has made detailed definitions for the application of the Ethernet and MPLS network interworking, draft-ietf-pwe3-ethernet-encap-09.txt, and for encapsulation of Ethernet services running in an MPLS network.  
      In the Ethernet and MPLS network interworking model, it is needed not only to perform the corresponding encapsulation process, but also to have a corresponding fault alarm mechanism; thus, when a fault occurs, it can be found timely so as to adopt a corresponding protection measure to guarantee the reliability of the service transmission between the Ethernet and the MPLS network. In the available draft, however, no fault alarm interworking mechanism has been provided for Operation, Administration and Maintenance (OAM) with regard to the Ethernet and MPLS network interworking.  
      At present, in Y.1711 published by the ITU-T, only a fault detection mechanism for the MPLS is defined in detail whereas the Ethernet and MPLS network interworking model does not provide a fault alarm notification mechanism for the interworking between the MPLS network and the Ethernet.  
      Because there is no fault alarm notification mechanism for the Ethernet and MPLS network interworking, there is no solution to an end-to-end OAM mechanism for the Ethernet and MPLS network interworking; thus, the reliability of the interworking between Ethernet and MPLS network can not be guaranteed.  
     SUMMARY OF THE INVENTION  
      A fault management method of an Ethernet and a Multi-protocol Label Switching (MPLS) network interworking network is provided, so that a fault can be found timely to guarantee the reliability of service transmission.  
      A device for fault management in an Ethernet and an MPLS network interworking network is provided so that a fault can be found timely to guarantee the reliability of service transmission.  
      The method for fault management in an Ethernet and a Multi-protocol Label Switching (MPLS) network interworking network includes:  
      in the interworking network, monitoring the interworking network by a fault monitoring entity;  
      when detecting a fault in the interworking network, the fault monitoring entity sending a fault alarm notification message to an Ethernet End System.  
      The device for fault management in an Ethernet and a Multi-protocol Label Switching (MPLS) network interworking network, configured in the interworking network, includes:  
      an Ethernet End System;  
      a network interworking entity; and  
      a fault monitoring entity, used for monitoring the interworking network, and sending a fault alarm notification message to the Ethernet End System in the interworking network when detecting a fault in the interworking network.  
      It can be seen from the solution mentioned above in accordance with the present invention that the present invention, based on the Ethernet and MPLS network interworking model defined in Y.1415, provides the corresponding process for a fault notification under various fault conditions when the MPLS is used as a backbone network to bear the Ethernet service. That is to say, in accordance with the present invention, fault alarm information can be sent timely to the peer end when there is a fault in the interworking network such that end-to-end management of alarm for occurring faults may be guaranteed in the Ethernet and MPLS network interworking, which may make it possible for the entity at the end which obtains the corresponding alarm information to adopt proper protection measures timely, thus effectively improving the reliability of service transmission in the interworking network communication process. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       FIG. 1  is a schematic diagram illustrating the Ethernet and MPLS network interworking model.  
       FIG. 2  is a schematic diagram illustrating a specific implementing process of the method in accordance with an embodiment of the present invention. 
    
    
     EMBODIMENTS OF THE INVENTION  
      The embodiments of the present invention are mainly to implement an OAM interworking function when an MPLS network is used as the network bearer of an Ethernet service, such that fault management under various fault conditions, based on the Ethernet and MPLS network interworking function model in Y.1415, could be implemented, and the end-to-end OAM management in the Ethernet and MPLS network interworking could be guaranteed.  
      Before the method in accordance with the embodiment of the present invention is described, the Ethernet and MPLS network interworking model in Y.1415 will be briefly introduced.  FIG. 1  is a schematic diagram illustrating the Ethernet and MPLS network interworking model in Y.1415.  
      Ethernet End System 1  and Ethernet End System 2  are peers of each other in  FIG. 1 , and when one end detects a fault, it is necessary to notify the opposite end through a Maintenance Entity (ME), for example, to insert a fault notification message in the ME; when Interworking Function Entity  1  (IWF 1 ) or IWF 2  detects a fault, it is necessary to notify Ethernet End System 1  or Ethernet End System 2  adjacent to the IWF.  
      An MPLS network can not be awared between Ethernet End Systems, but can be awared between IWFs; therefore, it is necessary to implement the OAM interworking function between an Ethernet and an MPLS network, and the IWF is a function entity for implementing the OAM interworking. In a core MPLS network, only the entities related to the MPLS exist.  
      In the interworking network model shown in  FIG. 1 , the faults which are likely to occur specifically include:  
      (1) upstream/downstream Ethernet has a fault, that is, the Ethernet End System has a fault;  
      (2) upstream IWF, that is, IWF 1 , has a fault;  
      (3) downstream IWF, that is, IWF 2 , has a fault;  
      (4) an interconnection Label Switching Path (LSP) in the MPLS network has a fault.  
      It should be noted here that the upstream and the downstream are pre-defined; and it is presumed in this document that Ethernet End System 1  is the upstream Ethernet End System, and Ethernet End System 2  is the downstream Ethernet End System; correspondingly, IWF 1  located at the same side of the MPLS network as Ethernet End System 1  is the upstream IWF, and IWF 2  located at the same side of the MPLS network as Ethernet End System 2  is the downstream IWF.  
      In order to monitor a fault in the interworking network, in the system as shown in  FIG. 1 , a fault management device, that is, a fault monitoring entity used for monitoring the interworking network according to an embodiment of the present invention is added; when a fault in the interworking network is detected, the fault monitoring entity will send a fault alarm notification message to the Ethernet End System in the interworking network. The fault monitoring entity can be set in the Ethernet End System or the IWF.  FIG. 2  is a schematic diagram illustrating the concrete implementing process according to the method in accordance with the embodiment of the present invention, and to give a further understanding of the embodiment of the present invention, various fault alarming processes of the faults likely to appear are hereinafter described in detail, respectively, as shown in  FIG. 1  and  FIG. 2 .  
      Ethernet End System 2 , when receiving an Ethernet Alarm Indication Signal (ETH-AIS) message, or receiving no Ethernet Continuity Check (ETH-CC) message from the opposite end Ethernet End System 1  for a pre-configured period of time, will send an Ethernet Remote Fault Indication (ETH-RDI) message to the peer of the opposite end, that is, Ethernet End System 1 , so as to notify the Ethernet End System 1  of the fault information in the interworking network. The ETH-AIS message may be from Ethernet End System 1 , or may be from IWF 2  adjacent to Ethernet End System 2 .  
      As shown in scene  1  of  FIG. 2 , the process for handling a network fault of the upstream/downstream Ethernet includes:  
      in the Ethernet having the fault, i.e. Ethernet End System 1 , which is taken here as an example, a Forward Alarm ETH-AIS message is inserted in the ME of Ethernet End System 1  so as to send a alarm notification to the direction of Ethernet End System 2 ;  
      upon receiving the ETH-AIS message, Ethernet End System 2  generates and sends a reverse ETH-RDI message to the ME of Ethernet End System 1  at the opposite end;  
      both the ETH-AIS message and the ETH-RDI message, when traversing the MPLS network, need to perform the process of encapsulation/de-encapsulation in the Ethernet and the MPLS network interworking model as defined by the protocol. Refer to the protocol for specific implementation, and no further description is herein given.  
      The processing of a fault in the upstream/downstream network is basically the same except that  
      (1) the position where the Forward Alarm message is inserted is different: when the upstream Ethernet has a fault, the ETH-AIS message is inserted in the ME of the upstream Ethernet node, and when the downstream Ethernet has a fault, the ETH-AIS message is inserted in the ME of the downstream Ethernet node,  
      (2) because of the difference in the inserted position, the ETH-AIS message generated by the upstream node needs to be encapsulated through the format defined according to Y.1415 in the upstream IWF, and upon traversing the MPLS network, the ETH-AIS is de-encapsulated in the downstream IWF; whereas the ETH-AIS message generated by the downstream node needs to be encapsulated through the format defined according to Y.1415 in the downstream IWF, and upon traversing the MPLS network, the ETH-AIS message is de-encapsulated in the upstream IWF.  
      As shown in scene  2  of  FIG. 2 , the process for handling a fault in the upstream IWF, that is, IWF 1 , i.e., a fault at the side connected to the MPLS network in the IWF is described as follows:  
      the faults occurring in IWF 1  can be categorized into two different cases, which will be described, respectively, as follows.  
      The first case is: the IWF 1  fault does not impact the OAM function of the MPLS part in IWF 1 ; in this case, the MPLS LSP bears the Ethernet service works normally, in other words, the LSP will not generate a fault alarm; but the IWF 1  fault prevents the ME of Ethernet End System 2  from receiving the ETH-CC message sent by the ME of the Ethernet End System 1  at the opposite end within the pre-configured period of time. The corresponding processing in this case includes:  
      the ME of Ethernet End System 2  enters the fault state, and sends a reverse alarm. ETH-RDI message to the direction of Ethernet End system 1 .  
      The second case is: the IWF 1  fault impacts the OAM function of the MPLS part in IWF 1 ; in this case, the OAM function of the MPLS part in IWF 1  can not work normally, no MPLS Connectivity Verification (MPLS-CV) packet can be sent normally, and the LSP fault state can be detected at the LSP end connected to IWF 2 . The corresponding processing in this case includes:  
      IWF 2  translates the LSP fault state into the corresponding ETH-AIS message, and sends the message to the ME of Ethernet End System 2 ;  
      the ME of Ethernet End System 2 , upon receiving the ETH-AIS message, sends a reverse alarm ETH-RDI massage to the direction of Ethernet End System 1 .  
      Obviously, in  FIG. 1 , it is likely that a fault occurs at the side of IWF 2  connected to the MPLS. The corresponding processing is similar to the above, which will not be described further here.  
      As shown in scene  3  of  FIG. 2 , the process for handling a fault in the downstream IWF, that is IWF 2 , i.e., a fault at the side of IWF 2  connected to the Ethernet, and the processing can be categorized into two cases, which are described, respectively, as follows.  
      The first case is: the IWF 2  fault does not impact the OAM function of the Ethernet part in IWF 2 . The processing includes:  
      when IWF 2  has the fault, the OAM function of the Ethernet part in IWF 2  translates the fault into the corresponding ETH-AIS message and sends the message to the ME of Ethernet End System 2 ;  
      the ME of Ethernet End System 2  receives the ETH-AIS message, and sends a reverse alarm ETH-RDI message to the direction of Ethernet End System 1 .  
      The second case is: the IWF 2  fault impacts the OAM function of the Ethernet part in IWF 2 , then the processing includes:  
      when the OAM function of the Ethernet part in IWF 2  does not work normally, the ME of Ethernet End System 2  receives the ETH-CC message sent by the opposite end, and enters the fault state;  
      the ME of Ethernet End System 2  sends the ETH-RDI message to the direction of the peer Ethernet End System 1  in the opposite end.  
      Obviously, in  FIG. 1 , it is likely that a fault occurs at the side of IWF 1  connected to the Ethernet. The corresponding processing is similar as the above, which will not be described further here.  
      As shown in scene  4  of  FIG. 2 , the process for handling a fault occurring in the interconnection LSP of the MPLS network can be categorized into two cases, which are described, respectively, as follows:  
      the first case is: the interconnection LSP fault is originated from the link layer bearing the MPLS LSP; and according to the protocol definition, the MPLS can acquire a link layer fault alarm indication through network management. The corresponding processing in this case includes:  
      the OAM in the MPLS translates the link layer alarm indication into the corresponding MPLS Forward Fault Indication (MPLS-FDI) message, and sends the message to IWF 2 ;  
      IWF 2  translates the received MPLS-FDI into the corresponding ETH-AIS message, and sends the message to Ethernet End System 2 ;  
      the ME of Ethernet End System 2 , upon receiving the ETH-AIS, sends a reverse alarm ETH-RDI message to the direction of Ethernet End System 1 .  
      The second case is: the interconnection LSP fault is originated from the MPLS LSP, and the corresponding processing in this case includes:  
      IWF 2  receives no MPLS-CV packet as the MPLS LSP has a fault, then IWF 2  translates the LSP fault into the corresponding ETH-AIS message and sends the message to the direction of Ethernet End System 2 ;  
      the ME of Ethernet End System  2  receives the ETH-AIS message, and sends a reverse alarm ETH-RDI to the direction of Ethernet End System 1 .  
      In the foregoing description of the fault alarm process for various faults, all the OAM packets, that is, the fault alarm messages, are handled by the following process of encapsulation/de-encapsulation defined in Y.1415.  
      As shown in  FIG. 1 , the Ethernet OAM packet sent from Ethernet End System 1  to the direction of Ethernet End System 2  needs to be encapsulated in IWF 1  into the MPLS packet according to the Y.1415 definition, and to be transmitted in the MPLS network; in IWF 2 , the corresponding MPLS packet needs to be de-encapsulated, then the Ethernet OAM packet is obtained, and will be transmitted to Ethernet End System 2 .  
      For the packet sent from Ethernet End System 2  to Ethernet End System 1 , the corresponding encapsulation/de-encapsulation process is symmetrical with the foregoing process, and no further description will be given.  
      To sum up, the embodiments of the present invention have defined the fault notification process under various fault conditions based on the Ethernet and MPLS network interworking model in Y.1415, thus implementing the end-to-end OAM implementation mechanism and effectively improving the service transmission reliability in the communication process of interworking network.  
      The foregoing are just preferred embodiments of this invention and are not used for limiting the protection scope thereof. Any modification, equivalent replacement and improvement under the spirit and principle of this invention should be covered by the protection scope of the present invention.