CN103746841A - Failure recovery method and controller - Google Patents

Failure recovery method and controller Download PDF

Info

Publication number
CN103746841A
CN103746841A CN201310744223.4A CN201310744223A CN103746841A CN 103746841 A CN103746841 A CN 103746841A CN 201310744223 A CN201310744223 A CN 201310744223A CN 103746841 A CN103746841 A CN 103746841A
Authority
CN
China
Prior art keywords
controller
node
photosphere
layer
path
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.)
Pending
Application number
CN201310744223.4A
Other languages
Chinese (zh)
Inventor
宋雪飞
夏寅贲
郭宏翔
张东旭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201310744223.4A priority Critical patent/CN103746841A/en
Publication of CN103746841A publication Critical patent/CN103746841A/en
Priority to PCT/CN2014/093842 priority patent/WO2015101168A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/28Routing or path finding of packets in data switching networks using route fault recovery

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the invention provides a failure recovery method. The failure recovery method comprises the steps of obtaining first topological information by a first controller, wherein the first topological information comprises topological information of an IP (Internet Protocol) layer, topological information of an optical layer and information of an interlayer link, and the interlayer link is a link between a node of the IP layer and a node of the optical layer; obtaining failure information by the first controller, wherein the failure information at least comprises failure information of the optical layer; determining business related to the failure information and a business failure path of the business by the first controller according to the failure information; determining a business recovery path of the business failure path by the first controller according to the first topological information and the failure information, wherein the business recovery path is used for transmitting the business. According to the failure recovery method provided by the embodiment of the invention, the whole-network topological information and the whole-network failure information of an IP-over-Optical network can be obtained through the first controller, the business recovery path can be further determined, thus the optimal business recovery path can be provided according to whole-network topology, and the consumed time for failure recovery is shorter.

Description

