CN101145996A - Failure management method for interaction between Ethernet and multi-protocol label switching network - Google Patents
Failure management method for interaction between Ethernet and multi-protocol label switching network Download PDFInfo
- Publication number
- CN101145996A CN101145996A CNA2007101814986A CN200710181498A CN101145996A CN 101145996 A CN101145996 A CN 101145996A CN A2007101814986 A CNA2007101814986 A CN A2007101814986A CN 200710181498 A CN200710181498 A CN 200710181498A CN 101145996 A CN101145996 A CN 101145996A
- Authority
- CN
- China
- Prior art keywords
- ethernet
- end system
- message
- network
- mpls
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention relates to a fault management method for the Ethernet network intercommunicated with multi-protocol label switching network, which mainly includes monitoring the fault information occurring in an intercommunicated network by the Ethernet terminal system; and constructing corresponding alarm message when a fault occurs in the network, and transmitting the message to the Ethernet terminal system on the opposite terminal. The invention can transmit fault alarm information to corresponding peer at opposite terminal in time when a fault occurs in the intercommunicated network, thereby ensuring the intercommunication between the Ethernet and MPLS network, achieving terminal-to-terminal fault alarm management, and effectively improving task transmission reliability in communication process of intercommunication network.
Description
Technical field
The present invention relates to network communications technology field, relate in particular to the failure management method of a kind of Ethernet and multi-protocol tag exchange network interconnection.
Background technology
Along with the development of the network communications technology, Ethernet (Ethernet) is professional constantly to be developed to metropolitan area network, telecommunications network from local area network (LAN).In the ever-increasing Ethernet service of future generation of demand, MPLS (multiprotocol label switching) relies on its unique advantages to become first-selected network technology, and promptly Ethernet and MPLS business intercommunication become development trend.
The model of Ethernet and MPLS business intercommunication has been done the framework definition at ITU-T in Y.1415, simultaneously, in the PWE3 of IETF working group, made detailed regulation at Ethernet and MPLS intercommunication application draft draft (draft-ietf-pwe3-ethernet-encap-09.txt).Detailed regulation has been carried out in encapsulation when promptly moving in MPLS at the Ethernet business.
In the model of Ethernet and MPLS business intercommunication, not only need to carry out corresponding encapsulated delivery and handle, simultaneously; also need corresponding fault warning mechanism, realize when breaking down, can in time finding; so that take the corresponding protection measure, guarantee reliability of service transmission.Yet in existing corresponding draft, the fault warning intercommunication mechanism at the OAM (Operation and Maintenance) of Ethernet and MPLS business intercommunication does not but provide corresponding solution.
At present, ITU-T publish Y.1711 in only the fault detection mechanism in the MPLS network has been made detailed regulation.And, promptly how to realize the fault warning administrative mechanism in Ethernet and the MPLS business intercommunication model for how solving MPLS and the end-to-end OAM of Ethernet intercommunication network (Operation and Maintenance) mechanism, still there is not corresponding solution.
Do not provide corresponding solution just because of present fault warning intercommunication mechanism at Ethernet and MPLS OAM, make for OAM mechanism neither one total solution end to end, thereby also just can't guarantee the reliability of Ethernet and MPLS business intercommunication.
Summary of the invention
In view of above-mentioned existing in prior technology problem, the purpose of this invention is to provide the failure management method of a kind of Ethernet and multi-protocol tag exchange network interconnection, realize when breaking down, can in time finding, guarantee reliability of service transmission.
The objective of the invention is to be achieved through the following technical solutions:
The invention provides the failure management method of a kind of Ethernet and multi-protocol tag exchange network interconnection, comprising:
A, in intercommunication network, the fault message that occurs in the ethernet end system monitoring intercommunication network;
B, when in monitoring network, breaking down, then construct the fault alarm message, and to ethernet end system is sent.
Described steps A comprises:
When ethernet end system is received Ethernet alarm indication message or do not received the Ethernet detection messages that the opposite end ethernet end system sends, determine to break down in the intercommunication network.
Among the present invention, when Ethernet broke down, described steps A comprised:
A1, the ethernet end system that breaks down send Ethernet alarm indication message to the opposite end ethernet end system;
After A2, opposite end ethernet end system are received described message, determine that intercommunication network breaks down.
Described steps A 1 comprises:
The maintenance entity place of the ethernet end system that breaks down inserts forward direction Ethernet alarm indication message, and sends to the opposite end ethernet end system.
Among the present invention, the interworking function entity in intercommunication network breaks down, and causes the MPLS network can't operate as normal the time, and described steps A also comprises:
The interworking function entity of described interworking function entity opposite end will detect the label switching path LSP fault, and send Ethernet alarm indication message to the ethernet end system of correspondence.
Described steps A also comprises:
The interworking function entity of described opposite end is not received when MPLS connects the availability verification message, is determined that corresponding LSP breaks down.
Among the present invention, when the link layer of carrying LSP broke down, described steps A also comprised:
A3, multiprotocol label switching MPLS network send the indication of MPLS forward direction defective by the ethernet end system of middle interworking function entity to correspondence;
A4, described intermediate function entity receive that described MPLS predecessor's defective indication back generates Ethernet alarm indication message, and send to the ethernet end system of described correspondence.
Among the present invention, when LSP broke down, described steps A also comprised:
When interworking function entity does not receive that MPLS connects the availability verification message, generate corresponding Ethernet alarm indication message, and send to the ethernet end system of correspondence.
Described step B comprises:
When in monitoring network, breaking down, then construct Ethernet remote bug indication information message, and send to the opposite end ethernet end system.
The failure management method of described Ethernet and multi-protocol tag exchange network interconnection also comprises:
The message that ethernet end system transmits warning information to opposite end ethernet end system being used to of sending need carry out handling based on the encapsulation or the decapsulation of mpls protocol during through interworking function entity.
As seen from the above technical solution provided by the invention, the present invention is Ethernet and the MPLS business intercommunication model based on Y.1415 middle definition, provide when MPLS is professional as backbone network carrying Ethernet, at the respective handling flow process of the fault notification under the various defect states.Be that the present invention has realized can sending fault warning information to corresponding opposite end peer-to-peer in time when breaking down in the intercommunication network; thereby can effectively guarantee in Ethernet and the MPLS network interworking; the end-to-end management that can realize at the fault warning that occurs; an end entity of being convenient to obtain corresponding fault warning information can adopt the corresponding protection measure, effectively improves reliability of service transmission in the intercommunication network communication process.
Description of drawings
Fig. 1 is the model schematic diagram of Ethernet and MPLS business intercommunication;
Fig. 2 is the specific implementation process schematic diagram of the method for the invention.
Embodiment
The present invention mainly be for realize MPLS as bearer network carrying Ethernet the OAM IWF when professional.Thereby can on based on Ethernet in Y.1415 and MPLS IWF model basis, realize the fault notification in the OAM IWF model under the various defect states, guarantee the end-to-end OAM management of Ethernet and MPLS network interworking.
In Y.1415, Ethernet that provides and MPLS business intercommunication model are as shown in Figure 1.
Ethernet end system Ethernet End System 1 and Ethernet End System 2 peer-to-peer each other among Fig. 1 when an end monitors when breaking down, needs the notice opposite end; When monitoring on interworking function entity IWF1 or the IWF2 when breaking down, then need to notify the Ethernet EndSystem1 or the Ethernet End System2 that are adjacent.
Perception is less than the existence of MPLS network between Ethernet End System (ethernet end system).Between IWF (IWF), therefore existence that then can perception MPLS network, need realize the function of OAM intercommunication between Ethernet and MPLS, and IWF is a functional entity of realizing the OAM intercommunication.In Core MPLS (center MPLS) network, have only the related entities of MPLS to exist.
In intercommunication network model shown in Figure 1, the fault that may occur specifically comprises:
(1) upstream/downstream Ethernet fault, promptly ethernet end system breaks down;
(2) upstream IWF (IWF1) fault;
(3) downstream IWF (IWF2) fault;
(4) lsp failure that interconnects in the MPLS network.
For the present invention there being further understanding, respectively the fault warning processing procedure of the various faults that may occur is described respectively below in conjunction with illustrated in figures 1 and 2.
The main handling process of method of the present invention as shown in Figure 1, comprising:
When ethernet end system 2 is received the Ethernet alarm indication signal, when perhaps ethernet end system 2 is not received the ETH-CC that ethernet end system sends (Ethernet connect check) message within the predetermined time, then will be that ethernet end system 1 sends Ethernet remote bug indication message to the peer-to-peer of opposite end, to notify ethernet end system 1 with the fault message in the intercommunication network.Described Ethernet alarm indication signal can also can be sent for the IWF2 (IWF) with ethernet end system 2 adjacency for what sent by ethernet end system 1.
Shown in sight among Fig. 21, comprise for the upstream/downstream Ethernet fault handling process that occurs:
Locate to insert forward alarm ETH-AIS (Ethernet alarm indication signal) message at Ethernet (is example with the Ethernet End System1) ME (maintenance entity) that produces fault, send alarm notification to EthernetEnd System2 direction;
After Ethernet End System2 receives ETH-AIS, can produce the ME place of reverse ETH-RDI (indication of Ethernet remote bug) message to opposite end Ethernet End System1;
ETH-AIS message and ETH-RDI message all need the processing procedure through encapsulation/decapsulation when passing through the MPLS network.
On/handling process basically identical during the Ethernet fault of downstream, the base only is not:
(1) the position difference of insertion forward alarm: during the Ethernet fault of upstream, insert ETH-AIS at Ethernet node M E place, upstream, during the Ethernet fault of downstream, insert ETH-AIS at Ethernet node M E place, downstream;
(2) owing to the insertion position difference, the ETH-AIS message that upstream node produces need pass through the MPLS network, according to the form encapsulation ETH-AIS message of Y.1415 definition, passes through the MPLS network, decapsulation ETH-AIS message in IWF2 at the IWF1 place; The ETH-AIS message that produces for downstream node then need encapsulate the ETH-AIS message by the form according to Y.1415 definition at IWF2 place, pass through the MPLS network after, decapsulation ETH-AIS message in IWF1.
Shown in sight among Fig. 22, the fault that upstream IWF (being the IWF1 among Fig. 1) is occurred promptly is connected the processing procedure that side breaks down and comprises with the MPLS network among the IWF:
The fault that upstream IWF1 occurs specifically can be divided into two kinds of different situations and be described respectively.
First kind of situation is: the IWF1 fault does not influence the OAM(Operation Administration Maintenance) of MPLS part among the IWF1, and corresponding processing procedure comprises:
In this case, the MPLS LSP operate as normal of carrying Ethernet service, promptly LSP can not produce fault warning; But because the ETH-CC that the fault of IWF1 makes Ethernet End System2 ME place can not receive opposite end Ethernet End System1 ME sends (Ethernet connects inspection) message;
Therefore, the ME of Ethernet End System2 will enter malfunction, and send reverse alarm ETH-RDI indication to EthernetEnd System1 direction.
Second kind of situation is: the OAM(Operation Administration Maintenance) of MPLS part among the IWF1 fault effects IWF1, and corresponding processing procedure comprises:
In this case, MPLS part of O AM function cisco unity malfunction among the IWF1, MPLS-CV among the IWF1 (MPLS connects availability verification) message can not normally send, and will detect the lsp failure state in the LSP of IWF2 terminal;
IWF2 corresponds to the ETH-AIS message with the malfunction of LSP, and is sent to Ethernet EndSystem2;
After Ethernet End System2 ME receives the ETH-AIS message, send reverse alarm ETH-RDI indication to Ethernet EndSystem1 direction.
Certainly, IWF2 is connected side and also may breaks down among Fig. 1 with MPLS, and at this moment, corresponding processing procedure is similar with above-mentioned processing procedure, so detailed description no longer.
Shown in sight among Fig. 23, break down for downstream IWF (IWF2), promptly be connected the processing procedure that side breaks down among the IWF with ethernet network and comprise:
The processing tool that breaks down for downstream IWF2 can body be divided into two kinds of different situations to be described respectively.
First kind of situation is: the IWF2 fault does not influence the situation of the OAM(Operation Administration Maintenance) of Ethernet part among the IWF2, specifically comprises:
When breaking down in the IWF2 place, and the OAM(Operation Administration Maintenance) of the part of the Ethernet among the IWF2 just often, and the OAM(Operation Administration Maintenance) of Ethernet part can correspond to the IWF2 fault ETH-AIS and mail to the EndSystem2 place among the IWF2;
At the ME place of End System2, when receiving ETH-AIS, send reverse alarm ETH-RDI indication to Ethernet End System1 direction.
Second kind of situation is: the situation of the OAM(Operation Administration Maintenance) of Ethernet part among the IWF2 fault effects IWF2 specifically comprises:
When among the IWF2 during Ethernet part of O AM function cisco unity malfunction, enter malfunction thereby will cause the ME of End System2 to can not receive the ETH-CC message of sending the opposite end;
The ME of Ethernet End System2 will send to opposite end peer-to-peer Ethernet End System1 direction and be sent to ETH-RDI alarm indication.
Certainly, IWF1 is connected side and also may breaks down among Fig. 1 with ethernet network, and at this moment, corresponding processing procedure is similar with above-mentioned processing procedure, so detailed description no longer.
Shown in sight among Fig. 24, the processing procedure that breaks down for interconnection LSP comprises:
The fault that occurs for the LSP of interconnection specifically can be divided into two kinds of situations and describe respectively.
First kind of situation is: the described source of trouble is from the link layer that carries MPLS LSP, and corresponding processing procedure comprises:
The link layer fault can be by MPLS-FDI or by webmaster announcement link layer fault;
MPLS OAM(Operation Administration Maintenance) entity corresponds to MPLS-FDI with the alarm of link layer indication and sends to EthernetEnd System2;
At the IWF2 place, correspond to the ETH-AIS message and continue to send;
At the ME place of End System2, receive the ETH-AIS message after, will send reverse alarm ETH-RDI indication to Ethernet EndSystem1 direction.
Second kind of situation is: the source of trouble is from MPLS LSP itself, and corresponding processing procedure comprises:
When the MPLS lsp failure, because can not receive the MPLS-CV message, IWF2 corresponds to ETH-AIS to lsp failure and mails to Ethernet End System2 direction at the IWF2 place;
At the ME place of Ethernet End System2, when receiving ETH-AIS, send reverse alarm ETH-RDI indication to Ethernet EndSystem1 direction.
In the description of above-mentioned fault warning processing procedure at various faults, the flow process of the encapsulation/decapsulation of regulation during Y.1415 all OAM messages (being the fault warning message) are all followed.
Referring to shown in Figure 1, send to the Ethernet OAM message of Ethernet End System2 direction from Ethernet End System1, described Ethernet OAM message need be encapsulated as the MPLS message according to Y.1415 regulation at the IWF1 place, and in the MPLS network, transmit; At the IWF2 place, need carry out decapsulation to corresponding M PLS message and handle, and obtain described Ethernet OAM message, be sent to Ethernet End System2 place then.
For the message that sends to Ethernet End System1 direction from Ethernet End System2, corresponding encapsulation/decapsulation handling process and above-mentioned processing procedure symmetry are so no longer describe in detail.
In sum, the present invention is based on Y.1415 middle Ethernet and MPLS business intercommunication model, defined, realized end-to-end OAM realization mechanism when fault notification flow process under the various defect situation occurring.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (10)
1. the failure management method of Ethernet and multi-protocol tag exchange network interconnection is characterized in that, comprising:
A, in intercommunication network, the fault message that occurs in the ethernet end system monitoring intercommunication network;
B, when in monitoring network, breaking down, then construct the fault alarm message, and to ethernet end system is sent.
2. the failure management method of Ethernet according to claim 1 and multi-protocol tag exchange network interconnection is characterized in that, it is characterized in that, described steps A comprises:
When ethernet end system is received Ethernet alarm indication message or do not received the Ethernet detection messages that the opposite end ethernet end system sends, determine to break down in the intercommunication network.
3. the failure management method of Ethernet according to claim 2 and multi-protocol tag exchange network interconnection is characterized in that, when Ethernet broke down, described steps A comprised:
A1, the ethernet end system that breaks down send Ethernet alarm indication message to the opposite end ethernet end system;
After A2, opposite end ethernet end system are received described message, determine that intercommunication network breaks down.
4. the failure management method of Ethernet according to claim 3 and multi-protocol tag exchange network interconnection is characterized in that, described steps A 1 comprises:
The maintenance entity place of the ethernet end system that breaks down inserts forward direction Ethernet alarm indication message, and sends to the opposite end ethernet end system.
5. the failure management method of Ethernet according to claim 2 and multi-protocol tag exchange network interconnection, it is characterized in that, interworking function entity in intercommunication network breaks down, and causes the MPLS network can't operate as normal the time, and described steps A also comprises:
The interworking function entity of described interworking function entity opposite end will detect the label switching path LSP fault, and send Ethernet alarm indication message to the ethernet end system of correspondence.
6. the failure management method of Ethernet according to claim 5 and multi-protocol tag exchange network interconnection is characterized in that, described steps A also comprises:
The interworking function entity of described opposite end is not received when MPLS connects the availability verification message, is determined that corresponding LSP breaks down.
7. the failure management method of Ethernet according to claim 2 and multi-protocol tag exchange network interconnection is characterized in that, when the link layer of carrying LSP broke down, described steps A also comprised:
A3, multiprotocol label switching MPLS network send the indication of MPLS forward direction defective by the ethernet end system of middle interworking function entity to correspondence;
A4, described intermediate function entity receive that described MPLS predecessor's defective indication back generates Ethernet alarm indication message, and send to the ethernet end system of described correspondence.
8. the failure management method of Ethernet according to claim 2 and multi-protocol tag exchange network interconnection is characterized in that, when LSP broke down, described steps A also comprised:
When interworking function entity does not receive that MPLS connects the availability verification message, generate corresponding Ethernet alarm indication message, and send to the ethernet end system of correspondence.
9. according to the failure management method of each described Ethernet of claim 1 to 8 and multi-protocol tag exchange network interconnection, it is characterized in that described step B comprises:
When in monitoring network, breaking down, then construct Ethernet remote bug indication information message, and send to the opposite end ethernet end system.
10. the failure management method of Ethernet according to claim 9 and multi-protocol tag exchange network interconnection is characterized in that, this method also comprises:
The message that ethernet end system transmits warning information to opposite end ethernet end system being used to of sending need carry out handling based on the encapsulation or the decapsulation of mpls protocol during through interworking function entity.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101814986A CN101145996B (en) | 2005-04-15 | 2005-04-15 | Failure management method for interaction between Ethernet and multi-protocol label switching network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101814986A CN101145996B (en) | 2005-04-15 | 2005-04-15 | Failure management method for interaction between Ethernet and multi-protocol label switching network |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200510064584XA Division CN100502303C (en) | 2005-04-15 | 2005-04-15 | Method for managing fault of Ethernet and multi-protocol tag exchange network interconnection |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101145996A true CN101145996A (en) | 2008-03-19 |
| CN101145996B CN101145996B (en) | 2011-08-24 |
Family
ID=39208309
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101814986A Expired - Fee Related CN101145996B (en) | 2005-04-15 | 2005-04-15 | Failure management method for interaction between Ethernet and multi-protocol label switching network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101145996B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112714006A (en) * | 2019-10-24 | 2021-04-27 | 中兴通讯股份有限公司 | Link fault state notification method, device, equipment and medium |
| CN117978612A (en) * | 2024-03-28 | 2024-05-03 | 成都格理特电子技术有限公司 | Network fault detection method, storage medium and electronic equipment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7092361B2 (en) * | 2001-12-17 | 2006-08-15 | Alcatel Canada Inc. | System and method for transmission of operations, administration and maintenance packets between ATM and switching networks upon failures |
| US7088674B2 (en) * | 2001-12-27 | 2006-08-08 | Alcatel Canada Inc. | Method and apparatus for checking continuity of leaf-to-root VLAN connections |
| CN1553637A (en) * | 2003-05-29 | 2004-12-08 | 烽火通信科技股份有限公司 | Fault indicating technology for Ethernet optical fibre transceiver |
-
2005
- 2005-04-15 CN CN2007101814986A patent/CN101145996B/en not_active Expired - Fee Related
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112714006A (en) * | 2019-10-24 | 2021-04-27 | 中兴通讯股份有限公司 | Link fault state notification method, device, equipment and medium |
| CN112714006B (en) * | 2019-10-24 | 2024-05-17 | 中兴通讯股份有限公司 | Link fault state notification method, device, equipment and medium |
| CN117978612A (en) * | 2024-03-28 | 2024-05-03 | 成都格理特电子技术有限公司 | Network fault detection method, storage medium and electronic equipment |
| CN117978612B (en) * | 2024-03-28 | 2024-06-04 | 成都格理特电子技术有限公司 | Network fault detection method, storage medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101145996B (en) | 2011-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100502303C (en) | Method for managing fault of Ethernet and multi-protocol tag exchange network interconnection | |
| CN100365998C (en) | System and method for implementing OAM function of ethernet and multi-protocol tag exchange network | |
| US8804534B2 (en) | Interworking between MPLS/IP and Ethernet OAM mechanisms | |
| US8886831B2 (en) | System and methodology for fast link failover based on remote upstream failures | |
| CN101316225B (en) | Fault detection method, communication system and label exchange router | |
| CN100512292C (en) | Apparatus and method of real-time recovering service | |
| CN103178971B (en) | PON guard method and device | |
| EP1978681B1 (en) | Methods and devices for judging pw connection state and notifying ac connection state | |
| US7839795B2 (en) | Carrier Ethernet with fault notification | |
| US20090196172A1 (en) | Method and apparatus for ethernet ring protection | |
| US20090199040A1 (en) | Method and device for implementing link pass through in point-to-multipoint network | |
| CN100359860C (en) | Multiprotocol label switching network protection switching method | |
| EP3323227B1 (en) | Restoring an mpls ring network | |
| WO2006034645A1 (en) | A method for processing the failure between the egress lsr and the data equipment connected therewith | |
| WO2011015011A1 (en) | Method and system for ring network fault detection and locating | |
| EP2129042B1 (en) | A multicast network system, node and a method for detecting a fault of a multicast network link | |
| CN102611610B (en) | The method and system of a kind of many same paths tunnels centralized management | |
| JP2009212863A (en) | Line status monitoring circuit, node, communication system, and failure occurrence determining method | |
| WO2011020257A1 (en) | Method and apparatus for notifying failure lsp information | |
| CN101599873B (en) | Detection method of connectivity and device therefor | |
| CN101145996B (en) | Failure management method for interaction between Ethernet and multi-protocol label switching network | |
| CN101494801B (en) | Method, system and network appliance for fault recovery | |
| CN1917439B (en) | Method of fault management in intercommunication network between Ethernet and MPLS | |
| JP5040862B2 (en) | SCTP association aggregation apparatus, communication system including the apparatus, and routing method | |
| JP2014090260A (en) | Packet transmission system, and packet transmission quality detection method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110824 Termination date: 20160415 |