The method of fault recovery and controller
Technical field
The embodiment of the present invention relates to the communications field, and more specifically, relates to a kind of method and controller of fault recovery.
Background technology
In IP-over-Optical network model, procotol (Internet Proticol, IP) layer photoreactive layer controlled respectively independently of each other, not dynamic collaborative between two two-layer control planes.
While breaking down in IP-over-Optical network, what generally take is the mode based on holdoff-timer.Preferentially carry out photosphere recovery, photosphere recovers unsuccessfully or after overtime, carries out the recovery of IP layer again.The mode of this holdoff-timer generally realizes by timer being set at IP layer.In IP-over-Optical network, break down, and this fault causes the time of service disconnection to surpass at timer after set time period, IP layer just can carry out path recovery.
For example, when the photosphere in IP-over-Optical network breaks down, a kind ofly may be: at timer, in set time period, the control plane of photosphere does not complete photosphere and recovers.So at timer after set time period, just further by the control plane of IP layer, carry out the recovery of IP layer.
And wherein, the control plane of photosphere does not complete the reason that photosphere recovers, be likely that the set time period of timer is too short, cause the control plane of photosphere not have time enough to complete photosphere recovery.But if the set time period long enough of timer, when the control plane ability of photosphere does not complete photosphere recovery, the control plane of IP layer carries out the recovery of IP layer again after also needing to wait for the sufficiently long time so.Can cause the overlong time of fault recovery like this, also further cause the overlong time of service disconnection.
Summary of the invention
The embodiment of the present invention provides a kind of method of fault recovery, can solve the problem of the overlong time of IP-over-Optical network disaster recovery.
First aspect, a kind of method of fault recovery is provided, comprise: the first controller obtains the first topology information, described the first topology information comprises the topology information of procotol IP layer, the information of the topology information of photosphere and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere; Described the first controller obtains fault message, and described fault message at least comprises the fault message of described photosphere; Described the first controller, according to described fault message, is determined the business relevant with described fault message and the traffic failure path of described business; Described the first controller, according to described the first topology information and described fault message, is determined the business recovery path in described traffic failure path, and described business recovery path is for the transmission of described business.
In conjunction with first aspect, in the possible implementation of the first, after the business recovery path in described definite described traffic failure path, described method also comprises: described the first controller is sent to second controller by the first configuration information, described the first configuration information configures the path relevant with the node of described photosphere, described business recovery path for described second controller on the node of described photosphere, wherein, described the first configuration information is the relevant configuration information of the node with described photosphere in described business recovery path.
In conjunction with the possible implementation of the first of first aspect, in the possible implementation of the second, described the first controller is master controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described method also comprises: described the first controller is sent to IP layer controller by the second configuration information, described the second configuration information configures the path relevant with the node of described IP layer, described business recovery path for described IP layer controller on the node of described IP layer, wherein, described the second configuration information is the relevant configuration information of the node with described IP layer in described business recovery path.
In conjunction with the possible implementation of the first of first aspect, in the third possible implementation, described the first controller is IP layer controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described method also comprises: described the first controller configures path relevant with the node of described IP layer in described business recovery path on the node of described IP layer.
In conjunction with first aspect or above-mentioned any possible implementation, in the 4th kind of possible implementation, the topology information of described photosphere is obtained from described second controller by described the first controller, and the information of described interlayer link is obtained from described second controller by described the first controller.
In conjunction with first aspect or above-mentioned any possible implementation, in the 5th kind of possible implementation, described the first controller is according to described the first topology information and described fault message, determine the business recovery path in described traffic failure path, comprise: described the first controller is according to described the first topology information and described fault message, determine the second topology information, the new topology information of the described photosphere comprising in described the second topology information is different from the topology information of the described photosphere comprising in described the first topology information; Described the first controller, according to described the second topology information, is determined the described business recovery path in described traffic failure path.
In conjunction with first aspect or above-mentioned any possible implementation, in the 6th kind of possible implementation, described fault message also comprises: the fault message of the fault message of described IP layer and/or described interlayer link.
Second aspect, provides a kind of method of fault recovery, comprising: second controller obtains the fault message of photosphere; Described second controller is sent to the first controller by the fault message of described photosphere, so that described the first controller is determined the business relevant with described fault message and the business recovery path of described business according to the fault message of described photosphere with topology information, described topology information comprises the information of the topology information of described photosphere, the topology information of procotol IP layer and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere.
In conjunction with second aspect, in the possible implementation of the first, described method also comprises: described second controller obtains the topology information of photosphere; Described second controller is sent to described the first controller by the topology information of described photosphere.
In conjunction with the possible implementation of the first of second aspect or second aspect, in the possible implementation of the second, described method also comprises: described second controller receives the configuration information that described the first controller sends, and described configuration information is the relevant configuration information of the node with described photosphere in described business recovery path; Described second controller configures path relevant with the node of described photosphere in described business recovery path on the node of described photosphere according to described configuration information.
In conjunction with second aspect or above-mentioned any possible implementation, in the third possible implementation, described second controller is sent to the first controller by the fault message of described photosphere, comprise: described second controller, according to recovery policy, is determined the fault message of described photosphere is sent to described the first controller.
The third aspect, a kind of controller is provided, described controller comprises: the first acquiring unit, be used for obtaining the first topology information, described the first topology information comprises the topology information of procotol IP layer, the information of the topology information of photosphere and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere; Second acquisition unit, for obtaining fault message, described fault message at least comprises the fault message of described photosphere; The first determining unit, for the described fault message obtaining according to described second acquisition unit, determines the business relevant with described fault message and the traffic failure path of described business; The second determining unit, the described fault message obtaining for described the first topology information of obtaining according to described the first acquiring unit and described second acquisition unit, determine the business recovery path in the described traffic failure path that described the first determining unit is determined, described business recovery path is for the transmission of described business.
In conjunction with the third aspect, in the possible implementation of the first, described controller also comprises: transmitting element, be used for: the first configuration information is sent to another controller, described the first configuration information configures the path relevant with the node of described photosphere, described business recovery path for described another controller on the node of described photosphere, wherein, described the first configuration information is the relevant configuration information of the node with described photosphere in described business recovery path.
In conjunction with the possible implementation of the first of the third aspect, in the possible implementation of the second, described controller is master controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described transmitting element, also for: the second configuration information is sent to IP layer controller, described the second configuration information configures the path relevant with the node of described IP layer, described business recovery path for described IP layer controller on the node of described IP layer, wherein, described the second configuration information is the relevant configuration information of the node with described IP layer in described business recovery path.
In conjunction with the possible implementation of the first of the third aspect, in the third possible implementation, described controller is IP layer controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described transmitting element, also for: on the node of described IP layer, configure the path relevant with the node of described IP layer, described business recovery path.
In conjunction with the third aspect or above-mentioned any possible implementation, in the 4th kind of possible implementation, the topology information of described photosphere is that described controller obtains from described another controller, and the information of described interlayer link is that described controller obtains from described another controller.
In conjunction with the third aspect or above-mentioned any possible implementation, in the 5th kind of possible implementation, described the second determining unit, specifically for: according to described the first topology information and described fault message, determine the second topology information, the new topology information of the described photosphere comprising in described the second topology information is different from the topology information of the described photosphere comprising in described the first topology information; According to described the second topology information, determine the described business recovery path in described traffic failure path.
In conjunction with the third aspect or above-mentioned any possible implementation, in the 6th kind of possible implementation, described fault message also comprises: the fault message of the fault message of described IP layer and/or described interlayer link.
Fourth aspect, provides a kind of controller, and described controller comprises: the first acquiring unit, for obtaining the fault message of photosphere; The first transmitting element, fault message for described photosphere that described the first acquiring unit is obtained is sent to the first controller, so that described the first controller is determined the business relevant with described fault message and the business recovery path of described business according to the fault message of described photosphere with topology information, described topology information comprises the information of the topology information of described photosphere, the topology information of procotol IP layer and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere.
In conjunction with fourth aspect, in the possible implementation of the first, described controller also comprises: second acquisition unit, also for obtaining the topology information of photosphere; The second transmitting element, also the topology information for described photosphere that described second acquisition unit is obtained is sent to described the first controller.
In conjunction with the possible implementation of the first of fourth aspect or fourth aspect, in the possible implementation of the second, described controller also comprises: receiving element, the configuration information sending for receiving described the first controller, described configuration information is the relevant configuration information of the node with described photosphere in described business recovery path; Dispensing unit configures the path relevant with the node of described photosphere, described business recovery path for the described configuration information receiving according to described receiving element on the node of described photosphere.
In conjunction with fourth aspect or above-mentioned any possible implementation, in the third possible implementation, described the first acquiring unit, specifically for: according to recovery policy, determine the fault message of described photosphere is sent to described the first controller.
The embodiment of the present invention is obtained the topology information of the whole network and the fault message of the whole network of IP-over-Optical network by the first controller, and further determines business recovery path.Can provide optimum business recovery path according to full mesh topology like this, and fault recovery is consuming time shorter.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme of the embodiment of the present invention, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the schematic diagram of IP-over-Optical network.
Fig. 2 is the schematic diagram of a scene of the embodiment of the present invention.
Fig. 3 is the flow chart of method of the fault recovery of one embodiment of the invention.
Fig. 4 is the flow chart of method of the fault recovery of another embodiment of the present invention.
Fig. 5 is the flow chart of method of the fault recovery of another embodiment of the present invention.
Fig. 6 is the flow chart of method of the fault recovery of another embodiment of the present invention.
Fig. 7 is the block diagram of the controller of one embodiment of the invention.
Fig. 8 is the block diagram of the controller of another embodiment of the present invention.
Fig. 9 is the block diagram of the controller of another embodiment of the present invention.
Figure 10 is the block diagram of the controller of another embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Embodiment based in the present invention, those of ordinary skills, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
Fig. 1 is the schematic diagram of IP-over-Optical network.Solid box shown in Fig. 1 represents IP layer, and dotted line frame represents photosphere.Node 101 to 104 is wherein the node of IP layer, the node that node 105 to 107 is photosphere.
Suppose, business node 101 in the IP-over-Optical network shown in Fig. 1 to the actual transmission paths of node 104 is: node 101 → node 102 → node 105 → node 107 → node 104.IP aspect, this transmission path is node 101 → node 102 → node 104, as shown in the solid black lines arrow in Fig. 1.
When the node 105 of photosphere and the link occurs fault between node 107, as the star representation node 105 in Fig. 1 and the fiber cut failure between node 107.Now, node 105 and node 107 can be found the loss of light signal, just carry out the protection switching operation of photosphere.For example, the light path between node 105 and node 107 is switched to node 105 → node 106 → node 107.Now, the node 101 of IP layer to the actual transmission paths of node 104 becomes: node 101 → node 102 → node 105 → node 106 → node 107 → node 104.But IP aspect, this transmission path is still node 101 → node 102 → node 104.
On the other hand, the mechanism that has similar heartbeat detection between the node of IP layer maintains the connection between node.When the time that heartbeat between node 102 and node 104 is interrupted surpasses the holdoff timer that it sets in advance, just think that fault has appearred in the link between node 102 and node 104, now IP layer just starts quick heavy-route (Fast Route Restoration, FRR).For example, node 101 can be switched to node 101 → node 103 → node 104 to the transmission path of node 104, and this is the transmission path IP aspect, as shown in the black dotted lines arrow in Fig. 1.And now node 101 to the actual transmission paths of node 104 becomes: node 101 → node 103 → node 106 → node 107 → node 104.
Actual, while breaking down, first by photosphere, carry out protection switching operation in IP-over-Optical network, if in the holdoff of IP layer timer, photosphere does not complete protection switching operation, just start FRR by IP layer.
Because IP layer photoreactive layer is separate, it is enough large that IP layer can only arrange holdoff timer, and guarantee photosphere is carried out the time of protection switching operation.But holdoff timer overlong time, can cause the overlong time of service disconnection.And, by the protection switching operation of photosphere, or the transmission path that redefines of the FRR by the IP layer optimal transmission paths in IP-over-Optical network not necessarily, the wasting of resources may be caused.
Fig. 2 is the schematic diagram of a scene of the embodiment of the present invention.Solid box shown in Fig. 2 represents IP layer, and dotted line frame represents photosphere.(Provider Edge, the PE) equipment 208 of Provider Edge wherein and PE equipment 209 are the PE equipment of IP layer, and node 201 to 205 is the node of IP layer, the node that node 211 to 215 is photosphere.
In the embodiment of the present invention, the node of IP layer can be router, can be also switch, or can be also other switching equipment, and the present invention is not construed as limiting this.The node of photosphere can be optical transfer network (Optical Transport Network, OTN) equipment, or can be dense wave division multipurpose (Dense Wavelength Division Multiplexing, DWDM) equipment, or can be also other light device, the present invention be not construed as limiting this.
Fig. 3 is the flow chart of method of the fault recovery of one embodiment of the invention.Method shown in Fig. 3 comprises:
301, the first controllers obtain the first topology information, and this first topology information comprises the topology information of IP layer, the information of the topology information of photosphere and interlayer link, and this interlayer link is the link between the node of IP layer and the node of photosphere.
302, the first controllers obtain fault message, and this fault message at least comprises the fault message of photosphere.
303, the first controllers, according to fault message, are determined the business relevant with fault message and the traffic failure path of this business.
304, the first controllers, according to the first topology information and fault message, are determined the business recovery path in traffic failure path, and this business recovery path is for the transmission of this business.
The embodiment of the present invention is obtained the topology information of the whole network and the fault message of the whole network of IP-over-Optical network by the first controller, and further determines business recovery path.Can provide optimum business recovery path according to full mesh topology like this, and fault recovery is consuming time shorter.
In the embodiment of the present invention, fault message comprises the number of fault, can be Single Point of Faliure, can be also multipoint fault.Single Point of Faliure refers to that in IP-over-Optical network, only having a fault, multipoint fault to refer to has at least two faults in IP-over-Optical network.
In the embodiment of the present invention, fault message also comprises the type of fault, can be node failure, can be also link failure.Node failure can be the node failure of IP layer, can be also the node failure of photosphere.Link failure can be the internodal link failure of IP layer, can be the internodal link failure of photosphere, can be also the fault of the interlayer link between IP layer photoreactive layer.Wherein, node failure can be that indivedual ports of node are malfunctioning, or can be also the fault of whole node, or can be also the fault of Cross module of the inside of node.Link failure can be link with node between be connected disconnection, can be also the disconnected fibre in the middle of link.
In the embodiment of the present invention, fault message also comprises location of fault.For example, be the fault of which node of which layer, or the fault of which bar link.
Particularly, in the embodiment of the present invention, fault message also can comprise the fault message of IP layer and/or the fault message of interlayer link.
Alternatively, in step 302, the first controller can directly obtain fault message from node or other controllers, also can be first from node or other controller receiving alarm information, further according to the content of warning information, determine fault message again, the present invention is not construed as limiting this.Wherein, warning information can include but not limited to node ID, port id, alarm level and event type.
In the embodiment of the present invention, the first controller can be IP layer controller, or can be also the master controller of IP-over-Optical network, and the present invention is not construed as limiting this.
Alternatively, the first controller can be master controller.
Particularly, in step 301, the first controller obtains the first topology information, can comprise: the topology information of obtaining IP layer from IP layer controller; From photosphere controller, obtain the topology information of photosphere; From IP layer controller or from the information of link between photosphere controller securing layer.And further can determine according to the information of the topology information of the topology information of IP layer, photosphere and interlayer link first topology information of the whole network of IP-over-Optical network.
In step 302, the first controller obtains fault message, can comprise: the fault message that obtains photosphere from photosphere controller.
Alternatively, as an embodiment, fault message also can comprise the fault message of IP layer and/or the fault message of interlayer link.Further, also can comprise the fault message that obtains IP layer from IP layer controller, also can comprise from IP layer controller or from the fault message of link between photosphere controller securing layer.
In step 303, the first controller is according to fault message, determines business that this fault message the affects path in this IP-over-Optical network, i.e. the traffic failure path of this business.
In step 304, the first controller can be determined the second topology information according to the first topology information and fault message.This second topology information is the new topology information of removing in the first topology information after the information of the link that fault message interrupts.And, the new topology information of the photosphere comprising in this second topology information is different from the topology information of the photosphere comprising in the first topology information.Further, the first controller can, according to the second topology information, be determined the business recovery path in traffic failure path.
Particularly, the second topology information comprises the new topology information of IP layer, the new topology information of photosphere and the fresh information of intermediate line link.And the new topology information of photosphere is different from the old topology information of photosphere.Wherein, the old topology information of said photosphere refers to the topology information of the photosphere in the first topology information of obtaining in step 301.
If fault message only includes the fault message of photosphere,, the new topology information of IP layer is identical with the old topology information of IP layer, and the fresh information of intermediate line link is identical with the old information of intermediate line link.If fault message comprises the fault message of photosphere and the fault message of IP layer,, the new topology information of IP layer is different from the old topology information of IP layer, and the fresh information of intermediate line link is identical with the old information of intermediate line link.If fault message comprises the fault message of photosphere and the fault message of interlayer link,, the new topology information of IP layer is identical with the old topology information of IP layer, and the fresh information of intermediate line link is different from the old information of intermediate line link.If fault message comprises the fault message of the fault message of photosphere, the fault message of IP layer and interlayer link,, the new topology information of IP layer is different from the old topology information of IP layer, and the fresh information of intermediate line link is different from the old information of intermediate line link.Wherein, the old topology information of said IP layer refers to the topology information of the IP layer in the first topology information of obtaining in step 301, and the old information of intermediate line link refers to the information of the intermediate line link in the first topology information of obtaining in step 301.
And, after step 304, the first controller can be sent to photosphere controller by the first configuration information, this first configuration information is for photosphere controller configuration service restoration path on the node of photosphere path relevant with the node of photosphere, and this first configuration information is the configuration information relevant with node photosphere in business recovery path.
If the relevant path of the node with IP layer in business recovery path, the path relevant with the node from IP layer in traffic failure path is different, the first controller also can be sent to the second configuration information IP layer controller, this second configuration information is for IP layer controller configuration service restoration path on the node of IP layer path relevant with the node of IP layer, and this second configuration information is the relevant configuration information of the node with IP layer in business recovery path.
Like this, the first controller can obtain the topology information of the whole network and the fault message of the whole network of IP-over-Optical network, can carry out in time fault recovery.
Alternatively, the first controller can be also IP layer controller.
Particularly, in step 301, the first controller obtains the first topology information, can comprise: directly obtain the topology information of IP layer and the information of interlayer link; From second controller, obtain the topology information of photosphere.Further, can determine according to the information of the topology information of the topology information of IP layer, photosphere and interlayer link first topology information of the whole network of IP-over-Optical network.The second controller here can be photosphere controller.
In step 302, the first controller obtains fault message, can comprise: the fault message that obtains photosphere from photosphere controller.
Alternatively, as an embodiment, fault message also can comprise the fault message of IP layer and/or the fault message of interlayer link.Further, also can comprise the fault message that obtains IP layer from the node of IP layer, from the node of IP layer or from the fault message of link between second controller securing layer.
In step 303, the first controller is according to fault message, determines business that this fault message the affects path in this IP-over-Optical network, i.e. the traffic failure path of this business.
In step 304, the first controller can be determined the second topology information according to the first topology information and fault message.This second topology information is the new topology information of removing in the first topology information after the information of the link that fault message interrupts.And, the new topology information of the photosphere comprising in this second topology information is different from the topology information of the photosphere comprising in the first topology information.Further, the first controller can, according to the second topology information, be determined the business recovery path in traffic failure path.
Particularly, the second topology information comprises the new topology information of IP layer, the new topology information of photosphere and the fresh information of intermediate line link.And the new topology information of photosphere is different from the old topology information of photosphere.Wherein, the old topology information of said photosphere refers to the topology information of the photosphere in the first topology information of obtaining in step 301.
If fault message only includes the fault message of photosphere,, the new topology information of IP layer is identical with the old topology information of IP layer, and the fresh information of intermediate line link is identical with the old information of intermediate line link.If fault message comprises the fault message of photosphere and the fault message of IP layer,, the new topology information of IP layer is different from the old topology information of IP layer, and the fresh information of intermediate line link is identical with the old information of intermediate line link.If fault message comprises the fault message of photosphere and the fault message of interlayer link,, the new topology information of IP layer is identical with the old topology information of IP layer, and the fresh information of intermediate line link is different from the old information of intermediate line link.If fault message comprises the fault message of the fault message of photosphere, the fault message of IP layer and interlayer link,, the new topology information of IP layer is different from the old topology information of IP layer, and the fresh information of intermediate line link is different from the old information of intermediate line link.Wherein, the old topology information of said IP layer refers to the topology information of the IP layer in the first topology information of obtaining in step 301, and the old information of intermediate line link refers to the information of the intermediate line link in the first topology information of obtaining in step 301.
Particularly, the first controller can, according to this second topology information, adopt unified resource allocation algorithm to determine business recovery path.That is to say, the first controller can be determined a business recovery path of relatively optimizing according to the occupation condition of IP-over-Optical the whole network, can guarantee like this transmission of this business, and can reduce the wasting of resources.
For example, even if fault message only includes the fault message of photosphere, this business recovery path is compared with traffic failure path, and the path of the path of possible photosphere and IP layer is all not identical.
And, after step 304, the first controller can be sent to second controller by the configuration information relevant with node photosphere in business recovery path, and this configuration information is for second controller configuration service restoration path on the node of photosphere path relevant with the node of photosphere.
Particularly, the first controller can be sent to second controller by configuration information relevant with the node of photosphere in business recovery path by protocol interface.
Further, the first controller can receive the feedback information that second controller sends, and this feedback information is that second controller sends after by the path configurations relevant with node photosphere success in business recovery path.
If the relevant path of the node with IP layer in business recovery path, the path relevant with the node from IP layer in traffic failure path is different, the first controller also can be on the node of IP layer the path relevant with the node of IP layer in configuration service restoration path.
Particularly, the form that the first controller can stream table is issued to the node of corresponding IP layer.
Alternatively, as an embodiment, after step 304, the first controller can discharge the shared resource of connection of interrupting because of fault message, and further upgrades because discharging the variation of the seizure condition of caused Internet resources.Thereby can guarantee the resource of using business recovery path to transmit.
Fig. 4 is the flow chart of method of the fault recovery of another embodiment of the present invention.Method shown in Fig. 4 comprises:
401, second controller obtains the fault message of photosphere.
402, second controller is sent to the first controller by the fault message of photosphere, so that the first controller is determined the business relevant with this fault message and the business recovery path of this business according to the fault message of this photosphere with topology information, this topology information comprises the information of the topology information of photosphere, the topology information of IP layer and interlayer link, and interlayer link is the link between the node of IP layer and the node of photosphere.
The embodiment of the present invention is obtained the topology information of the whole network and the fault message of the whole network of IP-over-Optical network by the first controller, and further determines business recovery path.Can provide optimum business recovery path according to full mesh topology like this, and fault recovery is consuming time shorter.
In the embodiment of the present invention, second controller is photosphere controller, and the first controller is IP layer controller or master controller.
Alternatively, as an embodiment, the method shown in Fig. 4 also can comprise: second controller obtains the topology information of photosphere, and the topology information of photosphere is sent to the first controller.
Alternatively, as another embodiment, the method shown in Fig. 4 also can comprise: second controller receives the configuration information that the first controller sends, and this configuration information is the configuration information relevant with node photosphere in business recovery path.Further, second controller is according to this configuration information path relevant with the node of photosphere in configuration service restoration path on the node of photosphere.
Particularly, the form that second controller can be shown by stream is issued to this configuration information the node of corresponding photosphere.
And, after second controller completes above-mentioned configuration, can discharge the shared resource of connection of interrupting because of fault message of photosphere, and further upgrade because discharging the variation of the seizure condition of caused Internet resources.Thereby can guarantee the resource of using business recovery path to transmit.
In step 401, second controller can directly obtain from the node of photosphere the fault message of photosphere, or, second controller can be first from the node receiving alarm information of photosphere, further according to the content of warning information, determine fault message again, the present invention is not construed as limiting this.
Particularly, the physical monitoring ability that the node of photosphere relies on node self to support, on the receive direction on interconnect port, monitor luminous power and sport 0 or while being reduced to certain threshold value, generate a corresponding warning information, and warning information is reported to second controller.Wherein, alarm information can include but not limited to node ID, port id, alarm level and event type.
Alternatively, as an embodiment, in step 401, second controller also can securing layer between the fault message of link.And correspondingly, in step 402, second controller can be sent to the first controller by the fault message of the fault message of photosphere and interlayer link.
Alternatively, in step 402, second controller can, according to recovery policy, be sent to the first controller by the fault message of this photosphere.Wherein, this recovery policy is stored on second controller, the strategy that this recovery policy is carried out fault recovery for this second controller.
Particularly, recovery policy when recovery policy can be IP layer and photosphere, now, after step 401, second controller does not carry out fault recovery, directly performs step 402, and fault message is sent to the first controller.And the first controller can be carried out the FRR of IP layer, and determine business recovery path according to the reserved resource of IP layer is reserved, or the reserved resource reserved according to the reserved resource of photosphere and IP layer simultaneously of the first controller is reserved and is determined business recovery path.
Or recovery policy can be the order recovery strategy of IP layer after first photosphere, now, after step 401, second controller can be carried out photosphere and switch according to the fault message of photosphere, determines the fault recovery path of photosphere.In step 402, the fault recovery path of the fault message photoreactive layer of photosphere is sent to the first controller in the lump again.Subsequently, the first controller can determine to adjust or do not adjust business recovery path according to the topology information of the whole network.
Or recovery policy can be the individual layer recovery policy of photosphere, now, after step 401, second controller can be according to the fault message of photosphere, and the reserved resource that execution sets in advance at photosphere is reserved and scheme is switched in interconnection, determines business recovery path.In this case, if second controller can complete the individual layer of photosphere, recover, second controller no longer performs step 402, and second controller is no longer sent to fault message the first controller.
Alternatively, this recovery policy can be operation management maintain (Operation Administration and Maintenance, the OAM) configuration information being stored in second controller.This recovery policy can be pre-configured.
The embodiment of the present invention for convenience of description, the embodiment in following Fig. 5 and Fig. 6 is usingd the scene shown in Fig. 2 as describing scene, and the business of take between the PE equipment 208 shown in Fig. 2 and PE equipment 209 is described as example.
As shown in Figure 2, PE equipment 208 can pass through node 201 or node 203 access networks, and PE equipment 209 can pass through node 205 access networks.And suppose that the service transmission path between PE equipment 208 and PE equipment 209 is PE equipment 208 → node 203 → node 213 → node 215 → node 205 → PE equipment 209.
Fig. 5 is the flow chart of method of the fault recovery of another embodiment of the present invention.Method shown in Fig. 5 comprises:
501, photosphere controller 207 obtains the topology information of photosphere.
The topology information of this photosphere comprises the annexation between each node of photosphere.
After step 501, the link generation fiber cut failure between node 213 and node 215.
502, photosphere controller 207 obtains the fault message of photosphere.
Particularly, on node 213 and the receive direction of node 215 on interconnect port, monitor luminous power and sport 0 or while being reduced to certain threshold value, generate respectively a corresponding warning information, and warning information is reported to photosphere controller 207.The warning information that photosphere controller 207 reports in conjunction with node 213 and node 215, can determine the fault message of photosphere.The fault message of this photosphere comprises location of fault: the link between node 213 and node 215, and the type of fault: disconnected fine.
503, photosphere controller 207 is sent to IP layer controller 206 by the fault message of the topology information photoreactive layer of photosphere.
Should note, in this step, photosphere controller 207 can be sent to IP layer controller 206 by the fault message of the topology information photoreactive layer of photosphere simultaneously, or, photosphere controller 207 also can successively be sent to IP layer controller 206 by the fault message of the topology information photoreactive layer of photosphere, and the present invention is not construed as limiting this.
Particularly, photosphere controller 207, according to recovery policy, is determined the fault message of photosphere is sent to IP layer controller 206.
504, IP layer controller 206 determined business and traffic failure path.
Particularly, IP layer controller 206 determines that according to the fault message of photosphere the business that this fault message affects is the business between PE equipment 208 and PE equipment 209, and can further determine that the traffic failure path of this business is: PE equipment 208 → node 203 → node 213 → node 215 → node 205 → PE equipment 209.
It should be noted that IP layer controller 206 determine traffic failure path according to determined business and the first topology information.Wherein, the first topology information refers to the topology information of the whole network that comprises IP layer photoreactive layer.
Particularly, IP layer controller 206 need be determined the first topology information according to the topology information of the topology information of the topology information of IP layer, photosphere and interlayer link.Wherein, the topology information of the topology information of IP layer and interlayer link is stored in this IP layer controller 206 in advance.
505, IP layer controller 206 determined business recovery path.
Particularly, IP layer controller 206 determined the second topology information according to the fault message of photosphere and the first topology information, and determine business recovery path according to the second topology information, and this business recovery path is for the business transmission between PE equipment 208 and PE equipment 209.
Wherein, the second topology information is the new topology information of removing in the first topology information after the information of the link that the fault message of photosphere interrupts, and between not having, connects between this second topology information instructs node 213 and node 215.
For example, suppose that IP layer controller 206 adopts the determined business recovery of unified resource allocation algorithm path to be: PE equipment 208 → node 203 → node 213 → node 214 → node 215 → node 205 → PE equipment 209.
506, IP layer controller 206 is sent to photosphere controller 207 by configuration information relevant with the node of photosphere in business recovery path.
Particularly, business recovery path is compared with traffic failure path, and the node of related IP layer is identical, and also identical through the transmission relation of the node of IP layer.In business recovery path and traffic failure path, the node of related IP layer is node 203 and node 205.And the upper hop of the equal instructs node 203 in business recovery path and traffic failure path is PE equipment 208, down hop is node 213.The upper hop of the equal instructs node 205 in business recovery path and traffic failure path is node 215, and down hop is PE equipment 209.Therefore, IP layer controller 206 do not need to reconfigure the information on node 203 and node 205.
Particularly, business recovery path is compared with traffic failure path, and the node of related photosphere is different.In traffic failure path, the node of related photosphere is node 213 and node 215, and in business recovery path, the node of related photosphere is node 213, node 214 and node 215.Therefore, the informational needs on node 213, node 214 and node 215 reconfigures.
507, photosphere controller 207 is according to path relevant with the node of photosphere in configuration information configuration service restoration path.
Particularly, the form that photosphere controller 207 is shown by stream is issued to node 213, node 214 and node 215 by this configuration information.That is, the down hop of photosphere controller 207 instructs node 213 is node 214, and the down hop of instructs node 214 is node 215.
Like this, just, completed the foundation in the business recovery path between PE equipment 208 and PE equipment 209.
Fig. 6 is the flow chart of method of the fault recovery of another embodiment of the present invention.Method shown in Fig. 5 comprises:
601, IP layer controller 206 obtains the topology information of IP layer and the topology information of interlayer link; Photosphere controller 207 obtains the topology information of photosphere.
602, photosphere controller 207 is sent to IP layer controller 206 by the topology information of photosphere.
603, IP layer controller 206 determined the first topology information.
Particularly, IP layer controller 206 determined the first topology information according to the topology information of the topology information of the topology information of IP layer, photosphere and interlayer link.The first topology information is the topology information of the whole network.
Suppose after step 603, the link generation fiber cut failure between node 203 and node 213, and node 212 produces malfunctioning fault simultaneously.
604, IP layer controller 206 obtains the first warning information, and photosphere controller 207 obtains the second warning information.
Particularly, the first warning information that IP layer controller 206 receiving nodes 203 send, the dropout of the port that this first warning information instructs node 203 is connected with node 201.
Photosphere controller 207 receives the second warning information being sent by node 211, node 213 and node 214.The dropout of the port that the warning information instructs node 211 that wherein, node 211 sends is connected with node 212.The dropout of the port that the warning information instructs node 214 that node 214 sends is connected with node 212.The dropout of the port that the warning information instructs node 213 that node 213 sends is connected with node 212, and the dropout of the port that is connected with node 203 of instructs node 213.
605, photosphere controller 207 is sent to IP layer controller 206 by the second warning information.
Particularly, photosphere controller 207, according to recovery policy, is sent to IP layer controller 206 by the second warning information.This recovery policy can be the OAM configuration information being stored in photosphere controller 207.
606, IP layer controller 206 determined fault message.
Particularly, IP layer controller 206 can, according to fault judgment mechanism, in conjunction with the first warning information and the second warning information, be determined fault message.This fault judgment mechanism can be pre-configured according to monitoring capability of 206 pairs of faults of this IP layer controller etc.The monitoring capability of fault is comprised and knows the consuming time etc. of fault.
Wherein, this fault message comprises the number of fault, the type of location of fault and fault.This fault message comprises the fiber cut failure between node 203 and node 213, and the malfunctioning fault of node 212.
607, IP layer controller 206 determined business and traffic failure path.
Particularly, IP layer controller 206 is according to fault message, determine that the business that this fault message affects is the business between PE equipment 208 and PE equipment 209, and the traffic failure path of this business is PE equipment 208 → node 203 → node 213 → node 215 → node 205 → PE equipment 209.
608, IP layer controller 206 determined business recovery path.
Particularly, IP layer controller 206 can be determined the second topology information according to the first topology information and fault message, and determines business recovery path according to the second topology information, and this business recovery path is for the business transmission between PE equipment 208 and PE equipment 209.
Wherein, the second topology information is the new topology information of removing in the first topology information after the information of the link that fault message interrupts.
Particularly, IP layer controller 206 can carry out cross-layer negotiation and decision-making according to this second topology information, and in conjunction with network resource status, determines that an optimum service reconstruction path is business recovery path.
For example, the determined business recovery of IP layer controller 206 path can be PE equipment 208 → node 201 → node 211 → node 213 → node 215 → node 205 → PE equipment 209.
The path relevant with the node of IP layer in 609, IP layer controller, 206 configuration service restoration paths.
Particularly, the form that IP layer controller 206 can stream table is issued to PE equipment 208 and node 201 by the first configuration information.This first configuration information is configuration information relevant with the node of IP layer in business recovery path.That is, the down hop of this first configuration information indication PE equipment 208 is node 201, and the down hop of instructs node 201 is node 211.And configuration information on node 205 is identical with the configuration information on node 205 in traffic failure path, now IP layer controller 206 is without re-starting configuration at node 205.
610, IP layer controller 206 is sent to photosphere controller 207 by configuration information relevant with the node of photosphere in business recovery path.
Particularly, business recovery path is compared with traffic failure path, and the node of related photosphere is different.In traffic failure path, the node of related photosphere is node 213 and node 215, and in business recovery path, the node of related photosphere is node 211, node 213 and node 215.Therefore, the informational needs on node 211, node 213 and node 215 reconfigures.
611, the path relevant with the node of photosphere in photosphere controller 207 configuration service restoration paths.
Particularly, the form that photosphere controller 207 is shown the second configuration information by stream is issued to node 211 and node 213.This second configuration information is configuration information relevant with the node of photosphere in business recovery path.And configuration information on node 215 is identical with the configuration information on node 215 in traffic failure path, now photosphere controller 207 is without re-starting configuration at node 215.That is, the down hop of photosphere controller 207 instructs node 211 is node 213, and the upper hop of node 213 is node 211.
Alternatively, after step 611, photosphere controller 207 can send feedback information to IP layer controller 206, and this feedback information is used to indicate photosphere controller 207 and sets up the process in path relevant with the node of photosphere in business recovery path and complete.Subsequently, IP layer controller 206 can discharge traffic failure path shared resource on node 203.
It should be noted that in the embodiment of the present invention, step 609 also can be carried out after step 610 again, or step 609 also can be carried out after step 611 again.The present invention is not construed as limiting this.
Like this, in the embodiment of the present invention, IP layer controller can obtain the topology of IP layer photoreactive layer, and the fault message that can obtain IP layer photoreactive layer, for the multipoint fault occurring, also can determine in time business recovery path.
Fig. 7 is the block diagram of the controller of one embodiment of the invention.Controller 700 shown in Fig. 7 comprises the first acquiring unit 701, second acquisition unit 702, the first determining unit 703 and the second determining unit 704.
The first acquiring unit 701 is for obtaining the first topology information, and this first topology information comprises the topology information of IP layer, the information of the topology information of photosphere and interlayer link, and this interlayer link is the link between the node of IP layer and the node of photosphere.Second acquisition unit 702 is for obtaining fault message, and this fault message at least comprises the fault message of photosphere.The fault message of the first determining unit 703 for obtaining according to second acquisition unit 702, determines the business relevant with this fault message and the traffic failure path of this business.The fault message that the second determining unit 704 is obtained for the first topology information of obtaining according to the first acquiring unit 701 and second acquisition unit 702, determine the business recovery path in the traffic failure path that the first determining unit 703 is definite, this business recovery path is for the transmission of this business.
The embodiment of the present invention is obtained the topology information of the whole network and the fault message of the whole network of IP-over-Optical network by the first controller, and further determines business recovery path.Can provide optimum business recovery path according to full mesh topology like this, and fault recovery is consuming time shorter.
Alternatively, as an embodiment, controller 700 also can comprise transmitting element, for the first configuration information is sent to another controller, this first configuration information configures the path relevant with the node of photosphere, this business recovery path for another controller on the node of photosphere, wherein, the first configuration information is the configuration information relevant with node photosphere in business recovery path.
Alternatively, as another embodiment, controller 700 is master controller, the relevant path of the node with IP layer in business recovery path, when the path relevant with the node from IP layer in traffic failure path is different, transmitting element, also can be used for: the second configuration information is sent to IP layer controller, this second configuration information is for IP layer controller configuration service restoration path on the node of IP layer path relevant with the node of IP layer, wherein, the second configuration information is the relevant configuration information of the node with IP layer in business recovery path.
Alternatively, as another embodiment, controller 700 is IP layer controller, the relevant path of the node with IP layer in business recovery path, when the path relevant with the node from IP layer in traffic failure path is different, transmitting element, also can be used for: the path relevant with the node of IP layer in configuration service restoration path on the node of IP layer.
Alternatively, as another embodiment, the topology information of photosphere is that controller 700 obtains from this another controller, and the information of interlayer link is that controller 700 obtains from this another controller.
Alternatively, as another embodiment, the second determining unit 704 can be specifically for: according to the first topology information and fault message, determine the second topology information, the new topology information of the photosphere comprising in this second topology information is different from the topology information of the photosphere comprising in the first topology information; According to this second topology information, determine the business recovery path in traffic failure path.
Alternatively, as another embodiment, fault message also comprises: the fault message of the fault message of IP layer and/or interlayer link.
Controller 700 can be realized each process being realized by the first controller in the embodiment of Fig. 3 to Fig. 6, does not avoid repetition, repeats no more here.
Fig. 8 is the block diagram of the controller of another embodiment of the present invention.Controller 800 shown in Fig. 8 comprises: the first acquiring unit 801 and the first transmitting element 802.
The first acquiring unit 801 is for obtaining the fault message of photosphere.The first transmitting element 802 is sent to the first controller for the fault message of photosphere that the first acquiring unit 801 is obtained, so that the first controller is determined the business relevant with fault message and the business recovery path of this business according to the fault message of this photosphere with topology information, topology information comprises the information of the topology information of photosphere, the topology information of IP layer and interlayer link, and interlayer link is the link between the node of IP layer and the node of photosphere.
The embodiment of the present invention is obtained the topology information of the whole network and the fault message of the whole network of IP-over-Optical network by the first controller, and further determines business recovery path.Can provide optimum business recovery path according to full mesh topology like this, and fault recovery is consuming time shorter.
Alternatively, as an embodiment, controller 800 also can comprise second acquisition unit and the second transmitting element.Second acquisition unit can be used for obtaining the topology information of photosphere.The topology information of the photosphere that the second transmitting element can be used for second acquisition unit to obtain is sent to the first controller.
Alternatively, as another embodiment, controller 800 also can comprise receiving element and dispensing unit.Wherein, the configuration information that receiving element sends for receiving the first controller, this configuration information is the configuration information relevant with node photosphere in business recovery path.Configuration information on the node of photosphere configuration service restoration path with the node of the photosphere relevant path of dispensing unit for receiving according to receiving element.
Alternatively, as another embodiment, the first acquiring unit 801 can be specifically for: according to recovery policy, determine the fault message of photosphere is sent to the first controller.
Controller 800 can be realized each process being realized by second controller in the embodiment of Fig. 3 to Fig. 6, does not avoid repetition, repeats no more here.
Fig. 9 is the block diagram of the controller of another embodiment of the present invention.Controller 900 shown in Fig. 9 comprises: processor 901, memory 902, receiving circuit 903 and transtation mission circuit 904.
Receiving circuit 903 is for obtaining the first topology information, and this first topology information comprises the topology information of IP layer, the information of the topology information of photosphere and interlayer link, and this interlayer link is the link between the node of IP layer and the node of photosphere.And obtaining fault message, this fault message at least comprises the fault message of photosphere.The fault message of processor 901 for obtaining according to receiving circuit 903, determines the business relevant with this fault message and the traffic failure path of this business.And the fault message that obtains of the first topology information of obtaining according to receiving circuit 903 and receiving circuit 903, determine the business recovery path in traffic failure path, this business recovery path is for the transmission of this business.
The embodiment of the present invention is obtained the topology information of the whole network and the fault message of the whole network of IP-over-Optical network by the first controller, and further determines business recovery path.Can provide optimum business recovery path according to full mesh topology like this, and fault recovery is consuming time shorter.
Each assembly in controller 900 is coupled by bus system 905, and wherein bus system 905, except comprising data/address bus, also comprises power bus, control bus and status signal bus in addition.But for the purpose of clearly demonstrating, in Fig. 9, various buses are all designated as to bus system 905.
The method that the invention described above embodiment discloses can be applied in processor 901, or is realized by processor 901.Processor 901 may be a kind of integrated circuit (IC) chip, has the disposal ability of signal.In implementation procedure, each step of said method can complete by the integrated logic circuit of the hardware in processor 901 or the instruction of form of software.Above-mentioned processor 901 can be general processor, digital signal processor (Digital Signal Processor, DSP), application-specific integrated circuit (ASIC) (Application Specific Integrated Circuit, ASIC), ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic device, discrete hardware components.Can realize or carry out disclosed each method, step and logic diagram in the embodiment of the present invention.General processor can be that microprocessor or this processor can be also the processors of any routine etc.Step in conjunction with the disclosed method of the embodiment of the present invention can directly be presented as that hardware decoding processor is complete, or complete with the hardware in decoding processor and software module combination.Software module can be positioned at random access memory (Random Access Memory, RAM), in the storage medium of this area maturation such as flash memory, read-only memory (Read-Only Memory, ROM), programmable read only memory or electrically erasable programmable memory, register.This storage medium is positioned at memory 902, and the information in processor 901 read memories 902 completes the step of said method in conjunction with its hardware.
Alternatively, as an embodiment, transtation mission circuit 904 can be used for the first configuration information to be sent to another controller, this first configuration information configures the path relevant with the node of photosphere, this business recovery path for another controller on the node of photosphere, wherein, the first configuration information is the configuration information relevant with node photosphere in business recovery path.
Alternatively, as another embodiment, controller 900 is master controller, the relevant path of the node with IP layer in business recovery path, when the path relevant with the node from IP layer in traffic failure path is different, transtation mission circuit 904 also can be used for: the second configuration information is sent to IP layer controller, this second configuration information is for IP layer controller configuration service restoration path on the node of IP layer path relevant with the node of IP layer, wherein, the second configuration information is the relevant configuration information of the node with IP layer in business recovery path.
Alternatively, as another embodiment, controller 900 is IP layer controller, the relevant path of the node with IP layer in business recovery path, when the path relevant with the node from IP layer in traffic failure path is different, transtation mission circuit 904 also can be used for: the path relevant with the node of IP layer in configuration service restoration path on the node of IP layer.
Alternatively, as another embodiment, the topology information of photosphere is that controller 900 obtains from this another controller, and the information of interlayer link is that controller 900 obtains from this another controller.
Alternatively, as another embodiment, processor 901 can be specifically for: according to the first topology information and fault message, determine the second topology information, the new topology information of the photosphere comprising in this second topology information is different from the topology information of the photosphere comprising in the first topology information; According to this second topology information, determine the business recovery path in traffic failure path.
Alternatively, as another embodiment, fault message also comprises: the fault message of the fault message of IP layer and/or interlayer link.
Controller 900 can be realized each process being realized by the first controller in the embodiment of Fig. 3 to Fig. 6, does not avoid repetition, repeats no more here.
Figure 10 is the block diagram of the controller of another embodiment of the present invention.Controller 1000 shown in Figure 10 comprises: processor 1001, memory 1002, receiving circuit 1003 and transtation mission circuit 1004.
Receiving circuit 1003 is for obtaining the fault message of photosphere.Transtation mission circuit 1004 is sent to the first controller for the fault message of photosphere that receiving circuit 1003 is obtained, so that the first controller is determined the business relevant with fault message and the business recovery path of this business according to the fault message of this photosphere with topology information, topology information comprises the information of the topology information of photosphere, the topology information of IP layer and interlayer link, and interlayer link is the link between the node of IP layer and the node of photosphere.
The embodiment of the present invention is obtained the topology information of the whole network and the fault message of the whole network of IP-over-Optical network by the first controller, and further determines business recovery path.Can provide optimum business recovery path according to full mesh topology like this, and fault recovery is consuming time shorter.
Each assembly in controller 1000 is coupled by bus system 1005, and wherein bus system 1005, except comprising data/address bus, also comprises power bus, control bus and status signal bus in addition.But for the purpose of clearly demonstrating, in Figure 10, various buses are all designated as to bus system 1005.
The method that the invention described above embodiment discloses can be applied in processor 1001, or is realized by processor 1001.Processor 1001 may be a kind of integrated circuit (IC) chip, has the disposal ability of signal.In implementation procedure, each step of said method can complete by the integrated logic circuit of the hardware in processor 1001 or the instruction of form of software.Above-mentioned processor 1001 can be general processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic device, discrete hardware components.Can realize or carry out disclosed each method, step and logic diagram in the embodiment of the present invention.General processor can be that microprocessor or this processor can be also the processors of any routine etc.Step in conjunction with the disclosed method of the embodiment of the present invention can directly be presented as that hardware decoding processor is complete, or complete with the hardware in decoding processor and software module combination.Software module can be arranged in the storage medium of this area maturations such as RAM, flash memory, ROM, programmable read only memory or electrically erasable programmable memory, register.This storage medium is positioned at memory 1002, and the information in processor 1001 read memories 1002 completes the step of said method in conjunction with its hardware.
Alternatively, as an embodiment, receiving circuit 1003 also can be used for obtaining the topology information of photosphere.The topology information that transtation mission circuit 1004 also can be used for photosphere that receiving circuit 1003 is obtained is sent to the first controller.
Alternatively, as another embodiment, receiving circuit 1003 also can be used for receiving the configuration information that the first controller sends, and this configuration information is the configuration information relevant with node photosphere in business recovery path.Configuration information on the node of photosphere configuration service restoration path with the node of the photosphere relevant path of processor 1001 for receiving according to receiving element.
Alternatively, as another embodiment, receiving circuit 1003 can be specifically for: according to recovery policy, determine the fault message of photosphere is sent to the first controller.
Controller 1000 can be realized each process being realized by second controller in the embodiment of Fig. 3 to Fig. 6, does not avoid repetition, repeats no more here.
Those of ordinary skills can recognize, unit and the algorithm steps of each example of describing in conjunction with embodiment disclosed herein, can realize with the combination of electronic hardware or computer software and electronic hardware.These functions are carried out with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.Professional and technical personnel can specifically should be used for realizing described function with distinct methods to each, but this realization should not thought and exceeds scope of the present invention.
Those skilled in the art can be well understood to, and for convenience and simplicity of description, the specific works process of the system of foregoing description, device and unit, can, with reference to the corresponding process in preceding method embodiment, not repeat them here.
In the several embodiment that provide in the application, should be understood that disclosed system, apparatus and method can realize by another way.For example, device embodiment described above is only schematic, for example, the division of described unit, be only that a kind of logic function is divided, during actual realization, can have other dividing mode, for example a plurality of unit or assembly can in conjunction with or can be integrated into another system, or some features can ignore, or do not carry out.Another point, shown or discussed coupling each other or direct-coupling or communication connection can be by some interfaces, indirect coupling or the communication connection of device or unit can be electrically, machinery or other form.
The described unit as separating component explanation can or can not be also physically to separate, and the parts that show as unit can be or can not be also physical locations, can be positioned at a place, or also can be distributed in a plurality of network element.Can select according to the actual needs some or all of unit wherein to realize the object of the present embodiment scheme.
In addition, each functional unit in each embodiment of the present invention can be integrated in a processing unit, can be also that the independent physics of unit exists, and also can be integrated in a unit two or more unit.
If described function usings that the form of SFU software functional unit realizes and during as production marketing independently or use, can be stored in a computer read/write memory medium.Understanding based on such, the part that technical scheme of the present invention contributes to prior art in essence in other words or the part of this technical scheme can embody with the form of software product, this computer software product is stored in a storage medium, comprise that some instructions are with so that a computer equipment (can be personal computer, server, or the network equipment etc.) carry out all or part of step of method described in each embodiment of the present invention.And aforesaid storage medium comprises: various media that can be program code stored such as USB flash disk, portable hard drive, ROM, RAM, magnetic disc or CDs.
The above; be only the specific embodiment of the present invention, but protection scope of the present invention is not limited to this, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; can expect easily changing or replacing, within all should being encompassed in 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 (22)

1. a method for fault recovery, is characterized in that, described method comprises:
The first controller obtains the first topology information, and described the first topology information comprises the topology information of procotol IP layer, the information of the topology information of photosphere and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere;
Described the first controller obtains fault message, and described fault message at least comprises the fault message of described photosphere;
Described the first controller, according to described fault message, is determined the business relevant with described fault message and the traffic failure path of described business;
Described the first controller, according to described the first topology information and described fault message, is determined the business recovery path in described traffic failure path, and described business recovery path is for the transmission of described business.
2. method according to claim 1, is characterized in that, after the business recovery path in described definite described traffic failure path, described method also comprises:
Described the first controller is sent to second controller by the first configuration information, and described the first configuration information configures the path relevant with the node of described photosphere, described business recovery path for described second controller on the node of described photosphere,
Wherein, described the first configuration information is the relevant configuration information of the node with described photosphere in described business recovery path.
3. method according to claim 2, it is characterized in that, described the first controller is master controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described method also comprises:
Described the first controller is sent to IP layer controller by the second configuration information, and described the second configuration information configures the path relevant with the node of described IP layer, described business recovery path for described IP layer controller on the node of described IP layer,
Wherein, described the second configuration information is the relevant configuration information of the node with described IP layer in described business recovery path.
4. method according to claim 2, it is characterized in that, described the first controller is IP layer controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described method also comprises:
Described the first controller configures path relevant with the node of described IP layer in described business recovery path on the node of described IP layer.
5. according to the method described in claim 1 to 4 any one, it is characterized in that, the topology information of described photosphere is obtained from described second controller by described the first controller, and the information of described interlayer link is obtained from described second controller by described the first controller.
6. according to the method described in claim 1 to 5 any one, it is characterized in that, described the first controller, according to described the first topology information and described fault message, is determined the business recovery path in described traffic failure path, comprising:
Described the first controller is according to described the first topology information and described fault message, determine the second topology information, the new topology information of the described photosphere comprising in described the second topology information is different from the topology information of the described photosphere comprising in described the first topology information;
Described the first controller, according to described the second topology information, is determined the described business recovery path in described traffic failure path.
7. according to the method described in claim 1 to 6 any one, it is characterized in that, described fault message also comprises: the fault message of the fault message of described IP layer and/or described interlayer link.
8. a method for fault recovery, is characterized in that, described method comprises:
Second controller obtains the fault message of photosphere;
Described second controller is sent to the first controller by the fault message of described photosphere, so that described the first controller is determined the business relevant with described fault message and the business recovery path of described business according to the fault message of described photosphere with topology information, described topology information comprises the information of the topology information of described photosphere, the topology information of procotol IP layer and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere.
9. method according to claim 8, is characterized in that, described method also comprises:
Described second controller obtains the topology information of photosphere;
Described second controller is sent to described the first controller by the topology information of described photosphere.
10. method according to claim 8 or claim 9, is characterized in that, described method also comprises:
Described second controller receives the configuration information that described the first controller sends, and described configuration information is the relevant configuration information of the node with described photosphere in described business recovery path;
Described second controller configures path relevant with the node of described photosphere in described business recovery path on the node of described photosphere according to described configuration information.
Method described in 11. according to Claim 8 to 10 any one, is characterized in that, described second controller is sent to the first controller by the fault message of described photosphere, comprising:
Described second controller, according to recovery policy, is determined the fault message of described photosphere is sent to described the first controller.
12. 1 kinds of controllers, is characterized in that, described controller comprises:
The first acquiring unit, be used for obtaining the first topology information, described the first topology information comprises the topology information of procotol IP layer, the information of the topology information of photosphere and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere;
Second acquisition unit, for obtaining fault message, described fault message at least comprises the fault message of described photosphere;
The first determining unit, for the described fault message obtaining according to described second acquisition unit, determines the business relevant with described fault message and the traffic failure path of described business;
The second determining unit, the described fault message obtaining for described the first topology information of obtaining according to described the first acquiring unit and described second acquisition unit, determine the business recovery path in the described traffic failure path that described the first determining unit is determined, described business recovery path is for the transmission of described business.
13. controllers according to claim 12, is characterized in that, described controller also comprises:
Transmitting element, for: the first configuration information is sent to another controller, and described the first configuration information configures the path relevant with the node of described photosphere, described business recovery path for described another controller on the node of described photosphere,
Wherein, described the first configuration information is the relevant configuration information of the node with described photosphere in described business recovery path.
14. controllers according to claim 13, it is characterized in that, described controller is master controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described transmitting element, also for:
The second configuration information is sent to IP layer controller, and described the second configuration information configures the path relevant with the node of described IP layer, described business recovery path for described IP layer controller on the node of described IP layer,
Wherein, described the second configuration information is the relevant configuration information of the node with described IP layer in described business recovery path.
15. controllers according to claim 13, it is characterized in that, described controller is IP layer controller, the relevant path of the node with described IP layer in described business recovery path, when the path relevant with the node from described IP layer in described traffic failure path is different, described transmitting element, also for:
On the node of described IP layer, configure path relevant with the node of described IP layer in described business recovery path.
16. according to claim 12 to the controller described in 15 any one, it is characterized in that, the topology information of described photosphere is that described controller obtains from described another controller, and the information of described interlayer link is that described controller obtains from described another controller.
17. according to claim 12 to the controller described in 16 any one, it is characterized in that, and described the second determining unit, specifically for:
According to described the first topology information and described fault message, determine the second topology information, the new topology information of the described photosphere comprising in described the second topology information is different from the topology information of the described photosphere comprising in described the first topology information;
According to described the second topology information, determine the described business recovery path in described traffic failure path.
18. according to claim 12 to the controller described in 17 any one, it is characterized in that, described fault message also comprises: the fault message of the fault message of described IP layer and/or described interlayer link.
19. 1 kinds of controllers, is characterized in that, described controller comprises:
The first acquiring unit, for obtaining the fault message of photosphere;
The first transmitting element, fault message for described photosphere that described the first acquiring unit is obtained is sent to the first controller, so that described the first controller is determined the business relevant with described fault message and the business recovery path of described business according to the fault message of described photosphere with topology information, described topology information comprises the information of the topology information of described photosphere, the topology information of procotol IP layer and interlayer link, and described interlayer link is the link between the node of described IP layer and the node of described photosphere.
20. controllers according to claim 19, is characterized in that, described controller also comprises:
Second acquisition unit, also for obtaining the topology information of photosphere;
The second transmitting element, also the topology information for described photosphere that described second acquisition unit is obtained is sent to described the first controller.
21. according to the controller described in claim 19 or 20, it is characterized in that, described controller also comprises:
Receiving element, the configuration information sending for receiving described the first controller, described configuration information is the relevant configuration information of the node with described photosphere in described business recovery path;
Dispensing unit configures the path relevant with the node of described photosphere, described business recovery path for the described configuration information receiving according to described receiving element on the node of described photosphere.
22. according to claim 19 to the controller described in 21, it is characterized in that, described the first acquiring unit, specifically for: according to recovery policy, determine the fault message of described photosphere is sent to described the first controller.
CN201310744223.4A 2013-12-30 2013-12-30 Failure recovery method and controller Pending CN103746841A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201310744223.4A CN103746841A (en) 2013-12-30 2013-12-30 Failure recovery method and controller
PCT/CN2014/093842 WO2015101168A1 (en) 2013-12-30 2014-12-15 Failure recovery method and controller

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201310744223.4A CN103746841A (en) 2013-12-30 2013-12-30 Failure recovery method and controller

Publications (1)

Publication Number Publication Date
CN103746841A true CN103746841A (en) 2014-04-23

Family

ID=50503832

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201310744223.4A Pending CN103746841A (en) 2013-12-30 2013-12-30 Failure recovery method and controller

Country Status (2)

Country Link
CN (1) CN103746841A (en)
WO (1) WO2015101168A1 (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104539445A (en) * 2014-12-01 2015-04-22 北京百度网讯科技有限公司 Method and device for managing service resources
WO2015101168A1 (en) * 2013-12-30 2015-07-09 华为技术有限公司 Failure recovery method and controller
CN106850424A (en) * 2015-12-07 2017-06-13 中国联合网络通信集团有限公司 A kind of system of selection, the apparatus and system in IP layers of path
CN107302849A (en) * 2016-02-16 2017-10-27 华为技术有限公司 The distribution method and device of a kind of light path
CN107872384A (en) * 2016-09-28 2018-04-03 中兴通讯股份有限公司 The method of adjustment and device of a kind of network bandwidth
CN109716716A (en) * 2016-12-02 2019-05-03 华为技术有限公司 Joint route method for building up and device
CN111200506A (en) * 2018-11-19 2020-05-26 中兴通讯股份有限公司 Fault sensing method and device and controller
CN111984474A (en) * 2020-09-27 2020-11-24 苏州浪潮智能科技有限公司 Method, system and equipment for recovering double-control cluster fault
CN111988682A (en) * 2019-05-22 2020-11-24 华为技术有限公司 Network control method, device and system
WO2020248634A1 (en) * 2019-06-13 2020-12-17 华为技术有限公司 Fault protection method, device and system for optical network
WO2021103800A1 (en) * 2019-11-27 2021-06-03 华为技术有限公司 Method and apparatus for recommending fault repairing operation, and storage medium

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111885630B (en) * 2020-07-01 2023-06-30 中国联合网络通信集团有限公司 Data transmission method and communication device
CN113727221B (en) * 2021-08-13 2023-06-23 烽火通信科技股份有限公司 Intelligent control method, device and system for optical network
CN115623364A (en) * 2022-09-08 2023-01-17 烽火通信科技股份有限公司 Method and system for IP and optical network protection switching cooperative management and control

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102136940B (en) * 2010-12-31 2013-10-09 华为技术有限公司 Network recovery method and device
CN102186124B (en) * 2011-04-29 2014-01-15 东北大学 Utility-based interlayer coordination method in WDM (Wavelength Division Multiplexing) optical network
CN103746841A (en) * 2013-12-30 2014-04-23 华为技术有限公司 Failure recovery method and controller

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015101168A1 (en) * 2013-12-30 2015-07-09 华为技术有限公司 Failure recovery method and controller
CN104539445B (en) * 2014-12-01 2018-02-23 北京百度网讯科技有限公司 A kind of method and apparatus for management business resource
CN104539445A (en) * 2014-12-01 2015-04-22 北京百度网讯科技有限公司 Method and device for managing service resources
CN106850424A (en) * 2015-12-07 2017-06-13 中国联合网络通信集团有限公司 A kind of system of selection, the apparatus and system in IP layers of path
CN107302849B (en) * 2016-02-16 2020-08-07 华为技术有限公司 Light path distribution method and device
CN107302849A (en) * 2016-02-16 2017-10-27 华为技术有限公司 The distribution method and device of a kind of light path
CN107872384A (en) * 2016-09-28 2018-04-03 中兴通讯股份有限公司 The method of adjustment and device of a kind of network bandwidth
CN109716716A (en) * 2016-12-02 2019-05-03 华为技术有限公司 Joint route method for building up and device
CN109716716B (en) * 2016-12-02 2021-03-02 华为技术有限公司 Method and device for establishing joint route
CN111200506A (en) * 2018-11-19 2020-05-26 中兴通讯股份有限公司 Fault sensing method and device and controller
CN111200506B (en) * 2018-11-19 2023-08-29 中兴通讯股份有限公司 Fault sensing method and device and controller
CN111988682B (en) * 2019-05-22 2022-11-04 华为技术有限公司 Network control method, device and system
CN111988682A (en) * 2019-05-22 2020-11-24 华为技术有限公司 Network control method, device and system
WO2020248634A1 (en) * 2019-06-13 2020-12-17 华为技术有限公司 Fault protection method, device and system for optical network
WO2021103800A1 (en) * 2019-11-27 2021-06-03 华为技术有限公司 Method and apparatus for recommending fault repairing operation, and storage medium
US11743113B2 (en) 2019-11-27 2023-08-29 Huawei Technologies Co., Ltd. Fault rectification operation recommendation method and apparatus, and storage medium
CN111984474B (en) * 2020-09-27 2022-08-19 苏州浪潮智能科技有限公司 Method, system and equipment for recovering double-control cluster fault
CN111984474A (en) * 2020-09-27 2020-11-24 苏州浪潮智能科技有限公司 Method, system and equipment for recovering double-control cluster fault

Also Published As

Publication number Publication date
WO2015101168A1 (en) 2015-07-09

Similar Documents

Publication Publication Date Title
CN103746841A (en) Failure recovery method and controller
US8886831B2 (en) System and methodology for fast link failover based on remote upstream failures
US9203732B2 (en) Recovery of traffic in a connection-oriented network
CN101317388B (en) Apparatus and method for multi-protocol label switching label-switched path protection switching
CN101965691B (en) Cable redundancy and networked system
CN103560955A (en) Method and device for switching between redundancy devices
JP2005521334A (en) Network management system
EP2608459A2 (en) Router, virtual cluster router system and establishion method thereof
CN102137009B (en) Method, system and equipment for processing Dual-layer service in network
CN102638735B (en) Optical node device and business switching method thereof
CN102474446A (en) Recovery mechanism for point-to-multipoint traffic
CN105721546A (en) Multi-data integration service platform based on industrial Internet of Things (IoT) communication
CN103534982A (en) Method, equipment and network virtualization system for protecting business reliability
US20160204976A1 (en) Identifying the absence and presence of a ring protection link owner node in an ethernet network
CN105634848B (en) A kind of virtual router monitoring method and device
CN106233679A (en) A kind of Network method for building up, Cooperation controlling center and network system
CN109981353B (en) Method and system for protecting adjacent station redundancy in frame type network communication equipment
CN103001802B (en) Ether port failure self-repairing method and system
KR20180122513A (en) Method and framework for traffic engineering in network hypervisor of sdn-based network virtualization platform
CN105515869A (en) Out-of-band management method and device for virtual switching unit
CN104125079A (en) Method and device for determining double-device hot-backup configuration information
CN102792636B (en) There is provided and recover the method for survivability, equipment and communication network
CN103036724A (en) State information transmission method and network equipment and combination equipment
CN102611577A (en) LDP (Label Distribution Protocol) conversation-based method, device and system for protecting PWs (Pseudo Wires)
JP5388189B2 (en) Network equipment

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20140423